A model-driven approach for collaborative service-oriented architecture design

Abstract

In a collaborative context, the integration of industrial partners deeply depends on the ability to use a collaborative architecture to interact efficiently. In this paper, we propose to tackle this point according to the fact that partners of the collaboration respect the SOA (Service-Oriented Architecture) paradigm. We propose to design such a collaborative architecture according to MDA (model-Driven Architecture) principles. We aim at using business models (the needs) to design a logical model of a solution (logical architecture) as a principal step to reach the final collaborative solution. This paper presents the theoretical aspects of this subject and the dedicated transformation rules. Finally, we show the prototype of a demonstration tool embedding the transformation rules and running those principles.

Mediation information system engineering based on hybrid service composition mechanism

“…The first iteration of the MISE project (MISE 1.0, 2006-2010), did provide four design-time services which aimed to (i) characterize a collaborative situation based on a dedicated ontology [3], (ii) extract and transform the knowledge embedded in that ontology in order to model a collaborative business process [3], (iii) transform that collaborative business process model into a logical UML (Unified Modeling Language) model of the mediation information system [4] and finally (iv) transform this logical model into the files required for the deployment of an ESB (Enterprise Service Bus) giving efficient support to the collaborative situation [5]. However, in the first iteration, there were some weak points:…”

Modelling collaborative business services

“…The second research stream (IEC TC 65/290/DC, 2002;Kosanke, 2005;Touzi et al, 2009) offers different levels of collaborative maturity an organisation can adopt: communicating (capable of exchanging and sharing information), open (capable of sharing business services and functionalities with others), federated (capable of working with others according to a set of collaborative processes that have common objectives and to ensure its own objectives) and interoperable (capable of working together without a special effort; partners appear as a homogeneous and seamless system). Medlin (2003) adapts previous works to introduce the ideal coordination contexts in a service network, including market, relational and contract-hierarchy.…”

“…Regarding approaches based on business processes, the collaborative business services modelling deals primarily with inter-organisational business process modelling such as business process modelling notation (BPMN, 2009), Petri Nets and UML (Gou et al, 2000;Grossmann et al, 2008;Ryu and Yucesan, 2007;Touzi et al, 2009). These approaches describe information sharing between service partners with message exchanges, which are considered as static objects.…”

Model Refinement in the Model Driven Architecture Context

“…Model Driven Architecture (MDA) promotes the use of models as the main artifacts through all software development stages: System specification, project, implementation and tests (Touzi et al, 2009). MDA proposal consists in reducing the semantic distance between the business domain and the implementation platform domain.…”

“…In addition, implementations can fully or partially derive from their models through the application of model transformations (Singh and Sood, 2009). According to the MDA approach, software design comprises the following stages (Touzi et al, 2009):…”