Software risk management: requirements-based risk metrics
James Dean Palmer, Richard Parker Evans · 2002
There are several problems associated with current approaches to requirements-based risk metrics for software risk management. For example, the approaches are qualitative and limit risk considerations to probability of occurrence and severity of impact. They also do not take into account the relative size of the requirements category of which they are a part, i.e. the development effort needed to implement that requirements category. Finally, quantitative factors are not used. The advanced integrated requirements engineering system (AIRES) provides automated support for the quantitative identification and extraction of requirements-based software risk metrics throughout the requirements engineering life cycle. The AIRES risk assessment framework and techniques for the integrated application of both semantic and syntactic rules provide for effective, efficient, and comprehensive identification of requirements at risk in large complex multiple segment systems. A review of a portion of the requirements for a Navy Gun Mount System is included to provide an example of the use of AIRES to support the development of requirements-based risk metrics.>