ICT 1

INF5120”Modellbasert Systemutvikling”

”Modelbased System development”

Lecture 7: 08.03.2010SoaML modeling

ICT 2

INF5120 - Lecture plan - 2010 1: 25/1: Introduction to MBSU, MDA, OO and Service/SOA modeling, Overall EA, 4 parts: MDE/SSS/MS/MDI

(AJB)

Part I: MDE – Model Driven Engineering 2: 1/2: MDE I: Metamodeling. DSL and UML profiles, MDA technologies (XMI, Eclipse, EMF/GMF) (AJB/BRE)

Part II: SSS – Service Science and Service/SOA technologies 3: 8/2: SSS I: Service science (top down) - Service and SOA Technologies (bottom up) (AJB)

Part I continued: MDE – Model Driven Engineering 4: 15/2: MDE II: Model transformations with MOFScript, ATL and other technologies (GO/JO) 5 :22/2: MDE III: Code generation with MOFScript, ATL and other technologies (GO/JO)

Part III: MOS – Modeling of Services - with SoaML 6: 1/3: MOS I: Business Process Modeling (CIM) - with BPMN 2.0, and BMM, EA with UPDM (AJB) 7: 8/3: MOS II: Soaml, UML2 and SysML, Modelio SOA and Scope, –Collaboration and Component models (AJB) 8: 15/3: MOS III: SoaML (PIM) and Requirements modeling , CIM->PIM and SoaML (AJB) 9: 22/3: MOS IV: Method Engineering and SPEM / EPF - for Service systems (BRE)

EASTER Part IV – Model Driven Interoperability 10: 12/4: MS V: SOA and Service Design, Migration to SOA/Cloud Patterns with ADM (AJB ) 11: 19/4: MDI I: Semantic Web with Ontologies and Model Driven Interoperability (TIR) 12: 26/4: MDI II: Semantic Services and Model Driven Interoperability (TIR) 13: 3/5: MDE IV: Evolution and industrial practice of modelbased technologies (AJB++)

14: 10/5: Course summary and preparation for Exam 31/5 (AJB)

Exam: May 31st, 2010 (Monday), 0900-1200 (3 hours)

ICT

Oblig 2 (Group work) Create CIM, PIM and PSM models for an existingTravel

agency to start to offer bookings through the web – for bookings through Internet of packaged travels (including flights, hotel, and car options).

Goals include Internet based travel reservation, optimal travel planning, improving the quality of customer satisfaction and financial optimisation, suppport automation of the accounting department and cash flow management, and to follow up on personnel load and satisfaction and collaboration between the various departments (sales, marketing, accounting, etc.) Process support for ISO 9000 certification.

3

ICT

Outline

L7-1: SoaML introduction

SoaML Collaboration models SoaML Composite structure models

L7-2: SysML introduction

ICT 5

CIM to PIM to PSM

Flexible business models

Flexible business models

Interconnectedheterogeneous SOA platform

models

Interconnectedheterogeneous SOA platform

models

Heterogeneous SOA platforms

metamodels

Heterogeneous SOA platforms

metamodels

Business metamodelsBusiness

metamodelsflexible

Business ModelsBusiness

metamodels

Semantically -enabled

heterogeneous SOA model

Unified and standardised

metamodel for SOA & SHA

Transformationrules

Transformer(engine)

according to

according to

transformationengine

Transformationrules

Transformer(engine)

transformationengine

Semantically -enabled

heterogeneous SOA platform

models

Semantically -enabled

heterogeneous SOA platform metamodels

according to

EPCPOP*BPDM, BPMNBMM…

Heterogeneousservice platformsWSAJXTAOGSAJACK, JADEWSMO, WSMX…

Executable businessprocesses

Service interfacesService contracts

Service enactmentBusiness rules

SLAsParameterized

services…

GoalsBusiness rules

Business processesBusiness services

E-contracts…

Executable artefactsXSD, WSDL, BPEL

Teams and plansResource

managementSemantic Web

Services…

Wh

at s

ervi

ce- o

rien

ted

asp

ects

to

cap

ture

in

mo

del

s

Wh

ich

met

amo

del

s an

d l

ang

uag

es t

o u

se

CIM

PIM

PSM

UPMSHA Agents

Grid

Semantic WebServices

ServiceVariability

WebServices

P2P

FlexibleBusiness Models

HeterogeneousPlatforms

ICT

Use of OMG metamodels BPMN (BPMN 2.0) BMM UML 2.0 SoaML OSM VDM Case Management SBVR ODM

6

ICT

SoaML Historikk(Service oriented architecture modeling language)

7

OMG RFP – September 2006 3 initial submissions – June 2007 Merge process in 2008 and 2009 SoaML 1.0 ferdigstilt desember 2009 SoaML 1.0 adopteres av OMG i mars 2010 FTF chairs: Arne J. Berre, SINTEF og Jim Amsden, IBM

http://www.soaml.org

ICT

Service

A service is value delivered to another through a well-defined interface and available to a community (which may be the general public). A service results in work provided to one by another.

ICT

Mappings between BPMN 2.0 and SoaML BPMN participants are mapped to SoaML participants BPMN conversation diagrams are mapped into SoaML

service architectures BPMN choregraphies are mapped into process for

interactions between SoaML particpants – a basis for services

BPMN service tasks are invocations of web services (more as an implementation level service)

ICT

Service Architecture Modeling with SoaML collaboration models

ICT

Services Architecture

A ServicesArchitecture (or SOA) is a network of participant roles providing and consuming services to fulfill a purpose. The services architecture defines the requirements for the types of participants and service realizations that fulfill those roles.

The services architecture puts a set of services in context and shows how participants work together for a community or organization without required process management.A community ServicesArchitecture is defined using a UML Collaboration.

Shipping service

Ship Status service

Purchasing service

ICT

Inside the Seller/Manufacturer

Order

Conformation

Shipped

Ship Req

Shipped

Delivered

Order Processing

Accounting

Service

ICT

ServiceContract

A ServiceContract defines the terms, conditions, interfaces and choreography that interacting participants must agree to (directly or indirectly) for the service to be enacted - the full specification of a service which includes all the information, choreography and any other “terms and conditions” of the service. A ServiceContract is binding on both the providers and consumers of that service. The basis of the service contract is also a UML collaboration that is focused on the interactions involved in providing a service. A participant plays a role in the larger scope of a ServicesArchitecture and also plays a role as the provider or user of services specified by ServiceContracts.

ICT

Service Contract

The service contract specifies the details of the service – what information, assets and responsibilities are exchanged and under what rules

Role within

service

Role within

service

Service Contract

Service interface

corresponding to role

Service interface

corresponding to role

Information processed by

order processor

Information received by

orderer

typetype

ICT

Simple Protocol Choreography for Ordering Service Contract

Could also be specified in BPMN, in principle

ICT

Participants

Participant

Participant

Participants represent logical or real people or organizational units that participate in services architectures and/or business processes. In SoaML participants provide and use services, defining their external contract

ICT

Service Modelling with SoaML Port/Connector models – extending

UML 2.0 composite structure models

ICT

Service ports and Service Participants

A Service port s the offer of a service by one participant to others using well defined terms, conditions and interfaces. A Service port defines the connection point through which a Participant offers its capabilities and provides a service to clients.A Service port is a mechanism by which a provider Participant makes available services that meet the needs of consumer requests as defined by ServiceInterfaces, Interfaces and ServiceContracts. A Service port is represented by a UML Port on a Participant stereotyped as a «Service, .

ICT

ServiceInterface

a ServiceInterface can be the type of a service port. The service interface has the additional feature that it can specify a bi-directional service – where both the provider and consumer have responsibilities to send and receive messages and events. The service interface is defined from the perspective of the service provider using three primary sections: the provided and required Interfaces, the ServiceInterface class and the protocol Behavior.

ICT

Participant with Service and Request ports

The type of a Request port is also a ServiceInterface, or UML Interface, as it is with a Service port The Request port is the conjugate of a Service port in that it defines the use of a service rather than its provision. This will allow us to connect service providers and consumers in a Participant.- Can be transformed to appropriate interface/implementation code.

ICT

Conclusion Both BPMN 2.0 and SoaML will become final standards

in 2010 A BPMN-SoaML harmonisation team is working on

alignment and synergy between the two specifications – they will complement each other with the process and service perspective, respectively

BPMN 2.0 with SoaML enables working with services and service composition at an abstraction level suitable for business stakeholders

Tool vendors are preparing support for BPMN 2.0 (incrementally) and SoaML (already)

ICT 25

Next Lecture – March 15th, 2010 SoamL

UML 2.0 - Collaboration Diagrams, OOram

UML 2.0 Port Connector Models and Components

Service Science – IBM, Jørn Berg Nordlund