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 moderately large projects:

• After initial brainstorming, the class will develop about four possible project topics.
• Each student will join a team of about four to refine the topic, develop a design, and write a full implementation.
• Periodically, each group will report to the full class about their topic's specificiations, development, and testing.

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:

• Martin Fowler, UML Distilled, Third Edition: A Brief Guide to the Standard Object Modeling Language, Addison-Wesley/Pearson, 2004.

• Arthur J. Riel, Object-Oriented Design Heuristics, Addison-Wesley, 1996.

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.

• Labs: A few laboratory sessions will review elements of a UML environment and a software version-control system.

• 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 pPioneer Web) 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 large software projects. Each student will collaborate with a group to refine a project specification, and then to design and implement the project. Each group will make periodic reports on their decisions and progress to the entire class. Each group member will be expected to participate in each aspect of the project, including the presentations to the class.

• Hour Tests tentatively are scheduled for Friday, September 30, and Monday, November 21. 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..

Students are responsible for submitting labs and discussion questions by specified deadlines. For lab work, a penalty of 25% per class will be assessed for any work turned in late, even work submitted at the end of a class period. However, an extension of at least one class period is automatically granted if the department's computer network is down for an unscheduled period for a period of three or more hours during the week preceding the due date. Normally, a program or laboratory write-up is due every third class meeting.

Discussion questions submitted late will not be accepted.

Students may lose significant credit for failure to particiapte in group activities. For example, you should expect a penalty for missing a class that is scheduled for a group meeting or a group presentation.

Absolute Deadline: All work, including the group projects, must be turned in by Friday, December 9 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: 15%

Labs: 10%

Project Work in Groups: 45%

Hour Tests: 30%

If you have physical, psychiatric, or learning disabilities and require accommodations, you should follow these steps:

• Talk to a counselor in the Academic Advising Office, and provide that office with appropriate documentation of your disability.
• In consultation with the Academic Advising Office, determine what accommodations seem appropriate.
• Bring a letter about these accommodations from the Academic Advising Office to each of your instructors.

I would be delighted to talk with you to wok out any details.

This document is available on the World Wide Web as

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

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