Abstract—Although Model Driven Architecture has taken successful steps toward model-based software development, this approach still faces complex situations and ambiguous questions while applying to real world software systems. One of these questions - which has taken the most interest and focus - is how model transforms between different abstraction levels, MDA proposes. In this paper, we propose an approach based on Story Driven Modeling and Aspect Oriented Programming to ease these transformations. Service Oriented Architecture is taken as the target model to test the proposed mechanism in a functional system. Service Oriented Architecture and Model Driven Architecture [1] are both considered as the frontiers of their own domain in the software world. Following components - which was the greatest step after object oriented - SOA is introduced, focusing on more integrated and automated software solutions. On the other hand - and from the designers' point of view - MDA is just initiating another evolution. MDA is considered as the next big step after UML in designing domain. Keywords—SOA, MDA, SDM, Model Transformation, Middleware Transparency, Aspects and Jini. I. INTRODUCTION HE goal of this research is to provide a successful and usable conjunction between these two technologies. We have tried to provide a simple yet effective process which can be viewed as a framework. In the vision inspired by this framework, SOA is the product and MDA makes its production line. During this process, input model is provided via XMI [2] standard and with a high level of abstraction. Proposed framework analyses the elements and their relations within the given model and tries to recognize the SOA components. In two phases (Fig. 1), the input model is first transformed into a SOA profile based model and then into a middleware independent code. Middleware transparency is achieved via the concept of Aspect. The final phase of framework is to transform middleware transparent code into an executable code based on one of known middlewares for SOA. Jini middleware and pre-process weaving is used in the last phase. Rest of the paper is organized as follows: section II introduces proposed SOA profile. Sectiın III, IV and V relatively focus on the 1st, 2nd and 3rd phases of the framework. Section VI contains some implementation details and finally, section VII will conclude the paper. Authors are with Islamic Azad University, Naragh Branch and Malayer Branch, Iran (e-mail: alitaee@gmail.com). II. PROFILE FOR SERVICE-ORIENTED ARCHITECTURES As shown in Fig. 1, generating a profile for service-oriented architecture is the first step to produce such a framework. This profile enables the designer to describe the platform specific model based on SOA. Profiles are standard techniques for extending UML. By using profiles for precise modeling, we ensure that the designed model can be used in different views of MDA with the same concepts, as we are following the MDA for defining standard models. The elements of SOA profile is selected based on knowledge of the main elements of service-oriented architectures (Fig. 2). Fig. 2 Components of SOA [3] Fig. 3 Proposed SOA Profile A Middleware Transparent Framework for Applying MDA to SOA Ali Taee Zade, Siamak Rasulzadeh, and Reza Torkashvan T World Academy of Science, Engineering and Technology 42 2008 253