ECSS-E-ST-10C System Engineering General Requirements (2009 edition)

Clause 5.2: Requirement engineering – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)

ECSS-E-ST-10C System Engineering General Requirements (2009 edition) 5.2.3.3: Identify the requirements that drive system risk

What does 5.2.3.3 require?

The team responsible for system engineering singles out the requirements that bear strongly on system risk and takes the requirements analysis deep enough to expose the elements behind those risks.

Maintained by Gerard Blokdyk

Other controls in Clause 5.2: Requirement engineering – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)

5.2.1 Analyse customer requirements and derive controlled lower-level requirements
5.2.2 Keep forward and backward traceability of every requirement
5.2.3.1 Establish consistent technical requirements specifications and a specification tree
5.2.3.2 Consolidate incomplete, ambiguous or contradictory requirements at the start of each phase
5.2.3.4 Assign verification methods to every requirement and record them in the verification matrix
5.2.3.5 Allocate system requirements and their verification methods to lower levels
5.2.3.6 Verify that requirements are consistent and non-redundant across levels
5.2.3.7 Validate requirements against the expressed needs with the customer in phase 0

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpoint All ECSS-E-ST-10C System Engineering General Requirements (2009 edition) controls