Software Safety Tutorial

1. N-CSSC Net-Centric Software & Systems Consortium Planning Meeting February 20 - 22, 2008 Software Safety Tutorial Jeff Tian SMU tian@engr.smu.edu Eric Wong UTD ewong@utdallas.edu Dung T. Huynh UTD huynh@utdallas.edu

2. N-CSSC Problem Description • Software safety: key competency in defense, aerospace/aeronautics, healthcare, automotive, energy, and other industries • Catastrophic impact of selected software failures • Necessary condition in some project bidding • Needknowledge/competence in 2 key areas: • State-of-the-art methodologies and technologies • Industry-specific standards/regulations/practices • Extension: Sponsor-driven new research topics Net-Centric Software & Systems Consortium

3. N-CSSC Existing Solutions • Software safety engineering: basic techniques • Software safety = property of being accident-free • Accident (or mishap): failure with severe consequences • Analysis: identification/analysis of hazards or preconditions to accidents using fault-/event-tree analysis (FTA/ETA), FMEA, etc. • Safety assurance/improvement via hazard elimination/reduction/control and risk/damage reduction • Industry-specific regulations, standards, and practices • Needed: guideline for required competency for specific needs under a specific environment Net-Centric Software & Systems Consortium

4. N-CSSC Our Solution • Help industrial partners gain software safety competency using an integrated strategy • Basic knowledge about software safety engineering: Customization of an existing course at SMU • Industry-specific regulations, standards, and practices • Advanced research/expertise at consortium universities • Focus: specific needs of industrial partners • Producing tutorial package(s) and exploring advanced research in related topics 5/24/2014 Net-Centric Software & Systems Consortium

5. N-CSSC Our Solution (cont.) • Foundation Sponsor-driven advanced research: utilizaing expertise in testing/QA for safety, formal verification, embedded system safety/dependability, Industrial Partner Needs • Sw safety fundamentals: • basic concepts • analysis techniques • design for safety • systematic integration • Industry-specific info: • defense • aerospace/aeronautics • other std/reg/practices 5/24/2014 Net-Centric Software & Systems Consortium

6. N-CSSC Experimental Plan • Basic knowledge/competency: • Starting point: SMU graduate-level course CSE 8317 on software reliability and safety • To be extended/customized/packaged for specific needs of our industrial partners • Industry-specific contents: • Categorization/summary of specific regulations, standards and practices in a comprehensive framework • Initiating/steering relevant research: • Inventory of existing expertise at consortium universities • Projects: extend faculty expertise to satisfy industrial needs Net-Centric Software & Systems Consortium

7. N-CSSC Industry Member Benefits • Key benefit: Gain competency as enabler to compete in certain projects/marketplace • Basic and industry-specific knowledge as a packaged tutorial • Flexible delivery methods • Team expertise: resilient/fault-tolerant • Long term needs to drive consortium university research in relevant areas Net-Centric Software & Systems Consortium

8. N-CSSC Deliverables and Budget • Tutorial on software safety • Input: specific/explicit needs of industrial partners • Output/deliverables in three increments: • basic knowledge + industry specific info + final package • Duration and total budget: $76K for 1 year Net-Centric Software & Systems Consortium