Building Up and Reasoning About Architectural Knowledge

Kruchten, Philippe; Lago, Patricia; Vliet, Hans van

doi:10.1007/11921998_8

Cited by 226 publications

(187 citation statements)

References 20 publications

Supporting

Mentioning

186

Contrasting

Order By: Relevance

“…Architectural decision models are used to document architectural decisions [11,13,14]. These architectural models capture selected decision options and justifications for these decisions.…”

Section: Reusable Architectural Decision Modelsmentioning

confidence: 99%

Reusable Architectural Decision Model for Model and Metadata Repositories

Mayr

Zdun

Dustdar

2009

Formal Methods for Components and Objects

View full text Add to dashboard Cite

Abstract. Models are gaining importance in software development, for instance in the MDD field, as well as in other disciplines such as biology and physics. Hence, tool support is needed to manage these models and metadata about the models. Model repositories support this trend by managing these model artifacts. While setting up model and metadata repositories, architects have to make several fundamental design decisions and balance various forces. In this paper we describe reusable knowledge in form of reusable architectural decisions for ITarchitects in setting-up, planning, and developing model and metadata repositories, as well as the main decision drivers. Our decisions are documented in a reusable architectural decision model that can be instantiated for a concrete system. It also supports a lightweight approach to architecture documentation. A case study illustrates the decisions made when setting up our own data access object model repository by walking through the reusable architectural decision model.

show abstract

“…Architectural decision models are used to document architectural decisions [11,13,14]. These architectural models capture selected decision options and justifications for these decisions.…”

Section: Reusable Architectural Decision Modelsmentioning

confidence: 99%

Reusable Architectural Decision Model for Model and Metadata Repositories

Mayr

Zdun

Dustdar

2009

Formal Methods for Components and Objects

View full text Add to dashboard Cite

show abstract

“…Decomposition relationship: The Decomposition relationship is in line with 'Comprises (Is Made of, Decomposes into)' of Kruchten's ontology [17]. Decomposition relationships signify how generic EA decisions decompose into more detailed design decisions in the context of a specific EA artifact.…”

Section: Ea Decision Relationshipsmentioning

confidence: 93%

“…Based on ontologies for software architecture design decisions [16,17], we define four types of relationships:…”

Section: Ea Decision Relationshipsmentioning

confidence: 99%

Capturing Design Rationales in Enterprise Architecture: A Case Study

Plataniotis

Kinderen

Proper

2014

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. We aim for rationalizing Enterprise Architecture, supplementing models that express EA designs with models that express the decision making behind the designs. In our previous work we introduced the EA Anamnesis approach for architectural rationalization, and illustrated it with a fictitious case study. In this paper we evaluate our approach in terms of its ability to capture design rationales in the context of a real life case study. Together with stakeholders from the business and IT domains of a Luxembourgish Research and Technology Organization, we captured the design rationales behind the introduction of a new budget forecast business process. Our case study shows that EA Anamnesis can reflect the design rationales of the stakeholders, also linking business and IT concerns. Furthermore our study shows that, for this particular case, the stakeholders often used heuristics (commonsensical "short cuts") to make their decision, or even made decisions without considering alternative choices. Finally, we discuss what the lessons learned from this case imply for further research.

show abstract

“…This concept illustrates the EA decisions that were rejected (alternatives) in order to address a specific EA issue [10,11].…”

Section: Ea Anamnesis Design Decision Conceptsmentioning

confidence: 99%

An Empirical Evaluation of Design Decision Concepts in Enterprise Architecture

Plataniotis¹,

Kinderen²,

Linden³

et al. 2013

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Enterprise Architecture (EA) languages describe the design of an enterprise holistically, typically linking products and services to supporting business processes and, in turn, business processes to their supporting IT systems. In earlier work, we introduced EA Anamnesis, which provides an approach and corresponding meta-model for rationalizing architectural designs. EA Anamnesis captures the motivations of design decisions in enterprise architecture, alternative designs, design criteria, observed impacts of a design decision, and more. We argued that EA Anamnesis nicely complements current architectural languages by providing the capability to learn from past decision making.In this paper, we provide a first empirical grounding for the practical usefulness of EA Anamnesis. Using a survey amongst 35 enterprise architecture practitioners, we test the perceived usefulness of EA Anamnesis concepts, and compare this to their current uptake in practice. Results indicate that while many EA Anamnesis concepts are perceived as useful, the current uptake in practice is limited to a few concepts -prominently 'rationale' and 'layer'. Our results go on and show that architects currently rationalize architectural decisions in an ad hoc manner, forgoing structured templates such as provided by EA Anamnesis. Finally, we interpret the survey results discussing for example possible reasons for the gap between perceived usefulness and uptake of architectural rationalization.

show abstract

Building Up and Reasoning About Architectural Knowledge

Cited by 226 publications

References 20 publications

Reusable Architectural Decision Model for Model and Metadata Repositories

Reusable Architectural Decision Model for Model and Metadata Repositories

Capturing Design Rationales in Enterprise Architecture: A Case Study

An Empirical Evaluation of Design Decision Concepts in Enterprise Architecture

Contact Info

Product

Resources

About