inf5120 ”modellbasert systemutvikling” ”modelbased system … · inf5120 model based system...

INF5120 Model based System Development 24.01.2011

1

Telecom and Informatics 1

INF5120

”Modellbasert Systemutvikling”

”Modelbased System development”

Lecture 1: 24.01.2011Arne-Jørgen Berre


Welcome to INF5120 “Model based

System development”

Model based System Development

http://www.uio.no/studier/emner/matnat/ifi/INF5120/v11/

Earlier: Modellering med objekter, Modeling with objects

Lecturers:

Arne-Jørgen Berre

Franck Fleurey

Brian Elvesæter

Gøran Olsen, Dumitru Roman, and Guest lecturers

Email: [email protected]

Responsible for Obligatory exercises:

Weiqing Zhang, Tore Vatnan

Email: [email protected]



mailto:[email protected]







2


INF5120 - Lecture plan - 2011

1: 24/1: Introduction to Model Based System Development (INF5120)

Part I: MDE – Model Driven Engineering

2: 31/1: MDE I: Metamodels, Domain specific languages and UML profiles, (EMF, Kermeta)

3: 7/2: MDE II: Metamodeling, MDLE and DSL Tools (EMF, GMF, ATL, Kermeta)

4: 14/2: MDE III: Model transformations - MOFScript,

6: 28/2: MDE IV: Method Engineering with SPEM / EPF/SEMAT (Note date and lecture number !)

Part II: SSI – Service Innovation and Engineering

5 :21/2: SIE I: Service Innovation and CSI, Enterprise Architecture and Service methodologies

7: 7/3: SIE II::Business Process Modeling with BPMN 2.0

8: 14/3: SIE III: User-oriented design – with Use cases and UI models

9: 21/3: SIE IV: Service modeling with SoaML,

10: 28/3: SIE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud

Part IV – Model Driven Interoperability

11: 4/4: MDI I: Semantic technologies, Ontologies and Semantic annotations

12: 11/4: MDI II: Model Driven Service Interoperability

EASTER

13: 2/5: MDE III: ADM and Migration to Cloud computing

14: 9/5: Conclusion and Summary for INF5120 - Preparation for Exam

Exam: May 30th, 2011 (Monday), 0900-1300 (4 hours)

Lecturers (from SINTEF): Arne J. Berre, Franck Fleurey, Brian Elvesæter, Dumitru Roman, … and Guest lectures

Telecom and Informatics

Obligatory Exercises - 2011

1: 24/1: Introducing links to Eclipse, EMF, GMF, Eugenia, Kermeta and Modelio

2: 31/1: Introduction to Oblig 1, Individual - Eclipse and EMF tutorial, Kermeta

3: 7/2: EMF and GMF tutorial, Kermeta

4 :14/2: MOFScript in practice, Kermeta

5: 21/2: Preparations/Questions for Oblig 1 delivery, Establish groups for Oblig 2

(25/2: Delivery of Oblig 1)

6: 28/2: – Going through Oblig 1, Intro to Oblig 2, EPF-SPEM tools

7: 7/3: BPMN and SoaML tools

8: 14/3: Preparations /Questions for Oblig 2a delivery

9: 21/3: UML2, SoaML tools

10: 28/3: tools for SOA/BPM realisation – Generation of code from Modelio etc.

(1/4: Delivery of Oblig 2a)

11: 4/4: Going through Oblig 2a delivery, Semantic web/Ontology/MDI tools

12: 11/4: Oblig 2B intro, Preparations /Questions for Oblig 2b delivery

29/4: Delivery of Oblig 2b

13: 2/5: Going through Oblig 2B

14: 9/5: Going through old Exams, 2009, 2010

INF9120 – Extra Oblig: essay on Model based system development related to thesis topic – or similar


3


Course literature – available on web Material from all lectures and OBLIG 1 and 2 a/b

Some selected articles and documents, and subset of standard documents from OMG – see handbooks from last year(s). We are currently updating the handbooks for this year.

A.J. Berre & B. Elvesæter: Model Driven Engineering - MDE, Handbook. Part 1 - MDA.

A.J. Berre & B. Elvesæter: Service Science and Service Oriented Architectures - SOA, Handbook. Part 2 - SOA.

A.J. Berre & B. Elvesæter: Model Driven Interoperability - MDI, Handbook. Part 4 - MDI.

Practical use of tools (OBLIG):

EMF - http://www.eclipse.org/modeling/emf/

GMF - http://www.eclipse.org/gmf/

Kermeta: http://www.kermeta.org/

Eugenia – http://www.eclipse.org/gmt/epsilon/doc/eugenia/

See also: http://live.eclipse.org/node/575

Modelio - http://www.modeliosoft.com/

MOFScript -http://www.eclipse.org/gmt/mofscript/

BPMN – http://www.eclipse.org/stp/bpmn

ATL - http://www.eclipse.org/gmt/atl/ og http://www.modelbased.net/

SoaML - www.soaml.org


Course literature – available on web Material from all lectures and OBLIG 1 and 2 a/b

Some selected articles and documents, and subset of standard documents from OMG

BPMN – www.omg.org/bpmn (BPMN v2 Beta 1)

SoaML – Latest standard document (SoaML Beta 2) – Articles by Jim Amsden, IBM, on SoaML (1 to 5), Article by Cory Casanave, Model Driven Solutions,

Some selected articles on MDI

K. Arnarsdóttir, A.-J. Berre, A. Hahn, M. Missikoff, F. Taglino: Semantic mapping: ontology-based vs. model-based

approach Alternative or complementary approaches?, EMOI06Ppaper.pdf.

Arne-Jørgen Berre, Fangning Liu, Jiucheng Xu, Brian Elvesæter: Model Driven Service Interoperability through use

of Semantic Annotations, 2009. I-ESA paper. Fulltext.

http://www.uio.no/studier/emner/matnat/ifi/INF5120/v08/undervisningsmateriale/INF5120-Part-I-MDE.pdf




http://www.uio.no/studier/emner/matnat/ifi/INF5120/v08/undervisningsmateriale/INF5120-Part-II-SOA.pdf




http://www.uio.no/studier/emner/matnat/ifi/INF5120/v08/undervisningsmateriale/INF5120-Part-IV-MDI.pdf




http://www.eclipse.org/modeling/emf/

http://www.eclipse.org/gmf/

http://www.kermeta.org/

http://www.eclipse.org/gmt/epsilon/doc/eugenia/

http://live.eclipse.org/node/575

http://www.modeliosoft.com/

http://www.eclipse.org/gmt/mofscript/

http://www.eclipse.org/stp/bpmn

http://www.eclipse.org/gmt/atl/

http://www.modelbased.net/

http://www.soaml.org/

http://www.omg.org/bpmn

http://www.uio.no/studier/emner/matnat/ifi/INF5120/v07/undervisningsmateriale/EMOI06Ppaper.pdf

http://www.uio.no/studier/emner/matnat/ifi/INF5120/v09/undervisningsmateriale/MDI-I-ESA-2009.pdf


4


OBLIGS: – “MDE tools in practice”

Oblig 1 a/b: Design a Kermeta and GMF based editor in

Eclipse with EMF and use of MOFScript etc. for

transformations to Java. (TBD).

OBLIG 2a – Smart House– with BPMN/SoaML modeling.

(TBD).

OBLIG 2b part 1/2 - MDI support etc.

INF9120 – Extra Oblig: essay on Model based system

development related to thesis topic – or similar

7


Exam

Case-based (ref. earlier exams)

All written material can be used

09-13 (4 hours) –

Monday 30 . May 2011


5


3 parts of the course

MDE I-V (Model Driven Engineering)

SSS (Service Innovation and Service Engineerins)

MDI I-II (Model Driven Interoperability)

Each part will have a separate handbook

9


Objectives

Model based System Development

- through ”modeling with objects and services”

2 roles:

1) Tool developer (Software Factory)

2) Application developer, (user of Software Factory).

Object-oriented -> Componentbased -> Service oriented Reuse

Learn techniques MDA – Model driven architecture

Meta Modeling and modelltransformation *

SOA – Service oriented architecture

Unified Modeling Language (UML 2.0) – for architecture

MDI – Model Driven Interoperability


6


Change in course from 2010

We will use a new Metamodel environment, Kermeta, on

top of EMF, instead of only focusing on GMF. We will keep

the sequence from 2010 and 2008 with a bottom up

MDLE approach(rather than top down as we had in 2009)

– with first learning the principles and technologies for

MDE in February. We will also give a short introduction to

the focus area of Service Innovation, Service Science and

Service Engineering, before finalising the MDE part. .

In March we will focus on how to practice a model driven

approach to Services (MOS), and in April we will introduce

the topic of Semantic Web/services and Model Driven

Interoperability (MDI) – before a final conclusion of the

course

11


New since last year

Initial focus on Eclipse with EMF and GMF and

transformation tools

Use of Modelio commercial modeling tool – for UML2 and

BPMN 2.0 (This is a new version of Objecteering)

New focus on “Service Science” – with Service Innovation

(with BI/NHH), Service Design (OAH) and Service

Engineering (UIO)

New standards: Focus on OMG MDA standards, and on

SoaML with links to BPMN 2.0, SysML and UPDM.

12


7


Which OMG modeling standards will

you learn ?

SoaML – SOA Modeling Language

UML 2.0 – what is new in version 2

MDA – Model Driven Architecture

BPMN 2.0 – Business Process Modeling Notation

BMM _ Business Motivation Model

SysML – Systems Engineering Modeling Language

SPEM – Software Process Engineering Metamodel

QVT, MOF2Text – Query, View, Transformation

See www.omg.org

13


Which tools/environments will you

learn ?

Eclipse EMF and XMI, Principles of GMF

EuGENia – for GMF

MOFScript (Model2Text, Model2Model)

EPF/SPEM Software Process Modeler

Modelio UML Modeler (BPMN, UML 2, SysML)

Modelio SOA Solution (SoaML)

Overview of ATL, KerMeta, OpenArchitectureWare-OAW,

Microsoft OSLO

Ref. also IBM RSA/RSM, Enterprise Architect, Magic Draw

supporting SoaML and BPMN

14

http://www.omg.org/


8


OBLIG 1: – “MDE tools in practice”

Design a GMF based editor in Eclipse with EMF and use

of MOFScript for transformations:

Practical use of

EMF

GMF

EuGENia

MOFScript

Compare with UML profiles

Individual work

15


OBLIG 2 – “Smart House Design” –

increments with group presentations

CIM models (BPMN)

CIM models (Scope, Goal, Requirements)

Requirements models

SoaML models

Access to web based sensor services

16

MOFScript transformations to Java and potentially to

different technologies/platforms

Discussion on Model Driven Interoperability


9


Requirements for the course

Student at UIO

Only assumption is basic knowledge of UML and Java

(but not UML 2.0)


Course literature – Update to become

available on web Material from all lectures and OBLIG

Some selected articles and documents, and subset of standard documents from OMG

Handbook: ”Model Driven Engineering - MDE” , A.J. Berre & B. Elvesæter

Handbook: ”Service Innovation and Service Engineering ” , A.J. Berre & B. Elvesæter

Handbook: ” Model Driven Interoperability - MDI”, A.J. Berre & B. Elvesæter







Papyrus UML2 - http://www.papyrusuml.org

ATL - http://www.eclipse.org/gmt/atl/ og http://www.modelbased.net/

JEE 5.0 - http://java.sun.com/javaee/technologies/






http://www.papyrusuml.org/

http://www.eclipse.org/gmt/atl/


http://java.sun.com/javaee/technologies/


10


Supporting literature

Book: Model-Driven Software Development: Technology, Engineering, Management (Paperback) by Thomas Stahl, Markus Voelter, Krzysztof Czarnecki

ISBN: 978-0-470-02570-3

Engineering Service Oriented Systems: A Model Driven Approach, Karakostas, Bill; Zorgios, Yannis

ISBN10: 1599049686 ISBN13: 9781599049687Cover: Hardcover April 2008


Supporting literature – EMF and GMF

Book: Eclipse Modeling Framework (2nd Edition) (Paperback)

Dave Steinberg (Author), Frank Budinsky (Author), Marcelo Paternostro

(Author), Ed Merks (Author)

Book: Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit

(Paperback)

Richard C. Gronback

http://www.amazon.com/exec/obidos/search-handle-url/103-7761124-5606221?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Thomas%20Stahl

http://www.amazon.com/exec/obidos/search-handle-url/103-7761124-5606221?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Markus%20%20Voelter

http://www.amazon.com/exec/obidos/search-handle-url/103-7761124-5606221?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Krzysztof%20Czarnecki

http://www.amazon.com/s/ref=ntt_athr_dp_sr_1?_encoding=UTF8&sort=relevancerank&search-alias=books&field-author=Dave%20Steinberg

http://www.amazon.com/s/ref=ntt_athr_dp_sr_2?_encoding=UTF8&sort=relevancerank&search-alias=books&field-author=Frank%20Budinsky

http://www.amazon.com/s/ref=ntt_athr_dp_sr_3?_encoding=UTF8&sort=relevancerank&search-alias=books&field-author=Marcelo%20Paternostro

http://www.amazon.com/s/ref=ntt_athr_dp_sr_4?_encoding=UTF8&sort=relevancerank&search-alias=books&field-author=Ed%20Merks

http://www.amazon.com/Richard-C.-Gronback/e/B002JBAVWK/ref=ntt_athr_dp_pel_1


11


Kermeta – www.kermeta.org

21


UML 2.0

UML 2.0 and SysML Background and Reference material

See www.uml-forum.com/specs.htm

Også hos OMG:

http://www.omg.org/uml/ (UML)

http://www.omg.org/mda/ (MDA)

http://www.omg.org/cwm/ (MOF, XMI, CWM)


http://www.uml-forum.com/specs.htm



http://www.omg.org/uml/

http://www.omg.org/mda/

http://www.omg.org/cwm/


12


UML 2.0 recommend books:

UML 2.0 in a Nutshell

by Dan Pilone (Author), Neil Pitman (Author)

The Unified Modeling Language User Guide

Second edition (ISBN 0-321-26797-4)

(G, Booch, J. Rumbaugh, Jacobsson)


Open Services Innovation

Book:

January 2011


13


Exam

Case-based (ref. earlier exams)

All written material can be used

09-13 (4 hours) – (Note, extended from 3 from previous

years, we will, however, still keep the same amonunt of

work)

Monday 30. May 2011


OMG Model-Driven Architecture (MDA)

www.omg.org/mda


14


Automation in Software DevelopmentRequirements Requirements Requirements

Implementation

Source in a

general-purpose

language, e.g.,

Java or C++

Implementation

(may generate

code in

Java or C++)

Source in

domain-specific

language (DSL)

Implementation

(may generate

code in

Java or C++)

Source in

domain-specific

language (DSL)

High-level spec

(functional and

nonfunctional)

Manually

implement

Manually

implement

Manually

implement

Compile Compile Compile

Compile Compile

Implement

with

Interactive,

automated

support


PIM

CIM

BPDM, SBVR,

EDOC,UPMS,

PIM4SOA, ODM

ATL

PSM

MOFScript

BPMN, POP*, ARIS,

ArchiMate,

GERAM, GRAI, Zachman,

UEML, B.Rules

BPEL, WSDL, XML, XPDL,

OWL-S, WSML, WSDL-S

ADM

ADM

UML profiles and

metamodels for Java

JEE, BPEL, WSDL,

XML, XPDL,

OWL-S, WSML, WSDL-S

Code, Java JEE,

….

Platform

Independent

Model

Computational

Independent

Model

Platform

Specific

Model/Code

MDA

CIM, PIM

and

PSM/Code


15


Exte

nd

ing

CO

ME

T f

or

SO

A (

1)

Semantic

Space

Service-Oriented

Architecture Model

Web Service

Execution ArtefactsAgent

Execution Artefacts

BPEL

Execution Artefacts

P2P

Execution Artefacts

Web Service

Specification Model

Agent Specification

Model

BPEL Specification

Model

P2P Specification

Model

Model Transformation

UML Profile for Web Services

UML Profile for Agents

UML Profile for BPEL

UML Profile for P2P

Model Transformation

Architecture Specification

ATHENA Integrated

Execution Infrastructure

Registry

RepositoryService Wrappers (Enterprise A)

Evaluation & Negotiation of Available Functionality

Enhanced Service Interconnection Bus

Cross-org.

Intra-org.

Existing Enterprise Applications

PublicInfrastructure Services

Service Wrappers

(Enterprise X)

Service Wrappers

(Enterprise Y)

InternalInfrastructure Services

Process Execution Platform(BPEL)

Goal-orientedAdaptive ExecutionPlatform(Agents)

Goal-orientedAdaptive ExecutionPlatform(Agents)

ActiveModel Platform(AKMii)

ActiveModel Platform(AKMii)

Legend

Message-OrientedPlatform(MQSeries)

Message-OrientedPlatform(MQSeries)

Server-side Component Platform(.NET, J2EE)

Server-side Component Platform(.NET, J2EE)

ComposedWebServicePlatform(WebServices)

Business Process/Agent

Active (Business) Model

Web/Server Component

Middleware Process/Agent

Middleware Component

Adaptive Distributed Resource Mgt Platform (P2P)

Deployment

UML Profile for SOA

• Information

• Service

• Process

• QoS

Refe

ren

ce O

nto

log

y

annotated with

Model to Model Transformation

Model to Text

Transformation

OWL

Ontology

annotated

with

annotated

with

Enterprise

Model

UML Profile for POP*

• Process

• Organisation

• Product

• …

Model to Model

Transformation

Business

Requirements

Analysis

annotated with


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

source

target

transformation

engine

input

output

Transformation

rules

Transformer

(engine)

transformation

engine

source

Semantically-

enabled

heterogeneous

SOA platform

models

Semantically-

enabled

heterogeneous

SOA platform

metamodels

according to

input

targetoutput

EPC

POP*

BPDM, BPMN

BMM

…

Heterogeneous

service platforms

WSA

JXTA

OGSA

JACK, JADE

WSMO, WSMX

…

Executable business

processes

Service interfaces

Service contracts

Service enactment

Business rules

SLAs

Parameterized

services

…

Goals

Business rules

Business processes

Business services

E-contracts

…

Executable artefacts

XSD, WSDL, BPEL

Teams and plans

Resource

management

Semantic Web

Services

…

Wh

at

servic

e-o

rie

nte

d a

spects

to c

ap

ture

in

mod

els

Wh

ich

meta

mod

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

SoaML


16


UPMS (core)

UPMSHA (core)

Service Variability

UPMS

WSA

PIM4

SWS

PIM4

Agents

P2P/Grid/

Components

UPMSHA

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

J2EE, NetWeaver, .Net

BPMN BPDM BMM EPC

PIMs for different

Architectural

Styles

Realisation

Technologies

PSM

Models

CIM

Business

Models

PIM

Models


PIM-K

CIM-K

Ontologies Bus.Process Bus.Rules Goals NFA/Qualities Org

BPDM, SBVR,

EDOC,UPMS,

PIM4SOA, ODM

PSM-K

BPMN, POP*, ARIS,

ArchiMate,


UEML, B.Rules. ..

Technologies/Realisation-K

UML profiles and

metamodels for BPEL, WSDL, XML,

XPDL,

OWL-S, WSML, WSDL-S

Technology

Reliastion

Code

Information Process Services Rules NFA UI

Data Wflow/Comp Interfaces Rules NFA UI

XML, BPEL/XPDL, WSDL, SWRL, Security, AJAX

OWL, OWL-S/WSML WSDL-S, Induction, … QoS

Legacy and New systems/services, ERPs/ESAs


17


Technologies/Realisation

Information Services Process

XML,, Metro/WSDL BPEL/XPDL

OWL,WSML OWL-S/WSML SA/WSML ASM

ODM,

Concepts

BPMNCIM

PIM

Persistence API EJB 3.0, Java,

SoaML

Jack, JADE Jack, JADE Jack, JADE

SAP SAP SAP

BMM

INF5120 OMG standard focus

PSM


SHAPE Solution

Overview

SoaML

Core

Service

Variability

PIM4SWS

PIM4Agents

P2P/Grid/Components/…

SHA-ML

WSDL, WSMO, OWLS, JACK, JADE, JXTA, OGSA, CORBA, …

J2EE, NetWeaver, .Net, …

Flexible Business Modelling

BPMN EPC BMM

PIMs for different

Architectural Styles

Execution Environments

PSMImplementation Models

CIMBusiness Models

PIMSystem Models

…

2nd EC Review, Brussels, January 28th

2010


18


SHAPE Solution

MDE Technologies

35

Purpose /

BenefitProblem /

State-of-ArtSolution

developed

Future

Plans

Flexible

Business Modelling

Service &

SOA Modelling

Integration of

Agent Technology

Integration of

SWS Technologies

Service

Customization

1

2

3

4

5

Integrated &

guided business

modelling

• Business-IT-Gap

• Bus. Modeling

techniques not

integrated

• BPMN 2.0 support

• Cont. integration of

bus. modelling

• Backward analysis

• Business-IT-Gap

• Existing techn.

not integrated

Enable MDE for

services & SOA

• MDE for SOA

highly desired

• UML does not

support this

• Disseminate SoaML

• Commercialization

• SoaML Extensions

• SoaML metamodel

& profile

• Modelling tools

• Methodology

Automated

planning on top of

services

• Services are only

passive infrastruc.

• problem solving /

planning on top

• Standardiz. (AMP)

• Enhanced problem

solving using

services

• Framework & Tools

for integration with

SoaML

• Enhance AOSE

Handling Hetero-

geneity + automate

service usage

• Hetero. & dynamics

in larger systems

• SWS not aligned

with classic SE

• Standardization

(OMG,W3C,OASIS)

• MDE for Semantic

Technologies

MDE for SWS:

Framework, Tool,

Methodology

Customization &

personalization of

services

• Complex services

vs. indiv. user req.

• adequate techn-

iques not existing

• Standardiz. (CVL)

• Continue towards

comprehensive

serv. customization

• New approach

based on SPEL

• Metamodel, Tool,

Methodology


SHAPE Solution Matrix

36

Meta-

ModelsModel Trans-

formationsSHAPE Tool

Suite

SHAPE

Methodology

Flexible

Business Modelling

Service &

SOA Modelling

Integration of

Agent Technology

Integration of

SWS Technologies

Service

Customization

1

2

3

4

5

BPMN, EPC

Data, Org., Rules

BMM, Ontologies

SoaML

SHAML – Agent

Extension

SHAML – SWS

Extension

Service Variability

Metamodel

Tech

no

log

ical

Inn

ovati

on

s

CIM->CIM (mult.)

CIM -> PIM (mult.)

SoaML -> WS

SoaML -> JEE

SoaML -> PIM4Agents

PIm4Agents -> PSM

SoaML-> SWSPim

SWSPim -> WSMO

SoaML-> SV-Spec.

SV-Res. -> Soaml

CIMFlex

Modelio

Modelio

Composition Studio

PIM4Agents

WSMT

Service Variability

Tools

CIMFlex Modeling

BPMN + UML

Ontology Engin.

SoaML & WS

Modelling

Agent Modelling (PIM ->PIM2PSM->PSM)

Service Variability

Modelling &

Variant Creation

SWS Modelling (PIM ->PIM2PSM->PSM)

MDE Infrastructure


19


PIM-K

CIM-K

BPDM, SBVR,

EDOC,UPMS,

PIM4SOA, ODM

TR/QVT

PSM-K

TR/QVT

BPMN, POP*, ARIS,

ArchiMate,


UEML, B.Rules


OWL-S, WSML, WSDL-S

TR/M2T ADM

ADM

ADM

UML profiles and

metamodels for BPEL, WSDL, XML,

XPDL,

OWL-S, WSML, WSDL-S

Code

PIM-K

CIM-K

TR/QVT

PSM-K

TR/QVT


OWL-S, WSML, WSDL-S

TR/M2T ADM

ADM

ADM

Code

Semantic

Interoperability

Part 4: MDI

Model Driven

Interoperabtiliy

Organisational

Interoperability

Technical

Interoperability


EPF Composer

EPF Composer isa tool platform for process engineers,project leads, projectand program managerswho are responsiblefor mainteining and implementing processesfor development organizations or individual projects

Aims to:

provide for development practitioners a knowledge base of intelectual capital that allows them to browse, manage and deploy content.

provide process engineering capabilities by supporting processe engineers and project managers in selecting, tailoring, and rapidly assembling processes for their concrete development process.


20


Enterprise Modelling (EM) is a capability

for externalising, making and sharing

enterprise knowledge.

EM tools can either be:

• used stand-alone to produce various

kinds of model views,

• integrated as front-ends to other

systems,

• part of an environment providing a

contextual user-environment.

What is Enterprise Modelling?


Why Enterprise Architecture?

?

?

How can I

involve my people

in improving the

performance of the

business

How can I use best

practices to ensure

the success of the

business?

How can I

ensure that the IS technology

helps the work of my people?

?


21


Representations of Architecture

ARISZACHMAN GERAM

EN/ISO 19439

NIST

EKA -POPSEKA -POPSEKA -POPS

Athena OEA


Three Views in

DOD Architecture Framework and C4ISR-AF


22


To-be Operational DoDAF

As is To bearchitecture

Target

architecture

Architectural models supported

by the necessary tools.

Organisation

Hub

Current

Architectural Standards

New Form of Service-Team Organization

To-Be


Based on work by

John A. Zachman

VA Enterprise

Architecture

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTUAL)

Owner

SYSTEM MODEL

(LOGICAL)

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTUAL)

Owner

SYSTEM MODEL

(LOGICAL)

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

Things Important

to the Business

Entity = Class of

Business Thing

Processes

Performed

Function = Class of

Business Process

Semantic Model

Ent = Business Entity

Rel = Business Relationship

Business Process

Model

Proc = Business Process

I/O = Business Resources

Business Logistics

System

Node = Business Location

Link = Business Linkage

Work Flow Model

People = Organization Unit

Work = Work Product

Master Schedule

Time = Business Event

Cycle = Business Cycle

Business Plan

End = Business Objectiv e

Means = Business Strategy

Important

Organizations

People = Major

Organizations

Business

locations

Node = Major

Business Locations

Ev ents Significant

to the Business

Time = Major

Business Event

Business Goals

and Strategy

Ends/Means =

Major Business Goals

Logical Data

Model

Ent = Data Entity

Rel = Data Relationship

Application

Architecture

Proc = Application Function

I/O = User Views

Distributed System

Architecture

Node = IS Function

Link = Line Characteristics

Human Interface

Architecture

People = Role

Work = Deliv erable

Processing

Structure

Time = System Event

Cycle = Processing Cycle

Business Rule

Model

End = Structural Assertion

Means = Action Assertion

Physical Data

Model

Ent = Segment/Table

Rel = Pointer/Key

System

Design

Proc = Computer Function

I/O = Data Elements/Sets

Technology

Architecture

Node = Hardware/Softw are

Link = Line Specifications

Presentation

Architecture

People = User

Work = Screen Format

Control

Structure

Time = Ex ecute

Cycle = Component Cycle

Rule

Design

End = Condition

Means = Action

Data

Definition

Ent = Field

Rel = Address

Program

Proc = Language Statement

I/O = Control Block

Netw ork

Architecture

Node = Addresses

Link = Protocols

Security

Architecture

People = Identity

Work = Job

Timing

Definition

Time = Interrupt

Cycle = Machine Cycle

Rule

Design

End = Sub-Condition

Means = Step

Data

Ent =

Rel =

Function

Proc =

I/O =

Netw ork

Node =

Link =

Organization

People =

Work =

Schedule

Time =

Cycle =

Strategy

End =

Means =

Based on work by

John A. Zachman

VA Enterprise

Architecture

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTUAL)

Owner

SYSTEM MODEL

(LOGICAL)

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

SCOPE

(CONTEXTUAL)

Planner

ENTERPRISE

MODEL

(CONCEPTUAL)

Owner

SYSTEM MODEL

(LOGICAL)

Designer

TECHNOLOGY

MODEL

(PHYSICAL)

Builder

DETAILED

REPRESENTATIONS

(OUT-OF-CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

Things Important

to the Business

Entity = Class of

Business Thing

Processes

Performed

Function = Class of

Business Process

Semantic Model

Ent = Business Entity

Rel = Business Relationship

Business Process

Model

Proc = Business Process

I/O = Business Resources

Business Logistics

System

Node = Business Location

Link = Business Linkage

Work Flow Model

People = Organization Unit

Work = Work Product

Master Schedule

Time = Business Event

Cycle = Business Cycle

Business Plan

End = Business Objectiv e

Means = Business Strategy

Important

Organizations

People = Major

Organizations

Business

locations

Node = Major

Business Locations

Ev ents Significant

to the Business

Time = Major

Business Event

Business Goals

and Strategy

Ends/Means =

Major Business Goals

Logical Data

Model

Ent = Data Entity

Rel = Data Relationship

Application

Architecture

Proc = Application Function

I/O = User Views

Distributed System

Architecture

Node = IS Function

Link = Line Characteristics

Human Interface

Architecture

People = Role

Work = Deliv erable

Processing

Structure

Time = System Event

Cycle = Processing Cycle

Business Rule

Model

End = Structural Assertion

Means = Action Assertion

Physical Data

Model

Ent = Segment/Table

Rel = Pointer/Key

System

Design

Proc = Computer Function

I/O = Data Elements/Sets

Technology

Architecture

Node = Hardware/Softw are

Link = Line Specifications

Presentation

Architecture

People = User

Work = Screen Format

Control

Structure

Time = Ex ecute

Cycle = Component Cycle

Rule

Design

End = Condition

Means = Action

Data

Definition

Ent = Field

Rel = Address

Program

Proc = Language Statement

I/O = Control Block

Netw ork

Architecture

Node = Addresses

Link = Protocols

Security

Architecture

People = Identity

Work = Job

Timing

Definition

Time = Interrupt

Cycle = Machine Cycle

Rule

Design

End = Sub-Condition

Means = Step

Data

Ent =

Rel =

Function

Proc =

I/O =

Netw ork

Node =

Link =

Organization

People =

Work =

Schedule

Time =

Cycle =

Strategy

End =

Means =

Zachman Framework – for Enterprise

Architecture


23


CSI Norway – Center for Service Innovationled by Norwegian Business School, Bergen, SINTEF, AOH, Telenor,..

(National Center for Research Driven Innovation (SFI) – 20 Meuro

budget, 8 years 2011 – 2018)


CSI planned Activities


24


Service Modeling with SoaML – and

extensions (FP7 SHAPE project ++)

47

UPMSUPMS


Business Motivation Model (BMM) with

MeansRealizations


25


What is BPMN (Business Process

Modeling Notation) ?


BPMN example


26


System and objects

A system is a part of the real world which we choose to regard

as a whole, separated from the rest of the world during some

period of consideration.

A whole that we choose to consider as a collection of objects,

each object being characterized by attributes and by actions

which may involve itself and other objects.

Mental modell

Manifest ModelReal-World

phenomenon


Object oriented modeling

aRealWorld-

PhenomenaroleModels

anImplemented

SystemanObjectModel

Manifest Model

Real-Worldphenomenon

Mental modelEnvironmentModel environment

System model


27


OO Programming Terminology

Encapsulation

Object

Message

Method

Class

Instance

Inheritance

Polymorphism

Dynamic (Late) Binding


CRC Method, class, responsibilities,

and collaborators

Method to learn

the most basic OO concepts plus OO “thinking”

“The most effective way of teaching the idiomatic way of thinking

with objects is to immerse the learner in the "object-ness" of the

material. To do this we must remove as much familiar material as

possible, expecting that details such as syntax and programming

environment operation will be picked up quickly enough once the

fundamentals have been thoroughly understood.”

Technique also very useful

during informal and creative analysis and design

Created by Kent Beck and Ward Cunningham,

Textronix, 1989


28


The CRC-Card

an object of paper personalizing the object

Class (Name):

Responsibility: Collaborators:


Class, responsibilities, and

collaborators

ClassThe class name of an object creates a vocabulary for discussing a design. Indeed, many people have remarked that object design has more in common with language design than with procedural program design. We urge learners (and spend considerable time ourselves while designing) to find just the right set of words to describe our objects, a set that is internally consistent and evocative in the context of the larger design environment.

Responsibilities Responsibilities identify problems to be solved. The solutions will exist in many versions and refinements. A responsibility serves as a handle for discussing potential solutions. The responsibilities of an object are expressed by a handful of short verb phrases, each containing an active verb. The more that can be expressed by these phrases, the more powerful and concise the design. Again, searching for just the right words is a valuable use of time while designing.

CollaboratorsObjects which will send or be sent messages in the course of satisfying responsibilities. Collaboration is not necessarily a symmetric relation. For example in Smalltalk, View and Controller operate as near equals while OrderedCollection offers a service with little regard or even awareness of its client.


29


UML og ( R )UP

Unified

Modeling

Language

Process

Convergence Today

Unification leads to “standards”

Convergencein the future

Process frameworks through consensus

Two parts of a Harmonized Whole


UML Structural Modeling

Class Diagram

Object Diagram

Component Diagram (new in UML 2.0)

Package Diagram

Deployment diagram


30


UML Behavioral Modelling

Use Case Diagrams

Interactions

Sequence diagrams (enhanced in UML 2.0)

Timing diagrams (new in UML 2.0)

Interaction overview diagrams (new in UML 2.0)

Communication diagrams (i.e. collaboration diagram)

State machine diagrams (enhanced in UML 2.0)

Activity Diagrams (enhanced in UML 2.0)


Different kind of models

Conceptual models

Specification models

Implementation models


31


Service Science

SSME: Service Science, Management & Engineering

Operations Research and Industrial Engineering More realistic models of people

Computer Science and Electrical Engineering, Information Systems Software and systems that adaptively change with business

strategy

Economics and Business Strategy, Service Management and Operations Better models of scaling and innovation

Law and Political Economy Better models of social innovation – in what way is passing a law

innovation

Complex Systems and Systems Engineering Better model of robustness and fragility of service systems

(sustainability)

Service systems are value co-

creation configurations of

people, technology, internal and

external service systems

connected by value propositions,

and shared information (such as

language, laws, measures,

models, etc.).

This is a multidisciplinary approach in

understanding, defining, creating and

delivering service systems


Service Science

New academic cross discipline

Definition of 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. (SoaML)

Service Innovation

Service Design

Service Engineering


32


SOA – Service oriented architecture

From Objects (1967 – 1995+)

To Components (1990-2000+)

To Services (2000- 2010+)


SOA

Services

Messages

Dynamic discovery

Web services


33


Service Oriented Architecture

(SOA) definition

A set of components which can be invoked, and whose

interface descriptions can be published and discovered

(W3C).

The policies, practices, frameworks that enable application

functionality to be provided and consumed as sets of

services published at a granularity relevant to the service

consumer. Services can be invoked, published and

discovered, and are abstracted away from the

implementation using a single, standards-based form of

interface. (CBDI) (www.cbdiforum.com)


Extended service-oriented architecture

Composition

Description & Basic Operations

Mana-gement

•Capability•Inteface•Behavior•QoS

•Coordination•Conformance•Monitoring•QoS

•Publication•Discovery•Selection•Binding

Service provider

Service client

Service aggregator

performs

publishes

uses

Role actions

becomes

Operations•Assurance•Support

Market•Certification•Rating•SLAs

Service operator

Market maker

Managed services

Composite services

Basic services

Composition

Description & Basic Operations

Mana-gement

•Capability•Inteface•Behavior•QoS

•Coordination•Conformance•Monitoring•QoS

•Publication•Discovery•Selection•Binding

Service provider

Service client

Service aggregator

performs

publishes

uses

Role actions

becomes

Operations•Assurance•Support

Market•Certification•Rating•SLAs

Service operator

Market maker

Managed services

Composite services

Basic services

Papazoglou and GeorgakopoulosCACM,Oct. 2003


34


Dealing with Complexity – and Change

Working at the right level of abstraction

OO dealing with complexity

objects -> components -> services *SOA

Design by contract, role composition

Aspect-oriented programming

Use of patterns

Visual Modeling (MDA)

Architecture


PhaseClass

TraditionalSA/SD/ERA

SA-based OO

ERA-based OO

Hybrid SA/ER-based OO

SA - Yordon SD - Page Jones

ERA - Chen ER-Rel.db - 3NF

OO RT SA - Wards

OOA/OOD - Coad/Yordon

OMT - Rumbaugh et. al

Fusion - HP

OOAD - Booch (93 w/C++)

HOOD - ESA

OOSD - WassermanSD-basert OO

OO-based

RDOOD - Wirfs-Brock et. al

CRC-cards - Cunningham

OOram - Reenskaug et. al

ANALYSIS DESIGN DETAILED DESIGN

OOAD - Martin/Odell

OSDL-92 - CCITT/Bræk et. al

OOSE/ObjectOry - Jacobson

Ada(C++)-based

SDL-based OO

UML (96)Booch/OMT/ObjectOry

OOAD methods

Catalysis, Syntropy, SOMA, OBA, BHS, ...


35


Evolution of the UML

Booch ´91

Booch ´93

Unified Method 0.8

UML 1.0

OMT - 2

OMT - 1 OOSE

UML 0.9 & 0.91

OOPSLA ´95

June ´96 & Oct ´96

Submission of UML 1.1 to OMG

for adoption, Sept ´97

Other methods

public

feedback UML Partners’

Expertise

UML 1.1 (Sept. 1997)

Taskon,SINTEF

UML 1.4UML 2.0

(2004)


Evolution of methodologies

UML1.0

UML1.1

UML1.2

UML1.3

UML1.4

OMT

Objectory

Booch

UML Components

Catalysis

OOram

KobrA

COMET

COMET-S

UML4EDOC

UML2

Pulse

UP

RUP

Notation

Process

2001

1995-

1999

2000

Objecteering

SOA


36


See also: www.soaml.org

Final version of SoaML

per October , 2010


SoaML UML Profile & Metamodel


37


Example: Marketplace Services

Order

Conformation

Ship Req

Shipped

Shipped

Physical

DeliveryDelivered

Status

Provider

Consumer

Pro

vid

erC

onsu

mer

Consumer

Provider

GetItThere Freight Shipper

Mechanics Are Us

DealerAcme Industries

Manufacturer


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.


38


Compound services


Participants may be assemblies of other Participants (UML 2.0)

Participant

Participant part

Service – capabilities

typed by

ServiceInterface

Request – needs

typed by

ServiceInterface


39


MOFScript placed in the 4-layer

metamodel architecture (MDE)MOF

Source Metamodel

Source model

MOFScript language

MOFScript transformation

Targettext

MOFScript tool

engine

executed by

input

output

conforms to conforms to

conforms to

based on

M1

M2

M3

conforms to


Project Management

Process Configuration

RequirementsAnalysis

ArchitectureLevel

Class Level

Implementation

Test

Design

preliminaryiteration(s)

iter.#1

PhasesProcessComponents

Iterations

Elaboration Construction TransitionInception

SupportingComponents

iter.#2

iter.#n

iter.#n+1

iter.#n+2

iter.#m

iter.#m+1

Unified Process Framework

Process Workflows

Business ModelingRequirements

Analysis Design

ImplementationTest

Deployment

Management

Conf. Mngmt

Environment

Supporting Workflows

Disciplines


40


Modelio SOA method and tool

support

79


Resource

Service

Tier

Business

Service

Tier

User

Service

Tier

User

Interface

Tier

LS

RARA

LA

Concepts & Artifacts

Processes

Actors Bu

sin

ess

do

main

“Real world”Model world

Web Services

model

Web Services

implementation

model

Web Services

profile

model

Business

model

Domain model

Risk

analysis

Product vision

& product desc.

Requirements

model

boundarySystem

boundary

model

Use caseScenario

model

Other

requirementsPrototype

BCE model

Service-Oriented Architecturemodel

Component

structure

model

Service

interaction

model

Service

interface

model.

Tech

nic

al

do

main

COMET-S and SiSaS model architecture


41


Interoperability Framework

ATHENA Interoperability Framework ( each system is described by

enterprise models and different viewpoints, such as business,

process, service, information)


Next Lecture – MDE I

January 31st, 2011

Metamodeling

Domain specific languages

Eclipse EMF and GMF, Kermeta

UML profiles

Intro: See Eclipse EMF/GMF tutorials

http://www.eclipse.org/modeling/

Kermeta: www.kermeta.org

http://www.eclipse.org/modeling/



42


INF5120 Tools– available on web




Kermeta: http://www.kermeta.org/

Eugenia – http://www.eclipse.org/gmt/epsilon/doc/eugenia/

See also: http://live.eclipse.org/node/575




SoaML - www.soaml.org




http://www.eclipse.org/gmt/epsilon/doc/eugenia/

http://live.eclipse.org/node/575





http://www.soaml.org/

inf5120 ”modellbasert systemutvikling” ”modelbased system … · inf5120 model based system...

Documents