”Modellbasert Systemutvikling” ”Modelbased System development” · INF5120 Model based...

INF5120 Model based System Development 24.01.2011

1

Telecom and Informatics 1

INF5120

”Modellbasert Systemutvikling”

”Modelbased System development”

Lecture 3: 30.01.2012 Arne-Jørgen Berre

[email protected] or [email protected]


INF5120 - Lecture plan - 2012

Part I: SSI – Service Innovation and Agile Service/Software Engineering

Part II: SSMDE – Model Driven Engineering

Part III – Model Driven Interoperability and ADM

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

2: 23/1: SIE I: Enterprise Architecture, Role modeling-Collaboration and Value Networks – Verna Allee (VNA)

3: 30/1: SIE II:: Business Process Modeling with BPMN 2.0 and Business Model Innovation - Peter Lindgren (BMI)

4: 6/2: SIE III: AT ONE – Service Design, Agile User-oriented design – with Use cases/stories and UI models

5: 13/2: SIE IV: Service modeling with SoaML – Service modeling - Design, patterns

6: 20/2: SIE V: Information Modeling with UML and Design with DCI - Design, patterns

7: 27/2: MDE I: Software Process Model Frameworks – Essence/SEMAT, SPEM, EPF and ISO 24744 –Shihong Huang/Brian Elvesæter

8: 5/3: MDE II: Metamodels, Domain specific languages and UML profiles (Franck Fleurey)

9: 12/3: MDE III: Metamodeling, MDLE and DSL Tools (EMF, GMF, ATL, Kermeta)

10: 19/3: MDE IV: Model transformations - MOFScript, QVT DSLs with examples

11: 26/3: MDE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud transformations

2/4, 9/4: EASTER

12: 16/4: MDE VI: User Interface Modeling – IFML etc. - ESITO

13: 23/4: MDI I: Semantic technologies, Ontologies and Semantic annotations , Rules/SBVR

14: 30/4: MDI II: Model Driven Service Interoperability

15: 7/5: MDI III: ADM and Migration to Cloud computing

16: 13/5: Conclusion and Summary for INF5120 - Preparation of Exam

Exam: Monday June 4th, 2011, 1430-1830 (4 hours)

mailto:[email protected]

mailto:[email protected]


2


INF5120 – Oblig/Exercise plan - 2012

1: 16/1: None

2: 23/1: Guest lecture: Value Networks – Verna Allee (VNA)

3: 30/1: Guest lecture: Business Model Innovation - Peter Lindgren (BMI) – Establish groups

4: 6/2: AT ONE initial exercise – overall approach for Oblig 1 – “myServiceFellow”

5: 13/2: Group presentation



8: 5/3: MDE Tools – introduction – Oblig 2 intro

9: 12/3: MDE Tools II - EMF

10: 19/3: MDE Transformation tools

11: 26/3: MDE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud transformations

2/4, 9/4: EASTER

12: 16/4: MDE User Interface tools – ESITO o.a.

13: 23/4: Oblig 2 questions

14: 30/4: Oblig 2 delivery

15: 7/5: Oblig 2 summary

16: 13/5: Conclusion and Summary for INF5120 - Preparation of Exam

Exam: Monday June 4th, 2011, 1430-1830 (4 hours)

Telecom and Informatics

Outline

SiSaS methodology, sisas.modelbased.net

Oblig 1

NEFFICS methodology, neffics.modelbased.net

BPMN 2.0

Business Model Innovation


3


SiSaS – SINTEF Software as a Service

Methodology, sisas.modelbased.net

5


SiSaS – Disciplines and Practices

6


4




5


Oblig 1 – Group work – Service

Innovation and Design

9

Service Innovation and Design - for the Informatics Department

and students at the University of Oslo

-Value Networks (23/1)

-BPMN processes (30/1)

-Business Model Innovation (30/1)

-AT ONE methodology (6/2)

-Service Innovation/identification/design/specification (13/2)

-Any areas for innovative services/apps/applications ?

-Use Modelio UML tool, www.modeliosoft.com

-Establish groups today


Oblig 1 – Group work – Service

Innovation and Design

10

Service Innovation and Design - for the Informatics Department

and students at the University of Oslo

Groups of 2-4 persons

Select one focus area within the processes and services of Ifi that you

would like to concentrate on. Course registration, Course interaction,

Study lab, ….. Consider all touchpoints between you and Ifi.

http://www.modeliosoft.com/


6


BPMN

(Business Process

Model and Notation)


What is BPMN ?


7


BPMN example


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, …


8


BPMN History

16

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/


History for BPMN


9


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


BPMN requirements


10


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)


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.


11



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.



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.


12


BPMN Diagram elements


Diagram elements (2)


13


Activities


Task


14


Sub-processes


Events


15


Start Events


Intermediate Events


16


Intermediate events (normal flow)


Intermediate events (linked to Boundary)


17


End events


Gateways


18


Exclusive Gateways


Exclusive Gateways, based on data


19


Exclusive Gateways, based on events


Inclusive Gateways


20


Complex Gateways


Complex Gateways


21


Parallell Gateways


Conectors


22


Sequence flow


Conditions in sequence flow


23


Default sequence flow


Message flow


24


Associations


Swim lanes


25


Pool


Lanes


26


Artifacts


Text annotations


27


Data objects


Groups


28


Extended artifacts


Normal flow


29


Link events


Process leves


30


Data flow


Exceptions


31


Compenations and transacations


Loops


32


Timers


Ad hoc processes


33


EPC og BPMN

EPC EPC

BPMN


Orchestration versus Choreography


34


Orkestrering


Koreografi


35


Eksempel


Prosess informasjon


36


Forslag


BPMN Eksempler …


37




38




39



Example – doctor’s office

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


40




41




42



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


43


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.


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.


44


Collaboration diagram example


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.


45


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.


Content

EA and the Zachman Framework

Architectural Frameworks - (IEEE/ 1471/ISO 42010, UML

2.x, TOGAF, UPDM (DODAF/MODAF)

OO Modeling and abstraction levels

Role modeling

UML Collaboration modeling

GRASP - General Responsibility Assignment Software

Patterns

VNA – Value Network Analysis, Verna Allee

103


46


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 (IBM, 1987)



47


Use of OMG metamodels

BPMN (BPMN 2.0)

BMM

UML 2.0

SoaML

OSM

VDM

Case Management

SBVR

ODM

106


OMG standards coverage

107

Data

(What)

Function

(How)

Network

(Where)

People

(Who)

Time

(When)

Motivation

(Why)

Scope

(Contexts)

Business

(Concepts)

System

(Logic)

Technology

(Physics)

Component

(Assemblies)

List of things

important

to business

List of processes

that the business

performs

List of locations

which the business

operates

List of organizations

important to the

business

List of events/cycles

important to the

business

List of business

goals/strategies

Semantic Model

Business

Process

Model

Business

Logistics

System

Workflow

Model

Master

Schedule

Business

Plan

Logical Data ModelApplication

Architecture

Distributed

System

Architecture

Human

Interface

Architecture

Process

Structure

Business Rule

Model

Physical Data Model System DesignTechnology

Architecture

Presentation

Architecture

Control

Structure

Rule

Design

Data Definition ProgramNetwork

Architecture

Security

Architecture

Timing

Definition

Rule

Definition

Operation

(Instances)Data Function Network Organization Schedule Strategy

BMM

SBVR

VDM OSMSBVR

DTFV

BPMN

UMLIMM

(CWM)

CMPM

SoaML

ODM


48


Context and Goals

Interactions

Interface

Channels

Roles

Actors

Resources

Functions

Tasks

Executors

Processes

Orchestra- tion

Workflows

Information

Data

Stores and

Messages

EFA

Extra

Functional

Aspects

QoS

SLA

Monitoring,

adaptation

Inte

ract

ion

Requirements

Funct

ion

Co

ord

inat

ion

Info

rmat

ion

Qual

ity

Design

Implementation

Infrastructure

Str

uct

ure

BPMN Role

Models SoaML UML

Class

Ontologies

Goal oriented

Use cases/stories

UI OCL

collaboration

ASD

Framework

with

INF5120

Modeling

techniques

Model Driven Architecture/MDE


The Alexander Osterwalder canvas

Businss Model Innovation


49


www.businessmodelgeneration.com

110


www.businessmodelgeneration.com


50


www.neffics.eu

EU project, 2010-2013, 4 Meuro, led by SINTEF & Induct


Business Model Innovation

113

Peter Lindgren,

Univ. of Aalborg

Denmark


51


Business Model Frameworks – with

Modeling support – from NEFFICS

114

Building block Incremental innovation

‘Do what we do but better’

Radical innovation

‘Do something different’

Value proposition Offering ’more of the same’ Offering something different (at least to the

company)

Target customer Existing market New market

Value chain

architecture

[Internal]

Exploitation (e.g. internal, lean,

continuous improvements)

Exploration (e.g. open, flexible, diversified)

Competences Familiar competences (e.g.

improvement of existing technology,

HR, organizational system, culture)

Disruptively new, unfamiliar, competences (e.g.

new emerging technology, new HR skills,

organizational systems, culture)

Network Partners Familiar (fixed) network New (dynamic) networks (e.g. alliance, joint-

venture, community)

Relations Continuous improvements of existing

relations (e.g. channels)

New relations, relationships (e.g. channels

physical, digital, virtual, personal)

Profit formula Existing processes to generate

revenues followed-by/or incremental

processes of retrenchments and cost

cutting

New processes to generate revenues followed-

by /or disruptive processes of retrenchments and

cost cutting


NEFFICS BMI (1/2)


52


NEFFICS BMI (2/2)


Basis for

VDML

standardisation

Organization

Model

Capability

Model

Business

Model

REA-Resource

Event Agent

Value Network

Value Stream

Porter Value

Chain

VDML

Shared

Services


53


Relations

Profit formula (Cost+Revenue)

Target customers

Competences

Network

Value chain

Value proposition

Osterwalder versus NEFFICS

+ new idea: Enhance role collaborations (with value networks)

as a focal point for relations – supporting enactement and simulation of the model

REA (ownership - POA)

Value stream Value network

Role collaborations


Next Lecture – February 6th, 2012

Service Innovation and Design

AT ONE

Requirements modeling and Use cases – User stories

Service Design, Service Innovation and User Experiences

Oblig 1 further details …

”Modellbasert Systemutvikling” ”Modelbased System development” · INF5120 Model based...

Documents

Transcript of ”Modellbasert Systemutvikling” ”Modelbased System development” · INF5120 Model based...