Lines in the Water

Proper, Henderik A.; Land, Martin Op ’t

doi:10.1007/978-3-642-16770-6_9

Cited by 34 publications

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, an enterprise architecture (EA) decision names the decision that is made in the context of an Enterprise Transformation [13]. Regarding the distinction between made decision and alternative decision, see the decision relationship"alternative".…”

Section: Decision Propertiesmentioning

confidence: 99%

See 1 more Smart Citation

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

Section: Decision Propertiesmentioning

confidence: 99%

“…technical) part. The outcome of EA decisions can be observed during an ex-post analysis of the architecture [13]. Some of the consequences of EA decisions are revealed during the implementation phase, or during the maintenance of the existing architecture design.…”

Section: Decision Propertiesmentioning

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

show abstract

“…technical) part. Some of the consequences of EA decisions are revealed during the implementation phase, or during the maintenance of the existing architecture design [12]. These unanticipated consequences are exactly captured by the concept of an observed impact.…”

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

Enterprise Modelling in the Age of Digital Transformation

Gils

Proper

2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Lines in the Water

Cited by 34 publications

References 14 publications

Capturing Design Rationales in Enterprise Architecture: A Case Study

Capturing Design Rationales in Enterprise Architecture: A Case Study

An Empirical Evaluation of Design Decision Concepts in Enterprise Architecture

Enterprise Modelling in the Age of Digital Transformation

Contact Info

Product

Resources

About