SDLC blueprint

Handbook

Phased delivery — major processes & flow maps

```mermaid

Phased delivery — major processes & flow maps

1. Classic stage sequence (simplified)

flowchart LR I[Initiate] --> P[Plan] P --> D[Design] D --> B[Build] B --> T[Test] T --> U[UAT] U --> R[Release] R --> O[Operate]

Overlap stages where policy allows; gates sit on arrows.

2. Gate decision

flowchart TD G[Gate pack submitted] --> C{Exit criteria met?} C -->|No| H[Hold + actions] H --> G C -->|Yes| N{Steer / sponsor approves?} N -->|No| X[Defer / kill / replan] N -->|Yes| Y[Enter next stage]

3. Change control path (scope)

flowchart LR CR[Change request] --> IA[Impact analysis] IA --> B{Steer decision} B -->|Approve| BL[Re-baseline] B -->|Reject| Q[Queue or drop]

4. Traceability thread

flowchart LR Req[Requirement ID] --> DS[Design ref] DS --> TC[Test case] TC --> RN[Release note]

5. Phases A–F (typical mapping)

Blueprint phase Typical phased locus
A Shape Initiate; charter; high-level requirements
B Plan Planning; WBS; schedule baseline
C Build Design and implementation per baseline
D Verify Test phases; inspections; exit evidence
E Release UAT; deployment; handover
F Learn Operate; warranty; benefits realization

6. Flow details (walkthrough)

Stage sequence — The linear diagram is pedagogical; real programs may overlap stages where policy allows. Gates sit on transitions; each stage produces baselines the next consumes. Map org stage names to blueprint A–F for one language across RAID, audits, and agents.

Gate decision — Gate packs prove exit criteria (quality, risk, readiness). Failed criteria mean hold and corrective actions, not silent waivers. Sponsor or steering approval commits spend and the next baseline; defer, kill, or replan are valid.

Change control — Change requests and impact analysis (schedule, cost, risk, traceability) feed steering decisions: re-baseline with versioned artifacts, or reject/queue. Ad-hoc scope without this path breaks audit trails.

Traceability — Requirement ID → design → test case → release note supports impact analysis and demonstrates coverage to auditors.

7. Authoritative sources & further reading

PMI — Standards & guides is listed in REFERENCE-LINKS.md for practitioner depth (some networks block automated fetches to pmi.org).

Canonical source

Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/phased/process-and-flows.md first; regenerate with docs/build-handbook.py.