Architecture decision-making in support of complexity control

Authors:
Andrzej Zalewski;Szymon Kijas
Affiliations:
Warsaw University of Technology, Institute of Automatic Control and Computational Engineering;Warsaw University of Technology, Institute of Automatic Control and Computational Engineering
Venue:
ECSA'10 Proceedings of the 4th European conference on Software architecture
Year:
2010

Citing 10
Cited 1

The mythical man-month (anniversary ed.)

The mythical man-month (anniversary ed.)
Patterns for decision making in architectural design: workshop summary

Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications (Addendum)
The 4+1 View Model of Architecture

IEEE Software
Design Decision Trees

IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Architecture Decisions: Demystifying Architecture

IEEE Software
Software Architecture as a Set of Architectural Design Decisions

WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
A web-based tool for managing architectural design decisions

ACM SIGSOFT Software Engineering Notes
Using Patterns to Capture Architectural Decisions

IEEE Software
Software Architecture Knowledge Management: Theory and Practice

Software Architecture Knowledge Management: Theory and Practice
Managing architectural decision models with dependency relations, integrity constraints, and production rules

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

Quantified Score

Hi-index	0.00

Visualization

Abstract

The main challenge of software engineering has always been to bring software complexity under control. Different kinds of abstractions have been devised and applied for that purpose at different levels of software design. Some of them have proven successful, such as function hierarchies, layers, API's, abstract classes, encapsulation, interfaces etc. and are widely used in practice. Concepts from the genre of software architecture should also help to manage software complexity. We argue that, before architecture decisions and architecture decision-making become a common industrial practice, they have to support software complexity management much more efficiently than at present. Despite the substantial progress already made, it is still a major challenge both in theory (architecture decisions representation and architecture decisionmaking methods) and practice (tool support).