Using Patterns to Capture Architectural Decisions

Authors:
Neil B. Harrison;Paris Avgeriou;Uwe Zdun
Affiliations:
Utah Valley State College;University of Groningen;Vienna University of Technology
Venue:
IEEE Software
Year:
2007

Citing 0
Cited 22

Architecting as decision making with patterns and primitives

Proceedings of the 3rd international workshop on Sharing and reusing architectural knowledge
Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach

ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Towards using architectural knowledge

ACM SIGSOFT Software Engineering Notes
Managing architectural decision models with dependency relations, integrity constraints, and production rules

Journal of Systems and Software
Structures to effectively share architectural knowledge

SE '08 Proceedings of the IASTED International Conference on Software Engineering
Architectural decision modeling with reuse: challenges and opportunities

Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Software architecture awareness in long-term software product evolution

Journal of Systems and Software
Architecture decision-making in support of complexity control

ECSA'10 Proceedings of the 4th European conference on Software architecture
Implementing reliability: the interaction of requirements, tactics and architecture patterns

Architecting dependable systems VII
The lonesome architect

Journal of Systems and Software
Capturing architecture evolution with maps of architectural decisions 2.0

ECSA'11 Proceedings of the 5th European conference on Software architecture
Controlling software architecture erosion: A survey

Journal of Systems and Software
The supportive effect of patterns in architecture decision recovery - A controlled experiment

Science of Computer Programming
Identifying architectural patterns used in open source software: approaches and challenges

EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment in Software Engineering
Architectural decision identification in architectural patterns

Proceedings of the WICSA/ECSA 2012 Companion Volume
Beyond ATAM: Early architecture evaluation method for large-scale distributed systems

Journal of Systems and Software
Does decision documentation help junior designers rationalize their decisions? A comparative multiple-case study

Journal of Systems and Software
Derivation of domain-specific architectural knowledge views from governance and security compliance metadata

Proceedings of the 28th Annual ACM Symposium on Applied Computing
Supporting architectural decision making for systems-of-systems design under uncertainty

Proceedings of the First International Workshop on Software Engineering for Systems-of-Systems
Pattern-oriented knowledge model for architecture design

Proceedings of the 17th Conference on Pattern Languages of Programs
A framework for acquisition and application of software architecture evolution knowledge: 14

ACM SIGSOFT Software Engineering Notes
Supporting consistency between architectural design decisions and component models through reusable architectural knowledge transformations

ECSA'13 Proceedings of the 7th European conference on Software Architecture

Quantified Score

Hi-index	0.00

Visualization

Abstract

All of software design involves developers making decisions and reifying those decisions in code. The decisions made during software architecting are particularly significant, as they have systemwide implications, especially on quality attributes. However, architects often fail to document their decisions well. This leads to architectural erosion: decisions made during later development might conflict with the original architectural decisions and thus cause significant system disruptions. Researchers are investigating various methods and tools to help architects effectively document their decisions. However, such documentation remains difficult, so we often lose knowledge of key architectural decisions. Architecture patterns can be an important way to capture and recover this knowledge. They are easy to use and provide a rich set of information about rationale, consequences, and related decisions. This article is part of a special issue on software patterns.