CS 298: Software Analysis and Design

Syllabus

Spring 1996

Instructor:
Brian L. Stuart

Office:
Math 419
Office Phone:
726-3725
Office Hours:
1:30--2:30 Tuesday and Thursday and 8:00--11:00 Monday, Wednesday and Friday.

Text:
Software Engineering: A Practitioner's Approach by Roger S. Pressman.
Objectives:
One way of viewing this course is that it's about the software crisis and what we can do about it. Objectives that are more to the point, however, include:
  1. You'll be better able to read and understand existing software.
  2. You'll be better able to write software that is:
    1. readable
    2. maintainable
    3. efficient
    4. portable, etc.
  3. You'll have some understanding of the major programming paradigms including procedural, functional, logic and object-oriented.
  4. You'll be able to utilize formal design methods.
  5. You'll be better able to manage software projects.

Grades:
There will be two exams, a midterm worth 15% and a final worth 20%. The remaining 65% will be divided among at least four programming projects. These projects will include at least one in some language other than C, at least one that will involve modifying existing code and at least one that will be done in teams.

All work will be conducted according to Rhodes' Honor Code.





Brian L. Stuart