From the series: Using Qualified Tools in a DO-178C Development Process
Bill Potter, MathWorks
Showing conformance to source code standards is an objective in DO-178C. Embedded Coder® has the capability to comply with MISRA® C:2012 coding standard. Polyspace Bug Finder™ is a static analysis tool that is used to analyze C source code for either handwritten code or for Embedded Coder generated code. Polyspace Bug Finder is used to verify that the source code conforms to the MISRA C:2012 mandatory coding rules as well as some other categories of rules. Those checks can be run directly from a menu in Simulink® after code generation. The Polyspace Bug Finder also provides the capability to measure code metrics, for example, cyclomatic complexity and comment density. A report indicating pass/fail for each of the MISRA checks and details of the source code metrics will be generated for each source code file. If a non-compliance is found, the report can navigate back to the line of code, as well as to the model element for that code. This report can be provided in various formats, such as Rich Text, Word, HTML or PDF for long-term archiving. The DO Qualification Kit provides the necessary artifacts to qualify automatic standards checking and metrics reporting by Polyspace Bug Finder.
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.
Choose your country to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .Select
You can also select a location from the following list: