MBD, OOT and Code Generation: A Cost-Effective Way to Speed Up HMI Certification Presagis Incorporated

Format:

Conference/Event

Author/Creator:

Marcil, Marcil, author.

Conference Name:

SAE 2012 Aerospace Electronics and Avionics Systems Conference (2012-10-30 : Phoenix, Arizona, United States)

Language:

English

Physical Description:

1 online resource

Place of Publication:

Warrendale, PA SAE International 2012

Summary:

This white paper explains the benefits of the Model-Based Design(MBD) approach and Object-Oriented Technology (OOT) that DO-178Cprovides. It also specifically focuses on the usage of Models andCOTS Qualifiable tools that automate or facilitate the verificationand validation of avionics applications constructed from Models inorder to ensure that there is no unintended function.Software running in Aircraft cockpits has dramatically increasedin complexity since DO-178B's revision in 1992. Furthermore,over the past 20 years, software development methods have madesignificant leaps forward and DO-178B has begun to show its agewith respect to the new technology introduced to facilitatesoftware development.This year the newly revamped DO-178C standard sets thecertification process record straight by embracing moderntechnology. DO-178C does not only solidify its foundation byclarifying its core document but also builds the infrastructure tosupport modern software development techniques already commonlyused in avionics development for at least a decade. Fortunately,DO-178C upgrades and clarifies DO-178B. DO-178C therefore considersfour techniques of contemporary software development practiceswhich are published as supplements to the core document: 1.Software Tool Qualification Considerations (TQC) [DO-330]. 2.Model-Based Design and Verification Supplement (MBDV) [DO-331]. 3.Object-Oriented Technology Supplement (OOT) [DO-332]. 4. FormalMethods Supplement (FM) [DO-333].Organizations can see gains not only in the reduction of thedevelopment cycle but also in the overall improvement of theDO-178C certification process; including reduction of schedule andcosts, and improvements in the quality and reliability.In the old school of thought, the methodology relies on textualspecifications and physical prototypes. That is why the informalText-Based Design approach is tightly associated with the waterfallmethodology where all the textual requirements are manually coded,inspected, and tested on a real embedded system. In this method,changes in any part of the waterfall chain are very costly andtime-consuming, leaving almost no room to iterate on thedesign.By contrast, in the Model-Based Design approach, thespecifications are self-contained in the Human Machine Interface(HMI) Model. The HMI requirements are defined in an unambiguous wayand often captured in a formal definition language. Model-BasedDesign offers a collaborative approach to avionics development andallows engineers to inexpensively experiment with various conceptsby deferring hardware integration until much later in thedevelopment process. Correcting problems in the early modelingphase is undeniably the strongest argument in favor of theModel-Based Design approach for developing certifiable ornon-certifiable avionics applications.This white paper is based on "MBD & Code Generation: ACost-Effective Way to Speed up HMI Certification," by LucMarcil, Presagis, Montréal, Québec (Canada) which was presented atthe 30th Digital Avionics Systems Conference in October 18th, 2011.© 2011 IEEE

Notes:

Vendor supplied data

Publisher Number:

2012-01-2137

Access Restriction:

Restricted for use by site license