ECSS Software Engineering Standards
The European Cooperation for Space Standardisation (ECSS) software engineering standards, including ECSS-E-ST-40C and ECSS-Q-ST-80C, define requirements for space software development processes and product assurance. ECSS-E-ST-40C covers the software engineering lifecycle, while ECSS-Q-ST-80C addresses software product assurance. These standards are used by the European Space Agency (ESA) and the European space industry.
Framework summaries on this platform are AI-assisted interpretations 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 (8)
5.2 Software-Related System Requirements
| Code | Title |
|---|---|
| ECSS-5.2.1 | System Requirements Analysis |
| ECSS-5.2.2 | Software Item Identification |
| ECSS-5.2.3 | System Requirements Review (SRR) |
| ECSS-E-40C-5.2.1 | System Requirements Analysis |
| ECSS-E-40C-5.2.2 | Software Item Identification |
5.3 Software Management
| Code | Title |
|---|---|
| ECSS-5.3.1 | Software Project Planning |
| ECSS-5.3.2 | Software Configuration Management |
| ECSS-5.3.3 | Review Milestones |
| ECSS-5.3.4 | Software Criticality Classification |
| ECSS-E-40C-5.3.1 | Project Planning |
| ECSS-E-40C-5.3.2 | Configuration Management |
| ECSS-E-40C-5.3.3 | Criticality Classification |
5.4 Software Requirements and Architecture
| Code | Title |
|---|---|
| ECSS-5.4.1 | Software Requirements Specification |
| ECSS-5.4.2 | Software Architecture Design |
| ECSS-5.4.3 | Preliminary Design Review (PDR) |
5.5 Software Design and Implementation
| Code | Title |
|---|---|
| ECSS-5.5.1 | Detailed Design |
| ECSS-5.5.2 | Software Coding |
| ECSS-5.5.3 | Unit Testing |
| ECSS-5.5.4 | Critical Design Review (CDR) |
5.6 Software Validation
| Code | Title |
|---|---|
| ECSS-5.6.1 | Software Validation Plan |
| ECSS-5.6.2 | Validation Against Technical Specification |
| ECSS-5.6.3 | Validation Against Requirements Baseline |
5.7 Software Delivery and Acceptance
| Code | Title |
|---|---|
| ECSS-5.7.1 | Software Delivery |
| ECSS-5.7.2 | Acceptance Review (AR) |
| ECSS-5.7.3 | Test Readiness Review (TRR) |
5.8 Software Verification
| Code | Title |
|---|---|
| ECSS-5.8.1 | Verification Planning |
| ECSS-5.8.2 | Requirements Verification |
| ECSS-5.8.3 | Integration Testing |
5.9-5.10 Operations and Maintenance
| Code | Title |
|---|---|
| ECSS-5.10.1 | Software Maintenance |
| ECSS-5.10.2 | Problem Reporting and Resolution |
| ECSS-5.9.1 | Software Operation |
| ECSS-E-40C-5.10.1 | Maintenance |
| ECSS-E-40C-5.9.1 | Operations Support |
Your Compliance Coverage
If you comply with ECSS Software Engineering Standards, you already cover:
HKMA Cyber Resilience Assessment Framework (C-RAF)
15%
5 controls mapped
Compare →ECSS-E-ST-40C: Space Engineering — Software
15%
5 controls mapped
Compare →CAIQ (CSA)
15%
5 controls mapped
Compare →+ 432 more: OWASP DevSecOps Maturity Model (DSOMM) (15%), ISO/IEC 27400:2022 (15%)
See all 435 mapped frameworks ↓Maps to 435 other frameworks
Frequently Asked Questions
What is ECSS Software Engineering Standards?
ECSS Software Engineering Standards is a compliance framework from Europe (ESA-led, multinational participation) with 8 domains and 33 controls. The European Cooperation for Space Standardisation (ECSS) software engineering standards, including ECSS-E-ST-40C and ECSS-Q-ST-80C, define requirements for space software development processes and product assurance. ECSS-E-ST-40C covers the software engineering lifecycle, while ECSS-Q-ST-80C addresses software product assurance. These standards are used by the European Space Agency (ESA) and the European space industry. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does ECSS Software Engineering Standards have?
ECSS Software Engineering Standards has 33 controls organised across 8 domains. The largest domains are 5.3 Software Management (7 controls), 5.2 Software-Related System Requirements (5 controls), 5.9-5.10 Operations and Maintenance (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does ECSS Software Engineering Standards map to?
ECSS Software Engineering Standards maps to 435 other compliance frameworks. The top mapping partners are HKMA Cyber Resilience Assessment Framework (C-RAF) (15% coverage), ECSS-E-ST-40C: Space Engineering — Software (15% coverage), CAIQ (CSA) (15% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with ECSS Software Engineering Standards compliance?
Start your ECSS Software Engineering Standards 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 Software Engineering Standards 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 33 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 693 frameworks.
Get Started Free →Free forever — no credit card required