A model-driven approach to weave architectural styles into service-oriented architectures

Author(s):  
Marcos López-Sanz ◽  
Juan Manuel Vara ◽  
Esperanza Marcos ◽  
Carlos E. Cuesta
2011 ◽  
Vol 20 (02) ◽  
pp. 201-220 ◽  
Author(s):  
MARCOS LÓPEZ-SANZ ◽  
JUAN MANUEL VARA ◽  
ESPERANZA MARCOS ◽  
CARLOS E. CUESTA

Model-driven development is recognized as one of the most promising approaches in software engineering. Recent research in the area highlights the importance of using an explicit architectural model in this context. Since service-oriented architectures have also demonstrated to be adequate to overcome current software needs, the idea of using the model-driven approach to generate service-oriented architectural models has successfully flourished in the last years. However, the emphasis on the Service-Oriented Computing (SOC) paradigm has led to the design of architectures lacking some desirable features. Knowing the benefits provided by architectural styles, we have found that their use can help us to overcome those needs. Our goal is to obtain a service-oriented model which satisfies the requirements of the concrete architecture and complies with the constraints and vocabulary defined for a specific architectural style. To achieve this, here, we propose to use a weaving model which merges the concrete architectural model with a model of the architectural style of choice.


Author(s):  
Huy Tran ◽  
Ta’id Holmes ◽  
Uwe Zdun ◽  
Schahram Dustdar

This chapter introduces a view-based, model-driven approach for process-driven, service-oriented architectures. A typical business process consists of numerous tangled concerns, such as the process control flow, service invocations, fault handling, transactions, and so on. Our view-based approach separates these concerns into a number of tailored perspectives at different abstraction levels. On the one hand, the separation of process concerns helps reducing the complexity of process development by breaking a business process into appropriate architectural views. On the other hand, the separation of levels of abstraction offers appropriately adapted views to stakeholders, and therefore, helps quickly re-act to changes at the business level and at the technical level as well. Our approach is realized as a model-driven tool-chain for business process development.


Author(s):  
Ingo Zinnikus ◽  
Gorka Benguria ◽  
Brian Elvesæter ◽  
Klaus Fischer ◽  
Julien Vayssière

Author(s):  
Marcos López-Sanz ◽  
Esperanza Marcos

Service-oriented architectures have, over the last decade, gradually become more important. The vast diversity of implementation and support platforms for this kind of architecture increases the complexity of the processes used to develop service-based systems. The task of specifying service architectures can be eased by following a model-driven approach and the appropriate model notations. In this chapter, the authors explore the architectural properties of the service-oriented paradigm and present part of a framework for the specification of service-oriented software architectures. The main idea is to use the separation into different abstraction levels fostered by the MDA proposal and tackle the software architecture specification progressively, stepping from conceptual to platform-specific levels. This chapter particularly concentrates upon describing UML profiles for the PIM and PSM levels of service-oriented architectural models, along with their corresponding metamodels. The use of the proposed profiles is illustrated in a case study in which the proposed profiles are implemented.


Sign in / Sign up

Export Citation Format

Share Document