Europe (ESA member states and the European space industry)

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

44 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

44 controls 0 frameworks share controls with it Europe (ESA member states and the European space industry) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1-4Scope, terms, and the system engineering discipline and process0
5.1Produce and maintain a system engineering plan0
5.2.1Analyse customer requirements and derive controlled lower-level requirements0
5.2.2Keep forward and backward traceability of every requirement0
5.2.3.1Establish consistent technical requirements specifications and a specification tree0
5.2.3.2Consolidate incomplete, ambiguous or contradictory requirements at the start of each phase0
5.2.3.3Identify the requirements that drive system risk0
5.2.3.4Assign verification methods to every requirement and record them in the verification matrix0
5.2.3.5Allocate system requirements and their verification methods to lower levels0
5.2.3.6Verify that requirements are consistent and non-redundant across levels0
5.2.3.7Validate requirements against the expressed needs with the customer in phase 00
5.2.3.8Maintain the requirements through to the end of phase F0
5.2.3.9Define the documents that form the requirements baseline0
5.3.1Perform mission, functional, physical, performance and cost analyses and document them0
5.3.2Establish environments, qualification and acceptance criteria, factors and margins0
5.3.3Conduct trade-off analyses and report them0
5.3.4Define, validate and maintain analysis methods, tools and models0
5.4.1.1Establish a whole-life system design from architecture, allocation and technology0
5.4.1.2Define, apportion and control technical budgets under the margin policy0
5.4.1.3Define, validate and maintain design methods, tools and models with an agreed coordinate system0
5.4.1.4Maintain the design definition file, the design justification file and the user manual0
5.4.2.1Define the complete configuration at every level and document it0
5.4.2.2Establish configuration baselines at defined milestones0
5.4.2.3Define and document the hierarchy and assembly sequence0
5.5Verify the complete product on its defined architecture per ECSS-E-ST-10-020
5.6.1Define, plan and manage the integrated technical effort0
5.6.2Keep the system engineering plan aligned with the project schedule0
5.6.3Define the engineering data repository and electronic exchange interfaces0
5.6.4Control external and internal interfaces through specifications and interface control documents0
5.6.5Define the coordinate systems and the units system0
5.6.6Control the technical budgets and define the margin policy0
5.6.7Identify, assess and plan candidate technologies0
5.6.8Contribute engineering data and controls to risk management0
5.6.9Assess every change proposal and nonconformance technically and control agreed actions0
6.1Overview of the phase model0
6.2Plan and monitor system engineering activities by project phase and identify critical elements0
6.3Phase 0: support need identification and propose system concepts0
6.4Phase A: finalise the needs and propose solutions with their risks0
6.5Phase B: establish the preliminary definition and demonstrate it meets the requirements0
6.6Phase C: establish the detailed definition and demonstrate the capability to meet the specification0
6.7Phase D: complete qualification and acceptance and prepare for operations0
6.8Phase E: support the launch campaign, operations and anomaly resolution0
6.9Phase F: support disposal and the Mission Close-out Review0
ADocument requirements definitions0

Tell me when ECSS-E-ST-10C System Engineering General Requirements (2009 edition) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for ECSS-E-ST-10C System Engineering General Requirements (2009 edition), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition