Case discussions
Practice engineering judgment through four textbook cases. Write your decision, evidence and missing information before consulting the reference.
Milestones and engineering gates
Blueprint first, three milestones for auth, rate limiting, and routing, each with acceptance criteria.
How would you define the first independently verifiable milestone? Which checks need rerunning?
Migration and architecture boundaries
Static recon first, event storming to recover the old workflow, a strangler migration, divergence records for ambiguous rules.
Which contracts must survive? What evidence would lead you to repair or rebuild?
Requirements, state and acceptance
Eight stages in one chain, from scaffold to deploy config, context rebuilt from saved facts, with release confirmed by an authorized owner.
How would you map user actions to state transitions and define failure behavior before implementation?
Evaluation, handover and adoption
Evidence-backed suggestions with human confirmation. Prohibitions block a cheaper candidate; verify handover and adoption separately. All numbers are teaching assumptions.
Can 94/100 with 3/20 red-line failures release? Why separate weekly activity from 30-day adoption?
Cases are teaching material; scenarios, samples and gates are not measured customer evidence or industry benchmarks. Record your judgment separately from the reference.
After your case notes, independently define requirements, implementation and acceptance in the capstone. Revisit modules to address gaps first.