비디오 및 웨비나

Using Qualified Tools in a DO-178C Development Process, Part 1: Introduction to Model-Based Development for DO-178C

From the series: Using Qualified Tools in a DO-178C Development Process

Bill Potter, MathWorks

This is an introduction to the use of Model-Based Design and formal methods in a process compliant with DO-178C, DO-331, DO-333, and DO-330. MathWorks tools may be used in both the development and verification phases of a DO-178C project. While MathWorks tools support a broad range of capabilities for both systems and software, there are recommended limited subsets for using the tools on embedded systems that need to be certified. Simulink^®, Stateflow^®, and Simulink Requirements™ are used to develop the design of the software in compliance with DO-331 Model-Based Development and Verification. Simulink Report Generator™ is used to provide a design description document and trace data, as required by DO-331 and DO-178C. The verification of the design is performed using Simulink Check™, Simulink Test™, Simulink Coverage™, and Simulink Design Verifier™. Simulink Design Verifier uses formal analysis in compliance with DO-333 Formal Methods. MATLAB Coder™, Simulink Coder™, and Embedded Coder^® are used to develop the source code for the system. Verification of the source code is performed using Simulink Code Inspector™, Polyspace Bug Finder™, and Polyspace Code Prover™. Polyspace Code Prover uses formal analysis in compliance with DO-333 Formal Methods. Verification of the executable object code is performed using Simulink Test and Simulink Coverage in conjunction with processor-in-the-loop testing capability. To take credit for the use of these tools, they must be qualified under the guidance of DO-330 Software Tool Qualification Considerations. The DO Qualification Kit provides the necessary documentation and testing artifacts to perform tool qualification for the tools that require it.

Product Focus

Series: Using Qualified Tools in a DO-178C Development Process

Part 1: Introduction to Model-Based Development for DO-178C Learn how to use of Model-Based Design and formal methods with Simulink, Stateflow, Embedded Coder, and the DO Qualification Kit in a process compliant with DO-178C, DO-331, DO-333, and DO-330.

Part 2: Qualified Model Verification – Requirements Tracing Perform tracing from models to requirements, in compliance with DO-178C and DO-331, using Simulink Requirements, and then generate a design description document using Simulink Report Generator.

Part 3: Qualified Model Verification – Simulation Perform simulation and model coverage analysis to verify models, in compliance with DO-178C and DO-331, using Simulink Test and Simulink Coverage.

Part 4: Qualified Model Verification – Model Standards Perform static analysis to verify model standards, consistency, and accuracy, in compliance with DO-178C and DO-331, using Simulink Check.

Part 5: Qualified Model Verification – Design Errors Perform formal methods analysis to verify model consistency and accuracy, in compliance with DO-178C and DO-333, using Simulink Design Verifier.

Part 6: Qualified Code Verification – Model To Code Use Embedded Coder and Simulink Code Inspector to generate code from models and verify that translation in compliance with DO-178C and DO-331.

Part 7: Qualified Code Verification – Code Standards Use Embedded Coder and Polyspace Bug Finder to generate code from models and verify coding standards in compliance with DO-178C and DO-331.

Part 8: Qualified Code Verification – Code Errors Perform formal methods analysis to verify code consistency and accuracy, in compliance with DO-178C and DO-333, using Polyspace Code Prover.

Part 9: Qualified Test Generation Use Simulink Design Verifier and Simulink Coverage to generate tests from models and verify low-level test coverage, in compliance with DO-178C and DO-331.

Part 10: Qualified Software Testing Use processor-in-the-loop capability and code coverage analysis to verify executable object code, in compliance with DO-178C and DO-331, with Simulink Test and Simulink Coverage.

Part 11: Tool Qualification Qualify MathWorks tools in compliance with DO-178C and DO-330 using the DO Qualification Kit.

Related Products

DO Qualification Kit

Learn more about the DO Qualification Kit

Next in Series

Part 2: Qualified Model Verification – Requirements Tracing

Related Videos and Webinars

Model-Based Design for DO-178C Software Development with...

Model-Based Design for DO-178C Software Development with...

Simulink for DO-178 Flight Software Development

Model-Based Design for DO-178C Software Development with...

Model-Based Design for DO-178C Software Development with...

Using Model-Based Methods Throughout the Control System...

Renault's Model-Based Design Powertrain Control Development...

Renault Model-Based Design Power Train Control Development...

Verification by Simulation Within the Model-Based...

Case Study: Dual Fuel Engine Control System Development...

Development of Engine Setpoint Controller Using Model-Based...

Model-Based Development as a Key Element for Continuous...

Customizing Modeling Guideline Checks Within a Continuous...

Model-Based Development: Preparing Students for Industry

Building Competency for In House Development with Model...

Application of MathWorks Tools for Bosch eBike System...

Assessing the Maturity of Model-Based Development Processes

Cost and Benefit of Model-Based Development of Automotive...

Development of Integrated Vehicle Safety Applications...

Aircraft Power Network Development with Model-Based Design