Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Patterns of Enterprise Application Architecture
Patterns of Enterprise Application Architecture
Refactoring: Improving the Design of Existing Code
Proceedings of the Second XP Universe and First Agile Universe Conference on Extreme Programming and Agile Methods - XP/Agile Universe 2002
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
Modeling and Documenting the Evolution of Architectural Design Decisions
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Architectural Decisions and Patterns for Transactional Workflows in SOA
ICSOC '07 Proceedings of the 5th international conference on Service-Oriented Computing
CVSM '09 Proceedings of the 2009 ICSE Workshop on Comparison and Versioning of Software Models
Reusable architectural decision models for enterprise application development
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Architectural decision modeling with reuse: challenges and opportunities
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Capturing the intention of model changes
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
A case study on co-evolution of software artifacts using integrated views
Proceedings of the WICSA/ECSA 2012 Companion Volume
Architecture-Centric modeling of design decisions for validation and traceability
ECSA'13 Proceedings of the 7th European conference on Software Architecture
ECSA'13 Proceedings of the 7th European conference on Software Architecture
| Hi-index | 0.00 |
Numerous design decisions are made in model-based software development which often are not documented explicitly. Hence, the design knowledge is 'in the designers mind' and communicated orally, if at all, and the rationale behind the decisions is lost. Existing tools tackle this problem for architectural decisions which refer to the higher level architecture of a system. However, these decisions are separate artifacts and not linked to individual design model elements. Hence, there is no automatic check whether the design models comply with made decisions. This paper presents concepts for explicitly linking design decisions and design model elements. As first class artifacts, design decisions can be used for documentation, consistency checking, and reuse. In case consistency constraints are violated, the user is notified that the design models no longer comply with the decisions made. Reuse is realized by extracting design model changes as reusable patterns for recurring decisions.