Documenting after the fact: Recovering architectural design decisions

Jansen, Anton; Bosch, Jan; Avgeriou, Paris

doi:10.1016/j.jss.2007.08.025

Cited by 84 publications

(41 citation statements)

References 56 publications

(92 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This model consists of three main architecture activities from industrial approaches, namely architectural analysis, architectural synthesis and architectural evaluation. Jansen et al adopt the model to describe architecture activities from the perspective of architectural decision making [15]. They suggest that architectural decisions are the result of a decision-making process comprised of the activities defined in Hofmeister et al 's general model.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Mature Architecting - A Survey about the Reasoning Process of Professional Architects

Heesch¹,

Avgeriou

2011

2011 Ninth Working IEEE/IFIP Conference on Software Architecture

Self Cite

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

“…The purpose of architectural analysis is to define and scope the problems that have to be solved by the architecture [3], [15]. The outcome of this activity is a set of architecturally significant requirements that serve as input for the architectural synthesis.…”

Section: A Architectural Analysismentioning

confidence: 99%

Mature Architecting - A Survey about the Reasoning Process of Professional Architects

Heesch¹,

Avgeriou

2011

2011 Ninth Working IEEE/IFIP Conference on Software Architecture

Self Cite

View full text Add to dashboard Cite

“…Besides concept and cluster analysis, other techniques have been proposed, involving the analysis of design decisions [31], the identification of change coupling in different versions included in a repository [32], or the use of information retrieval methods [33]. It remains future work to see whether and how such techniques can be applied to systems of similar size as our PMS case.…”

Section: Related Workmentioning

confidence: 99%

Splitting a large software repository for easing future software evolution—an industrial experience report

Glorie

Zaidman

Deursen

et al. 2009

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

SUMMARYPhilips Medical Systems produces medical diagnostic imaging products, such as MR, X-ray and CT systems. The software of these devices is complex, has been evolving for several decades and is currently a multi-MLOC monolithic software repository. In this paper we report on splitting a single software repository into multiple smaller repositories so that these can be developed independently, easing the software's evolution. For splitting the single software repository, we set up two experiments that involve well-known analysis techniques, namely formal concept analysis and clustering. Because of the sheer size of the monolithic software repository, we also propose to use a 'leveled approach', which implies that the analysis technique is applied in several iterations, whereby in some iterations only part of the application is subjected to the analysis technique. Unfortunately, both analysis techniques failed to produce an acceptable partitioning of the monolithic software repository, even if they are combined with our newly proposed leveled approach. We provide a number of valuable lessons learned, which might prevent others from falling into the same pitfalls.

show abstract

“…Choi 1990, Kazman 1999, Jansen 2008. Further advances in such efforts have the potential to automatically produce architectural descriptions that can either be manually or semi-automatically annotated with their license constraints, and thus enable automated construction and assessment of build-time software system architectures.…”

Section: Discussionmentioning

confidence: 99%