Project Deliverables

The project deliverables have been broken down in "logical" sets. We cannot impose a micro-schedule that would be applicable to all the teams. You have to be in charge of planning the delivery of the various artifacts. However, you have to turn in the set, at the latest, by the due date listed on the class schedule. You are free to deliver the corresponding set before the date listed. If you think that your team cannot meet the deadline for a given set, you have to notify the Teaching Assistant, at least 1 week in advance, with a valid justification for the delay. Last minute requests for extensions will be ignored, and will lead to significant deduction in the number of points assigned to that set. Consecutive requests for extensions will also be ignored.

Rebasline LCA package (80 points)

Operational Concept Description (OCD) (5)
System and Software Requirements Definition (SSRD) (15)
System and Software Architecture Description (SSAD) and Rose Model Files (MDL) (25)
Feasibility Rationale Description (FRD) (5)
Life Cycle Plan (LCP) (25). Must include:

COCOMO™ II run
COCOMO™ II Data Collection Form (as an Appendix)

Prototype(s) (5)

IOC Working Set (270 points)
Assigning points to the Construction Set is difficult, as it depends on the number of iterations. You should deliver one construction set at the end of each iteration. We expect teams to have between 2-3 iterations, and the points will be divided accordingly: e.g., if you have 2 iterations, then each Construction Set delivered will be worth 135 points. One iteration is not acceptable. More than 3 iterations may be overkill. If your team decides to do 2 iterations, then the points can be split so that 90 points are given to the first iteration and 180 to the second.

It appears as if the "working system" doesn't get any point. This is not the case. If by the end of the semester, you do not have a "working" system, you will not get more than a certain percentage (to be determined by many factors) of the total points assigned to the Construction, Transition and Support Set. You are expected to "plan the flight, and fly the plan". You are mostly following a design-to-schedule approach: however, if you start significantly and unexpectedly scaling down the planned capabilities (which you should have thoroughly identified by the rebaselined LCA), due to poor project planning or management, your grades on the Iteration Plans, and Iteration Assessment Reports will be adversely affected. Similarly, Iteration Plans and Iteration Assessment Reports that misrepresent the current state of the Construction, will receive very low grades.

Documentation

As-built specs (90)

As-built Operational Concept Description (OCD) (5)

As-built System and Software Requirements Definition (SSRD) (15)

As-built System and Software Architecture Description (SSAD) and Rose Model Files (MDL) (60)

As-built Feasibility Rationale Description (FRD) (10)

Summary of the revisions

Iteration Plans (30) (one per iteration)

Inspection Plan (15) (one overall)

Inspection Reports (30) (at least 1 inspection report per iteration)

Test Plan (15) (one overall)

Test Reports (30) (at least 1 test report per iteration)

Quality Management Plan (20) (one overall)

Release Description (20) (one per iteration)

Iteration Assessment Reports (20) (one per iteration)

Implementation Set

Source Code Baselines (including comments in the source files)

Associated Compile-Time Files

Component Executables (you should have a working increment at the end of each iteration that could be demonstrated to the Teaching Assistant or to a Review Board)

Transition Set (50 points)

Transition Plan (including some Training planning) (20)
User Manual (30)

Support Set (30 points)

Support Plan (15)
Training materials (including tutorials and sample data) (5)
Regression Test Package (5)
Packaged Tools and Procedures (5)

Data Collection Set (20 points)

Size Report (including Source Lines Of Code (SLOC) estimates) (one size report per iteration)
COCOMO™ II & COQUALMO Data Collection Form (including actuals)
COCOMO™ II TOOL Data Collection Form
COCOTS Data Collection Form
CORADMO Data Collection Form

All deliverables should be properly stored in the CS 577 Archive, in accordance with the course guidelines. Failure to do so, will result in a significant deduction in the number of points assigned to the affected set.