COMP 310
Fall 2014
Course Information
COMP 310
|
Course Information |
|
|
Class will be held every Monday, Wednesday and Friday from 1:00 PM - 1:50 PM in Duncan Hall Room 1064.
Labs will be held in the OEDK Computer Lab at
Dr. Stephen Wong -- See home page for contact and office hour information.
Teaching Assistants e-mail (at rice.edu) Office Hours (all are 2 hr blocks) & Location (Subject to change, so check often!) Kyle Adams kyle.w.adams Sun. 8:00 PM Weiss Commons Xin Chen xin.chen Wed. 1:00 PM and Tues. 3:30 PM Duncan Hall 2nd floor atrium lounge (east side usually) Max Payton max.s.payton Mon. 7:00 PM in Weiss Commons Kyle Kurihara khk1 Thurs. 3:00 PM in Sid Richardson Commons Yijie Li yl68 Mon. 7:00 PM DH3092 Terry Tang terry.tang Mon 3:00 DH 3113 Martha Witick mw36 Tues. 4:00 PM DH 3052 All Comp310 staff are also available by appointment!
Entire class (including staff, replace the " at " with "@"): comp310f14 at owlspace-ccm.rice.edu
IMPORTANT: In order to send a message to the above address, the e-mail address in your Owlspace address MUST MATCH YOUR RETURN ADDRESS EXACTLY. Generally, this means that you must send from that same account but even that can fail if you use a different alias as the return address.
Just the staff: comp310 at rice.edu (replace the " at " with "@")
Please do not send e-mail directly to the instructor or any specific staff member, as doing so will only delay the response.
Please DO start your subject line with "Comp310: " so that your message can be easily identified as being class-related!
Though none of the existing text books truly meet our needs and requirements, we like the following book and highly recommend it for the course.
- Head First Design Patterns, First Edition, by Eric Freeman and Elizabeth Freeman, O'Reilly, 2004. ISBN 0-596-00712-4.
We also have a few other recommendations.
- The Java Programming Language, 4th edition, by Arnold, Gosling, and Holmes, Addison-Wesley,
James Gosling is the creator of Java. This is the definitive Java reference. However, this book does not cover all the topics of the course and will be used only as a reference for Java syntax and semantics.
- Design Patterns, Elements Of Reusable Object-Oriented Software, by Gamma, Helm, Johnson, and Vlissides, Addison-Wesley, 1995. ISBN 0201633612
This is the bible of the pattern community. It predates Java. The authors are affectionately referred to as the Gang of Four (GoF). All examples are written in C++ and/or Smalltalk. It can be hard to read if you are not familiar with these two languages, though the ideas are language independent. The "pattern language" used in this book also requires a lot of getting used to. We have learned so much from this book, and we are still reading it and learning from it. There is a version on CD-ROM which is cheaper (and perhaps, more versatile). We strongly recommend it, especially to any student considering further work in object-oriented programming.
- Thinking in Java, 4'th ed., by Bruce Eckel, Prentice Hall PTR.
Good OO treatment, with a little more detail on syntax than Gosling's book. Students often find it useful for "nuts-and-bolts" information on programming. The full text of earlier editions are available as a free download from www.bruceeckel.com. Also at the web site is his on-line only book: Thinking in Patterns with Java, which is recommended reading.
COMP 215 or equivalent: students should already be familiar with the full Java syntax and have experience writing procedural programs and algorithms in Java including the basic usage of classes, objects and inheritance as well as simple generics.
Object-oriented programming is the major software paradigm used in large systems today. This includes most desktop applications such a office productivity software, data management applications and even the main frameworks of many games. But object-oriented programming and design (OOP/D) absolutely rules in the enterprise-class arena, the globe-spanning, mission-critical systems that, via the Internet, tie together international corporations from one end of the Earth to the other. In Comp310, we will discover how to use state-of-the-art object-oriented programming and design techniques to create flexible and scalable software systems that can interact with eachother from anywhere in the world. We will learn about software design patterns and how they are used in multiple programming paradigms. Through a combination of theory and coding, the class will explore how highly decoupled systems with dynamically configurable behaviors are designed and implemented. The class will learn how to use design patterns as both a means of expressing fundamental computer science concepts as well as the building blocks in an abstract decomposition of a complex problem. In addition, the class will learn to use industry standard tools and technologies such as the Eclipse integrated development environment, Subversion source control and round-trip engineering design tools.
The course format will be that of lectures covering the theoretical, engineering and technological aspects of object-oriented programming and design that will be implemented in the project-like homework assignments. These homework projects will build upon each other as much as possible, culminating in a networked application.
Theory
Highly decoupled systems:
Design patterns:
Technologies
Please follow the navigation link to the Home page above to see the topical schedule for lectures and labs.
The turn-in mechanism will be the student's individual Comp310 Subversion repository on CLE@R, using the Subclipse version control plug-in in Eclipse. Please see
The course grade will be based on: TENTATIVE
- Homework Assignments (70% total)
- Design Activities (10% total)
- Final Project (20% = 5% Milestone 1 + 15% Milestone 2)
Assignments’ due dates and rules will be clearly stated at the time they are given.
No make-up work will be given unless there is a legitimate excuse such as proof of medical emergency. All permissions must be requested and approved in writing (hard copy or e-mail) BEFORE the due date!
We reserve the right to modify the above weightings at any time.
- No assignments will accepted late without express written permission from an instructor BEFORE the due date of the assignment. Excused lateness will not be penalized unless otherwise decided by the instructor (student will be notified at time of request).
- Extension requests will be considered ONLY for the following reasons and are NOT automatically accepted:
- Illness or unexpected travel occurring during or extending into the second half of the time period between the previous assignment due date and the current assignment due date.
- Pre-planned travel that covers more than half of the time period between the previous assignment due date and the current assignment due date.
- Unexpected technical problems that prevent the submission of the assignment such as a network or SVN outage.
- Note that broken computers or faulty software installations are not acceptable justifications because all work can be completed and submitted from the OEDK lab computers.
- The following will NOT be considered as valid reasons for extensions:
- Excessive work in other classes.
- Any extension request made less than 48 hours before a deadline unless for an emergency or unplanned event as detailed above.
- Travel to conferences or interviews where one is gone for less than half of the assignment time period. This includes the preparation for such trips.
- Starting late and/or discovering that the assignment is more difficult than anticipated.
- Not being able to meet with an assignment partner, if one is required by the assignment.
- Any extension request must be accompanied by proof of having already made a concerted effort to complete the assignment, including SVN commits and meetings with the staff. Extensions will not be granted if no work has been done already on the assignment.
- If a late, unexcused submission is accepted at all, which is solely at the instructor's discretion and which is NOT the default policy:
- The assignment will be penalized at least 5% of the total possible score per day on top of any normal markdowns, rounded up to the nearest day.
- If more one week after the due date, the assignment will not be accepted and will be given an automatic "0" score.
Principles of Object Oriented Programming courses:
Rice University has a student-run academic honor system. Each student has personal responsibility for honesty in their own academic conduct. Each student has the responsibility to report any suspected problems to the Honor Council in a timely fashion. During any Rice exam, the student is expected to write the honor pledge on the outside of the exam:
On my honor, I have neither given nor received aid on this examination.
The Computer Science Department takes the Rice Honor System very seriously and handles all violations accordingly. General rules of conduct concerning collaboration will be spelled out before assignments or exams are distributed (see for instance, above). When in doubt, contact an instructor before proceeding.
For this class, the following additional restrictions MUST be observed:
You may not look at solutions to assignments from past semesters or from other students. Furthermore, attempting to take credit for someone else’s work by turning it in as your own constitutes plagiarism, as defined by the Rice Honor Code.
You may not make your work in the class available to others in any form during or after the class. In particular, you may not place your code anywhere on the Internet that is viewable by others.
For example, posting one's code to a publicly viewable GitHub or other sort of repository or web page would be in violation of the above restrictions.
For more information concerning the Rice Honor System, see:
Any student with a documented disability needing academic adjustments or accommodations is requested to speak with us during the first two weeks of class. All discussions will remain confidential. Students with disabilities should also contact Disability Support Services in the Ley Student Center.
Previous Offerings of Comp310:
Staff SharePoint Site (login req'd)
Staff Notes (login req'd)
© 2014 by Stephen Wong