1 / 26

RTCA DO-178C “Software Considerations in Airborne Systems and Equipment Certification”

RTCA DO-178C “Software Considerations in Airborne Systems and Equipment Certification”. Brock Greenhow March 21, 2013. Software mishaps in Aerospace Engineering. Ariane Five rocket explosion Southern Airways 242 Gimli Glider Patriot Missile. Future of Safety Critical Software.

audra-ford
Download Presentation

RTCA DO-178C “Software Considerations in Airborne Systems and Equipment Certification”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RTCA DO-178C“Software Considerations in Airborne Systems and Equipment Certification” Brock Greenhow March 21, 2013

  2. Software mishaps in Aerospace Engineering • Ariane Five rocket explosion • Southern Airways 242 • Gimli Glider • Patriot Missile

  3. Future of Safety Critical Software • Increased lines of code • Increased complexity • Increased criticality • Technology changes • More with less • Increased outsourcing and offshoring • Attrition of experienced engineers • Lack of available training

  4. Background of DO-178 • 1982 – DO-178 • 1985 – DO-178A • 1992 – DO-178B • 2001 – DO-248B • 2011 – DO-178C and supplemental material • 2011 – DO-248C

  5. Differences from DO-178B to C • Added examples and explanations • Used clearer language and terminology • Added more objectives • Bi-directional tracing • Parameter Data Item Files • Technology Supplements

  6. ARP4754A System Development • System Requirements • Allocate requirements to software • Validate requirements • Communication • Plan for changes to come from software

  7. ARP4761 Aircraft and System Safety • Safety Program Plan • FHA and SFHA’s • PASA and PSSA’s • Software Safety • Improves with time • Errors are not as obvious • Need specific requirements • Involve safety and systems in software requirement reviews

  8. Safety continued

  9. Safety Continued

  10. Overview of DO-178C • Software Planning • Software Requirements • Software Design • Software Integration • Software Verification • Software Configuration Management • Software Quality Assurance • Software Certification

  11. Software Planning • Five Plans • PSAC • SDP • SVP • SCMP • SQAP • Three Standards • Software Requirement Standards • Software Design Standards • Software Coding Standards

  12. Software Requirements • Foundation to good software • Refine Systems Requirements • Allocate enough time • Software Requirement Cycle • Bi-Directional Tracing • Baseline SWRD

  13. Software Design • Architecture • Structural-based • Object-oriented • Low-level Requirements • Bi-Directional Tracing • SWDD

  14. Software Implementation • Coding • Languages and compilers • Good programming • Standards • Traceability • Integration • Build process • Load process • Analyze memory and addresses

  15. Software Verification • Reviews • Plans, requirements, design, test data • Analyses • Code and integration • Coverage • Other • Tests • RBTs, integration • Cases, procedures, results • Tracing

  16. Software Verification Continued • Verification of Verification • SCA, MC/DC • Test data reviews • Problem Reporting • Failures become PR or CR • PR or CR process • CIA • SVCP

  17. Software Configuration Management • Beginning to End • All life cycle data • CC1 or CC2 • SCI • Life cycle data and versions • SLECI and Problem Reporting

  18. Software Quality Assurance • Customer’s needs • Review plans and write SQAP • Life cycle data audits and approval • Reviews • Witness tests, builds, and loads • Problem reporting • Conformity review • Document activities for records

  19. Software Certification • Develop and submit PSAC • PSAC approval • Submittal and approval of SCI and SAS • SOIs

  20. Supplemental Materials • DO-330 Software Tool Qualification • DO-331 Model-Based Development and Verification • DO-332 Object-Oriented Technology • DO-333 Formal Methods

  21. Software Tool Qualification • Separate Document compared to DO-178B • Three criteria • TQL • Life Cycle similar to whole software • Tool verification • Reviews • RBTs

  22. Model-Based Development and Verification • 2 types of Models • Specification • Design • Benefits • Potential Risks

  23. Object-Oriented Technology • Most popular • Additional/Modified objectives • Plans • Development • Verification • Vulnerability guidance

  24. Formal Methods • Changes • Plans • Verification objectives • Benefits • Challenges

  25. Sources • Pictures • http://blog.copdfoundation.org/wp-content/uploads/2012/09/C-Users-sschlegel-Pictures-Question-Mark-Man.jpg • Information • Rierson, L. (2013). Developing safety-critical software. Boca Raton, FL: CRC Press. • Jacklin, S. A. NASA, (2012). Certification of safety-critical software under do-178c and do-278a . Retrieved from Ames Research Center website: http://ntrs.nasa.gov/search.jsp?R=20120016835 • Arnold, D. (2000, August 23). The explosion of the ariane 5. Retrieved from http://www.ima.unm.edu/~arnold/disasters/ariane.html • Arnold, D. (2000, August 23). The patriot missile failure. Retrieved from http://www.ima.unm.edu/~arnold/disasters/patriot.html • Nelson, W. H. (1997). The gimli glider. Retrieved from http://www.wadenelson.com/gimli.html • Fleury, M. K. (2009, April 29). Crash of southern airways flight 242, georgia. Retrieved from http://suite101/article/crash-of-southern-airways-flight-242-a113420

  26. Questions?

More Related