Phase 04
Requirements, rules and traceability
Translate stakeholder needs and pain points into prioritized, testable requirements, governed rules and acceptance evidence.
Inspect the evidence
Pain pointPP-01
RequirementFR-001
RuleRULE-002
DesignTO-BE 02
TestUAT-003
MeasureKPI-02
Selected requirement baseline
| ID | Type | Requirement | Priority |
|---|---|---|---|
| BR-001 | Business | Reduce avoidable intake rework while preserving assisted channels. | Must |
| FR-001 | Functional | Present fields and evidence based on program and responses. | Must |
| FR-002 | Functional | Validate mandatory information before submission. | Must |
| FR-003 | Functional | Create one case and transfer captured data without re-keying. | Must |
| FR-004 | Functional | Assign priority and queue using approved rules. | Must |
| FR-005 | Functional | Require authorized, reasoned and audited routing overrides. | Must |
| FR-006 | Functional | Show applicants safe status, outstanding action and contact route. | Should |
| FR-008 | Functional | Synchronize status, notice and reporting from one decision event. | Must |
| DR-001 | Data | Store each status transition as an immutable event. | Must |
| NFR-001 | Non-functional | Support accessibility, keyboard, zoom, contrast and assisted service. | Must |
| NFR-002 | Non-functional | Apply least privilege, encryption, retention and audit logging. | Must |
| NFR-004 | Non-functional | Refresh KPI data daily with lineage and failed-load alerting. | Should |
Business-rule governance
| ID | Rule | Implementation point | Owner |
|---|---|---|---|
| RULE-001 | Minimum submission | Validation service | Program Policy |
| RULE-002 | Dynamic document checklist | Rules service | Program Policy |
| RULE-003 | Emergency priority | Queue rule | Operations |
| RULE-004 | High-complexity review | Workflow gate | Operations |
| RULE-005 | Public status mapping | Status API | Operations + Privacy |
| RULE-006 | SLA warning | Event monitor | Operations |
| RULE-007 | Decision synchronization | Orchestration | Technology + Data |
| RULE-008 | Override audit | Audit event | Privacy + Security |
My analysis and method Why this phase matters
Requirements create a contract between the business problem and the solution. Traceability proves why each feature exists and how it will be tested.
Capability demonstrated
What this work shows
Wrote clear, prioritized statements with sources and acceptance summaries.
Assigned owners, exceptions, implementation points and test IDs.
Linked pain point, requirement, rule, design, test and measure.
Fictional municipal scenario, synthetic data, simulated discovery and validation. No City of Toronto affiliation or claimed production outcome.