A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Recording the reasons for design decisions
ICSE '88 Proceedings of the 10th international conference on Software engineering
Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Why and How of Requirements Tracing
IEEE Software
Specification and Analysis of System Architecture Using Rapide
IEEE Transactions on Software Engineering - Special issue on software architecture
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Evolution Support by Homogeneously Documenting Patterns, Aspects and Traces
CSMR '02 Proceedings of the 6th European Conference on Software Maintenance and Reengineering
Reconciling Software Requirements and Architectures: The CBSP Approach
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Architecture Decisions: Demystifying Architecture
IEEE Software
ECBS '05 Proceedings of the 12th IEEE International Conference and Workshops on Engineering of Computer-Based Systems
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Recovering architectural assumptions
Journal of Systems and Software
A survey of architecture design rationale
Journal of Systems and Software
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
Tool Support for Architectural Decisions
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Survey of Traceability Approaches in Model-Driven Engineering
EDOC '07 Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference
Introducing Tool Support for Managing Architectural Knowledge: An Experience Report
ECBS '08 Proceedings of the 15th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems
Enriching software architecture documentation
Journal of Systems and Software
Journal of Systems and Software
Towards handling architecture design, variability and evolution with model transformations
Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems
Building up and reasoning about architectural knowledge
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
Hi-index | 0.00 |
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.