Before code
Check the need, scope, rule, and expected outcome.
QUALITY THROUGHOUT
Start with a checkable promise. Every correction returns to the failed check and to the behavior it could have affected.
Check the need, scope, rule, and expected outcome.
Review the change. Check the component and its connections.
Exercise the full journey, access restrictions, workload, and operating response.
Observe the service. Investigate failures and use them to improve the next version.
THREE DIFFERENT DECISIONS
The identified version met the stated criterion.
The Client accepted the agreed software outcome.
Live-use protection, coverage, and operating procedures are ready.
Keep the feedback loop open. A pilot can reveal a misunderstood task. Operation can reveal a missing alert. Return to the affected rule, design, implementation, and checks.