Abstract
Today, testing on-board software consumes approx. 30% of the effort for a software project. Improvements in this area will help to save a significant amount of time and money. As discussed in the research community, model based approaches are a very promising solution to save costs while increasing software quality at the same time. Failure Detection, Isolation and Recovery (FDIR) is a significant part of today's flight software. Approx. 30% of the test effort is spent on this functionality. The basis for the FDIR is the failure mode effect analysis (FMEA). Therefore, the approach we present hereafter starts from a “traditional” text based FMEA document.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
