In the ever-evolving world of
aviation, where safety is paramount, the role of software in airborne systems
cannot be overstated. Ensuring that the software in aircraft and related
equipment operates with absolute reliability and safety is a monumental challenge.
It is precisely this challenge that the DO-178C standard, also known as
“Software Considerations in Airborne Systems and Equipment Certification,”
seeks to address. Representing the latest evolution in a series of standards,
DO-178C provides a comprehensive framework for the development, certification,
and maintenance of safety-critical software in the aerospace industry
Software development process in DO-178C
The software development process
in DO-178C is a crucial component of the standard, as it provides a systematic
approach to developing safety-critical software for use in airborne systems.
The process follows a structured and rigorous methodology to ensure the
airworthiness and safety of the software. Here are the key steps and activities
involved in the software development process of DO-178C:
1. Planning
(Software Development Plan – SDP):
The process begins with the creation of a Software
Development Plan (SDP). The SDP outlines the overall approach to software
development, including objectives, criticality levels, and development and
verification strategies. It defines the scope of the software development
effort and serves as a roadmap for the project.
2. Requirements
Analysis (Software Requirements – SRD):
In this phase, software engineers analyze and
establish software requirements based on system-level requirements and safety
objectives. These requirements are documented in the Software Requirements Data
(SRD) and serve as the foundation for subsequent design and development
activities.
3. High-Level
Design (Software Design Description – SDD):
The high-level design phase involves creating a
Software Design Description (SDD) that defines the overall architecture and
structure of the software. It identifies software components, interfaces, and
data flows. The SDD ensures that the software design aligns with the specified
requirements.
4. Low-Level
Design (Software Design Description – SDD):
Building upon the high-level design, software
engineers create detailed Low-Level Design (LLD) documentation. The LLD
specifies how each software component is implemented, including algorithms,
data structures, and coding standards.
5. Implementation
(Source Code):
In this phase, developers write the actual source
code for the software. The code must adhere to the Low-Level Design (LLD)
documentation and coding standards. Comprehensive documentation of the code is
essential for traceability.
6. Verification
and Testing:
Verification activities include unit testing,
integration testing, and system testing. These tests are designed to verify
that the software components operate as intended and meet their specified
requirements. Test cases are developed based on the Software Verification Plan
(SVP).
7. Traceability:
Throughout the development process, traceability
ensures that every requirement, design element, and line of code is traceable
back to specific software and system requirements. This ensures consistency and
alignment with higher-level objectives.
8. Documentation:
Comprehensive documentation is a fundamental
requirement in DO-178C. Each phase of development, including requirements,
design, code, and testing, requires detailed documentation. This documentation
is essential for certification and auditing purposes.
9. Configuration
Management:
Software Configuration Management (SCM) processes are
employed to control and manage changes to software configuration items (SCIs)
throughout the development lifecycle. This ensures version control and
traceability of changes.
10. Change
Control:
Changes to software requirements, design, or code
must be carefully controlled and documented. The impact of changes on safety
and certification objectives is assessed, and appropriate actions are taken to
maintain airworthiness.
11. Tool
Qualification:
If software development tools are used, they must
undergo a tool qualification process to ensure their reliability and
suitability for the development process.
12. Safety
Assessment:
A safety assessment is performed to evaluate the
software’s safety-critical aspects, including potential hazards, risk
mitigation measures, and safety objectives. This assessment informs safety
certification efforts.
13. Certification:
The final step in the process is the certification of
the software by the appropriate certification authority (CA), such as the
Federal Aviation Administration (FAA) in the United States or the European
Union Aviation Safety Agency (EASA) in Europe. The CA reviews all
documentation, test results, and safety assessments to determine if the
software is airworthy and safe for use in airborne systems.
Verification and Validation in DO-178C
Verification and validation
(V&V) are critical processes in DO-178C (Software Considerations in
Airborne Systems and Equipment Certification) that ensure the safety and
airworthiness of software used in airborne systems, including aircraft and
related equipment. These processes are designed to confirm that the software
performs its intended functions correctly and reliably. Here’s an explanation
of verification and validation in DO-178C:
Verification:
Verification in DO-178C focuses
on confirming that the software has been correctly developed. It involves
checking whether the software has been designed, coded, and integrated in
accordance with the specified requirements and standards. The primary goal of
verification is to ensure that each software component meets its intended
functionality, is free from defects, and operates as expected. Key aspects of
verification in DO-178C include:
1. Unit
Testing: Developers perform unit testing to
validate individual software components (such as modules or functions) in
isolation. This ensures that each component operates correctly and
conforms to the design and requirements.
2. Integration
Testing: Integration testing involves
verifying the interactions between software components and their
interfaces. It ensures that integrated components work together seamlessly
and meet their specified functions.
3. System
Testing: System testing evaluates the entire
software system in its operational environment. It assesses the system’s
behavior under various conditions and scenarios, including both normal and
abnormal situations.
4. Requirements
Traceability: Verification activities
should be traceable to the software requirements. This means that each
test case or verification activity should be linked back to specific
software requirements, ensuring that all requirements are verified.
5. Structural
Coverage Analysis: DO-178C
mandates structural coverage analysis, which assesses the completeness of
testing by measuring code coverage (e.g., statement coverage, branch
coverage). High levels of code coverage are required for critical
software.
6. Code
Reviews and Inspections: Formal
code reviews and inspections are conducted to identify defects and ensure
that coding standards and guidelines are followed.
7. Documentation: Comprehensive
documentation of verification activities, test cases, results, and
traceability is essential for demonstrating compliance with DO-178C
requirements.
Validation:
Validation in DO-178C focuses on
confirming that the software meets its intended functionality and performance
objectives within the context of the entire aircraft system. It ensures that
the software operates correctly when integrated into the aircraft and interacts
with other system components. Key aspects of validation in DO-178C include:
1. System
Integration Testing: Validation
activities involve testing the software within the aircraft’s integrated
environment, considering the interaction between software and hardware
components, as well as external factors.
2. Real-World
Scenarios: Validation testing includes
real-world scenarios, such as flight simulations, to assess the software’s
behavior under actual operating conditions.
3. Safety
Assessment: A safety assessment is performed as
part of the validation process to evaluate potential hazards and risks
associated with the software. Mitigation measures are identified and
implemented to ensure safety.
4. Environmental
Testing: Validation may include environmental
testing to assess how the software performs under extreme conditions, such
as temperature variations, electromagnetic interference, and vibration.
5. Performance
Testing: Validation verifies that the
software meets its performance requirements, such as response times,
throughput, and data accuracy.
6. User
Acceptance Testing: In
some cases, user acceptance testing involves feedback from pilots,
operators, or other end-users to validate that the software meets their
needs and expectations.
Both verification and validation
are essential for ensuring that software in airborne systems is safe, reliable,
and compliant with DO-178C standards. These processes contribute to the overall
airworthiness of the aircraft and help mitigate risks associated with software
failures in critical aviation applications.
This Blog Part taken from Visure Blog "DO-178C Risk Management for Airborne Systems and Equipment"
