Architectural Decay during Continuous Software Evolution and Impact of ‘Design for Change’ on Software Architecture

Riaz, Muhammad Sohail; Sulayman, Muhammad; Naqvi, Husnain

doi:10.1007/978-3-642-10619-4_15

Cited by 27 publications

(21 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…When an architecture is unsuitable to facilitate new requirements but shortcuts are made nevertheless, technical debt is incurred. (See Del Rosso (2009); Riaz et al (2009)). …”

Section: Continuous Evolutionmentioning

confidence: 95%

See 1 more Smart Citation

Continuous software engineering: A roadmap and agenda

Fitzgerald

Stol

2017

Journal of Systems and Software

516

387

View full text Add to dashboard Cite

“…When an architecture is unsuitable to facilitate new requirements but shortcuts are made nevertheless, technical debt is incurred. (See Del Rosso (2009); Riaz et al (2009)). …”

Section: Continuous Evolutionmentioning

confidence: 95%

“…As systems evolve, an architecture may start to decay which results in a degenerated architecture (Riaz et al, 2009). Riaz et al (2009) investigated architectural decay, identifying factors that contribute to this, and potential measures to mitigate such decay.…”

Section: Continuous Evolutionmentioning

confidence: 99%

Continuous software engineering: A roadmap and agenda

Fitzgerald

Stol

2017

Journal of Systems and Software

516

387

View full text Add to dashboard Cite

“…In their seminal work on architectural mismatch [7], Garlan et al demonstrate that implicit architectural assumptions are one major factor impeding effective reuse or evolution of code-and architecture-level artifacts. This is related to phenomena such as architectural decay [17]. Roeller et al [18] propose an approach for retroactively finding such architectural assumptions in existing software architectures and make them explicit.…”

Section: Related Workmentioning

confidence: 99%

Documenting Early Architectural Assumptions in Scenario-Based Requirements

Landuyt

Truyen

Joosen

2012

2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture

View full text Add to dashboard Cite

In scenario-based requirement elicitation techniques such as quality attribute scenario elicitation and use case engineering, the requirements engineer is typically forced to make some implicit early architectural assumptions. These architectural assumptions represent initial architectural elements such as supposed building blocks of the envisaged system.Such implicitly specified assumptions are prone to ambiguity, vagueness, duplication, and contradiction. Furthermore, they are typically scattered across and tangled within the different scenario-based requirements. This lack of modularity hinders navigability of the requirement body as a whole.This paper discusses the need to explicitly document otherwise implicit architectural assumptions. Such an explicit intermediary between quality attribute scenarios and use cases enables the derivation and exploration of interrelations between these different requirements. This is essential to lower the mental effort required to navigate these models and facilitates a number of essential activities in the early development phases such as the selection of candidate drivers in attribute-driven design, architectural trade-off analysis and architectural change impact analysis.

show abstract

“…The research community has developed a significant body of work regarding the related concepts of "erosion", "drift", "degradation", and "decay" [17,9,12,19,21]. A few surveys were published which give general, technically-focused overviews and taxonomies of the field [7,11,8,2].…”

Section: Motivationmentioning

confidence: 99%

Evidence in architecture degradation and consistency checking research

Herold

Blom

Buckley

2016

Proccedings of the 10th European Conference on Software Architecture Workshops

View full text Add to dashboard Cite

Theory suggests that software development may benefit from applying architecture consistency checking and hence, academics have focused on this area. In such circumstances it is important to characterize the overall focus of the field, in order to assess the actual impact of the research work carried out to date, identifying where researchers are placing their effort and which sub-topics are being neglected. In doing so a map is provided for researchers allowing them focus on relevant research gaps and avoiding saturated sub-topics, to deliver results relevant for academia and industrial practice.The goal of this paper is to shed some light on the current state of research in software architecture degradation and consistency checking, particularly focusing on empirical evidence. Preliminary, yet significant results from an ongoing mapping study, as a precursor to a more detailed literature review, are presented and discussed. These results show that solution-proposals constitute a large part of the body of work. In addition, they show that case studies, with potentially limited external validity, are prevalent in terms of empirical design. We argue that the proportion of empirical studies needs to be expanded and that existing case studies should be complemented by experiments and surveys, assessing its impact in practice.

show abstract

Architectural Decay during Continuous Software Evolution and Impact of ‘Design for Change’ on Software Architecture

Cited by 27 publications

References 15 publications

Continuous software engineering: A roadmap and agenda

Continuous software engineering: A roadmap and agenda

Documenting Early Architectural Assumptions in Scenario-Based Requirements

Evidence in architecture degradation and consistency checking research

Contact Info

Product

Resources

About