|Instructor||Textbooks||Course Work||Discussion Questions||Schedule ( .dvi format / postscript / pdf format )|
Computer Science 223 provides a framework for the study of the development of large software systems. Components of the course include:
In additional to discussing basic principles, techniques, and heuristics for large system development, students in the course also develop a large scale project. In this section, students will work collectively to develop the specification and design of a specific system, including a description of the components and class interfaces. Students then will work in groups of (about) 2 to implement the various components. Programming will be in the Java programming language.
Henry M. Walker
Office: Science 2420
Telephone: extension 4208
Office hours are posted weekly on the bulletin board outside my office.
Additional hours can be scheduled by appointment.
If you wish, you may reserve a half hour meeting by signing up on the weekly schedule.
This courses uses two textbooks:
Arthur J. Riel, Object-Oriented Design Heuristics, Addison-Wesley, 1996.
Sinan Si Alhir, UML in a Nutshell: A Desktop Quick Reference, O'Reilly, 1998.
Since students will be implementing components and interfaces in Java, students may wish to consult one of the many Java language books on the market.
While the schedule for this course is expected to evolve, a Tentative Class Schedule is available in .dvi , postscript and pdf formats.
Also, if you are logged into the departmental network and want a copy printed, click duerer to have a copy printed on the printer duerer, and click pacioli to have a copy printed on the printer pacioli .
Course Work will involve a combination of the following activities.
Deadlines for specific assignments will be posted on-line at http://www.cs.grinnell.edu/~walker/courses/223.sp02/assignments In each case, work is due at the start of each class specified. A penalty of 25% per class meeting will be assessed for any assignment turned in late, even work submitted at the end of a class. However, an extension of at least one class period is automatically granted if department's computer network is down for an unscheduled period for a period of three or more hours during the week preceding the assignment. Normally, a program or laboratory write-up is due every third class meeting.
Absolute Deadline: All work must be turned in
by Friday, May 10 at 5:00 pm;
work received after that time will not be counted in the grading of the course.
The final grade will be based upon each student's demonstration of her or his understanding of and facility in programming, not on the performance of the class as a whole nor on a strict percentile basis. While some flexibility may be possible in determining a final semester grade, the following percentages approximate the relative weights attached to various activities in this course.
|Discussion Questions: 10%||Assignments: 15%||Project Work in Groups: 45%||Hour Tests: 30%|
This document is available on the World Wide Web as
created January 11, 2002|
last revised March 14, 2002
|For more information, please contact Henry M. Walker at firstname.lastname@example.org.|