Requirements Traceability Matrix

Requirements Traceability Matrix

Tracks each REQ-### requirement in Software-Requirements-Specification to its verification evidence and implementing code, and allocates each SYS-REQ-### in System-Requirements-Specification to software requirements. Columns mirror repo-standards-review's rtm-template.csv (ReqID,Requirement,Source,Priority,TestID,TestArtifact,CodeRef,Status). Each row lives on its own linked ID page. The standards scan rebuilds the table from those pages; signed-in GitHub users can see the rebuilt table, a generated, non-authoritative view, in each scan run summary. TEST-014 and TEST-041 through TEST-069 are planned cases in Planned-Windows-Bootstrap-Test-Cases. TEST-070 through TEST-088 are planned cases in Planned-Cross-Platform-Qualification-Test-Cases. TEST-089 through TEST-105, and TEST-107 through TEST-135, are indexed in Planned-Specification-And-System-Contract-Test-Cases. Each test page states whether its cases are planned or executed; the index itself does not imply a passing implementation or live qualification result.

• REQ-001
• REQ-002
• REQ-003
• REQ-004
• REQ-005
• REQ-006
• REQ-007
• REQ-008
• REQ-009
• REQ-010
• REQ-011
• REQ-012
• REQ-013
• REQ-014
• REQ-015
• REQ-016
• REQ-017
• REQ-018
• REQ-020
• REQ-021
• REQ-022
• REQ-023
• REQ-024
• REQ-025
• REQ-026
• REQ-027
• REQ-028
• REQ-029
• REQ-030
• REQ-031
• REQ-032
• REQ-033
• REQ-034
• REQ-035
• REQ-036
• REQ-037
• REQ-038
• REQ-039
• REQ-040
• REQ-041
• REQ-042
• REQ-043
• REQ-044
• REQ-045
• REQ-046
• REQ-047
• REQ-048
• REQ-049
• REQ-050
• REQ-051
• REQ-052
• REQ-053
• REQ-054
• REQ-055
• REQ-056
• REQ-057
• REQ-058
• REQ-059
• REQ-060
• REQ-061
• REQ-062
• REQ-063
• REQ-064
• REQ-065
• REQ-066
• REQ-067
• REQ-068
• REQ-069
• REQ-070
• REQ-071
• REQ-072
• REQ-073
• REQ-074
• REQ-075
• REQ-076
• REQ-077
• REQ-078
• REQ-079
• REQ-080
• REQ-081
• REQ-082
• REQ-083
• REQ-084
• REQ-085
• REQ-086
• REQ-087
• REQ-088
• REQ-089
• REQ-090
• REQ-091
• REQ-092
• REQ-093
• REQ-094
• REQ-095
• REQ-096
• REQ-097
• REQ-098
• REQ-099
• REQ-100
• REQ-101
• REQ-102
• REQ-103
• REQ-105
• REQ-106
• REQ-107
• REQ-108
• REQ-109
• REQ-110
• REQ-111
• REQ-112
• REQ-113
• REQ-114
• REQ-115
• REQ-116
• REQ-117
• REQ-118
• REQ-119
• REQ-120
• REQ-121
• REQ-122
• REQ-123
• REQ-124
• REQ-125
• REQ-126
• REQ-127
• REQ-128
• REQ-129
• REQ-130
• REQ-131
• REQ-132
• REQ-133
• REQ-134

System-To-Software Allocation

Each system row allocates to the software IDs in its CodeRef cell. The listed tests are representative; each allocated software row above retains its complete test and evidence references. A system row remains planned until system-level integration evidence is reviewed, regardless of an individual software row's status.

• SYS-REQ-001
• SYS-REQ-002
• SYS-REQ-003
• SYS-REQ-004
• SYS-REQ-005
• SYS-REQ-006
• SYS-REQ-007
• SYS-REQ-008
• SYS-REQ-009
• SYS-REQ-010
• SYS-REQ-011
• SYS-REQ-012
• SYS-REQ-013
• SYS-REQ-014
• SYS-REQ-015
• SYS-REQ-016
• SYS-REQ-017
• SYS-REQ-018
• SYS-REQ-019
• SYS-REQ-020
• SYS-REQ-021
• SYS-REQ-022
• SYS-REQ-023
• SYS-REQ-024
• SYS-REQ-025
• SYS-REQ-026
• SYS-REQ-027
• SYS-REQ-028
• SYS-REQ-029
• SYS-REQ-030
• SYS-REQ-031
• SYS-REQ-032
• SYS-REQ-033
• SYS-REQ-034
• SYS-REQ-035

Status legend

• Verified (live): directly observed working via a real dispatch/run, pointing at a durable, re-checkable artifact (an issue, an immutable release tag, or a re-runnable workflow's own logic) -- never at a bare, ephemeral workflow run ID as if that one past run were itself the permanent proof. Not a unit test suite yet -- see repo-standards-review's Coverage gate, VITechnologies/projectbuddy#8, which is tracking adding real automated test coverage.
• Verified (manual): confirmed true by reading the actual code/docs, but no automated regression test exists yet to catch a future regression.
• Planned: documented intent, not yet independently verified even manually beyond the doc text itself.