emovis CTIO Research Hub
HomeProcessTraceability chain
Section 2 of 9
Connecting requirements to delivery

Traceability chain — straight out of the RTM

Every link below comes directly from the RTM columns, so scope is traceable end to end.

StageWhat it carriesRTM source
RTM RequirementRequirement # + Descriptioncols 3–6
Detailed req + RulesDDD Volume/Section + BR # + Confluencecols 33–60
JIRA Epic / DevJira Dev # + Sprint #cols 61–62
Web / App sub-tasksBuilt by GRM under the Development stream
System testTest Type + Test JIRA Ticket # + Statuscols 64–69
Acceptance / ReleaseAccepted for Release + Final Acceptancecols 88–102
⚠ Source gap to close

The RTM has Omnichannel – Web (col 79) but no separate Mobile / App column. To filter and trace GRM's mobile-app scope cleanly, add an "App" impact column before building the backlog.

Why this matters

Every web/app sub-task is traceable backward to a requirement and a business rule, and forward to a test ticket and a client acceptance record — so "done" is provable, not asserted.