ESTÁNDARES DE LA INDUSTRIA
DO-178C y estándares relacionados
DO-178C es una actualización del estándar DO-178B y contiene suplementos que se correlacionan estrechamente con las prácticas actuales de desarrollo y verificación de la industria; por ejemplo, desarrollo y verificación basados en modelos (DO-331) y métodos formales (DO-333). La cualificación de las herramientas se aborda en DO-330.
MATLAB y Simulink soportan el diseño basado en modelos para DO-178C como se ilustra a continuación y como se describe en esta serie de vídeos.
“Modelar con Simulink es fundamental para el trabajo relacionado con ARP 4754 de nuestro equipo; en concreto, la validación de los requisitos a nivel de sistema, el desarrollo de pruebas basadas en requisitos y la definición de los requisitos de software de bajo nivel que utiliza nuestro proveedor para producir código de vuelo DO-178 Level A mediante Simulink y Embedded Coder.”
Rodrigo Fontes Souto, Embraer
Estándares DO-178 con MATLAB y Simulink
Managing Requirements and Traceability
Manage your system requirements with end-to-end traceability:
- Produce requirements with rich text, images, and all their attributes
- Review and demonstrate completeness with your objectives
- Generate the requirement documentation for certification audits
Customer Success
Explore Products
Implementing and Verifying Your Design
Design an architecture and make implementation choices so that your design is robust and maintainable:
- Decompose your implementation and componentize
- Manage your data coupling and control coupling
- Check your design for accuracy and ;compliance with industry standards (DO-178C/DO-331, DO-254 checks)
- Generate design documentation for certification audits
- Generate code and ensure compliance between code and models
Customer Success
Demonstrating Your Code Quality
Automatize code validation through the Motor Industry Software Reliability Association (MISRA) compliance and formal methods:
- Check code quality and maintainability by inspecting code with regards to MISRA or CERT-C rules
- Reduce low-level testing activities leveraging formal methods (DO-333)
Customer Success
Test and requirements traceability in coverage results.
Testing Your Implementation Based on Requirements
Demonstrate conformance to the requirements regarding functional and technical expectations:
- Re-use the test procedures used to mature the requirements for formal testing
- Use requirements-based testing for model development
Customer Success
“We have the same high level of confidence in the quality of the generated code as in the code created using our traditional manual processes. With Embedded Coder we know we are generating the right code, and with Simulink Code Inspector we can guarantee that it is traceable to the model.”
Jillian Alfred, Bell 525 fly-by-wire control law designer
Learn More
Comuníquese con ventas
Más información