ECSS Requirement Risk Analysis (space-systems/ecss/e10-req-risk-analysis)
Use when the task is analysing the technical/requirement risk of a
candidate or derived requirement at a given flow-down level under
ECSS-E-ST-10C clause 5.2.3.3, feeding the project risk register, and
defining mitigation consistent with M-ST-80.
Domain quick reference
- ECSS-E-ST-10C clause 5.2.3.3 requires each level of the requirement
flow-down (customer TS through every lower-level TS) to analyse the
technical/requirement risk of its requirements and enter the result
in the project risk register.
- Risk is scored as likelihood x severity (each 1-5), consistent with
the ECSS risk-management standard (M-ST-80): risk index bands into
low (<=4), medium (5-9), high (10-16), very_high (17-25).
- Medium, high, and very_high risks require a defined mitigation
before the requirement can be baselined; low risks may be logged and
accepted (waived) without one.
- This leaf scopes requirement-level risk analysis only. Broader
technical risk management across the whole project (identification,
analysis, mitigation, residual-risk tracking) is the sibling
e10-risk-mgmt leaf (10C clause 5.6.8).
Workflow
- For each requirement at the level under analysis, score likelihood
and severity (1-5 each) and compute the risk index and risk class.
- Enter the scored requirement into the project risk register with
its description (status: identified).
- If the risk class is medium, high, or very_high, define a
mitigation and record it against the register entry (status:
mitigated). If low, either leave it logged or waive it with a
recorded rationale (status: waived).
- Check the register for the level (or the whole flow-down): every
entry requiring mitigation must be mitigated before the
requirement baseline can proceed.
- Carry residual/open risk forward; do not baseline a requirement
with an open medium-and-above risk.
Pitfalls
- Baselining a requirement while a medium-and-above risk is still
only "identified" (no mitigation recorded) — the gate is skipped.
- Waiving a risk that requires mitigation instead of mitigating it
(waiver is only valid for risks that do not require mitigation).
- Scoring likelihood or severity outside 1-5, or leaving the
description blank so the register entry is not traceable to a
rationale.
- Confusing this leaf's per-requirement risk analysis with the
broader project technical risk management process (identification,
mitigation, residual tracking across the whole project) — see the
sibling e10-risk-mgmt leaf (10C clause 5.6.8).
Behavior contract (gate 3)
The risk-scoring, register-entry, mitigation, and register-readiness
logic is exercised by the gate 3 contract test:
scripts/test_e10_req_risk_analysis.py against
scripts/e10_req_risk_analysis_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_req_risk_analysis.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e10-req-risk-analysis3description: "Use when assessing the technical/requirement risk of a candidate or derived requirement during ECSS-E-ST-10C flow-down: determine likelihood x severity into a risk class, feed the project risk register, and gate baselining on a defined mitigation for medium-and-above risk consistent with M-ST-80. Trigger: ecss, e-st-10c, requirement risk, risk register, risk analysis, technical risk, mitigation, m-st-80, risk index, likelihood severity."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-risk-analysis15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, requirement-risk, risk-register, mitigation, m-st-80, systems-engineering]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Requirement Risk Analysis (space-systems/ecss/e10-req-risk-analysis)2324Use when the task is analysing the technical/requirement risk of a25candidate or derived requirement at a given flow-down level under26ECSS-E-ST-10C clause 5.2.3.3, feeding the project risk register, and27defining mitigation consistent with M-ST-80.2829## Domain quick reference3031- ECSS-E-ST-10C clause 5.2.3.3 requires each level of the requirement32 flow-down (customer TS through every lower-level TS) to analyse the33 technical/requirement risk of its requirements and enter the result34 in the project risk register.35- Risk is scored as likelihood x severity (each 1-5), consistent with36 the ECSS risk-management standard (M-ST-80): risk index bands into37 low (<=4), medium (5-9), high (10-16), very_high (17-25).38- Medium, high, and very_high risks require a defined mitigation39 before the requirement can be baselined; low risks may be logged and40 accepted (waived) without one.41- This leaf scopes requirement-level risk analysis only. Broader42 technical risk management across the whole project (identification,43 analysis, mitigation, residual-risk tracking) is the sibling44 e10-risk-mgmt leaf (10C clause 5.6.8).4546## Workflow47481. For each requirement at the level under analysis, score likelihood49 and severity (1-5 each) and compute the risk index and risk class.502. Enter the scored requirement into the project risk register with51 its description (status: identified).523. If the risk class is medium, high, or very_high, define a53 mitigation and record it against the register entry (status:54 mitigated). If low, either leave it logged or waive it with a55 recorded rationale (status: waived).564. Check the register for the level (or the whole flow-down): every57 entry requiring mitigation must be mitigated before the58 requirement baseline can proceed.595. Carry residual/open risk forward; do not baseline a requirement60 with an open medium-and-above risk.6162## Pitfalls6364- Baselining a requirement while a medium-and-above risk is still65 only "identified" (no mitigation recorded) — the gate is skipped.66- Waiving a risk that requires mitigation instead of mitigating it67 (waiver is only valid for risks that do not require mitigation).68- Scoring likelihood or severity outside 1-5, or leaving the69 description blank so the register entry is not traceable to a70 rationale.71- Confusing this leaf's per-requirement risk analysis with the72 broader project technical risk management process (identification,73 mitigation, residual tracking across the whole project) — see the74 sibling e10-risk-mgmt leaf (10C clause 5.6.8).7576## Behavior contract (gate 3)7778The risk-scoring, register-entry, mitigation, and register-readiness79logic is exercised by the gate 3 contract test:80scripts/test_e10_req_risk_analysis.py against81scripts/e10_req_risk_analysis_logic.py (stdlib unittest, offline). Run:82python3 scripts/test_e10_req_risk_analysis.py8384## Compliance8586- ECSS standards are freely downloadable (ESA); cite the source and87 paraphrase per standards-map.yaml.88- compliance: STANDARDS-REF, gated: false.