 |
||
|
Advanced Search |
||
|
|||||
|
Quality Assurance < Software Quality < Results Home
|
|
Click here to complete a short survey. The results of this survey will be used to help us improve the research program and this website.
Click here to view research projects that had new research results added in the last 90 days.
|
| Assurance and Recertification of Safety-Critical Software in Legacy Systems | |
| Point of Contact |
Janie Hill Janice.L.Hill@nasa.gov |
| Dates | January 2007 - January 2010 |
| Problem | The assurance of legacy systems from a safety perspective is of particular importance when reuse of the system is considered. A problem arises when attempting to carry out the requirements of a software safety standard on real time legacy systems with safety-critical software. This research will apply a new methodology to multiple projects at KSC to retrospectively make a 'safety case' for real time legacy systems with safety-critical software. The objective of this research is to test the methodology on multiple legacy systems with safety-critical software, using the NASA Software Safety standard and a component of software risk, to 'recertify' the software for safe reuse in a different application. The end result of the research will be a tool that can be used by government and industry to apply safety standards in general to recertify with confidence the use of legacy systems with safety-critical software. |
| Objective | From January through September 2007, select 6 or more projects at KSC for the study. Assess current status of compliance with the NASA Software Safety Standard. Develop rationales and logically equivalent safety requirements (see description in Approach). Identify the risk based questions and questionnaires to use on the projects. Develop a software risk evaluation strategy. Identify measurable data to capture and metrics to calculate and analyze.From September 2007 through February 2009, pilot the methodology on the legacy systems. Collect measurement data. Design software tool that implements methodology. Submit progress reports every 3 months.From March 2009 through December 2009, evaluate the methodology results, test software tool, and submit final report on the research. |
| Results |
Exec_SAS_07_Legacy_Safety_Hill.ppt SAS_07_Tech_Pres_Legacy_Safety_Hill.ppt A Software Safety Risk Taxonomy for Use in Retrospective Safety Cases.doc |
| Keywords | Legacy systems with Safety-Critical Software, Reuse Recertification, and Safety Case |
| Categories |
Quality Assurance Software Safety Reuse Analysis |
|
| |
|
Curator: Josh Stonestreet NASA Official: Lisa Montgomery |
|
NASA Privacy, Security, Notices |