CompSci 100e: Program Design & Analysis II(Fall 2009)
| Home |
| Course Information |
| Calendar |
| Resources |
| Assignments |
| APT problems |
| Lab |
| Help sessions |
| Discussion Forum |
| Blackboard |
| Oasis |
Index
- Course Description
- Time and Place
- Staff
- Texts and Software
- Topics
- Web, Discussion, and Blackboard
- Grading
- Course Policies
Course Description
Same as Computer Science 100, for students who have taken Engineering 53. Object-oriented design and programming using Java and C++ emphasizing abstract data types and their lower-level implementations. Advanced data structures including balanced trees, hash tables, graphs. Intuitive and rigorous analysis of algorithms.
Prerequisite: Engineering 53 or equivalent experience
Time and Place
4:25pm-5:40pm on Mondays and Wednesdays; Perkins 2-071l
Labs 4:25-5:40 Fridays in Perkins 2-071.
Staff
Professor
 |
Office: D235 LSRC Office Phone: (919) 660-6550 Office hours: Fridays 1:00-2:30, any time my door is open (which is most of the time), or by appointment |
Teaching Assistants
 |
Undergraduate Teaching Assistants
|
TBA |
Contact the staff at cps100 AT cs.duke.edu.
Texts and Software
Introduction to Programming in Java: An Interdisciplinary Approach, Required, by Robert Sedgwick and Kevin Wayne
Textbooks are available in the Duke textbook store. If you want to buy books online, please click on the book images above to buy from Amazon and contribute to undergraduate computer science research at Duke. We will use the Sedgewick & Wayne book quite a bit in the beginning of the semester and assign from exercises from there. You may need that book to complete some of the assignments, so that book is required.
Software for the course will be provided via this website or in lab.
Topics covered
See calendar for tentative list of topics.Web, Discussion Forum, and Blackboard
Most of the course materials, including the syllabus, lecture notes, reading assignments, homework, programming FAQs, etc., will be available through the course Web page (http://www.cs.duke.edu/courses/fall09/cps100e/).
The discussion forum is useful for posting questions that are likely to be of interest to the rest of the class. We very much encourage students in the class to post responses to questions. We will monitor the the newsgroup regularly, and post responses to questions that have not previously been asked or answered. Before posting a question, please do make sure that you have read all previous messages and that your question has not yet been discussed.
We will use the Blackboard course management system for posting official grades and some course materials, and for turning in some assignments. (https://courses.duke.edu/bin/common/course.pl?course_id=_87947_1)
Programming project feedback will be posted on Oasis.
Finally, please check your email regularly, as important course announcements will be sent via email.
Grading
Grading is done on an absolute, but adjustable scale. This means that there is no curve. Anyone earning 90% or more of the total number of points available will receive a grade in the A range; 80% or more guarantees a grade in the B range, 70% or more guarantees a grade in the C range, 60% or more guarantees a grade in the D range. This scale may slide down, but it will not go up.
There will be several types of assignments during the term, each contributing to your final grade by approximately the following percentages:
To receive a grade of A or A+ you must exceed expectations. This means you must do everything required extraordinarily well or you must do more than is required and do this well. In other words, to earn an A you must do more than merely meet the requirements, you must go beyond them.
In order to earn an A+ you must do some of the optional assignments and exceed expectations in general.
| major programming assignments | 30% |
| APT programs | 10% |
| Labs/quizzes/classwork/community | 16% |
| tests (2) | 24% |
| final exam | 20% |
Course Policies
Individual extensions will be granted only for medical reasons (see the Short-term Illness Notification policy) or other circumstances beyond your control that must be presented with an official Dean's excuse. We do not grant extensions after an assignment is due, you must request an extension before an assignment is due.If you have personal reasons to ask for an extension, and you do so at least a week in advance, it's possible to get one, so please ask.
Late Programming Projects
Assignments turned in on time receive no penalty. Assignments turned in up to two days late incur a 10% penalty. Assignments turned in more than two days late incur a 25% penalty. Assignments will not be accepted after one week has passed from the due date.In general, the weekend counts as one day.
If you're having trouble, be sure to see a UTA/TA and preferably the professor in charge of the course as far before the due date as possible. Don't give up, ask for help.
Other Assignments
You cannot make up an in-class or recitation assignment. We will provide opportunities to earn "extra" points on in-class work so that if you miss a small number of these your grade won't be affected. However, frequent absences from class will affect the portion of your grade based on quizzes and in-class work.
Points on assignments will vary. Harder assignments will be worth more than previous assignments, and most assignments will get harder as the semester progresses (harder means takes more time, requires more thought).
Collaboration Policy
Quizzes and Exams taken online or in-class must be your own work, you should not collaborate on them.
On programming assignments, you may consult with professors, and TAs/UTAs about any aspect of the assignment. You may consult with other students only in a general way, e.g., about debugging or Java issues, or questions about wording on the assignment. You cannot actively work with someone unless the assignment specifically grants permission to work together with another student.
Consult means you can discuss the programs before writing code, and get help with debugging your program, but you should write your own code. Writing one program and making multiple copies of it is NOT acceptable! For each assignment you are expected to include a list of the people with whom you have consulted (including students, TAs, tutors, professors) as part of your submission. This information is required with each assignment. It is part of your README file, and failure to provide it will result in rejection of the assignment as complete. You may be able to resubmit.
See the departmental Collaboration Policy for more information.
Exams
Tests will be held during the lecture time and in the same room. The final will also be in the same room.You can bring a limited number of sheets of notes to the midterm exams. The final exam will be open book/open-note.