View documentation for other releases
Learn more about DO Qualification Kit
• Getting Started with DO Qualification Kit
• User's Guide
• Tool Qualification
Qualification Process
Propose Tool Qualification Plan to Certification Authorities
Document Tool Operational Requirements
Verify That the Tool Satisfies Tool Operational Requirements
Provide Certification Authorities with Tool Qualification Results
• Access and Manage Qualification Artifacts
Access Artifacts Using the Certification Artifacts Explorer
Manage Artifacts Using the Certification Artifacts Explorer
Delete Certification Packages from the Certification Artifacts Explorer
Certification Artifacts Explorer Limitations
• Traceability Matrix Creation
• Generate a Traceability Matrix
• Add Comments to a Traceability Matrix
Traceability Matrix Limitations
• References
Normative References
• Workflows
• Model-Based Design Workflow for DO-178B
• Tool Description
Overview of the Tools
Independence of the Tools
Model and Source Code Development and Verification
Potential Tool Errors and Detection
Object Code Development and Verification
Test Case Development
• DO-178B Software Life Cycle
DO-178B Software Life Cycle Overview
Model-Based Design Workflow in DO-178B
• Planning Process
Software Development and Integral Processes Activities are Defined
Transition Criteria, Inter-Relationships, and Sequencing Among Processes are Defined
Software Life-Cycle Environment Is Defined
Additional Considerations are Addressed
Software Development Standards are Defined
Software Plans Comply with DO-178B
Software Plans are Coordinated
• Software Development Process
High-Level Requirements are Developed
Derived High-Level Requirements are Developed
Software Architecture Is Developed
Low-Level Requirements are Developed
Derived Low-Level Requirements are Developed
Source Code Is Developed
Executable Object Code Is Produced and Integrated in the Target Computer
• Verification of Requirements Process
Software High-Level Requirements Comply with System Requirements
High-Level Requirements Are Accurate and Consistent
High-Level Requirements Are Compatible with the Target Computer
High-Level Requirements Are Verifiable
High-Level Requirements Conform to Standards
High-Level Requirements Are Traceable to System Requirements
Algorithms Are Accurate
• Verification of Design Process
Low-Level Requirements Comply with High-Level Requirements
Low-Level Requirements Are Accurate and Consistent
Low-Level Requirements Are Compatible with the Target Computer
Low-Level Requirements Are Verifiable
Low-Level Requirements Conform to Standards
Low-Level Requirements Are Traceable to High-Level Requirements
Software Architecture Is Compatible with High-Level Requirements
Software Architecture Is Consistent
Software Architecture Is Compatible with the Target Computer
Software Architecture Is Verifiable
Software Architecture Conforms to Standards
Software Partitioning Integrity Is Confirmed
• Verification of Coding and Integration Process
Source Code Complies with Low-Level Requirements
Source Code Complies with Software Architecture
Source Code Is Verifiable
Source Code Conforms to Standards
Source Code Is Traceable to Low-Level Requirements
Source Code Is Accurate and Consistent
Output of Software Integration Process Is Complete and Correct
• Testing of Outputs of Integration Process
Executable Object Code Complies with High-Level Requirements
Executable Object Code Is Robust with High-Level Requirements
Executable Object Code Complies with Low-Level Requirements
Executable Object Code Is Robust with Low-Level Requirements
Executable Object Code Is Compatible with Target Computer
• Verification of Verification Process Results
Test Procedures Are Correct
Test Results Are Correct and Discrepancies Explained
Test Coverage of High-Level Requirements Is Achieved
Test Coverage of Low-Level Requirements Is Achieved
Test Coverage of Software Structure (Modified Condition/Decision) Is Achieved
Test Coverage of Software Structure (Decision Coverage) Is Achieved
Test Coverage of Software Structure (Statement Coverage) Is Achieved
Test Coverage of Software Structure (Data Coupling and Control) Is Achieved
• Software Configuration Management Process
Configuration Items Are Identified
Baselines and Traceability Are Established
Problem Reporting, Change Control, Change Review, and Configuration Status Accounting Are Established
Archive, Retrieval, and Release Are Established
Software Load Control Is Established
Software Life Cycle Environment Control Is Established
• Software Quality Assurance Process
Assurance Is Obtained That Software Development and Integral Processes Comply with Approved Software Plans and Standards
Assurance Is Obtained That Transition Criteria for the Software Life Cycle Processes are Satisfied
Software Conformity Review Is Completed
• Certification Liaison Process
Communication and Understanding Between the Applicant and the Certification Authority Is Established
The Means of Compliance Is Proposed and Agreement with the Plan for Software Aspects of Certification is Obtained
Compliance Substantiation Is Provided
• Acronyms
Acronyms
• Functions
• Release Notes
Symbols A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
By Category
Alphabetical List