IV&V Facility Research Program Results and SARP Results  

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.


Risk Assessment of Software Architectures
Point of Contact Hany Ammar
hammar@wvu.edu
Dates October 2003 - May 2007
Problem The recently released report of the Columbia Accident Investigation Board (issued August 24, 2003), Repeatedly mentions the keywords Risk/ hazard analysis and mitigation in its Recommendations Chapter. Risk/hazard analysis is clearly an important focus area of research and development at NASA. The problem addressed in this proposal is risk assessment of software specification and design artifacts based on software product metrics. We propose to develop techniques for severity analysis and a methodology for maintainability-based risk assessment at the architectural level. The proposed work builds on our recent contributions on developing techniques for risk assessment of UML dynamic specifications [Goseva03,Yacoub 02, Ammar01] and attempts to integrate this work with risk assessment based tools such as CARA and DPP used in NASA projects.
Objective The objectives of this proposal is to extend and integrate our techniques for risk assessment of software artifacts in the Defect Detection and Prevention (DDP) process developed at JPL and the NASA Criticality Analysis and Risk Assessment (CARA) process. These objectives are based on the NASA strategy for risk assessment as described in [Greenfield01].

The objectives are summarized as follows:

  1. Develop a methodology for severity analysis and integrate it with the risk assessment methodology as it applies to a NASA case study (first year).
  2. Integrate the risk assessment methodology with the DDP process developed at JPL (first year).
  3. Develop a methodology and a process for maintainability-based risk assessment and integrate it with the previously developed methodologies for reliability-based and performance-based risk assessment (second year).
  4. Develop a methodology for ranking software functions or components based on their risk factors and integrate it with CARA. (third year)
Results End of Year Briefing.ppt
SAS 05 Technical Presentation.ppt
SAS 05 Executive Presentation.ppt
SAS 06 Executive Presentation.ppt
SAS 06 Technical Presentation.ppt
Keywords Risk assessment, Software Metrics, Hazzard Analysis, Software Architectures, maintainability
Categories Quality Assurance
Quality Control
Software Reliability
Criticality Analysis
Design Analysis
Management & Planning of V&V
Process Improvement
Requirements Analysis
Software Architecture Assessment