Architectural-level risk analysis using UML

Risk assessment is an essential part in managing software development. Performing risk assessment during the early development phases enhances resource allocation decisions. In order to improve the software development process and the quality of software products, we need to be able to build risk an...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 2003-10, Vol.29 (10), p.946-960
Main Authors: Goseva-Popstojanova, K., Hassan, A., Guedem, A., Abdelmoez, W., Nassar, D.E.M., Ammar, H., Mili, A.
Format: Article
Language:English
Subjects:
Architecture
Computer architecture
Computer engineering
Computer programs
Connectors
Construction
Failure
Markov analysis
Mathematical models
Programming
Resource management
Risk
Risk analysis
Risk assessment
Risk factors
Risk management
Software
Software development
Software development management
Software quality
Software reliability
Statistics
Studies
Systems design
Unified Modeling Language
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Risk assessment is an essential part in managing software development. Performing risk assessment during the early development phases enhances resource allocation decisions. In order to improve the software development process and the quality of software products, we need to be able to build risk analysis models based on data that can be collected early in the development process. These models will help identify the high-risk components and connectors of the product architecture, so that remedial actions may be taken in order to control and optimize the development process and improve the quality of the product. In this paper, we present a risk assessment methodology which can be used in the early phases of the software life cycle. We use the Unified Modeling Language (UML) and commercial modeling environment Rational Rose Real Time (RoseRT) to obtain UML model statistics. First, for each component and connector in software architecture, a dynamic heuristic risk factor is obtained and severity is assessed based on hazard analysis. Then, a Markov model is constructed to obtain scenarios risk factors. The risk factors of use cases and the overall system risk factor are estimated using the scenarios risk factors. Within our methodology, we also identify critical components and connectors that would require careful analysis, design, implementation, and more testing effort. The risk assessment methodology is applied on a pacemaker case study.
ISSN:0098-5589
1939-3520
DOI:10.1109/TSE.2003.1237174