TY - GEN
T1 - Rationale, decisions and alternatives traceability for architecture design
AU - Gilson, Fabian
AU - Englebert, Vincent
PY - 2011
Y1 - 2011
N2 - When designing information systems, architects must often deal with many requirements and constraints. Also, many parties may collaborate during design phases. Therefore, the rationale and decisions sustaining the architecture model can be lost if not documented appropriately. However, in order to understand and maintain these systems, we need to have a clear picture of the rationale and decisions behind their designs. To tackle this problem, we propose a design approach combining architecturally significant requirement modelling and architecture modelling. Constraint and Requirement are attached to architectural constructs. And any modification in the architecture model resulting from a decision made in the requirement model is recorded as a model transformation. We present both modelling formalisms and explain how we combine them to increase the traceability of the rationale, design decisions and alternatives as well as the maintainability of information systems.
AB - When designing information systems, architects must often deal with many requirements and constraints. Also, many parties may collaborate during design phases. Therefore, the rationale and decisions sustaining the architecture model can be lost if not documented appropriately. However, in order to understand and maintain these systems, we need to have a clear picture of the rationale and decisions behind their designs. To tackle this problem, we propose a design approach combining architecturally significant requirement modelling and architecture modelling. Constraint and Requirement are attached to architectural constructs. And any modification in the architecture model resulting from a decision made in the requirement model is recorded as a model transformation. We present both modelling formalisms and explain how we combine them to increase the traceability of the rationale, design decisions and alternatives as well as the maintainability of information systems.
KW - architecture rationale
KW - architecture description language
KW - design decision
KW - traceability
KW - architecturally significant requirement
KW - architectural alternative
M3 - Conference contribution
SP - 4:1-4:9
BT - Proceedings of the 5th European Conference on Software Architecture: Companion Volume (ECSA '11) - Essen (Germany)
PB - ACM Press
ER -