The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
The 4+1 View Model of Architecture
IEEE Software
Embedded System Design
Tool Support for Architectural Decisions
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Visualizing Software Architectural Design Decisions
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Structuring the co-design of requirements and architecture
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Towards Resource-Aware Runtime Reconfigurable Component-Based Systems
SERVICES '10 Proceedings of the 2010 6th World Congress on Services
Naive architecting - understanding the reasoning process of students: a descriptive survey
ECSA'10 Proceedings of the 4th European conference on Software architecture
A classification of value for software architecture decisions
ECSA'10 Proceedings of the 4th European conference on Software architecture
Dynamically reconfigurable resource-aware component framework: architecture and concepts
ECSA'11 Proceedings of the 5th European conference on Software architecture
Building up and reasoning about architectural knowledge
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
| Hi-index | 0.00 |
Capturing architectural knowledge is very important for the evolution of software products. There is increasing awareness that an essential part of this knowledge is in fact the very process of architectural reasoning and decision making, and not just its end results. Therefore, a conceptual framework is needed that provides support for the process of architectural reasoning and making decisions. In this paper we introduce diagrams that advance existing achievements, address observed problems, and capture known insights in order to facilitate the process of architectural reasoning and its documentation, and in that way provide support for processes such as e.g. product evolution, architecture evaluation, and change impact analysis. An approach to architectural knowledge management is proposed in which a software architecture is modeled by a set of architectural reasoning diagrams, where each diagram is composed of several layers and addresses certain aspects of the system. These diagrams supplement existing ways to capture architecture descriptions, they share a set of common elements, and capture design decisions, their motivations and dependencies. A metamodel is given that defines those common elements and also defines the dependencies that exist between these elements both within and between layers. The proposed concepts and diagrams are illustrated on a software architecture for a component-based framework that needs to satisfy a given set of requirements and to address concerns of particular stakeholders.