Lecture 2: 26.01 - Universitetet i Oslo · Lecture 2: 26.01.2009 Arne-Jørgen Berre Telecom and...

46
INF5120 Model based System Development 26.01.2009 1 Telecom and Informatics 1 INF5120 BMM and BPMN ”Modelbased System development” Lecture 2: 26.01.2009 Arne-Jørgen Berre Telecom and Informatics 2 Lecture plan - 2009 1: 19/1: Introduction to MBSU, MDA, OO and Service/SOA modeling, Overall EA (AJB) 2: 26/1: MS I: Business Process Modeling (CIM) - with BPMN and BMM (AJB), Objecteering UML Modeler 3: 2/2: MS II: UML2 and SysML, Objecteering SOA and Scope, – Collaboration /Component models 4: 9/2: MDE I: Metamodeling , DSL and UML profiles, MDA technologies (XMI, Eclipse, EMF/GMF) (GO/BRE) 5: 16/2: MS III: SoaML I (PIM) and Requirements modeling , CIM->PIM, 6: 23/2: MS IV: Method Engineering and SPEM / EPF (BRE) 7: 2/3: MS V: SoaML II and Service Design (AJB) 8: 9/3: MDE II: Model transformations with MOScript, (ATL and QVT) – and JEE (GO) 9 :16/3:: MDE II: Code generation with MOFScript and other technologies (GO) 10: 23/3: MDE IV: PIM and Web Services teknologi (PSM) for SOA with WSDL/XML/BPEL (PSM) (BRE) 11: 30/3: MDI I: Model Driven Interoperability I (AJB) EASTER 12: 20/4: MDE V: Open ArchitectureWare/Kermeta, Microsoft OSLO etc. (Neil, Franck, Anthe) 13: 27/4: MDI II: Model Driven Interoperability - II - Ontologies, Semantic web and Semantic Modeling (AJB) 14: 4/5: Course summary Exam: May 29th, 2009 (Friday) AJB – Arne J. Berre BRE – Brian Elvesæter GO – Gøran Olsen

Transcript of Lecture 2: 26.01 - Universitetet i Oslo · Lecture 2: 26.01.2009 Arne-Jørgen Berre Telecom and...

INF5120 Model based System Development 26.01.2009

1

Telecom and Informatics 1

INF5120

BMM and BPMN

”Modelbased System development”

Lecture 2: 26.01.2009Arne-Jørgen Berre

Telecom and Informatics 2

Lecture plan - 2009

� 1: 19/1: Introduction to MBSU, MDA, OO and Service/SOA modeling, Overall EA (AJB)

� 2: 26/1: MS I: Business Process Modeling (CIM) - with BPMN and BMM (AJB), Objecteering UML Modeler

� 3: 2/2: MS II: UML2 and SysML, Objecteering SOA and Scope, – Collaboration /Component models

� 4: 9/2: MDE I: Metamodeling , DSL and UML profiles, MDA technologies (XMI, Eclipse, EMF/GMF) (GO/BRE)

� 5: 16/2: MS III: SoaML I (PIM) and Requirements modeling , CIM->PIM,

� 6: 23/2: MS IV: Method Engineering and SPEM / EPF (BRE)

� 7: 2/3: MS V: SoaML II and Service Design (AJB)

� 8: 9/3: MDE II: Model transformations with MOScript, (ATL and QVT) – and JEE (GO)

� 9 :16/3:: MDE II: Code generation with MOFScript and other technologies (GO)

� 10: 23/3: MDE IV: PIM and Web Services teknologi (PSM) for SOA with WSDL/XML/BPEL (PSM) (BRE)

� 11: 30/3: MDI I: Model Driven Interoperability I (AJB)

� EASTER

� 12: 20/4: MDE V: Open ArchitectureWare/Kermeta, Microsoft OSLO etc. (Neil, Franck, Anthe)

� 13: 27/4: MDI II: Model Driven Interoperability - II - Ontologies, Semantic web and Semantic Modeling (AJB)

� 14: 4/5: Course summary

� Exam: May 29th, 2009 (Friday)

� AJB – Arne J. Berre

� BRE – Brian Elvesæter

� GO – Gøran Olsen

INF5120 Model based System Development 26.01.2009

2

Telecom and Informatics

BMM and BPMN on the CIM level

ASPECT

LEVELInformation Service Process Rules Events Organization Goals NFA

CIM BPMN BMM

CIM2PIM

PIM

PIM2PSM

PSM

3

Telecom and Informatics

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.

INF5120 Model based System Development 26.01.2009

3

Telecom and Informatics

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).

Telecom and Informatics © Model

Systems, BMM and GRC

6

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

INF5120 Model based System Development 26.01.2009

4

Telecom and Informatics

Core concept for BMM

Telecom and Informatics © Model

Systems, BMM and GRC

8

BMM Core Concepts

INF5120 Model based System Development 26.01.2009

5

Telecom and Informatics

BMM meta-model in GMF

Telecom and Informatics

Buyers ends

INF5120 Model based System Development 26.01.2009

6

Telecom and Informatics

Sellers ends

Telecom and Informatics

Buyer’s means

INF5120 Model based System Development 26.01.2009

7

Telecom and Informatics

Seller’s means

Telecom and Informatics

High-Tech Marketing Business Plan

INF5120 Model based System Development 26.01.2009

8

Telecom and Informatics

High-Tech Marketing Business Plan

Telecom and Informatics

Business Motivation Model (BMM) with

MeansRealizations

INF5120 Model based System Development 26.01.2009

9

Telecom and Informatics

Buyer/Seller reference example

17

Telecom and Informatics

What is BPMN (Business Process

Modeling Notation) ?

INF5120 Model based System Development 26.01.2009

10

Telecom and Informatics

BPMN example

Telecom and Informatics

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.

INF5120 Model based System Development 26.01.2009

11

Telecom and Informatics

BPMN

(Business Process

Modeling Notation)

Telecom and Informatics

What is BPMN ?

INF5120 Model based System Development 26.01.2009

12

Telecom and Informatics

History for BPMN

Telecom and Informatics

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

,

Java

INF5120 Model based System Development 26.01.2009

13

Telecom and Informatics

BPMN requirements

Telecom and Informatics

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)

INF5120 Model based System Development 26.01.2009

14

Telecom and Informatics

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.

Telecom and Informatics

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.

INF5120 Model based System Development 26.01.2009

15

Telecom and Informatics

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.

Telecom and Informatics

BPMN Diagram elements

INF5120 Model based System Development 26.01.2009

16

Telecom and Informatics

Diagram elementer (2)

Telecom and Informatics

Activities

INF5120 Model based System Development 26.01.2009

17

Telecom and Informatics

Task

Telecom and Informatics

Sub-processes

INF5120 Model based System Development 26.01.2009

18

Telecom and Informatics

Events

Telecom and Informatics

Start Events

INF5120 Model based System Development 26.01.2009

19

Telecom and Informatics

Intermediate Events

Telecom and Informatics

Intermediate events (normal flow)

INF5120 Model based System Development 26.01.2009

20

Telecom and Informatics

Intermediate events (linked to Boundary)

Telecom and Informatics

End events

INF5120 Model based System Development 26.01.2009

21

Telecom and Informatics

Gateways

Telecom and Informatics

Exclusive Gateways

INF5120 Model based System Development 26.01.2009

22

Telecom and Informatics

Exclusive Gateways, based on data

Telecom and Informatics

Exclusive Gateways, based on events

INF5120 Model based System Development 26.01.2009

23

Telecom and Informatics

Inclusive Gateways

Telecom and Informatics

Complex Gateways

INF5120 Model based System Development 26.01.2009

24

Telecom and Informatics

Complex Gateways

Telecom and Informatics

Parallell Gateways

INF5120 Model based System Development 26.01.2009

25

Telecom and Informatics

Conectors

Telecom and Informatics

Sekvens flyt

INF5120 Model based System Development 26.01.2009

26

Telecom and Informatics

Conditions in sequece floww

Telecom and Informatics

Default sekvens flow

INF5120 Model based System Development 26.01.2009

27

Telecom and Informatics

Message flow

Telecom and Informatics

Associations

INF5120 Model based System Development 26.01.2009

28

Telecom and Informatics

Swim lanes

Telecom and Informatics

Pool

INF5120 Model based System Development 26.01.2009

29

Telecom and Informatics

Lanes

Telecom and Informatics

Artifacts

INF5120 Model based System Development 26.01.2009

30

Telecom and Informatics

Text annotations

Telecom and Informatics

Data objects

INF5120 Model based System Development 26.01.2009

31

Telecom and Informatics

Groups

Telecom and Informatics

Extended artifacts

INF5120 Model based System Development 26.01.2009

32

Telecom and Informatics

Normal flow

Telecom and Informatics

Link events

INF5120 Model based System Development 26.01.2009

33

Telecom and Informatics

Process leves

Telecom and Informatics

Data flow

INF5120 Model based System Development 26.01.2009

34

Telecom and Informatics

Exceptions

Telecom and Informatics

Compenations and transacations

INF5120 Model based System Development 26.01.2009

35

Telecom and Informatics

Loops

Telecom and Informatics

Timers

INF5120 Model based System Development 26.01.2009

36

Telecom and Informatics

Ad hoc processes

Telecom and Informatics

EPC og BPMN

EPCEPC

BPMN

INF5120 Model based System Development 26.01.2009

37

Telecom and Informatics

Orkestering versus Koreografi

Telecom and Informatics

Orkestrering

INF5120 Model based System Development 26.01.2009

38

Telecom and Informatics

Koreografi

Telecom and Informatics

Eksempel

INF5120 Model based System Development 26.01.2009

39

Telecom and Informatics

Prosess informasjon

Telecom and Informatics

Forslag

INF5120 Model based System Development 26.01.2009

40

Telecom and Informatics

BPMN Eksempler …

Telecom and Informatics

BPMN eksempel – Buyer/Seller

80

INF5120 Model based System Development 26.01.2009

41

Telecom and Informatics

Telecom and Informatics

INF5120 Model based System Development 26.01.2009

42

Telecom and Informatics

Telecom and Informatics

INF5120 Model based System Development 26.01.2009

43

Telecom and Informatics

Telecom and Informatics

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

INF5120 Model based System Development 26.01.2009

44

Telecom and Informatics

Telecom and Informatics

INF5120 Model based System Development 26.01.2009

45

Telecom and Informatics

Telecom and Informatics

INF5120 Model based System Development 26.01.2009

46

Telecom and Informatics

Telecom and Informatics 92

Next Lecture – February 2nd, 2009

� UML 2.0

� Collaboration Diagrams

� Port Connector Models and Components

� SysML

� Use of Softeam UML/BPMN modeling tool