A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Acme: an architecture description interchange language
CASCON '97 Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research
A comprehensive approach for the development of modular software architecture description languages
ACM Transactions on Software Engineering and Methodology (TOSEM)
KLAPER: An Intermediate Language for Model-Driven Predictive Analysis of Performance and Reliability
The Common Component Modeling Example
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
Integrating AADL within a Multi-domain Modeling Framework
ICECCS '09 Proceedings of the 2009 14th IEEE International Conference on Engineering of Complex Computer Systems
IEEE Transactions on Software Engineering
Architectural knowledge: getting to the core
QoSA'07 Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications
Developing next generation ADLs through MDE techniques
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Realizing architecture frameworks through megamodelling techniques
Proceedings of the IEEE/ACM international conference on Automated software engineering
MoScript: a DSL for querying and manipulating model repositories
SLE'11 Proceedings of the 4th international conference on Software Language Engineering
| Hi-index | 0.00 |
Architecture Description Languages (ADLs) are the means to define the software architecture of a complex system. ADLs are strongly related to stakeholder concerns: they must capture all design decisions fundamental for system's stakeholders. Stakeholder concerns are various and ever evolving, thus it is impossible to capture all system's concerns with a single ADL. The evolution of a concern may cause the used ADLs (or even the whole architecture framework) not to fit any more with the system-of-interest. In this work we propose an approach for describing software architectures with multiple and evolving stakeholder concerns. Under this perspective, the proposed approach allows (i) to define customized ADLs depending on the concerns held by the system's stakeholders, (ii) to provide interoperability between either customized and already existing ADLs, (iii) to realize architecture frameworks in which viewpoints, views and languages are set up depending on the system's stakeholders concerns. The approach is based on model-driven engineering technologies.