Software Architecture Risk Containers

Leigh, Andrew; Wermelinger, Michel; Zisman, Andrea

doi:10.1007/978-3-319-65831-5_12

Cited by 3 publications

(32 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The work in [1] [2] describes DR Containers derived from the Design Rule Spaces (DRSpaces) proposed by Xiao et al [3]. DRSpaces are graphs based on design rules (key interfaces) that split an architecture into independent modules.…”

Section: Related Workmentioning

confidence: 99%

“…To improve chances of project success, practitioners must be able to work with the risk container to manage the isolated risks. We concluded that more work is necessary to determine whether different types of risk containers are meaningful to practitioners [1].…”

Section: Introductionmentioning

confidence: 99%

“…Risk containers are defined as architecture subsets that can be used to separate areas of low and high risk within an overall architecture. The work in [1] [2] suggests that risk containers based on design rules support the isolation of error-proneness risks at design time. The ability to isolate risks does not mitigate the risk by itself.…”

Section: Introductionmentioning

confidence: 99%

“…be used to isolate real project risks; B. be formed from design artefacts used in practice; C. help to better manage mitigations used in practice. We investigated how well three different types of risk container can isolate error-proneness [1]. We observed that Design Rule (DR) Containers tend to have less sharing of classes and were more effective at isolating error-proneness risks than Use Case (UC) Containers.…”

Section: Introductionmentioning

confidence: 99%

“…Our research [1][2] provides some evidence that DR Containers satisfy clauses A and B. In this paper, we investigate if containers also satisfy clause C. We present the emerging results of an experiment 1 open until September 30, 2019, to garner further participation from the community.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Risk Containers - A Help or Hindrance to Practitioners?

Leigh

Wermelinger

Zisman

2019

2019 IEEE International Conference on Software Architecture Companion (ICSA-C)

Self Cite

View full text Add to dashboard Cite

Finding problems at the design stage reduces the cost to resolve them. Previous studies have indicated that error-proneness risks can be isolated into risk containers created from architectural designs, to help mitigate such risks early on. Here we describe an ongoing experiment to establish whether presenting designs as a collection of such containers helps practitioners manage the isolated risks. Participants must identify cyclic dependencies that could result in errorproneness and assess the impact of design changes. The emerging results suggest it takes participants longer to locate cyclic dependencies in collections of container diagrams than it does in a single diagram representing the whole design. Participants who reviewed collections of container diagrams tended to identify more cyclic dependencies correctly than those using a single diagram. Although, the results suggest that presenting a design as a collection of containers has no overall bearing on a participant's ability to correctly identify impacts of design changes, in cases where changes span multiple container diagrams no errors in change impact detection were observed. Errors were observed when assessing the same change using a single diagram representing the whole design.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%