ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software)
The European Cooperation for Space Standardisation (ECSS) provides two complementary standards for space software: ECSS‑E‑ST‑40C (Space engineering - Software) defines the software engineering lifecycle, processes, and product development requirements; ECSS‑Q‑ST‑80C (Product assurance - Software) specifies product‑assurance requirements, verification, validation, and safety considerations for software used in space missions. Together they cover requirements definition, design, implementation, testing, configuration management, quality assurance, and release for space‑flight software.
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 (25)
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 |
Assurance
| Code | Title |
|---|---|
| ECSS.Q80.7 | Software Reviews and Audits |
Configuration
| Code | Title |
|---|---|
| ECSS.Q80.5 | Software Configuration Management |
Delivery
| Code | Title |
|---|---|
| ECSS.E40.10 | Software Delivery and Acceptance |
Design
| Code | Title |
|---|---|
| ECSS.E40.4 | Software Architectural Design |
| ECSS.E40.5 | Software Detailed Design and Implementation |
Metrics
| Code | Title |
|---|---|
| ECSS.Q80.9 | Software Metrics and Process Improvement |
Operations
| Code | Title |
|---|---|
| ECSS.E40.11 | Software Operations and Maintenance |
Process
| Code | Title |
|---|---|
| ECSS.E40.1 | Software Engineering Process Definition |
Product Assurance
| Code | Title |
|---|---|
| ECSS.Q80.1 | Software Product Assurance Programme |
Quality
| Code | Title |
|---|---|
| ECSS.Q80.6 | Software Problem Reporting and Corrective Action |
Requirements
| Code | Title |
|---|---|
| ECSS.E40.2 | Software System Requirements Analysis |
| ECSS.E40.3 | Software Requirements Specification |
Reuse
| Code | Title |
|---|---|
| ECSS.Q80.4 | Software Reuse Justification |
Risk
| Code | Title |
|---|---|
| ECSS.Q80.2 | Software Criticality Classification |
Safety
| Code | Title |
|---|---|
| ECSS.Q80.3 | Software Dependability and Safety Analyses |
Security
| Code | Title |
|---|---|
| ECSS.Q80.8 | Cybersecurity in Software Product Assurance |
Tools
| Code | Title |
|---|---|
| ECSS.E40.12 | Tool Qualification |
Validation
| Code | Title |
|---|---|
| ECSS.E40.8 | Software Validation |
Verification
| Code | Title |
|---|---|
| ECSS.E40.6 | Software Unit Testing |
| ECSS.E40.7 | Software Integration and Integration Testing |
| ECSS.E40.9 | Software Verification |
Your Compliance Coverage
If you comply with ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software), you already cover:
HKMA Cyber Resilience Assessment Framework (C-RAF)
9%
5 controls mapped
Compare →NIS2 Directive
9%
5 controls mapped
Compare →DORA
9%
5 controls mapped
Compare →+ 455 more: ECSS-E-ST-40C: Space Engineering - Software (9%), CAIQ (CSA) (9%)
See all 458 mapped frameworks ↓Maps to 458 other frameworks
Frequently Asked Questions
What is ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software)?
ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) is a compliance framework from Europe (European Space Agency (ESA) and member states) with 25 domains and 54 controls. The European Cooperation for Space Standardisation (ECSS) provides two complementary standards for space software: ECSS‑E‑ST‑40C (Space engineering - Software) defines the software engineering lifecycle, processes, and product development requirements; ECSS‑Q‑ST‑80C (Product assurance - Software) specifies product‑assurance requirements, verification, validation, and safety considerations for software used in space missions. Together they cover requirements definition, design, implementation, testing, configuration management, quality assurance, and release for space‑flight software. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) have?
ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) has 54 controls organised across 25 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‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) map to?
ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) maps to 458 other compliance frameworks. The top mapping partners are HKMA Cyber Resilience Assessment Framework (C-RAF) (9% coverage), NIS2 Directive (9% coverage), DORA (9% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) compliance?
Start your ECSS‑E‑ST‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) 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‑40C (Space engineering - Software) and ECSS‑Q‑ST‑80C (Product assurance - Software) 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 54 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 768 frameworks.
Get Started Free →Free forever — no credit card required