Introduction to Software Engineering

CS3302 Spring Quarter 1997

Project Milestones

The following constitutes a nominal schedule for achieving milestones in the project portion of the course. Though each deliverable is the group's responsibility, one team member (indicated by the role below) will be assigned specific responsibility for the completion of that document. The "individual assignment portion of your grade will reflect how well your team performed on the project deliverable you are directly responsible for.
  1. Project Teams Defined

    Due: 4/10

    Project teams are finalized and topics chosen.

  2. Project Plan

    Due: 4/17

    Principal Responsibility of: Manager

    A document introducing the project topic, team members and providing a schedule for activities to be performed during the quarter. This schedule will be the basis for monitoring progress throughout the quarter.

    Grading criteria

  3. Requirements Document

    Due: 4/27

    Principal Responsibility of: Technical Writer

    An extended document that details all functional requirements of the delivered prototype. A section of this document also indicates nonfunctional requirements that will be used to test the system for acceptability and a storyboard will be used (and potentially presented to the class) to demonstrate how the system will look and be used.

    Grading criteria

  4. Test plan

    Due: not required this quarter

    Principal Responsibility of: Quality Assurance

    This document describes how the software product will be tested and includes a section to be filled in later on test results.

    Grading criteria

  5. Design Document

    Due: 5/8

    Principal Responsibility of: Architect

    A detailed description of how the system will be built, including, for example, a high-level software architecture and any component interfaces or interfaces object-oriented analysis and design to show the system structure.

    Grading criteria