DO-178 is the de facto international safety standard used to certify commercial avionic system software; it is increasingly used in other sectors and applications. DO-278 is derived from DO-178 and used for ground-based and space-based software. DO-178C and DO-278A are the current versions. They were published in December 2011 along with supplemental documents that extend or modify DO-178 and DO-278 guidance for software processes that employ specific technologies or techniques.
The supplemental documents are:
DO-178C, Section 12.2, states that qualification of a tool is only needed if its output is not verified. It then defines tool qualification levels (TQLs) based on the tool’s impact on software life-cycle processes. DO-178C references DO-330 for tool qualification details such as the objectives, guidance, and life-cycle data required for each TQL.
DO Qualification Kit supports DO-178C and DO-330. It also provides workflow guidance, traceability matrix generation, and other artifacts that facilitate your use of Simulink® and Polyspace® software tools for supplements including DO-331 and DO-333.
The tool user (not the tool vendor) is responsible for this qualification, and tool qualification must be done for each certification project.
DO Qualification Kit implements the tool qualification approach specified in DO-178C. To use DO Qualification Kit, follow these steps:
You need to execute the test cases and procedures from DO Qualification Kit in your MATLAB® or Polyspace installation environment. You should then compare your generated test results with the expected results from the kit and work to eliminate any differences. Simulink Report Generator™ is required for qualifying Simulink Check™, Simulink Coverage™, Simulink Code Inspector™ and Simulink Test™.
Note: Use of DO-178 qualified tools does not ensure the safety of the software or the system under consideration.
DO Qualification Kit provides detailed workflow guidance needed for developing and verifying systems using Model-Based Design. The workflow guidance describes process, methods, and tools used for each software development and verification step from high-level requirements validation to executable object code verification. It clearly identifies tool independence paths. New concepts for Model-Based Design introduced in DO-331 are explained and illustrated, including the role of simulation test cases and model coverage.
With DO Qualification Kit, you can generate a traceability matrix spreadsheet showing requirements-to-model-to-code bidirectional traceability paths and file information. You can also use DO Qualification Kit to generate a list of reported bugs that you can store and archive for key Simulink and Polyspace verification tools used for Model-Based Design.