# Trace a requirement to the reason and test that justify it

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Trace a requirement to the reason and test that justify it

ID: MHC-D-RESEARCH-1011 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/trace-a-requirement-to-the-reason-and-test-that-justify-it

A requirement number is an address, not an explanation.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A requested change has unclear value, or nobody knows what will be affected if it changes.

### Avoid when

- A missing parent does not automatically make a derived requirement unnecessary. Review the rationale; a perfectly linked chain can still contain a mistaken assumption.

### Explanation

Connect the requirement to its parent need, design response and verification evidence. Read the chain in both directions: why does this feature exist, and how will this need be checked? Maintain the links when requirements change instead of keeping a traceability table that describes an earlier project.

### Template

Need or derived rationale: [reason]. Requirement: [requirement]. Design response: [design]. Verification evidence: [test]. Affected links if changed: [impact].

### Example

A reconciliation report traces to the need to detect missing relationships, a defined comparison rule and test cases containing deliberate omissions.

### Check

A reviewer can move from the need to its test and back without an unexplained link.

### Limits

- A missing parent does not automatically make a derived requirement unnecessary. Review the rationale; a perfectly linked chain can still contain a mistaken assumption.

### Evidence and sources

- supports: Requirements traceability links stakeholder expectations, requirements, design and verification artifacts so relationships and change impacts can be examined. — RS-B75D1BA19EF45AF3. A link records an asserted relationship; it does not prove that the rationale is sound or the requirement is complete. (Sections 6.2.1.2.2 through 6.2.1.2.4)
- RS-B75D1BA19EF45AF3: 6.2 Requirements Management — https://www.nasa.gov/reference/6-2-requirements-management/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/check-that-it-meets-the-specification-and-solves-the-real-problem
