”modellbasert systemutvikling” ”modelbased system development” · ”modellbasert...

65
1 ICT 1 INF5120 ”Modellbasert Systemutvikling” ”Modelbased System development” Lecture 6: 01.03.2010 Business Process Modeling with BPMN and Goal Modeling with BMM (CIM Modeling), EA with UPDM 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)

Upload: dothuy

Post on 20-Nov-2018

236 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

1

ICT 1

INF5120

”Modellbasert Systemutvikling”

”Modelbased System development”

Lecture 6: 01.03.2010Business Process Modeling with BPMN and Goal Modeling with

BMM (CIM Modeling), EA with UPDM

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)

Page 2: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

2

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

L6-1: CIM-PIM-PSM and BMM/BPMN

Modelio tool support

BMM and Goal modeling

BPMN intro

L6-2: BPMN and BPMN 2.0

Page 3: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

3

ICT 5

CIM to PIM to PSM

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

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

se

rvic

e- o

rie

nte

d a

sp

ec

ts t

o c

ap

ture

in

mo

de

ls

Wh

ich

me

tam

od

els

an

d la

ng

ua

ge

s t

o u

se

CIM

PIM

PSM

UPMSHA Agents

Grid

Semantic Web

Services

Service

Variability

Web

Services

P2P

Flexible

Business Models

Heterogeneous

Platforms

ICT

Short course methodology

CIM modeling

CIM 2 PIM mapping

PIM modeling

PIM 2 PSM mapping

PSM modeling

6

Page 4: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

4

ICT 7

CIM – PIM - PSM

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

ICT 8

CIM-PIM-PSM Reference Matrix

Page 5: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

5

ICT

Use of OMG metamodels

BPMN (BPMN 2.0)

BMM

UML 2.0

SoaML

OSM

VDM

Case Management

SBVR

ODM

9

ICT 10

CIM – PIM – PSM methods

Information Service Process Rules Events Organization Goals NFA

CIM

Total: 40

Sources: ESIM,

SCM, SM, ISE,

ESOA, Cyc,

DILIGENT,

EOnto, MethOnto,

NeOn, OTK,

TOVE,

GERAM,ARIS,

EUP, COMET-S

Total: 25

Sources:

ESIM, SM, SCM,

SMART, SOMA,

ISE, ESOA,

GERAM,ARIS,

EUP COMET-S,

OGSOA

Total: 23

Sources: ESIM,

SAE,SCM, SM,

SMART, SOAD,

SOMA, ISE,

ESOA,

GERAM,ARIS,

EUP, COMET-S,

OGSOA

Total: 14

Sources: ESIM,

SM, SOMA, ISE,

ESOA, Cyc,

GERAM, EUP

Total: 4

Sources:

GERAM, EUP

Total: 15

Sources: ESIM,

SAE, SM,

SMART, SOMA,

ISE, ESOA,

GERAM,ARIS,

EUP

Total: 17

Sources: ESIM,

SM, SMART,

SOMA, ISE,

ESOA,

GERAM,ARIS,

EUP, COMET-S

Total: 11

Sources: ESIM,

SCM, SM,

SOMA, ISE,

ESOA, GERAM

CIM2PIM

Total: 1

Sources:

COMET-S

Total: 1

Sources:

COMET-S

Total: 1

Sources:

COMET-S

PIM

Total: 10

Sources: ESIM,

SCM, SM,

SMART, SOMA,

ISE, ESOA,

COMET-S,

OASIS

Total: 19

Sources: ESIM,

SAE, SCM,

SMART, SOAD,

SOMA, ISE,

ESOA, COMET-

S, OASIS,

OGSOA

Total: 21

Sources: ESIM,

SAE, SCM,

SMART, SOAD,

SOMA, ISE,

ESOA, OASIS,

OGSOA

Total: 7

Sources:

SMART, ISE,

ESOA

Total: 1

Sources: OASIS

Total: 6

Sources:

SMART, ESOA

Total: 1

Sources: SMART

Total: 10

Sources: ESIM,

SCM, SMART,

SOMA, ISE,

ESOA, OASIS

PIM2PSM

Total: 1

Sources:

COMET-S

Total: 3

Sources: ESOA,

COMET-S

Total: 2

Sources: ESOA

Total: 2

Sources: ESIM,

ESOA

Total: 1

Sources: ESIM,

Total: 1

Sources: ESIM,

Total: 1

Sources: ESIM,

PSM

Total: 11

Sources: ESIM,

SCM, SM,

SOAD, SOMA,

ISE, ESOA

COMET-S

Total: 21

Sources: ESIM,

SAE, SCM, SM,

SOAD, SOMA,

ISE, ESOA,

COMET-S

Total: 19

Sources: ESIM,

SAE, SCM, SM,

SOAD, SOMA,

ISE, ESOA

Total: 7

Sources: SM,

SOAD, SOMA,

ISE, ESOA

Total: 1

Sources: SOAD

Total: 4

Sources: SAE,

SM, SOAD

Total: 1

Sources: SOAD

Total: 5

Sources: SM,

SOMA, ESOA

Page 6: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

6

ICT 11

CIM – PIM – PSM methodsin this INF5120 course

Information Service Process Rules Organization Goals NFA

CIMSM: Dictionary

OSOA: Business

semantic model

SoaML

collaboration

diagram

BPMN SM: Business

rules

OSOA: Business

organisation

model

SM: Goals SM:

Requirements

CIM2PIM

manual

PIM

UML Class

diagram

SoaML

OSOA

UML Activitiy

diagrams,

sequence

diagrams, BPMN

PIM2PS

M

Objecteering

& MOFScript

Objecteering

& MOFScript

Objecteering

& MOFScript

PSMJava and

Web services

(XML)

Java and

Web services

(WSDL)

Java and

Web services

(BPEL)

ICT

CIM MODELING

12

Page 7: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

7

ICT

Modelio Scope Manager

Requirements

Goals

Business rules

Dictionaries

13

ICT

Requirements

14

Page 8: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

8

ICT

Goals

15

ICT

Business rules

16

Page 9: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

9

ICT

Dictionary

17

ICT

Traceability links

18

Page 10: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

10

ICT

CIM 2 PIM MAPPING

19

ICT

Process and use case relationship

20

Page 11: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

11

ICT

PIM MODELING

21

ICT

Modelio with SoaML and manual

mapping to SOA

Use the SoaML MDA component for SoaML modeling

Do manual mapping to the Objecteering Logical SOA

model Software model

(See separate SoaML presentation) next week

22

Page 12: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

12

ICT

Modelio SOA model

Business semantic model

Business organisation model

Logical model (from SoaML to SOA)

Business implementation model;

Software model

(See Modelio user guide/demonstration)

23

ICT

Objecteering SOA method and tool

support

24

Page 13: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

13

ICT

Objecteering for SOA

25

ICT 26

Current Component Architecture

Eclipse 3.4

WSMT

Plugins

ObjecteeringSoaML

model

PIM4Agents Solution

Plugins

Semantic

Web

Services

SoaML Plugins

(default tree editor)

UML2 SoaML

Profiled

model

Jack / Jade

CIMFlex Plugins

Tra

ce

ab

ility (S

INT

EF

)

Web

Services J2EE

SINTEF Composition

Studio

Grid / P2P

Page 14: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

14

ICT 27

Example mapping sequence

CIM BPMN with Objecteering

CIM2PIM Use case analysis and

Manual (later by MOFScript or ATL ?)

PIM SoaML – Objecteering

(Collaboration (serv.arch),

Port/Connector)

PIM2PIM Manual (later by MOFScript or ATL ?)

PIMs Objecteering SOA

PIM2PSM Draft automatic:

Java API and Design Patterns

PSM Web Services SOA:

UML Profiles for XML, WSDL, BPEL

PSM2Code Draft automatic: Java

Code SOA: XML, WSDL, BPEL

ICT

Architectural layers

28

Page 15: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

15

ICT

Different types of services

29

ICT 30

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 model architecture

Page 16: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

16

ICT

Logical architecture layers

31

ICT

Process component

32

Page 17: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

17

ICT

BMM and BPMN on the CIM level

ASPECT

LEVELInformation Service Process Rules Events Organization Goals NFA

CIM BPMN BMM

CIM2PIM

PIM

PIM2PSM

PSM

33

ICT

Business Motivation Model

The Business Motivation Model (BMM) is a meta-model of the

concepts essential for business governance.

underlying principle is ―Businesses are driven, not by change, but by

how they decide to react to change‖

vocabulary for governance

influencer

assessment

business policy

strategy

tactic

goal

Governance

Governance is necessary for the

successful adoption of SOA partly

because of the cross-

organizational nature of SOA

where service funders, designers,

implementers, maintainers, or

consumers are not located in the

same organization, business, IT

department, LOB, division, or

enterprise.

Page 18: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

18

ICT

two major areas of the Business

Motivation Model

The first is the Ends and Means of business plans. Among the Ends

are things the enterprise wishes to achieve — for example, Goals and

Objectives. Among the Means are things the enterprise will employ to

achieve those Ends — for example, Strategies, Tactics, Business

Policies, and Business Rules.

The second is the Influencers that shape the elements of the business

plans, and the Assessments made about the impacts of such

Influencers on Ends and Means (i.e., Strengths, Weaknesses,

Opportunities, and Threats).

ICT © Model

Systems, BMM and GRC36

Simplified View of BMM

Influencers Assessments

Ends

Means

Courses of

Action

Directives

What you

decided your

Enterprise

should do

Govern the

Courses of

Action

Business Operations

- Business Processes

- Business Rules

- Responsibilities

- Resources

- Services

References to

Page 19: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

19

ICT

Core concept for BMM

ICT © Model

Systems, BMM and GRC38

BMM Core Concepts

Page 20: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

20

ICT

BMM meta-model in GMF

ICT

Buyers ends

Page 21: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

21

ICT

Sellers ends

ICT

Buyer’s means

Page 22: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

22

ICT

Seller’s means

ICT

High-Tech Marketing Business Plan

Page 23: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

23

ICT

High-Tech Marketing Business Plan

ICT

Business Motivation Model (BMM) with

MeansRealizations

Page 24: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

24

ICT

Buyer/Seller reference example

47

ICT

What is BPMN (Business Process

Modeling Notation) ?

Page 25: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

25

ICT

BPMN example

ICT

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.

Note: This is also a Business Process – for Software dev.

Page 26: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

26

ICT

BPMN

(Business Process

Modeling Notation)

ICT

BPMN 2.0 and SoaML tools today

BPMN 2.0

Signavio has 2.0 Conversation and Choreography diagrams – a

SaaS solution

Most BPMN 1.2 are doing stepwise migration, making existing

parts 2.0 compliant

SoaML (in most UML tools)

Magic Draw (Cameo), Enterprise Architect, IBM RSA/RSM,

Modelio, …

Page 27: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

27

ICT

BPMN History

54

BPMN 1.0 (BPMI) – Mai 2004

BPMN1.x

BPMN 1.1 (OMG) – Januar 2008

BPMN 1.2 (OMG) – Januar 2009

BPMN 2.0 final Juni 2010

http://www.omg.org/spec/BPMN/2.0/

ICT

What is BPMN ?

Page 28: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

28

ICT

History for BPMN

ICT

BPMI.org Hourglass

Business Environment

Technology Implementation

BP

BPMN

BPEL

Focus Scope

Strategy Consultants

Process Designers

System Architects

Software Engineers

Business Analysts

Audiences: Purposes:

Execution

Modeling

Page 29: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

29

ICT

BPMN requirements

ICT

Core Set of Diagram Elements

The core set of modeling

elements enable the easy

development simple

Business Process

Diagrams that will look

familiar to most Business

Analysts (a flowchart

diagram)

Page 30: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

30

ICT

Complete Set of Diagram

Elements, Events

An Event is something

that ―happens‖ during the

course of a business

process. These Events

affect the flow of the

Process and usually have a

trigger or a result. They can

start, interrupt, or end the

flow.

ICT

Complete Set of Diagram

Elements, Activities, Cont.

A Sub-Process can be in

an expanded form that

shows the process details

of the a lower-level set of

activities.

Page 31: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

31

ICT

Complete Set of Diagram

Elements, Gateways

Gateways are modeling

elements that are used to

control how Sequence

Flows interact as they

converge and diverge within

a Process. If the flow does

not need to be controlled,

then a Gateway is not

needed.

ICT

BPMN Diagram elements

Page 32: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

32

ICT

Diagram elementer (2)

ICT

Activities

Page 33: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

33

ICT

Task

ICT

Sub-processes

Page 34: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

34

ICT

Events

ICT

Start Events

Page 35: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

35

ICT

Intermediate Events

ICT

Intermediate events (normal flow)

Page 36: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

36

ICT

Intermediate events (linked to Boundary)

ICT

End events

Page 37: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

37

ICT

Gateways

ICT

Exclusive Gateways

Page 38: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

38

ICT

Exclusive Gateways, based on data

ICT

Exclusive Gateways, based on events

Page 39: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

39

ICT

Inclusive Gateways

ICT

Complex Gateways

Page 40: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

40

ICT

Complex Gateways

ICT

Parallell Gateways

Page 41: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

41

ICT

Conectors

ICT

Sequence flow

Page 42: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

42

ICT

Conditions in sequece floww

ICT

Default sekvens flow

Page 43: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

43

ICT

Message flow

ICT

Associations

Page 44: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

44

ICT

Swim lanes

ICT

Pool

Page 45: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

45

ICT

Lanes

ICT

Artifacts

Page 46: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

46

ICT

Text annotations

ICT

Data objects

Page 47: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

47

ICT

Groups

ICT

Extended artifacts

Page 48: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

48

ICT

Normal flow

ICT

Link events

Page 49: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

49

ICT

Process leves

ICT

Data flow

Page 50: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

50

ICT

Exceptions

ICT

Compenations and transacations

Page 51: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

51

ICT

Loops

ICT

Timers

Page 52: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

52

ICT

Ad hoc processes

ICT

EPC og BPMN

EPCEPC

BPMN

Page 53: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

53

ICT

Orkestering versus Koreografi

ICT

Orkestrering

Page 54: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

54

ICT

Koreografi

ICT

Eksempel

Page 55: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

55

ICT

Prosess informasjon

ICT

Forslag

Page 56: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

56

ICT

BPMN Eksempler …

ICT

Page 57: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

57

ICT

ICT

Page 58: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

58

ICT

ICT

Page 59: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

59

ICT

Eksempel - legekontor

A text description of the choreography was presented as so:

1) Patient send a "I want to see doctor" message to the Receptionist

2) Receptionist send a "Are you available ?" message to a a list of

Doctors

3) One doctor send a "I'm available" message to the Receptionist.

4) Receptionist send a "I'll book you" message to the Doctor.

5) Receptionist send a "Go see doctor" message to the Patient

6) Patient send a "I feel sick" message to Doctor

7) Doctor send a "Prepare this medicine" message to Receptionist

8) Doctor send a "Pickup your medicine and you can leave" message

to Patient

9) Patient send a "I need my medicine" message to Receptionist

10) Receptionist send a "Here is your medicine" message to Patient

ICT

Page 60: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

60

ICT

ICT

Page 61: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

61

ICT

ICT

Page 62: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

62

ICT

BPMN 2.0: Major changes from

BPMN1.x Notational changes

New diagrams for Choreography and Conversation

New event-types (escalation, …)

Non-interrupting events

Event sub-process

Call Activity– replaces linked/reusable activity

Technical changes Formal metamodel – specified in UML

Interchange formats for semantic model interchange (XMI, XSD)

Interchange formats for diagram interchange (XMI, XSD)

XSLT transformations between XMI and XSD formats

ICT

Process diagram

Flowchart view

to sequence

activities within

an organization

Support the

modeling of

simple

processes

Enhanced by

BPMN to handle

more complex

concepts, such

as exception

handling,

transactions, and

compensation.

Page 63: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

63

ICT

Collaboration diagram

Provides a view

of the

interactions (flow

of messages)

between two or

more business

partners

(Participants).

Collaborations

can be combined

with Processes

to show how the

interactions are

related to the

internal Process

activities.

ICT

Collaboration diagram example

Page 64: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

64

ICT

Conversation diagram

example Allows a modeler

to group

Collaboration

interactions

between two or

more Participants,

which together

achieve a

common goal, e.g.

―negotiate

delivery‖

The grouping can

be based on

business keys

such as customer

id or shipping id.

ICT

Corresponding choreography

example• Provides a flowchart view to

sequence interactions between

Participants

• Choreographies define a

―business contract‖ or protocol to

which the Participants agree to

follow during real-time

interactions.

Page 65: ”Modellbasert Systemutvikling” ”Modelbased System development” · ”Modellbasert Systemutvikling” ”Modelbased System development ... (PIM) and Requirements modeling ,

65

ICT 142

Next Lecture – March 8th, 2010

SoamL

UML 2.0 - Collaboration Diagrams

UML 2.0 Port Connector Models and Components

SysML

Service Science – IBM, Jørn Berg Nordlund