Towards a model-driven approach to build component-based adaptable middleware
ARM '04 Proceedings of the 3rd workshop on Adaptive and reflective middleware
Generating CAM aspect-oriented architectures using Model-Driven Development
Information and Software Technology
Using MDE to Build a Schizophrenic Middleware for Home/Building Automation
ServiceWave '08 Proceedings of the 1st European Conference on Towards a Service-Based Internet
Model-Driven approach to Software Architecture design
SHARK '09 Proceedings of the 2009 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Using AOSD and MDD to Enhance the Architectural Design Phase
OTM '09 Proceedings of the Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: ADI, CAMS, EI2N, ISDE, IWSSA, MONET, OnToContent, ODIS, ORM, OTM Academy, SWWS, SEMELS, Beyond SAWSDL, and COMBEK 2009
Deriving detailed design models from an aspect-oriented ADL using MDD
Journal of Systems and Software
Towards a generic aspect oriented design process
MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS
Application MDA in a collaborative modeling environment
ICEC'07 Proceedings of the 6th international conference on Entertainment Computing
| Hi-index | 0.00 |
Distributed systems are inherently complex, and thereforedifficult to design and develop. Experience shows thatnew technologies-such as components, aspects, and applicationframeworks-can be effectively used for building distributedapplications. However, our experience also showsthat most of the applications built in that way are difficult tobe re-used, documented, and maintained. Probably, one ofthe major reasons is the lack of a clear separation betweenthe concepts used at different levels (application domain,application architecture, supporting application platform,programming language, etc.). In this paper we present ourexperience with a platform we developed for building distributedapplications using components and aspects. In particular,we show how many of the (conceptual) problems wehit when trying to document, re-use, and implement it indifferent contexts can be naturally solved with the adoptionof the MDA concepts. In addition, we describe the processwe followed for identifying and separating the entities thatlive in different "models" (in the MDA sense), and the requiredtransformations between them. MDA offers a goodframework for specifying different views of our model, andmappings to platform-specific profiles. In this way, we areable to address the particular needs of different stakeholders:from the designer interested in developing new applicationsfollowing our (component and aspect-based) modelingapproach, to the software vendor that wants to implementa proprietary version of our supporting middlewareframework in CORBA, EJB or .NET.