Research Results | Investigation of the Risk to Software Reliability of Requirements Changes


	Search:	Advanced Search

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.

Investigation of the Risk to Software Reliability of Requirements Changes
Point of Contact	Norman F. Schneidewind nschneid@nps.navy.mil
Dates	October 2001 - September 2004
Problem	While software design and code metrics have enjoyed some success as predictors of software quality, the measurement field is stuck at this level of achievement. If measurement is to advance to a higher level, we must shift our attention to the front-end of the development process, because it is during requirements analysis that errors are inserted into the process.
Objective	Identify the attributes of requirements that cause the software to be unreliable Quantify the relationship between requirements risk and reliability. If these attributes can be identified, then policies can be recommended to NASA for recognizing these risks and avoiding or mitigating them during development. Extend and validate our work in this area on the Space Shuttle to GSFC and JPL software projects.
Results	Report on results of Discriminant Analysis experiment.pdf Report on results of Trend Analysis experiment.pdf
Keywords	software reliabilty, code metrics, reliability risk, space shuttle, risk of faults and failures
Categories	Software Reliability Requirements Analysis Traceability Analysis

Curator: Josh Stonestreet
NASA Official: Lisa Montgomery