CS 410 Software Engineering

Team Number:

Team Name:

Developer Project:

Client Project:

____/5   Requirements Report

• level is suitable
• number of requirements sufficient

____/2   Review of Specification Report

____/2   Review of Management Plan

____/4   Evaluation

• extras noted
• deficiencies noted
• usefulness of user manual evaluated

____/2   Conduct Interview

____/8   Functional Specification Report

• introduction summary
• glossary
• user interface defined
• requirements testable
• requirements clear enough for another group to implement
• requirements numbered for cross-reference
• other reports/deliverables included
• I/O/errors discussed

____/4   Management Plan

• basic strategy
• schedule
• minimal system
• group organization
• cost estimate using COCOMO model

____/6   Overall Design Document

• overview of design

____/4   Design Walkthrough

• organized
• group participation
• report

____/10 Detailed Design Document

• complete design
• well-structured report
• user interface details
• modual/object design
• test schedules

____/6 Test Plan

• unit tests
• system tests
• user-interface tests
• procedures:
•     monitoring
•     reporting
•     correcting
• details of tests
• objectives
• success criteria

____/6   User Manual

• introduction
• how to use
• error recognition and handling
• known errors and deficiencies

____/4   Test Report

• results of all tests

____/15   Code

• clean/consistant layout
• documented
• well structured

____/10   Demo - User Interface

• meets clients requirements
• robust
• user interface

____/6   Project web site

• "good" design
• accessible

____/6   Document/report style

____     Late submissions

____     Change Pages for Reports

____/95   TOTAL