Skip to content
Ameen Abozaid
ARC-042

Architecture assurance

  • 5 Lessons
  • 3 h practice (estimate)
On this page 9 topics

Overview

Topics

  • Design reviews
  • testing evidence
  • operational acceptance

Learn first

3 h of practice (estimate)

Learning outcomes

  1. Run design reviews during delivery to catch drift from the approved architecture.
  2. Define the testing evidence needed for non-functional requirements (performance, security, resilience).
  3. Specify and verify operational acceptance before go-live.
  4. Decide go-live readiness from evidence.

Lessons

  1. 01Assurance during delivery
  2. 02Architecture drift
  3. 03Non-functional testing evidence
  4. 04Operational acceptance and go-live readiness
  5. 05Demo: finding drift in a delivery team's design

Lab and exercises

Lab

ARC-042-LAB1 · Larkspur assurance plan

Outcomes: 1–4 · Time: ~3 h

  1. Define assurance checkpoints across Larkspur delivery with focus, participants, and outputs.
  2. Create a drift log template and complete it for a provided design-versus-build comparison.
  3. For each Larkspur NFR, specify the test, the target, and the required evidence.
  4. Write an operational acceptance checklist (monitoring, alerting, runbooks, backup and restore, support, vendor escalation) with how each item is verified.
  5. Assess the provided set of test results and write a go, conditional go, or no-go recommendation.

Acceptance: go/no-go recommendation traceable to evidence.

Exercises (case-based; five exercises)

IDOutcomeTask
ARC-042-EX011Phase one runs for five months. Propose four assurance checkpoints and what each reviews.
ARC-042-EX021A team has added a cache of customer addresses that is not in the HLD. Classify it, state the options, and write the drift log entry.
ARC-042-EX032NFR: "checkout p95 under 2 s at peak". The team provides a load test run at 20% of peak volume with synthetic data. Is the evidence sufficient? State what you would require.
ARC-042-EX043Write five operational acceptance checks for the Larkspur platform and how each is verified in practice.
ARC-042-EX054Test results: functional pass, performance met, penetration test has one open high finding, restore test not done, rollback not rehearsed. Make a recommendation.
Show solutions
  • EX01 After the first slice (structure and integration style), before ERP and payment integration go live (contracts and failure handling), before pilot (NFR evidence, security findings), before go-live (readiness).
  • EX02 Drift, not necessarily bad; options: remove it, or accept via ADR with controls (data classification, retention, access, deletion); log entry with impact on privacy, owner, decision date.
  • EX03 Not sufficient: 20% of peak with synthetic data does not show peak behaviour; require peak (or above) volume, realistic data and mix, ERP latency included, p95 reported, tied to the requirement ID.
  • EX04 Examples: restore a backup and time it against RTO; trigger an alert and confirm the on-call receives it; run an incident drill with the vendor contact; confirm runbooks followed by someone who did not write them; verify access and permissions for support staff.
  • EX05 No-go for now or conditional go only if the high finding is fixed and retested, restore test completed, and rollback rehearsed by named dates; list each against evidence; residual risk accepted by the business owner.

All four outcomes are also covered by the lab acceptance and the quiz.

Workplace evidence: an assurance review or go-live decision you led.

Quiz

Outcomes: O1 design reviews and drift · O2 NFR testing evidence · O3 operational acceptance · O4 go-live decision.

A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.

  1. 1The ARB approved the design in March. In June a team's batch job reads ERP tables directly, against the HLD. This is:O1
  2. 2Best way to detect drift in a team's design?O1
  3. 3Assurance that ends at design approval is a mistake because:O1
  4. 4"Checkout p95 under 2 s at peak" is best evidenced by:O2
  5. 5A resilience requirement states the shop must keep taking orders when the ERP is unavailable. Evidence is:O2
  6. 6Which evidence is weakest?O2
  7. 7Which operational acceptance check is verified by doing, not reading?O3
  8. 8Which item belongs in operational acceptance for a mixed SaaS and owned estate?O3
  9. 9Functional and performance tests pass, but a high security finding is open and restore was never tested. The most defensible recommendation is:O4
  10. 10Who accepts residual risk at go-live?O4

Practical part

Go/no-go decision review on the Larkspur lab: assurance checkpoints, NFR evidence per requirement, operational acceptance checklist, and a recommendation traceable to the provided test results. Pass: quiz at least 8/10, at least four of five exercises correct, and a lab with a justified recommendation.

Common mistakes

Assurance that ends at design approval; go-live without NFR evidence.

Assessment

Go/no-go decision review.

Workplace evidence

An assurance review or go-live decision you led.

Career relevance

Assurance protects the business after the design is approved.

Type to search levels, phases, modules and lessons.