Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Introduction to the Special Issue on Software Architecture
IEEE Transactions on Software Engineering - Special issue on software architecture
Specification and Analysis of System Architecture Using Rapide
IEEE Transactions on Software Engineering - Special issue on software architecture
The Unified Modeling Language user guide
The Unified Modeling Language user guide
A language and environment for architecture-based software development and evolution
Proceedings of the 21st international conference on Software engineering
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Acme: architectural description of component-based systems
Foundations of component-based systems
Challenges of component-based development
Journal of Systems and Software
Specifying Distributed Software Architectures
Proceedings of the 5th European Software Engineering Conference
Mae---a system model and environment for managing architectural evolution
ACM Transactions on Software Engineering and Methodology (TOSEM)
| Hi-index | 0.00 |
We aim to rise software architecture evolution to a higher level of abstraction. We consider the software architecture through three abstraction levels namely, from the most abstract one: the meta level, the architectural one and the application level. According to this, we propose SAEV (Software Architecture EVolution Model). It can describe and manage the evolution at these different levels in a uniform way: as well the evolution of architectures as the evolution of applications. In addition, it can manage the evolution independently of any description or implementation language. For this, software architecture elements (like component, interface, connector and configuration) are considered as first-class entities and SAEV leans on its own concepts and evolution mechanism. SAEV associates to each architectural element its evolution strategy and evolution rules which define its evolution. These rules and strategies must respect all invariants defined on each architectural element to guarantee the coherence of architecture across the evolution.