CS650 FALL 1999
SOFTWARE DESIGN AND DEVELOPMENT

Professor: J. Lynch
Office: SC-381
Telephone: 268-2374
email:
jlynch@clarkson.edu
Office hours: MWF 2:00-4:00
Text: There is no text

SYLLABUS

The purpose of this course is to give you experience in working on a large software project as part of a group. Within reason, I would like to give everyone the opportunity to choose who their teammates are, and what project they would like to do. After the teams are set up and the projects are decided, each group will undertake the four major phases of a software project:

DEFINITION
DESIGN
CODING
TESTING

During each phase, each team will make informal and formal presentations to the rest of the class. Informal presentations can be just a verbal description of some aspect of the team's project, perhaps with the use of the blackboard. Formal presentations should involve some prepared visual aids, such as overhead transparencies, handouts, or projected computer displays. Each team can decide which members(s) will do the presentation. The final presentation will be (hopefully) a demonstration of the successfully completed software. Also, written documentation of each phase will be turned in.

Not every class will be devoted to presentations; there will be many times when I will meet with one or more groups. This could be to discuss the status of the project and any problems that are encountered, or to prepare for a presentation.

GRADING

There are no tests. At the end of the course, you will receive a letter grade based on your team's overall performance in all four phases of the project. This will include effectiveness of the presentations, quality of the written documentation, and of course the quality of the software. Except in very unusual circumstances, all members of a team will receive the same grade. I am not assigning numeric grades to any specific part of your project, nor is any part of your project worth a specific percentage of your final grade. If your team does poorly on some part, you can make up for it by doing an outstanding job on some other part. But don't think you can goof off all semester and end up with a good grade just by turning in a working piece of software. The most successful and enjoyable projects will be done by teams that stay on schedule and work steadily through the whole semester.