Abstract-The adoption of MDA in software development is increasing and is widely recognized as an important approach for building software systems. However, there´s a lack of standard terminology and notation addressing design aspects of an MDA process. The available MDA tools and environments are particularly focused in defining and executing model transformations, while a development process involves other important definitions which should be carried out during the process enactment. This paper presents an integrated approach for MDA process modeling and enactment based on specializations of some SPEM 2 concepts. To support and evaluate our approach a tool was developed and applied in two case studies.

It has been advocated that Aspect-Oriented Programming (AOP) is an effective technique to improve software maintainability through explicit support for modularising crosscutting concerns. However, in order to take the advantages of AOP, there is a need for supporting the systematic refactoring of crosscutting concerns to aspects. Existing techniques for aspect-oriented refactoring are too fine-grained and do not take the concern structure into consideration. This paper presents two categories towards a metaphorbased classification of crosscutting concerns driven by their manifested shapes through a system's modular structure. The proposed categories provide an intuitive and fundamental terminology for detecting concernoriented design flaws and identifying refactorings in terms of recurring crosscutting structures. On top of this classification, we define a suite of metaphor-based refactorings to guide the "aspectisation" of each concern category. We evaluate our technique by classifying concerns of 23 design patterns and by proposing refactorings to aspectise them according to observations made in previous empirical studies. Based on our experience, we also determine a catalogue of potential additional categories and heuristics for refactoring of crosscutting concerns.

No abstract

In order to use the MDA approach, several software processes have been defined over recent years. However, there is a need for specifying and maintaining MDA software process definitions systematically which can also support process enactment, reutilization, evolution, management and standardization. Some empirical investigations have been performed concerning the usage of several MDA-related approaches. In this paper we describe our technique for MDA software process specification and enactment, including tool support. We also present case studies and the concluding results on the application of our approach for process modeling.

The adoption of MDA in software development is increasing and is widely recognized as an important approach for building software systems. Meanwhile, the use of MDA requires the definition of a software process that guides developers in the elaboration and generation of models. While first model-driven software processes have started to appear, an approach for describing them in such way that they may be better communicated, understood, reused and evolved systematically by the development team is lacking. In this context, this paper presents an approach for the specification of MDA processes based on specializations of some SPEM 2 concepts. In order to support and evaluate our approach a tool was developed and applied in a particular MDA process for specific middleware services development.