Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach

Navarro, Elena; Cuesta, Carlos E.

doi:10.1007/978-3-540-88030-1_10

Cited by 11 publications

(23 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to provide ATRIUM with this facility, several relationships were defined in its metamodel, to allow the analyst to describe the AK as a network. As shown in [9], these relationships were first defined on operationalizations, as they are in charge of describing both the DDs and the DRs. The analysis performed in section 2 was considered in their definition, establishing the following relationships:…”

Section: Extending Atrium With Akrsmentioning

confidence: 99%

“…ATRIUM [9] is a model-driven software development methodology, designed to automate the transition from a goal-based requirements model to the proto-architecture of a system, with explicit support for AK.…”

Section: Extending Atrium With Akrsmentioning

confidence: 99%

“…They are analyzed highlighting their importance to comprehend the reasoning accomplished during software architecture (SA) specification. A core of concepts has been identified that has allowed us to extend an existing model-driven (MDD) methodology, ATRIUM [9]. It already has the support for DDs, but it previously lacked the support for relationships, which are added in the new version.…”

Section: Introductionmentioning

confidence: 98%

See 2 more Smart Citations

Weaving a network of architectural knowledge

Navarro

Cuesta

Perry

2009

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

Self Cite

View full text Add to dashboard Cite

Recent research in software architecture has reasserted an emphasis on keeping track of design decisions and their rationales during the development process, that is, on maintaining architectural knowledge (AK). This knowledge takes the form of explicit assets, interrelated in decision networks. We argue that the relationships structuring these networks contain valuable information, specially those describing negative semantics. For this reason, we have extended an architecture-centric, modeldriven development process, ATRIUM, which already provides support for AK, with new AK relationships to define AK as a network of knowledge.

show abstract

Section: Extending Atrium With Akrsmentioning

confidence: 99%

Section: Extending Atrium With Akrsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 98%

See 1 more Smart Citation

Weaving a network of architectural knowledge

Navarro

Cuesta

Perry

2009

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

Self Cite

View full text Add to dashboard Cite

show abstract

“…The traceability supported by the tools can be used to estimate those artifacts that are impacted by the change in a decision, as the majority of the mentioned tools lack fine grained links between decisions and small architectural artifacts (e.g., a UML class or component instead of an entire subsystem). In addition, the approach presented in [17] highlights the role of traceability in software architecture evolution and describe a method to manage such traceability for design decisions using a model-driven development approach. Software product lines (SPL) need to model also the dependencies of feature models (i.e.…”

Section: Related Workmentioning

confidence: 99%

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

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

“…This activity has been defined to generate the proto-architecture of the specific system [14]. It synthesizes the architectural elements from the ATRIUM scenario model that build up the system-to-be, along with its structure.…”

Section: Atrium At a Glancementioning

confidence: 99%

MORPHEUS: A Supporting Tool for MDD

Navarro

Gómez

Letelier

et al. 2010

Information Systems Development

Self Cite

View full text Add to dashboard Cite

Model-Driven Development (MDD) approach is gaining more and more attention both from practitioners and academics because its positive influences in terms of reliability and productivity in the software development process. ATRIUM is one of the current proposals following the MDD principles as the development is driven by models and a tool, MORPHEUS, support both its activities and models. This tool provides facilities for modelling, meta-modelling, and analysis and integrates an engine to execute transformations. In this work, this tool is presented describing both its architecture and its capabilities.

show abstract

Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach

Cited by 11 publications

References 19 publications

Weaving a network of architectural knowledge

Weaving a network of architectural knowledge

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

MORPHEUS: A Supporting Tool for MDD

Contact Info

Product

Resources

About