2010 21st Australian Software Engineering Conference 2010
DOI: 10.1109/aswec.2010.11
|View full text |Cite
|
Sign up to set email alerts
|

A Systematic Review on Architecting for Software Evolvability

Abstract: For long-lived systems, there is a need to address evolvability (i.e. a system's ability to easily accommodate changes) explicitly during the entire lifecycle. In this paper, we undertake a systematic review to obtain an overview of the existing studies in promoting software evolvability at architectural level. The search strategy identified 58 studies that were catalogued as primary studies for this review after using multi-step selection process. The studies are classified into five main categories of themes… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2011
2011
2022
2022

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 15 publications
(10 citation statements)
references
References 37 publications
0
10
0
Order By: Relevance
“…In the software life cycle, architects and developers to meet users' requirements with the software through the continuous evolution [1][2][3], in order to improve software performance [4], realize new functions [5], and improve software quality [6], stakeholders need to constantly modify the software to meet new requirements [7,8]. Software evolution is often accompanied by software architecture evolution [9]. As a high-level abstraction of software, software architecture hides the implementation details, algorithms, and data representation of source code [10], which helps developers and maintainers to understand software and repair problems as soon as possible [11].…”
Section: Introductionmentioning
confidence: 99%
“…In the software life cycle, architects and developers to meet users' requirements with the software through the continuous evolution [1][2][3], in order to improve software performance [4], realize new functions [5], and improve software quality [6], stakeholders need to constantly modify the software to meet new requirements [7,8]. Software evolution is often accompanied by software architecture evolution [9]. As a high-level abstraction of software, software architecture hides the implementation details, algorithms, and data representation of source code [10], which helps developers and maintainers to understand software and repair problems as soon as possible [11].…”
Section: Introductionmentioning
confidence: 99%
“…Here, the term is not used in the sense of environment-friendliness as in other domains, but instead in the sense of cost-effective longevity and endurance. We do not use the terms 'maintainability' (ISO/IEC 25000), 'modifiability' [14], or 'evolvability' [15,19], because they arguably include the notions of longevity and cost-effectiveness only to a limited extent.…”
Section: Sustainabilitymentioning
confidence: 99%
“…In the same manner, Roy and Graham [59] surveyed scenario-based evaluation methods, but provided only limited comparison of the metrics-based methods. Breivold and Crnkovic [19] provided a broad structured literature review on architecture evolvability, which also included experience-based methods, design methods, and knowledge management techniques but provided no sustainability analysis on the scenario-based and metrics-based evaluation methods.…”
Section: Related Reviewsmentioning
confidence: 99%
See 1 more Smart Citation
“…This question triggers the identification of the main indicators that contribute to negatively increasing the architectural degradation symptoms, which lead to generating problems such as deteriorating software performance [59,60], increasing software maintainability costs [61,62], and software architecture quality degradation [63,64].…”
Section: ) Developing a Review Protocolmentioning
confidence: 99%