CS 450 Software Design and Development
Course Syllabus -- Fall 1997

Instructor: C. Lynch
Office: SC371
Phone: x2384
email: clynch@sun.mcs.clarkson.edu

Office Hours:

  • Mon. 11:00-12:00 noon and 3:00-4:00 p.m.
  • Wed. 11:00-12:00 noon and 3:00-4:00 p.m.
  • Fri. 11:00-12:00 noon
  • and by appointment
Course Objectives:

  1. Students willlearn object oriented techniques for developing and designing software.
  2. Students will use these techniques to develop a major piece of software as a group project.

Textbook: "Object-Oriented Design Heuristics", by Arthur Riel,
Addison-Wesley, 1996.

Optional text: A textbook to learn or brush up on C++.

Grading Policy:

  • Projects 50%
  • Critiques of other projects 30%
  • Critiques of design process 20%
There are no exams.

The main portion of class time will consist of presentations by members of the class and class discussion. A very small part of the class will be lectures.

At the beginning of the class, students will find different projects, and break into teams. Each team will work on one project, using object oriented software engineering techniques. I will describe the different phases of a project, and each tema must go through those phases. For each phase of the project, I will expect class presentations and written reports. The 50% of the grade called "Projects" will be based on this.

Each team will create a web site for all the documentation of their projects. The members of other teams will review the decoumentation and write written criticisms of it. Also, there will be class discussions. The 30% of the grade called "Critiques of other Projects" will be based on this.

The textbook covers heuristics for the design of an object oriented system. At some points during the class, I will assign people to present some of those heuristics to the class, where we will have class discussions. The 20% of the class called "Critiques of design process" will be based on this.

Attendance is very important for this class, as you must participate in the class discussions of your project. Late assignments will only be accepted if an agreement has been worked out in advance. Interaction with other members of the class is highly encouraged. But direct copying will receive a grade of 0 for the first offense, and a notification to the academic integrity board for the second.

Tentative Course Outline
1. 9/1 Choose Projects and Teams
2. 9/8 Project Proposal
3. 9/15 Specifications
4. 9/23 Requirements and Prototype
5. 9/29 Analysis
10/6 - 10/7 ***Fall Recess***
6. 10/8 Analysis
7. 10/13 Design
8. 10/20 Design
9. 10/27 Design
10. 11/3 Implementation, Unit Test, Integration Test
11. 11/10 Implementation, Unit Test, Integration Test
12. 11/17 Implementation, Unit Test, Integration Test
11/26-11/28 *** Thanksgiving Recess ***
13. 12/1 Implementation, Unit Test, Integration Test
14. 12/8 System Test