Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Software Evolution
On the Impact of Evolving Requirements-Architecture Dependencies: An Exploratory Study
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
CoCoME - The Common Component Modeling Example
The Common Component Modeling Example
The Palladio component model for model-driven performance prediction
Journal of Systems and Software
IEEE Transactions on Software Engineering
Change impact analysis with a goal-driven traceability-based approach
International Journal of Intelligent Systems - Goal-driven Requirements Engineering
Linking design decisions to design models in model-based software development
ECSA'10 Proceedings of the 4th European conference on Software architecture
Supporting architectural design decisions evolution through model driven engineering
SERENE'11 Proceedings of the Third international conference on Software engineering for resilient systems
How do professional developers comprehend software?
Proceedings of the 34th International Conference on Software Engineering
Architecture-Centric modeling of design decisions for validation and traceability
ECSA'13 Proceedings of the 7th European conference on Software Architecture
| Hi-index | 0.00 |
When changing software systems, significant effort is spent on locating the architectural elements to be changed, how they relate to the existing and new requirements, and what decisions have led to the current state of the parts of the system to evolve. Model-based approaches have proposed formal metamodels to capture different aspects of the system, e.g. requirements specified in use cases and architectural models for the component design. Existing approaches still lack in an easy-to-use way to combine information from different models. We carried out a case study evolving the CoCoME software observing what are major points for improvement. In this paper, we discuss the results of the case study giving a list of requirements for tools or approaches supporting architecture-centric and model-based software evolution. Finally, we present our graph-based approach for integrated views which can help in overcoming some of the current limitations.