inf5120 model-based system development...sikkerhet adm/ metadata kommunikasjon data tjenester...

Information Day: Objective 1.2 26.02.2007

1

Telecom and Informatics

INF5120 – Model-based System

Development

Lecture #10-2: Introduction to Model-

driven interoperability and SemanticsApril 12th, 2010

Arne J. Berre, SINTEF ICT

Based on material developed in the ATHENA (IST-507849),

INTEROP (IST-508011), SHAPE, SWING, COIN and EMPOWER/MEMPOWER, JANUS-3 research projects.


Outline

Introduction

Some existing interoperability framework(EIF)

European SHAPE project (Service-Oriented

Heterganeous architecture and platform engineering)

BMM

SoaML

Alignment with BMM and SoaML

Other on going cases of SoaML and BMM


2


Introduction

Organizations are collaborating with other organizations in

order to meet their business objectives.

For business optimization, organizations re-structure their

business realizations by creating new constellations within

an enterprise and across the organizational border that

need to interoperate.

Key issue: service network, who is to produce the service,

who is to consume the service，business goals.

It seems BMM and SoaML can combine these issues

through:

Align goals with service-centric approach.


Introduction

BMM: Business motivation model

The Business Motivation Model specification provides a scheme or

structure for developing, communicating, and managing business plans in

an organized manner. Specifically, the Business Motivation Model does all

of the following:

• It identifies factors that motivate the establishing of business plans.

• It identifies and defines the elements of business plans.

• It indicates how all these factors and elements inter-relate. Among these

elements are those that provide governance for and guidance to the

business — Business Policies and Business Rules.

SoaML: Service-Oriented Architecture Modeling Language

OMG-backed, meant to bring a new type of modeling capability to the service-

oriented world (talk in detail later).


3


Reference

Latest BMM specification.

Latest UPMS specification.

SoaML community: http://www.soaml.org/


Interoperability Framework

ATHENA Interoperability Framework ( each system is described by

enterprise models and different viewpoints, such as business,

process, service, information)

X:/Documents and Settings/ajb/Local Settings/back folder/OMG STANARD/07-08-03.pdf

X:/Documents and Settings/ajb/Local Settings/back folder/OMG STANARD/08-11-01.pdf

http://www.soaml.org/


4


EIF version 2.0 (2009)

European Interoperability Framework


Definition: Interoperability

(Revised in 2008 in EIF v2, to include

common goals !)


5


EIF - Dimensions of Interoperability


Interoperability chain and levels


6


Interoperability levels


Reference model for Interoperability

- Link to areas in IT architecture

Admin, Business, Citizen A

Organisational

interoperability

Semantic

interoperability,

Informasjons

Innhold med

mening for:

Technical

interoperabilitet

(Technicall

standards)

Presentation

Process, rules

Services

Information/Data

Presentation

Process, rules

Services

Data

Communikasjon

Adm/Metadat

Security

Techn. sem/org

Workprocess

Goals

Organisation

Product

Concepts

Communikation

Organisational harmonisation,

in particular around process

Shared understanding of

the meaning/semantics i innhold ved

bruk av teknologier for

presentasjon/prosess/tjeneste/data

Interoperable technologies

Organisational interoperability

Semantic interoperability

Technical interoperability

T. sem/org. mod.

Sikkerhet

Adm/ Metadata

Kommunikasjon

Data

Tjenester

Prosess

Presentasjon

T. sem/org. mod.

Sikkerhet

Adm/ Metadata

Kommunikasjon

Data

Tjenester

Prosess

Presentasjon

T. sem/org. mod.

Sikkerhet

Adm/ Metadata

Kommunikasjon

Data

Tjenester

Prosess

Presentasjon

T. sem/org. mod.

Sikkerhet

Adm/ Metadata

Kommunikasjon

Data

Tjenester

Prosess

Presentasjon

Admin, Business, Citizen B

Organisational

interoperability

Semantic

interoperability,

Informasjons

Innhold med

mening for:

Technical

interoperabilitet

(Technicall

standards)

Presentation

Process, rules

Services

Information/Data

Presentation

Process, rules

Services

Data

Communikasjon

Adm/Metadat

Security

Techn. sem/org

Workprocess

Goals

Organisation

Product

Concepts

Communikation


7


Reference model for Interoperability

vs IDAbc EIF version 1

Organisational Interoperablilitet

Semantic Interoperability

Technical Interoperability

Admin, Business, Citizen A

Organisational

interoperability

Semantic

interoperability,

Informasjons

Innhold med

mening for:

Technical

interoperabilitet

(Technicall

standards)

Presentation

Process, rules

Services

Information/Data

Presentation

Process, rules

Services

Data

Communikasjon

Adm/Metadat

Security

Techn. sem/org

Workprocess

Goals

Organisation

Product

Concepts

Communikation

Organisational interoperability

Semantic interoperability

Technical interoperability

Admin, Business, Citizen B

Organisational

interoperability

Semantic

interoperability,

Informasjons

Innhold med

mening for:

Technical

interoperabilitet

(Technicall

standards)

Presentation

Process, rules

Services

Information/Data

Presentation

Process, rules

Services

Data

Communikasjon

Adm/Metadat

Security

Techn. sem/org

Workprocess

Goals

Organisation

Product

Concepts

Communikation


Run-time

Sem

Annot

Set

#2

InternetSem

Rec

Rules

#2

Local

Softwar

e &

Data

SwApp#1

Local

Softwar

e &

Data

SwApp#2

Sem

Annot

Set

#1

Sem

Rec

Rules

#1

ReferenceOntology

Architecture for semantic annotation and reconciliation

Reconciliation

Design-time


8


SHAPE project

16

UPMSUPMS

Telecom and Informatics 17

MDE for SOA / SHA

– using OMG MDA principles

Flexible

business modelsFlexible

business models

Interconnected

heterogeneous

SOA platform

models

Interconnected

heterogeneous

SOA platform

models

Heterogeneous

SOA platforms

metamodels

Heterogeneous

SOA platforms

metamodels

Business

metamodelsBusiness

metamodelsflexible

Business Models

Business

metamodels

Semantically -

enabled

heterogeneous

SOA model

Unified and

standardised

metamodel for

SOA & SHA

Transformation

rules

Transformer

(engine)

according to

according to

transformation

engine

Transformation

rules

Transformer

(engine)

transformation

engine

Semantically -

enabled

heterogeneous

SOA platform

models

Semantically -

enabled

heterogeneous

SOA platform

metamodels

according to

EPC

POP*

BPDM, BPMN

BMM…

Heterogeneous

service platforms

WSA

JXTA

OGSA

JACK, JADE

WSMO, WSMX

…

Executable business

processesService interfaces

Service contractsService enactment

Business rules

SLAs

Parameterized

services…

Goals

Business rules

Business processes

Business servicesE- contracts

…

Executable artefacts

XSD, WSDL, BPEL

Teams and plans

Resource

management

Semantic Web

Services

…

Wh

at

serv

ice

-ori

ente

d a

spec

ts t

o c

ap

ture

in

mo

del

s

Wh

ich

met

am

od

els

an

d l

an

gu

ages

to u

se

CIM

PIM

PSM

UPMSHA Agents

Grid

Semantic Web

Services

Service

Variability

Web

Services

P2P

Flexible

Business Models

Heterogeneous

Platforms


9

Telecom and Informatics 18

From CIM to PIM with BMM and SoaML

SoaML

Core

Service Variability

PIM4

WS-A

PIM4

SWS

PIM4

Agents

P2P/Grid/

Components

SoaML-SHA

WSDL, WSMO, OWL- S, JACK, JADE, JXTA, OGSA, J2EE, CORBA

J2EE, NetWeaver , .Net, …

BPMN BPDM BMM EPC

PIMs for different

Architectural Styles

Realization Technologies

PSMImplementation Models

CIMBusiness Models

PIMSystem Models

…



10


BMM

There are three main parts in the BMM.

Firstly, an End comprises things that the enterprise aims at

achieving, for example Goals and Objectives.

Secondly, the Means are what the enterprise will employ to

achieve Ends, for example Strategies, Tactics, Business Policies,

and Business Rules.

Finally, Influencers can change the elements of the business plans

through Assessments. The Ends, Means and Influencers are

related to each other in order to answer the following fundamental

question: What is needed to achieve what the enterprise wants to

achieve?


BMM and goal modeling

Objective:

reduce in cost and time, while

ensuring sufficient quality of the

analyses

Means

Establish platform secure

exchange of information

between health enterprises.

Consume analysis service with

lowest cost and shortest

process time with sufficient

quality.

Influencers


11


BMM summary

The values of BMM: Secures a holistic assessment of

possible actions and consequences, from business goal, business processes to technology.

Simpler options for following up decisions critical to business. What decisions have been made? Who made these decisions? When were the decisions made?

Enables simpler communication across large enterprises, between people in leading roles.

Enhanced traceability between strategy and actions ensures quicker and more correct decisions. Why do we need to do something about this? Which decisions are necessary? What are our business requirements?

Right hand picture is the companies that support BMM in Norway and UK


SoaML Profile (part of SoaML - UPMS)


12


Service models - health care examples

collaboration diagram used for representing contracts between the participants that interoperate.


Service models - health care examples

Service network


13


Goal alignment with BMM and service

collaboration with SoaML

26

Figure on the left shows an example

of a business motivation model that

captures the following

business requirements concerning the

processing of purchase orders:

· Establish a common means of

processing purchase orders.

· Ensure orders are processed in a

timely manner, and deliver the

required goods.

· Help minimize stock on hand.

· Minimize production and shipping

costs

This example of a BMM model shows

the business vision, the goals that

amplify that vision, and the objectives

that quantify the goals. It also shows

the business mission, the strategies

that are part of the mission plan, and

the tactics that implement the

strategies. Finally the strategies are

tied to the goals they support.

The example also shows a Process

Purchase Order contract that

formalizes the requirements into

specific roles, responsibilities, and

interactions. The Contract indicates

what motivation elements it realizes

through MeansRealizations.


Conclusion

What we have done:

We want to show the capability of SoaML in the organizational

interoperability level. The example is service identification from the

Norwegian national Health ICT architecture.

What we want to convince:

OMG standard BMM, SoaML can be used not only by business

people but also people in the public health and many other

domains to reach agreement on the provided and required service,

the goals matching them, which support the organizational

interoperability.

27


14


Conclusion

We suggest a :

Organisational Interoperability –by Goal alignment with BMM and service collaboration with SoaML -

requires mutually shared service related goals (ref. Recent EIF v2.0 definition) - we suggest to model goals with BMM and Services with SoaML, and to relate these by fulfillment relationship, in order to provide a concrete basis for the discussion and resolution of organisational interoperability.

More on the current status of the other development On going industrial cases include one from the Norwegian oil

company:

StatoilHydro: Production and process optimizationcases

One iron producing company from Germany:

Saarstahl -Manufacturing planning and control system, Creation and Optimization of Heats and Sequences,


Article 1:

Organizational interoperability

supported through goal alignment with

BMM and service collaboration with

SoaML

I-ESA 2009 paper

Han Fenglin, NTNU

Arne J. Berre, SINTEF

Espen Møller, Oslo University Hospital 22. April. 2009

29


15


Article 2:

Model Driven Service Interoperability

through use of Semantic Annotations

I-ESA 2009 paper

Arne-Jørgen Berre

Fangning Liu

Jiucheng Xu

Brian ElvesæterSINTEF ICT