Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Proceedings of the 4th ACM workshop on Quality of protection
An evaluation of business solutions in manufacturing enterprises
International Journal of Business Intelligence and Data Mining
Using risk analysis to evaluate design alternatives
AOSE'06 Proceedings of the 7th international conference on Agent-oriented software engineering VII
A collaborative user-centered approach to fine-tune geospatial database design
ER'12 Proceedings of the 2012 international conference on Advances in Conceptual Modeling
| Hi-index | 0.00 |
Early risk assessment is key in planning the development of systems, including systems that involve software. Such risk assessment needs a combination of the following elements: 驴 Severity estimates for the potential effects of failures, and likelihood estimates for their causes 驴 Fault trees that link causes to failures 驴 Efficacy estimates of design and process steps towards reducing risk 驴 Distinctions between preventing, alleviating and detecting (thereafter removing), risks 驴 Risk preventions that have potential side effects of themselves introducing risks The paper shows a unified approach that accommodates all these elements. The approach combines fault trees (from Probabilistic Risk Assessment methods) with explicit treatment of risk mitigations (a generalization of the notion of a "detection" seen in FMECA analyses). Fault trees capture the causal relationships by which failure mechanisms may combine to lead to failure modes. Risk mitigations encompass (and distinguish among) options to prevent risks, detect risks, and alleviate risks (i.e., decrease their impact should they occur). This approach has been embodied in extensions to a JPL-developed risk assessment tool, and is illustrated here on software risk assessment information drawn from an actual project's software system FMECA (Failure Modes, Effects and Criticality Analysis). Since its elements are typical of risk assessment of software and its system interface, the findings should be relevant to a wide range of software systems.