Requirements Engineering in Aviation Model-Based Development per DO-331

Join our webinar to learn more about

• High-level and low-level requirements as defined in DO-178C
• Key aspects of Specification model and Design model in DO-331
• The 5 model and requirement usage examples in DO-331 and their key differences

About our host

Martin Heininger has more than 20 years of experience in the field of methods and processes for the development of safety-critical embedded systems. He’s helped renowned customers in their DO-178C aerospace projects from the initial software concept to the final successful approval by the authorities. Based on this knowledge, he also advises many customers in the automotive industry, the railway industry and automation technology in safety-relevant software projects

Abstract

DO-178C explicitly defines high-level and low-level software requirements that need to be defined and verified in traditional aviation software development. If the model-based approach is applied according to the requirements of DO-331, the processes of requirements engineering need to be adapted.

Hosted by Heicon’s expert, this webinar provides an overview of using the model-based approach for developing aviation products. We analyze the difference between requirements engineering per DO-178C and DO-331, and provide fundamental insights into applying model-based systems engineering in aviation engineering. (This webinar was made possible by VECTOR Informatik.)