Requirements Traceability Matrix
Portfolio Demonstration — Simulated Consulting Project using fictional business data.Traceability principle
Every requirement should connect to a design component and at least one acceptance test. Status in this sample is proposed; no production implementation is claimed.
| Requirement | Design component | UAT test | Status |
|---|---|---|---|
| BR-01 Source and territory | Lead fields + validation | UAT-01 | Proposed |
| BR-02 Regional routing | Assignment rules / queues | UAT-02, 03 | Proposed |
| BR-03 Exception handling | Triage queue + report | UAT-04 | Proposed |
| BR-04 Follow-up task | Record-triggered Flow | UAT-05, 06 | Proposed |
| BR-05 Pipeline reporting | Reports + dashboard | UAT-07 | Proposed |
| BR-06 Duplicate review | Matching / duplicate rules | UAT-08 | Proposed |
Change control
When a rule changes, update the requirement, design decision and UAT script together. The sales manager approves business rules; the Salesforce administrator reviews platform impact.
This document is a fictional portfolio demonstration. It contains no client data and makes no claim of completed implementation or measured results.