SAS03/FaultPrediction 1 NASA OSMA SAS ‘03 Software Requirements Analysis As Fault Predictor Dolores R. Wallace SRS Technologies Software Assurance Technology Center http://satc.gsfc.nasa.gov [email protected]William M. Wilson SRS Technologies/SATC [email protected]
15
Embed
SAS03/FaultPrediction1 NASA OSMA SAS ‘03 Software Requirements Analysis As Fault Predictor Dolores R. Wallace SRS Technologies Software Assurance Technology.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAS03/FaultPrediction 1
NASA OSMA SAS ‘03
Software Requirements Analysis As Fault Predictor
Dolores R. Wallace
SRS TechnologiesSoftware Assurance Technology Center
* System Failure Reports** Details Not Yet Available*** Software Change Requests# System Detailed Design Spec not Requirement## Unformatted Text Problem reports
SAS03/FaultPrediction 13
Conclusions
• Data from many more projects is required to improve the possibility of finding a number of data sets with sufficient commonality to support analysis.
• Analysis approach needs to be expanded to include determining if failures attributed to documentation and design flaws are in reality related to deficiencies in requirements.
SAS03/FaultPrediction 14
Recommendations
Advocate and support:
• The use of NASA-STD-2100 documentation standard
• The use of a format to report problems and failures that is compatible with DDTS
• The creation and use of centralized Center repositories for data from completed projects.
SAS03/FaultPrediction 15
Summary
• Lessons– Getting data requires strong, interested Civil
servant advocate– Analyzing data requires tedious effort, even
with automated tools
• Future – Analyze latest set of data– Attempt correlations for the 4 data sets