Capstone acceptance and scope evidence
This required 18–26-hour integrated package strengthens the existing guided labs. Allocation: lessons/predictions 4–6 hours, scope/spike/review 9–13, assessment/repair 5–7. Author estimates require learner timing pilots and are included in the semester workload contract. Reuse the same service and evidence; avoid creating a second portfolio.
Prerequisite bridge
Bring the preceding module's implementation, risk record and failure observations. Separate assumptions, model results and actual runtime evidence. Review the specific prerequisite named in each lesson before its exercise. Missing runtime tools leave execution evidence pending; a written prediction is not an executed experiment.
Lesson sequence
- Turn the problem into falsifiable acceptance claims.
- Use a spike to resolve a decision rather than decorate it.
- Cut features without cutting the evidence needed to graduate.
Integrated experiment
Use the existing scope/risk workshop, domain discovery, quality views and three ADRs. Add one acceptance ledger and one decision-changing spike, then apply a fictional 25% capacity reduction. Preserve the initial and revised plan. A reviewer must be able to trace one user action through domain invariant, architecture view, implementation boundary and planned verification. The new packet complements the real capstone rather than replacing it with a fictional project.
Complete the assessment. Original guided labs, security controls, deployment/testing and peer requirements remain mandatory. Use synthetic data and a disposable local environment where supported; no cloud purchase is required by this extension.
Selective resources
C4 model; Google engineering review guidance. Revisit Semester 07 quality, domain and review lessons; no new book is required.