Unit 17: Capstone Requirements, Architecture, and Test Plan

The final project begins before the final code.

Your capstone must solve a credible problem for a defined audience and leave enough evidence that another programmer can evaluate whether the design actually meets its requirements.

This unit produces Version 1 and its validation plan.

By the end you should have:

• problem and audience statement;
• functional requirements;
• at least one quality constraint;
• data-structure decision;
• domain/object model;
• responsibility/dependency diagram;
• test matrix;
• runnable Version 1;
• at least one unresolved limitation or defect worth investigating in Unit 18.

The strongest project is not the largest. It is the one whose decisions and evidence can be defended.