Software maintenance and evolution: a roadmap
Proceedings of the Conference on The Future of Software Engineering
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
Diagrammatic Modeling of Architectural Decisions
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
Using Patterns to Capture Architectural Decisions
IEEE Software
Software Architecture Knowledge Management: Theory and Practice
Software Architecture Knowledge Management: Theory and Practice
Enriching software architecture documentation
Journal of Systems and Software
Journal of Systems and Software
Model-Centered Customizable Architectural Design Decisions Management
ASWEC '10 Proceedings of the 2010 21st Australian Software Engineering Conference
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Architecture decision-making in support of complexity control
ECSA'10 Proceedings of the 4th European conference on Software architecture
Architectural Decisions as Reusable Design Assets
IEEE Software
Evolution-centered architectural design decisions management
SEPADS'12/EDUCATION'12 Proceedings of the 11th WSEAS international conference on Software Engineering, Parallel and Distributed Systems, and proceedings of the 9th WSEAS international conference on Engineering Education
An approach to documenting and evolving architectural design decisions
Proceedings of the 2013 International Conference on Software Engineering
Hi-index | 0.00 |
Modern IT systems evolve being re-architected throughout their entire lifetime. Existing architecture decision-making approaches are oriented towards systems design, rather than systems evolution. However, real-life architecture evolution is substantially different to initial architectural design. It is a disorderly process, in most cases unrepeatable, and therefore difficult to be put into a predefined rut as most approaches try to do. MAD 2.0 model has been developed to support architect-practitioners working on systems evolution. It does not impose any predefined classification or hierarchy of architectural decisions and assumes a limited number of kinds of relations between architectural decisions. This makes a model of the decision process intuitive and easy to comprehend. To explain the choices made and capture their rationale, the entire decision situation is presented, including: the decision topic, considered design options, relevant requirements, and the advantages and disadvantages of every considered option. The proposed models and approach, supported by an appropriate modelling tool, has been validated in the real life conditions of one of the telecom companies.