ECSS Requirement Traceability (space-systems/ecss/e10-req-traceability)
Use when maintaining the bidirectional requirement traceability chain
under ECSS-E-ST-10C clause 5.2.2, after requirements have been analysed
(sibling e10-req-analysis) and flowed down (e10-trs-flowdown).
When to use
- Keeping the Requirements Traceability Matrix (RTM) current as
requirements, products and verifications change.
- Checking before a review gate that every requirement resolves both
directions: upward to the requirement(s) it originates from, and
downward to an allocated product and a verification record.
- Auditing a delivered RTM for broken, missing, or dangling links.
Domain quick reference
Trace directions (bidirectional, 5.2.2):
- Upward: derived requirement -> the customer/upper-level requirement
it was produced from. Customer-level requirements are the root and
have no upward link.
- Downward: requirement -> product(s) it is allocated to, and
requirement -> verification activity/record that closes it.
Procedure
- Collect the requirement records (id, level, parents, products,
verifications), product records and verification records.
- Run
python3 scripts/test_e10_req_traceability.py to confirm the
module's own contract still passes.
- From Python, import the sibling logic module and call:
import e10_req_traceability_logic as rtl
# records: dicts with id/level/parents/products/verifications
gaps = rtl.trace_gaps(requirements, products, verifications)
- Interpret gap codes (constant names on the module):
GAP_NO_UPWARD_TRACE - derived requirement without a parent.
GAP_NO_DOWNWARD_TRACE - customer requirement with neither a child
requirement nor a direct product allocation.
GAP_NO_PRODUCT_ALLOCATION - requirement with no product allocated
(customer requirements flowing to derived children are exempt).
GAP_NO_VERIFICATION_LINK - requirement with no verification record.
GAP_DANGLING_PARENT / GAP_DANGLING_PRODUCT /
GAP_DANGLING_VERIFICATION - link references a record outside the
given sets.
- Fix each gap in the RTM before the review gate; re-run
rtl.is_fully_traced(...) until it returns (True, {}).
Verification
- The offline unittest suite passes (
python3 -m unittest scripts.test_e10_req_traceability, or the test file directly).
- A clean bidirectional chain returns no gaps.
1---2name: e10-req-traceability3description: "Use when maintaining bidirectional requirement traceability under ECSS-E-ST-10C: keep the requirements traceability matrix (RTM) aligned across customer requirements, derived requirements, allocated products and verification records, and detect broken, missing or dangling trace links before review gates. ECSS-E-ST-10C clause 5.2.2 governs requirement traceability as part of system engineering requirement flow-down. Trigger: ecss, e-st-10c, requirement traceability, RTM, trace matrix, bidirectional trace, 5.2.2, space systems engineering."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e10-req-traceability15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, requirement-traceability, rtm, traceability-matrix, bidirectional-trace, systems-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Requirement Traceability (space-systems/ecss/e10-req-traceability)2324Use when maintaining the bidirectional requirement traceability chain25under ECSS-E-ST-10C clause 5.2.2, after requirements have been analysed26(sibling e10-req-analysis) and flowed down (e10-trs-flowdown).2728## When to use2930- Keeping the Requirements Traceability Matrix (RTM) current as31 requirements, products and verifications change.32- Checking before a review gate that every requirement resolves both33 directions: upward to the requirement(s) it originates from, and34 downward to an allocated product and a verification record.35- Auditing a delivered RTM for broken, missing, or dangling links.3637## Domain quick reference3839Trace directions (bidirectional, 5.2.2):4041- Upward: derived requirement -> the customer/upper-level requirement42 it was produced from. Customer-level requirements are the root and43 have no upward link.44- Downward: requirement -> product(s) it is allocated to, and45 requirement -> verification activity/record that closes it.4647## Procedure48491. Collect the requirement records (id, level, parents, products,50 verifications), product records and verification records.512. Run `python3 scripts/test_e10_req_traceability.py` to confirm the52 module's own contract still passes.533. From Python, import the sibling logic module and call:5455```python56import e10_req_traceability_logic as rtl57# records: dicts with id/level/parents/products/verifications58gaps = rtl.trace_gaps(requirements, products, verifications)59```60614. Interpret gap codes (constant names on the module):6263- `GAP_NO_UPWARD_TRACE` - derived requirement without a parent.64- `GAP_NO_DOWNWARD_TRACE` - customer requirement with neither a child65 requirement nor a direct product allocation.66- `GAP_NO_PRODUCT_ALLOCATION` - requirement with no product allocated67 (customer requirements flowing to derived children are exempt).68- `GAP_NO_VERIFICATION_LINK` - requirement with no verification record.69- `GAP_DANGLING_PARENT` / `GAP_DANGLING_PRODUCT` /70 `GAP_DANGLING_VERIFICATION` - link references a record outside the71 given sets.72735. Fix each gap in the RTM before the review gate; re-run74 `rtl.is_fully_traced(...)` until it returns `(True, {})`.7576## Verification7778- The offline unittest suite passes (`python3 -m unittest79 scripts.test_e10_req_traceability`, or the test file directly).80- A clean bidirectional chain returns no gaps.