Visure Solutions

Start Free Trial

DO-178A Standard Guide: Software Verification Tools

DO-178A Standard Guide: Software Verification Tools

Table of Contents


Aviation software plays a critical role in ensuring the safety and efficiency of aircraft operations. As software complexity continues to increase, the need for robust verification processes becomes paramount. The DO-178A standard, developed by the Radio Technical Commission for Aeronautics (RTCA), provides guidelines for the certification of software used in airborne systems. This article focuses specifically on the use of software verification tools within the DO-178A framework to achieve compliance and enhance software safety.

Understanding DO-178A and its Importance

The DO-178A Standard Overview

The DO-178A standard, formally titled “Software Considerations in Airborne Systems and Equipment Certification,” was first published in 1985. Its primary objective is to establish a uniform set of guidelines for the development and certification of airborne software systems. Compliance with DO-178A is mandatory for software used in commercial, military, and general aviation applications.

Importance of DO-178A Compliance

DO-178A compliance is crucial for the aviation industry as it ensures that software meets stringent safety and reliability requirements. By adhering to the standard, developers can minimize the risk of software-related failures, which can have catastrophic consequences. Compliance with DO-178A also fosters trust among regulatory bodies, airlines, and passengers, ensuring the highest levels of safety and reliability in aviation software.

Levels of DO-178A

Levels of DO-178A

DO-178A specifies three software levels: Level 1, Level 2, and Level 3. Level 1 represents the highest level of criticality, while Level 3 represents the lowest.

Level 1

Level 1 is the most rigorous and demanding level in terms of certification requirements. Software functions assigned to Level 1 have the highest criticality, and failure of these functions could result in catastrophic consequences, including loss of life and the aircraft itself. Examples of Level 1 software include flight controls and vital avionics systems.

Requirements and Documentation:

  • Complete and Unambiguous Requirements: Level 1 software must have complete and unambiguous requirements that are derived from system-level safety objectives.
  • Extensive Documentation: The certification authority requires a comprehensive set of documents for Level 1 software. This includes software development plans, configuration management plans, software requirements documents, software design documents, software verification plans, and more.
  • Formal Methods and Verification: Level 1 software requires the use of formal methods, formal verification techniques, and extensive testing to ensure the highest level of reliability and safety.

Level 2

Level 2 is assigned to software functions with a lower criticality level compared to Level 1. Failure of Level 2 functions may cause significant damage to the aircraft or systems, but the consequences are not considered catastrophic. Examples of Level 2 software include engine control systems and critical navigation functions.

Requirements and Documentation:

  • Well-Defined Requirements: Level 2 software must have well-defined requirements that are traceable to system-level safety objectives.
  • Controlled Development Process: The software development process at Level 2 should be well-controlled, with an emphasis on configuration management, documentation, and testing.
  • Comprehensive Verification: Verification activities for Level 2 software must cover a wide range of aspects, including functional testing, structural coverage analysis, and fault tolerance analysis.

Level 3

Level 3 represents the lowest criticality level in DO-178A. Software functions assigned to Level 3 have a minor impact on aircraft operation if they were to fail. The consequences of failure are generally limited to minor system disruptions. Examples of Level 3 software include passenger entertainment systems and non-critical monitoring functions.

Requirements and Documentation:

  • Defined Requirements: Level 3 software must have defined requirements that address system-level safety objectives.
  • Simplified Development Process: The software development process at Level 3 is simplified compared to Levels 1 and 2, with reduced documentation and testing requirements.
  • Basic Verification: Verification activities at Level 3 focus on demonstrating compliance with requirements and performing basic functional testing.

In summary, DO-178A specifies three software levels (Level 1, Level 2, and Level 3), with Level 1 being the most rigorous and requiring a comprehensive set of documents to be generated and made available to the certification authority. The criticality of the software functions determines the level assigned and influences the depth and rigor of the development and verification activities required for compliance with the DO-178A standard.

Software Verification in DO-178A

Verification Objectives

Software verification, a key aspect of DO-178A, aims to demonstrate that the developed software meets its specified requirements and operates reliably in the intended environment. Verification activities include the analysis, testing, and inspection of software artifacts throughout the development lifecycle.

Role of Software Verification Tools

Software verification tools are invaluable in achieving the objectives of DO-178A. These tools automate various verification activities, reducing the potential for human error and enhancing overall efficiency. They assist in code analysis, test case generation, and requirements traceability, thereby streamlining the verification process and improving software quality.

Types of Software Verification Tools

Static Analysis Tools

Static analysis tools analyze source code or executable binaries without executing them. They identify potential defects, coding rule violations, and other issues by examining the code structure, complexity, and compliance with coding standards. These tools assist in detecting common software errors, such as buffer overflows, null pointer dereferences, and uninitialized variables.

Dynamic Analysis Tools

Dynamic analysis tools execute software and monitor its behavior during runtime. They collect runtime information, such as variable values, function calls, and memory usage, allowing developers to identify defects, memory leaks, and performance bottlenecks. Dynamic analysis tools also facilitate the creation of test cases that exercise specific program paths, ensuring thorough test coverage.

Model-Based Testing Tools

Model-based testing tools utilize formal models, such as finite state machines or state charts, to generate test cases automatically. These tools provide a systematic approach to software testing by deriving test cases from the model, ensuring comprehensive coverage of all possible system behaviors. Model-based testing tools help identify corner cases, validate complex system interactions, and improve overall test efficiency.

Requirements Traceability Tools

Requirements traceability tools establish and maintain links between software requirements, design artifacts, and verification activities. These tools enable the mapping of requirements to specific test cases, ensuring that all requirements are adequately verified. Requirements traceability tools assist in compliance documentation and facilitate regulatory audits.

DO 178c Tool Qualification

Benefits and Challenges of Software Verification Tools

Benefits of Software Verification Tools

  • Increased Efficiency: Automation of verification activities reduces manual effort, accelerates the verification process, and improves productivity.
  • Enhanced Accuracy: Software verification tools can detect defects and vulnerabilities that might be missed during manual inspection or testing.
  • Improved Software Quality: The consistent application of verification tools helps identify and eliminate software errors, leading to higher-quality software.
  • Compliance Documentation: Verification tools generate reports and documentation that aid in demonstrating compliance with DO-178A requirements.

Challenges of Software Verification Tools

  • Tool Qualification: Verification tools used in DO-178A projects must be qualified to ensure their reliability and suitability for the intended purpose. Tool qualification can be a complex process, requiring additional effort and documentation.
  • Cost Considerations: Acquiring and maintaining software verification tools can involve significant costs. Organizations must carefully evaluate the benefits and cost-effectiveness of using these tools based on project requirements and constraints.
  • Tool Integration: Integrating software verification tools into existing development environments and workflows may present technical challenges, requiring coordination and expertise.


Compliance with the DO-178A standard is critical for the development and certification of safe and reliable aviation software. Software verification tools play a vital role in achieving DO-178A compliance by automating various verification activities, improving efficiency, and enhancing software quality. By leveraging static analysis, dynamic analysis, model-based testing, and requirements traceability tools, developers can ensure that their software meets stringent safety and reliability requirements. The use of these tools not only aids in complying with DO-178A but also enhances the overall development process, resulting in software that meets the highest standards of safety in the aviation industry.

Don’t forget to share this post!


The High Cost of Poor Requirements Management

June 06th, 2024

11 am EST | 5 pm CET | 8 am PST

Louis Arduin

Louis Arduin

Main Speaker

Impact & Solutions for Inefficient Requirements Management

Explore the significant impact that inefficient requirements management practices can have on project costs and timelines.