Emergency Dispatch rationale gap closure and GIS decomposition
System
{{entity:Emergency Dispatch System}} — interim QC triggered at session 257 (3 sessions since last QC at session 254). Project holds 95 requirements across 6 documents with 82 trace links. Three subsystems previously decomposed: {{entity:Call Handling Subsystem}} (6 components), {{entity:Computer-Aided Dispatch Subsystem}} (6 components), {{entity:Radio Communications Subsystem}} (6 components). Four subsystems remain: {{entity:Network Infrastructure Subsystem}}, {{entity:Records Management Subsystem}}, {{entity:Mobile Data Subsystem}}, {{entity:Geographic Information System Subsystem}}.
Findings
The primary finding was severe: all 53 requirements created in sessions 255–256 lacked rationale. Every SUB requirement ({{sub:SUB-REQS-010}} through {{sub:SUB-REQS-034}}), every IFC requirement ({{ifc:IFC-DEFS-006}} through {{ifc:IFC-DEFS-017}}), every VER entry, and three ARC decisions were created without --rationale. Verification attributes were correctly set on all requirements — the gap was exclusively in engineering justification.
Two duplicate architecture decisions were identified: ARC-DECISIONS-003 is a near-verbatim duplicate of {{sys:ARC-DECISIONS-002}} (Call Handling), and ARC-DECISIONS-005 duplicates {{sys:ARC-DECISIONS-004}} (CAD). Both duplicates tagged.
Lint reported 3 low-severity findings, all ontologically correct: the physical/abstract classification differences between the system entity and RF Network Gateway, and between {{entity:Dispatcher Workstation Interface}} and {{entity:Call-Taker Workstation}}, reflect genuine ontological distinctions. The 26 “missing SHALL” findings are ARC and VER entries that are design rationale and verification procedures by nature.
Six orphan requirements are all ARC-DECISIONS entries, which do not participate in the standard trace linksets.
VER coverage stands at 23/54 SUB+IFC requirements (43%), with all 20 IFC requirements now covered. The gap is in SUB requirements where only 3 of 34 have verification entries.
Corrections
Added engineering rationale to all 37 SUB and IFC requirements from sessions 255–256. Each rationale explains the derivation of performance values (e.g., {{sub:SUB-REQS-025}}‘s 48 voice paths derived from 24 dispatch positions × 2 concurrent transmissions), references applicable standards (NFPA 1221, CJIS v5.9, TIA-102.BACA-A, ITU G.114), and explains failure consequences.
Tagged ARC-DECISIONS-003 as duplicate-of-ARC-DECISIONS-002 and ARC-DECISIONS-005 as duplicate-of-ARC-DECISIONS-004. Added rationale to {{sys:ARC-DECISIONS-004}} and {{sys:ARC-DECISIONS-006}}.
Acknowledged all 3 lint findings as ontologically correct with session-257 references.
After QC, decomposed the {{entity:Geographic Information System Subsystem}} into 4 components: {{entity:Map Tile Server}} (tile rendering), {{entity:Geocoding Engine}} (address resolution), {{entity:Routing Engine}} (travel time computation), {{entity:Spatial Database}} (PostGIS geographic data store). Created 5 SUB requirements ({{sub:SUB-REQS-035}} through {{sub:SUB-REQS-039}}), 3 IFC requirements ({{ifc:IFC-DEFS-018}} through {{ifc:IFC-DEFS-020}}), 3 VER entries (VER-METHODS-021 through 023), and 1 ARC decision. All 11 trace links created.
flowchart TB
EDS["Emergency Dispatch System"]
CHS["Call Handling Subsystem"]
CAD["Computer-Aided Dispatch Subsystem"]
GIS["GIS Subsystem"]
RCS["Radio Communications Subsystem"]
MDS["Mobile Data Subsystem"]
RMS["Records Management Subsystem"]
NIS["Network Infrastructure Subsystem"]
EDS -->|contains| CHS
EDS -->|contains| CAD
EDS -->|contains| GIS
EDS -->|contains| RCS
EDS -->|contains| MDS
EDS -->|contains| RMS
EDS -->|contains| NIS
MTS["Map Tile Server"]
GCE["Geocoding Engine"]
RTE["Routing Engine"]
SDB["Spatial Database"]
GIS -->|contains| MTS
GIS -->|contains| GCE
GIS -->|contains| RTE
GIS -->|contains| SDB
GCE --> SDB
RTE --> SDB
MTS --> SDB
RTE -->|travel time| DDSM["Dispatch Decision Support Module"]
MTS -->|map tiles| DWI["Dispatcher Workstation Interface"]
GCE -->|coordinates| ALI["ANI/ALI Database Interface"]
Residual
SUB requirement verification coverage remains at 43% — the next QC or decomposition session should add VER entries for the highest-criticality SUB requirements (safety and performance requirements first).
Duplicate diagrams persist: two Context diagrams, two CAD Internal diagrams, two Radio Internal diagrams. These are cosmetic but should be cleaned up to avoid confusion.
Next
Three subsystems remain undecomposed: {{entity:Network Infrastructure Subsystem}}, {{entity:Records Management Subsystem}}, {{entity:Mobile Data Subsystem}}. Next session should decompose {{entity:Mobile Data Subsystem}} — it has the tightest coupling to the already-decomposed CAD subsystem through AVL data feeds and dispatch confirmation. After all 7 subsystems are decomposed, status moves to first-pass-complete for full QC.