Computer Science 223 provides a framework for the study of the development of large software systems. Components of the course include:

• elements of the software life cycle: specification, design, coding, testing, and maintenance;
• the use of UML as an aid in specification and design;
• use of object-oriented problem-solving strategies;
• prototyping;
• identification of testing frameworks;
• project coordination and interfaces;
• system integration and testing; and
• implications of maintenance.

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
E-mail: walker@cs.grinnell.edu
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.

• Assignments extend the range of problems considered in the course and help sharpen problem-solving skills. Parts of this course may involve individual or group exercises. Particularly at the beginning of the semester, assignments will aid in learning basic techniques that then will be applied on a larger scale to the class project.

• Labs: Laboratory sessions review various elements of the Java programming language and a UML environment.

• Discussion Questions: To encourage preparation for class, the tentative class schedule specifies several class periods for which students are to prepare discussion questions. For such classes, students will be expected to submit (via e-mail) two questions on the readings by 5:00 pm on the day before class. While many types of questions are appropriate (e.g., open-ended, clarifying, connective and relational, involving value conflicts), simple factual questions should be avoided (unless the facts are in dispute).

• Class Project: A substantial component of this course involves the development of a large class project. Initially students will collaborate in large groups to determine major elements of specification and design. As the project progresses, however, groups will become smaller, with different groups focusing on distinct components of the overall project. It is anticipated that detailed implementation will proceed in groups of about 2 students. A project index will provide information about various elements of this project.

• Hour Tests tentatively are scheduled for Friday, February 22, and Friday, April 19. Any changes in these dates will be announced in class at least one week in advance.

• Exam: Since this is a project-oriented course, there will be NO final examination during exam week..

Deadlines for specific assignments will be posted on-line at http://www.walker.cs.grinnell.edu/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

     http://www.walker.cs.grinnell.edu/courses/223.sp02/index.html

created January 11, 2002 last revised March 14, 2002
For more information, please contact Henry M. Walker at walker@cs.grinnell.edu.