Reusable Architectural Decision Models for Enterprise Application Development

Zimmermann, Olaf; Gschwind, Thomas; Küster, Jochen M.; Leymann, Frank; Schuster, Nelly

doi:10.1007/978-3-540-77619-2_2

Cited by 57 publications

(61 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Reusable architectural decision models proposed by Zimmermann et al [16,12] focus on solving these problems. A reusable architectural decision model enhances the basic decision model by steering the architectural decision making activities [12].…”

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

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

“…In our previous work [4,7] we introduced a conceptual framework for decision modeling with reuse to extend recent research on design decisions. Our work focused on the following main contributions:…”

Section: Motivation and Problem Identificationmentioning

confidence: 99%

“…We will later explain how it can be extended to support these concepts. We worked with more than one hundred practicing architects, who applied and appreciated the metamodel as well as the SOA guidance model instantiated from it [4], [7]. As part of our validation activities, we conducted a user survey.…”

Section: Motivation and Problem Identificationmentioning

confidence: 99%

“…Architectural Decision Knowledge Wiki is a Web 2.0 collaboration tool supporting the decision modeling capabilities and original UML metamodel first published in [7]. To support the extended metamodel introduced in the previous sections, the following additional features and components are required:…”

Section: Architectural Decision Knowledge Wiki/architectural Decisionmentioning

confidence: 99%

See 1 more Smart Citation

An Enhanced Architectural Knowledge Metamodel Linking Architectural Design Decisions to other Artifacts in the Software Engineering Lifecycle

Capilla

Zimmermann

Zdun

et al. 2011

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Software architects create and consume many interrelated artifacts during the architecting process. These artifacts may represent functional and nonfunctional requirements, architectural patterns, infrastructure topology units, code, and deployment descriptors as well as architecturally significant design decisions. Design decisions have to be linked to chunks of architecture description in order to achieve a fine-grained control when a design is modified. Moreover, it is imperative to identify quickly the key decisions affected by a runtime change that are critical for a system's mission. This paper extends previous work on architectural knowledge with a metamodel for architectural decision capturing and sharing to: (i) create and maintain fine-grained dependency links between the entities during decision identification, making, and enforcement, (ii) keep track of the evolution of the decisions, and (iii) support runtime decisions.

show abstract

“…UML is a language for those models, and tools like the IBM Rational Software Modeler 1 (RSM) or Borland Together assist the user in authoring them and also provide code generation facilities. Current decision management tools like the Architectural Decision Knowledge Wiki [2] and the Architectural Design Decision Support System (ADDSS) [3] help documenting, understanding, and developing software systems. Their primary goal is to capture, document, and maintain design decisions and also support users in making decisions during 1.…”

Section: Introductionmentioning

confidence: 99%

Integrating decision management with UML modeling concepts and tools

Könemann

2009

2009 Joint Working IEEE/IFIP Conference on Software Architecture &Amp; European Conference on Software Architecture

View full text Add to dashboard Cite

Numerous design decisions including architectural decisions are made while developing a software system, which influence the architecture of the system as well as subsequent decisions. Several tools already exist for managing design decisions, i.e. capturing, documenting, and maintaining them, but also for guiding the user by proposing subsequent decisions. In model-based software development, many decisions directly affect the structural and behavioral models used to describe and develop a software system and its architecture. However, the decisions are typically not connected to these models.In this paper, we propose an integration of a decision management and a UML-based modeling tool, based on use cases we distill from an example: the UML modeling tool shall show all decisions related to a model and allow extending or updating them; the decision management tool shall trigger the modeling tool to enforce design decisions (modify the models). We define tool-independent concepts and architecture building blocks supporting these requirements and present first ideas how this can be implemented in the IBM Rational Software Modeler and Architectural Decision Knowledge Wiki. This seamless integration of formerly disconnected tools could improve tool usability as well as decision maker productivity.

show abstract

Reusable Architectural Decision Models for Enterprise Application Development

Cited by 57 publications

References 9 publications

Reusable Architectural Decision Model for Model and Metadata Repositories

Reusable Architectural Decision Model for Model and Metadata Repositories

An Enhanced Architectural Knowledge Metamodel Linking Architectural Design Decisions to other Artifacts in the Software Engineering Lifecycle

Integrating decision management with UML modeling concepts and tools

Contact Info

Product

Resources

About