ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
ECSS system engineering general requirements for European space projects (2009 edition): the system engineering plan, requirement engineering and traceability, analyses and trade-offs, design, budgets and configuration, product verification, integration and control of the technical effort, and the activities and reviews of each project phase.
ECSS-E-ST-10C System Engineering General Requirements (2009 edition) is a compliance framework from Europe (ESA member states and the European space industry) with 7 domains and 41 controls. The largest domains are Clause 5.2: Requirement engineering – ECSS-E-ST-10C System Engineering General Requirements (2009 edition) (11 controls), Clause 5.6: System engineering integration and control – ECSS-E-ST-10C System Engineering General Requirements (2009 edition) (9 controls), Clause 6: System engineering activities by project phase – ECSS-E-ST-10C System Engineering General Requirements (2009 edition) (8 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (7)
Clause 5.1: System engineering plan – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.1 | Produce and maintain a system engineering plan |
Clause 5.2: Requirement engineering – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.1 | Analyse customer requirements and derive controlled lower-level requirements |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.2 | Keep forward and backward traceability of every requirement |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.1 | Establish consistent technical requirements specifications and a specification tree |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.2 | Consolidate incomplete, ambiguous or contradictory requirements at the start of each phase |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.3 | Identify the requirements that drive system risk |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.4 | Assign verification methods to every requirement and record them in the verification matrix |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.5 | Allocate system requirements and their verification methods to lower levels |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.6 | Verify that requirements are consistent and non-redundant across levels |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.7 | Validate requirements against the expressed needs with the customer in phase 0 |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.8 | Maintain the requirements through to the end of phase F |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.2.3.9 | Define the documents that form the requirements baseline |
Clause 5.3: Analysis – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.3.1 | Perform mission, functional, physical, performance and cost analyses and document them |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.3.2 | Establish environments, qualification and acceptance criteria, factors and margins |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.3.3 | Conduct trade-off analyses and report them |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.3.4 | Define, validate and maintain analysis methods, tools and models |
Clause 5.4: Design and configuration – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.1.1 | Establish a whole-life system design from architecture, allocation and technology |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.1.2 | Define, apportion and control technical budgets under the margin policy |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.1.3 | Define, validate and maintain design methods, tools and models with an agreed coordinate system |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.1.4 | Maintain the design definition file, the design justification file and the user manual |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.2.1 | Define the complete configuration at every level and document it |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.2.2 | Establish configuration baselines at defined milestones |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.4.2.3 | Define and document the hierarchy and assembly sequence |
Clause 5.5: Verification – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.5 | Verify the complete product on its defined architecture per ECSS-E-ST-10-02 |
Clause 5.6: System engineering integration and control – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.1 | Define, plan and manage the integrated technical effort |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.2 | Keep the system engineering plan aligned with the project schedule |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.3 | Define the engineering data repository and electronic exchange interfaces |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.4 | Control external and internal interfaces through specifications and interface control documents |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.5 | Define the coordinate systems and the units system |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.6 | Control the technical budgets and define the margin policy |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.7 | Identify, assess and plan candidate technologies |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.8 | Contribute engineering data and controls to risk management |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::5.6.9 | Assess every change proposal and nonconformance technically and control agreed actions |
Clause 6: System engineering activities by project phase – ECSS-E-ST-10C System Engineering General Requirements (2009 edition)
| Code | Title |
|---|---|
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.2 | Plan and monitor system engineering activities by project phase and identify critical elements |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.3 | Phase 0: support need identification and propose system concepts |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.4 | Phase A: finalise the needs and propose solutions with their risks |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.5 | Phase B: establish the preliminary definition and demonstrate it meets the requirements |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.6 | Phase C: establish the detailed definition and demonstrate the capability to meet the specification |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.7 | Phase D: complete qualification and acceptance and prepare for operations |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.8 | Phase E: support the launch campaign, operations and anomaly resolution |
| ecss-e-st-10c-system-engineering-general-requirements-2009-edition::6.9 | Phase F: support disposal and the Mission Close-out Review |
What is ECSS-E-ST-10C System Engineering General Requirements (2009 edition) and who does it apply to?
ECSS-E-ST-10C System Engineering General Requirements (2009 edition) is a compliance framework from Europe (ESA member states and the European space industry) with 7 domains and 41 controls. ECSS system engineering general requirements for European space projects (2009 edition): the system engineering plan, requirement engineering and traceability, analyses and trade-offs, design, budgets and configuration, product verification, integration and control of the technical effort, and the activities and reviews of each project phase. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does ECSS-E-ST-10C System Engineering General Requirements (2009 edition) actually require?
ECSS-E-ST-10C System Engineering General Requirements (2009 edition) has 41 controls organised across 7 domains. The largest domains are Clause 5.2: Requirement engineering – ECSS-E-ST-10C System Engineering General Requirements (2009 edition) (11 controls), Clause 5.6: System engineering integration and control – ECSS-E-ST-10C System Engineering General Requirements (2009 edition) (9 controls), Clause 6: System engineering activities by project phase – ECSS-E-ST-10C System Engineering General Requirements (2009 edition) (8 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of ECSS-E-ST-10C System Engineering General Requirements (2009 edition) do I already cover?
ECSS-E-ST-10C System Engineering General Requirements (2009 edition) does not currently have cross-framework mappings in our system. Check back as we continuously expand our mapping database.
How do I implement ECSS-E-ST-10C System Engineering General Requirements (2009 edition)?
Start your ECSS-E-ST-10C System Engineering General Requirements (2009 edition) compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about ECSS-E-ST-10C System Engineering General Requirements (2009 edition) requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 41 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,248 frameworks.
Get Started Free →Free forever, no credit card required