Colorado State University Computer Science Department

Software Development Methods
Fall 2001

To go to the CS314 Spring 2001 webpage, click here

CS314 on WebCT

All CS 314 students need to have a WebCT account. Your login and password from your Holly account will work on WebCT. Get an account on Holly here if you don't have one.

All lecture notes, assignments, projects and grades will be made available through WebCT. Announcements will be made through the bulletin board in WebCT. You can set up discussion groups and chat-rooms for the course using WebCT.

Click here to go to the password protected CS314 WebCT page.

Click here for instructions on using WebCT.

Objectives General Information Course Materials Quizzes
Assignments Projects Exams Grading

Course Objectives

Prerequisite: CS253 and all the prerequisites for CS253 including CS166 (Discrete Structures) and CS200 (Data Structures).

This course will expose students to techniques used to develop large software systems. Major topics include system and requirements engineering, object-oriented design, and systematic code testing techniques. Students will use CASE tools for many of the topics mentioned below.

The following topics will be covered in the course (not necessarily in the given order):

  1. Examples of disasters related to "bad" S/W Engineering
  2. Software product and process
  3. Project management
  4. Project planning
  5. Risk assessment
  6. Analysis
  7. Design
  8. Implemention
  9. Software configuration management
  10. Metrics
  11. Software quality assurance
  12. Software testing

General Information

Sudipto Ghosh
US Mail: Computer Science Department, Colorado State University, Fort Collins, CO 80523
Phone: (970) 491-4608
Fax: (970) 491-2466
Office Location: 224 University Services Center
Office Hours: MWF 2:30-3:30pm 224 University Services Center

Ketaki Kalgaonkar
US Mail: Computer Science Department, Colorado State University, Fort Collins, CO 80523
Phone: (970) 491-5944
Fax: (970) 491-2466
Office Location: South Lab 3nd Floor University Services Center
Office Hours: Time: TW 3-5pm

MWF 1:10-2:00
Clark C144

Late work will not be accepted without prior permission. Extensions may be granted when permission is sought in advance for reasons that are unexpected and beyond your control.

Homework assignments are to be done individually. Projects are to be done in groups. You are responsible for any announcements made in class.

All written work must be typed on 8.5 by 11 paper, have at least 1 inch margins and be printed in 10, 11 or 12 point type. Work should be single-spaced. Diagrams have to be drawn with the help of Rational Rose. All work must be neat and legible.

Read the departmental policy on cheating, incompletes and class attendance.

Course Materials

  • Required Text:
    1. Software Engineering: A Practitioners Approach Fifth Edition, Roger Pressman, McGraw-Hill, 2001.

  • Supplementary Texts: (Will be available in the library)
    1. Software Engineering, Ian Sommerville, Addison-Wesley, 2001.
    2. Software Engineering: Theory and Practice, S. Lawrence Pfleeger, Prentice Hall, 1998.

  • Course Notes will be accessible through WebCT only.


Several short quizzes will be given in class throughout the semester. These quizzes will also be discussed in class to increase class participation. The quizzes are worth 5% of the final grade.


There will be a few homework assignments spread out during the semester. Assignments will be made available through WebCT. Each assignment needs to be done individually. Most assignments will involve writing programs and testing. Some will involve using CASE tools. One or two may also involve writing a page or two. Assignments are worth 25% of the final grade.


Each student is expected to work in a group of three to develop a software system. Each group will produce a project plan, a requirements document, a design document and code for the project. The project is worth 20% of the final grade. Project descriptions will be available through WebCT The project will be assigned sometime in late September and will be divided into parts that follow the lecture material. Thus you will need to turn in parts of the project once every 3 weeks or so. The final project demo will be held in the last week of the semester (before finals week).


There are two exams: one midterm exam in class (20%) and one final exam (30%) during the final's week.

Exam Date
Midterm exam: October 5, in class
Final exam: December 11, 11:20 a.m. - 1:20 p.m


Homework: 25%
In class quizzes: 5%
Project: 20%
Midterm exam: 20%
Final exam: 30%

Final letter grades will be based on the relative distribution of total scores and not on any preset numerical grade. Click here to see your grades.

Last modified: August 14, 2001.