POSTER 10
Section 3 · Business Analysis — Domains 5 & 6
Traceability, Monitoring & Solution Evaluation
The back end that closes the value loop: keep every requirement linked from origin to test and under change control (traceability & monitoring), then confirm the deployed solution actually delivers the intended value (solution evaluation). No trace, no proof; no evaluation, no learning.
Visual Map — The Requirements Traceability Matrix (RTM)
| Business need / objective | Stakeholder req. | Solution req. | Design / build | Test case | Status |
|---|---|---|---|---|---|
| Cut line defects 50% | Operator alert on fault | FR-12 fault alarm <2s | PLC module M4 | TC-12 | Verified |
| Cut line defects 50% | Trace each reject | FR-15 log reject + cause | MES report R7 | TC-15 | Implemented |
Forward tracing = need → requirement → build → test (coverage). Backward tracing = test/feature → originating need (no orphans, no gold-plating). The RTM is the backbone for impact analysis & scope control.
Traceability & Monitoring
- Trace each requirement both ways; maintain coverage.
- Baseline approved requirements; control change via impact analysis.
- Track requirement states: proposed → approved → implemented → verified.
- Approve changes through the right authority before work proceeds.
Solution Evaluation
- Define evaluation criteria & KPIs (from the future-state measures).
- Collect actuals; compare actual vs expected value.
- Identify limitations / solution & enterprise gaps.
- Recommend: release · iterate · replace · retire.
Exam Concepts
- Traceability enables impact analysis & guards against scope creep.
- Evaluation can continue after go-live.
- Tie results back to the business case & benefits.
- A baseline is an approved version; changes are controlled.
Executive View
- Proof the investment paid off — value, not just delivery.
- Objective basis to continue, scale or kill.
- Traceability protects scope & supports audit / assurance.
Industry Example
Manufacturing
- Post go-live on the automated cell: measure OEE, scrap %, throughput vs the business case. Defects fell 42% (target 50%) → recommend tuning, then evaluate scaling to a second line.
Relationships
- RTM underpins integrated change control with the PM.
- Evaluation feeds benefits realisation (programs, Poster 16) & value (Poster 4).
- Findings inform portfolio continue/kill decisions (Poster 18).
Memory Hooks
- "Trace it · prove it · value it."
- RTM = the spine linking need → test. No trace, no proof.
- Evaluation answer = release · iterate · replace · retire.
60-sec Review
Forward vs backward tracing
Sketch an RTM row
4 requirement states
Evaluation: actual vs expected
4 evaluation outcomes
PMI Visual Wall · Poster 10 · Business Analysis — Traceability & Solution Evaluation · original instructional design · A3 landscape