25th International Conference on Software Engineering, 2003. Proceedings. 2003
DOI: 10.1109/icse.2003.1201297
|View full text |Cite
|
Sign up to set email alerts
|

Architectural level risk assessment tool based on UML specifications

Abstract: Recent evidences indicate that most faults in software systems are found in only a few of a system's components [1]. The early identification of these components allows an organization to focus on defect detection activities on high risk components, for example by optimally allocating testing resources [2], or redesigning components that are likely to cause field failures. This paper presents a prototype tool called Architecture-level Risk Assessment Tool (ARAT) based on the risk assessment methodology present… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0
1

Year Published

2003
2003
2008
2008

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 10 publications
(13 citation statements)
references
References 6 publications
0
12
0
1
Order By: Relevance
“…Referring to [7], their research provides risk assessment based on measures obtained from Unified Modeling Language (UML) artifacts. This tool can be used in the design phase of the software development process.…”
Section: Related Workmentioning
confidence: 99%
“…Referring to [7], their research provides risk assessment based on measures obtained from Unified Modeling Language (UML) artifacts. This tool can be used in the design phase of the software development process.…”
Section: Related Workmentioning
confidence: 99%
“…We develop a Markov model to determine scenarios risk factors using components and connector risk factors. This model provides exact closed form solutions for the scenarios risk factors, while the algorithm for traversal of the component dependency graphs used in [31] [30] based on the methodology presented in this paper. The paper is organized as follows: Section 2 describes the well-known cardiac pacemaker system and presents its UML specification based on the use case diagrams and sequence diagrams.…”
Section: Contributionsmentioning
confidence: 99%
“…Since the methodology is entirely analytical and provides a closed form solution, it is very suitable for sensitivity analysis and automation. In fact, a prototype of the risk assessment tool written in JAVA which reads the embedded UML information from Rational Rose, and calculates the various risk factors has already been developed (see chapter 9) [Wang, 2003].…”
Section: Discussionmentioning
confidence: 99%
“…Figure 6.1 describes the use case model of the risk assessment methodology. To automate this risk assessment methodology the UML model is implemented as a prototype tool and is described in chapter 8 [Wang, 2003]. The use case model of the proposed methodology is described as follows: Figure 6.1 Overall Use Case UML model of the proposed methodology…”
Section: Risk Assessment Methodologymentioning
confidence: 99%
See 1 more Smart Citation