Towards engineered architecture evolution

Chaki, Sagar; Diaz-Pace, Andres; Garlan, David; Gurfinkel, Arie; Özkaya, Ipek

doi:10.1109/mise.2009.5069889

Cited by 15 publications

(12 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Chaki et al [11] classify architecture evolution into three different types: maintenance focused evolution, which is an architecture evolution that falls under the classical notion of maintenance; open evolution, which has high uncertainty about the future business, technical, and market conditions; and closed evolution, in which the characteristics of the current and envisioned system's architectures are known. The notions of open and closed evolution are similar to our notions of definite and indefinite plans, but differ from ours in that the former focuses on how much we know about the system and the future, whereas the latter focuses on whether or not the system is intended to retire at a certain point of time.…”

Section: Related Workmentioning

confidence: 99%

“…Also our taxonomy provides another important dimension of deterministic plans and adaptive plans so that uncertainly in the real world can be explicitly coped with using adaptive plans. Chaki et al [11] show how closed evolution can be modeled with formal architecture evolution operators. The approach of using formal architecture operators for evolution description can be used to augment and elaborate our framework, and we believe that at the same time it can be developed further along the line of our framework.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Architecture-Based Planning of Software Evolution

Kang

Garlan

2014

Int. J. Soft. Eng. Knowl. Eng.

Self Cite

View full text Add to dashboard Cite

Software architecture allows us to make many decisions about a software system and analyze it even before it has been implemented, so as to make planned development possible. Similarly, architecture-based software evolution planning makes planned evolution possible by allowing us to make many decisions about the evolution of a software system and to analyze its evolution at the level of architecture design before software evolution is realized. In this paper, we develop a framework for architecture-based software evolution planning. It is done by defining various foundational terms and concepts, providing a taxonomy of software evolution plans, and then showing how to calculate values for various types of plans. By identifying and defining constituent foundational concepts, this conceptual framework makes precise the notion of 'architecture-based software planning'. By developing a value-calculation framework for software evolution plans, it also provides a basis for concrete methods for designing and evaluating evolution plans.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Architecture-Based Planning of Software Evolution

Kang

Garlan

2014

Int. J. Soft. Eng. Knowl. Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Chaki's approach [15] defines the "how" of software evolution through planned processes, Cook and Lehman try to explain the "what". Our study focuses instead on the "why", that is, the causes behind the problems observed.…”

Section: Related Workmentioning

confidence: 99%

Causes of premature aging during software development

Lavallee

Robillard

2011

Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th Annual ERCIM Workshop on Softwar

View full text Add to dashboard Cite

Much work has been done on the subject of what happens to software architecture during maintenance activities. There seems to be a consensus that it degrades during the evolution of the software. More recent work shows that this degradation occurs even during development activities: design decisions are either adjusted or forgotten. Some studies have looked into the causes of this degradation, but these have mostly done so at a very high level. This study examines three projects at code level. Three architectural pre-implementation designs are compared with their post-implementation design counterparts, with special attention paid to the causes of the changes. We found many negative changes causing anti-patterns, at the package, class, and method levels. After analysis of the code, we were able to find the specific reasons for the poor design decisions. Although the underlying causes are varied, they can be grouped into three basic categories: knowledge problems, artifact problems, and management problems. This categorization shows that anti-pattern causes are varied and are not all due to the developers. The main conclusion is that promoting awareness of anti-patterns to developers is insufficient to prevent them since some of the causes escape their grasp.

show abstract

“…In the first, "Towards Engineered Architecture Evolution" [3], Chaki, et al argue that close-ended architectural evolution, where the starting and ending design points are known, can be modeled as a sequence of steps. The authors present a framework to describe such evolution trajectories.…”

Section: Using Models In Software Evolutionmentioning

confidence: 99%

Workshop on modeling in software engineering at ICSE 2009

Baillargeon

Zschaler

Rumpe

et al. 2009

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

The Modeling in Software Engineering (MiSE) workshop series provides a forum for discussing the challenges associated with modeling software and with incorporating modeling practices into the software development process. The main goal of the series is to further promote cross-fertilization between the modeling communities (e.g., MODELS) and software-engineering communities.In particular, the workshop provides a medium to exchange innovative technical ideas and experiences related to modeling. The 2009 MiSE workshop provided a venue for presentation and discussion of eleven papers in the five areas of model evolution, domain specific languages, verification and validation, model transformation and state-of-the-art modeling usage in software development. These papers represent a 44% acceptance rate to the workshop. Three posters were also accepted. This report summarizes the discussions and conclusions of the workshop.

show abstract

Towards engineered architecture evolution

Abstract: Abstract

Cited by 15 publications

References 24 publications

Architecture-Based Planning of Software Evolution

Architecture-Based Planning of Software Evolution

Causes of premature aging during software development

Workshop on modeling in software engineering at ICSE 2009

Contact Info

Product

Resources

About