model-driven specification of interoperable service ... · enterprise architecture and service...
TRANSCRIPT
1
ICT 1
INF5120
”Modellbasert Systemutvikling”
”Modelbased System development”
Lecture 5: 21.02.2011 SIE I: Service Innovation and CSI,
Enterprise Architecture and Service methodologies
Arne-Jørgen Berre
ICT
Outline
L5-1: Service Innovation (Per Pedersen, NHH)
An introduction to services, service science, service innovation
and new service development
L5-2: Enterprise Architecture and Models (AJB)
Zachman, TOGAF, DODAF-MODAF-NAF (UPDM)
VDM – Value Definition Metamodel
BMM - Business Motivation Model
BPMN 2.0 and SoaML
CMPM – Case Management Meta Model
2
ICT
Content
Enterprise Architecture Modeling
with OMG Standards – Implementing Enterprise
Architectures via UML Profiles
EA and the Zachman Framework
Architectural Frameworks - (IEEE/ 1471/ISO 42010, ADL,
UML 2.x, TOGAF, UPDM (DODAF/MODAF), SoaML
(SHAPE), DSLs)
UPDM
Service modeling and Service oriented views
Tool support , Metamodels and UML profiles – No Magic,
Magic Draw
3
ICT
Business Model Frameworks – with
Modeling support – from NEFFICS
4
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
3
ICT 5
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)
ICT
TOGAF 9
6
4
ICT
Open
Group
ADM
7
ICT 8
5
ICT
Building block evolution
9
ICT
Service categories
10
6
ICT
Why and When: Historical Development of AF’s.
C4ISR
Architecture
Framework
v1.0
C4ISR
Architecture
Framework
v2.0
DoDAF
v1.0
MODAF
v1.0
1996
1997
2003
2005
DoDAF
v1.5
2007
MODAF
v1.1
2007
NAF
v1.0
2005
Scope of UPDM 1.0
Approved Sept 2008
MODAF
Meta-Model (M3)
expressed using
UML Notation
MODAF
v1.2
2008
NAF
v3.1
2007
DoDAF
V2.0
2009
DNDAF
v1.7
2008
Scope of UPDM 2.0
Started Sept 2009
TOGAF1 - … TOGAF9
MACCIS
Norway
ICT
DODAF 2.0 - viewpoints
12
7
ICT
EAEA – European Air Traffic
Management Enterprise Architecture
13
ICT 14
OMG Model-Driven Architecture (MDA)
www.omg.org/mda
8
ICT
IEEE 1471, ISO 42010
15
ICT
Use of OMG metamodels
BPMN (BPMN 2.0)
BMM
UML 2.0
SoaML
OSM
VDM
Case Management
SBVR
ODM
16
9
ICT
Zachman with OMG standards
17
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
SBVR
List of processes that
the business performs
VDM
List of locations which
the business operates
VDM
List of organizations
important to the business
OSM
List of events/cycles
important to the business
DTFV
List of business
goals/strategies
BMM
Semantic Model
ODM,
IMM (CWM)
Business Process
Model
BPMN, CMPM
Business Logistics
System
BPMN, CMPM
Workflow Model
OSM, BPMN,
CMPM
Master Schedule
BPMN, CMPM,
DTFV
Business
Plan
SBVR
Logical Data Model
ODM,
IMM (CWM), UML
Application
Architecture
SoaML, UML
Distributed
System Architecture
SoaML, UML
Human Interface
Architecture
BPMN, CMPM
Process Structure
BPMN, CMPM,
DTFV
Business Rule
Model
SBVR
Physical Data Model
IMM (CWM), UMLSystem Design
SoaML, UML
Technology
Architecture
SoaML, UML
Presentation
Architecture
Control Structure
BPMN, CMPM,
DTFV
Rule
Design
SBVR
Data Definition
IMM (CWM), UMLProgram
UML
Network
Architecture
UML
Security
Architecture
Timing
Definition
DTFV
Rule
Definition
SBVR
Operation
(Instances)Data Function Network Organization Schedule Strategy
ICT
OMG standards coverage
18
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
10
ICT
UPDM coverage
19
Data
(What)
Function
(How)
Network
(Where) People
(Who)
Time
(When)
Scope
(Contexts)
Business
(Concepts)
System
(Logic)
Technology
(Physics)
Component (Assemblies)
Operation
(Instances)
Motivation
(Why)
BPMN
SoaML
UPDM
ICT
Model Based Systems
Engineering and Interoperability
Business Architecture (SysML Context + BPMN
2.0/BMM)
System & IT Service
oriented Architecture
(UML&SysML/SoaML)
Enterprise Architecture (EA) for
Systems of Systems
(UPDM)
Mo
de
lDrive
n
Arc
hite
ctu
re (
MD
A,O
slo
)
Inte
ropera
bili
ty
Arc
hite
ctu
re (
MD
I)
BMM
BPMN
VDM
CaseMgmt
OSM
SBVR
UML 2.0
SoaML
SysML
11
ICT
UPDM 1.0 is a standardized way of expressing DoDAF 1.5 and MODAF 1.2 artefacts using UML and SysML UPDM is NOT a new Architectural Framework
UPDM is not a methodology or a process
UPDM 2.0 is scheduled to address DoDAF 2.0, MODAF 1.2, NAF 3.x, and DNDAF 1.7
UPDM 1.0 was developed by members of the OMG with help from industry and government domain experts.
UPDM 1.0 has been implemented by multiple tool vendors. Tools supporting UPDM 1.0 are available now.
What is UPDM? - Summary
ICT
UPDM: UML Profile for
DoDAF and MODAF Context
Stakeholders
US DoD
UK MOD
NATO
Canada/Australia
OMG, INCOSE
OMG
XMI, UML, SysML
BPMN
UPMS, BMM
End Users
Aerospace
Commercial
Tool Vendors
Software
Systems
Enterprise
UPDM Domain Meta Model
UPDM Profile Meta Model
UPDM Profile
&
Library
UML4SysML SysML
Exte
rna
l
Re
fere
nce
s
Tra
nsfo
rma
tio
ns
CADM
IDEF
XMI
AP233
BPMN
SoaML
NAF Meta Model CADM 1.5
DoDAF 2.0 Ontology
UML
SysML Extensions
SoaML, BMM, SBVr
Extensions
<<import/merge>>
MODAF Meta Model
DoDAF 1.5 Concepts
SSDD
UJTL
etc.
CDD
SF List
CONOPS
Products -- Reports -- Simulations
BMM
12
ICT
UPDM
23
ICT
UPDM - – Unified Model for DODAF
and MODAF
24
13
ICT
UPDM – Unified Model for DODAF and MODAF
25
ICT
UPDM RFC - Domain Meta Model Summary
14
ICT
UPDM RFC - Domain Meta Model Summary
(Packages.)
Package structure organizes stereotypes by viewpoint
Multiple viewpoints manage model complexity
ICT
UPDM RFC - Domain Meta Model Summary
(AV)
15
ICT
Service innovation is inherently
multidisciplinary
Science &
Engineering
Business
Administration
and
Management
Social Sciences
Global
Economy
& Markets
Business
Innovation
Technology
Innovation
Social-Organizational
Innovation
Demand
Innovation
SSME = Service Sciences, Management, and Engineering
Knowledge sources driving service innovations…
ICT
Economic evolution of services
What was occurring during these time periods that may have influenced shifts in
economies and changes in business?
1800s
Classical and
Neoclassic
Pre-Industrial
Society
Primarily
agrarian
economies
Industrial
Society
Good
dominate
economies
Post-Industrial Society
Information, knowledge,
and quality of life
economies
1980s
Customer
fulfillment and
satisfaction
1970s
Marketing
management and
experts
1950s
Decision
marketing
school
1900 – 1950s
Early formative
marketing
2000s
Services
dominant logic
16
ICT
What is a service?
In economics and marketing, a service is the non-material equivalent of a good.
It is claimed to be a process that creates benefits by facilitating either a change in customers, a change in their physical possessions, or a change in their intangible assets.
By supplying some level of skill, ingenuity, and experience, providers of a service participate in an economy without the restrictions of carrying stock (inventory) or the need to concern themselves with bulky raw materials. On the other hand, their investment in expertise does require marketing and upgrading in the face of competition which has equally few physical restrictions.
Per Wikipedia (2006):
ICT
Service dominant view
Three primary notions
1. Co-creation of value
2. Relationships
3. Service provisioning
17
ICT
Service Architecture
33
ICT
ESA –
Enterprise
Service
Architecture
with
BPMN and
SoaML
34
Product
Report Diagram
Ac-V2
Programme
Timelines
Behavior
Matrix Table
AV-1
Overview
&Summary
Information
AV-2
Integrated
Dictionary
SOV-E2
SHAPESoaML
Service Interface
Diagram
(Instead of SOV-2
Service Interface
Specification)
All Views
Report
StV-3
Capability
Phasing
Structure
OV-1 high level
Operational
Concept
Graphic
OV-E2 Shape SoaML
Service Architecture
Diagram (Instead of
OV-2 Operational
Node Relationship
Description)
OV-E4 Organization
Structure
Metamodel(OSM)
(Instead of
Organizational
Relationships Chart)
OV-7 Information
Model
SOV-1 Service
Taxonomy
SV-1 Recource
Interaction
Specification
SV-2 Resource
Comunications
Description
StV-E1 SHAPE
SoaML
Business Goal
Diagram
Instead of StV-
1 Enterprise
Vision
StV-2
Capability
Taxonomy
StV-5
Capability to
Organization
Deployment
Mapping
StV-4
Capability
Dependencies
Ac-V1
Acquisition
Clusters
SV-8
Capability
Configuration
Managemnet
SV-11
Physical
Schema
OV-5
Operational
Activity
Model
OV-E6b
SHAPE
SoaML
BPMN(Inste
ad of OV-6b
Operational
State
Transition
Description)
OV-E6c
SHAPE SoaML
BPMN((Instead
of OV-6c
Operational
Event-Trace
Description)
SOV-4b
Service
State Model
SOV-4c
Service
Interaction
Specification
SOV-5
Service
Functionality
Flow SV-E10b SHAPE
SoaML
BPMN(Insteadof
SV-10b Resource
State Transition
Description)
SV-E10c
SHAPE SoaML
BPMN(Instead
of Resource
Event-Trace
Description)
SV-4
Functionality
Description
OV-3
Operational
Information
Exchange
Matrix
SOV-3
Capability to
Service
Mapping
StV-6
Operational
Activity to
Capability
Mapping
SV-12 Service
Provision
SV-3
Resource
Interaction Matrix
SV-5 Function
To Operational
Activity
Traceability
Matrix
OV-3
Operational
Information
Exchange Matrix
OV-E6a Shape
SoaML
BPMN (Instead
of Operational
Rules Modell)
SOV-4a
Service
Constraints
SV-10a
Resource
Constraints
Specification
SV-6 Systems
Data Exchange
Matrix
SV-7 Resource
Performance
Actural
Parameters
Matrix
SV-9
Technology &
Skills Forecast
TV-1
Standards
Profile
TV-2
Standards
Forecast
18
ICT
Enterprise SOA
35
ICT 36
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
PSM Implementation Models
CIM Business Models
PIM System Models
…
19
ICT 37
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
ICT 38
CIM – PIM – PSM methods in this INF5120 course
Information Service Process Rules Organization Goals NFA
CIM SM: 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
PSM Java and
Web services
(XML)
Java and
Web services
(WSDL)
Java and
Web services
(BPEL)
20
ICT
Core concept for BMM
ICT © Model
Systems,
September
2008
BMM and GRC 40
BMM Core Concepts
21
ICT 28.02.2011
41
SHAPE project and SoaML
UPMS SoaML
ICT 42
CIM to PIM to PSM
Flexible
business models Flexible
business models
Interconnected
heterogeneous
SOA platform
models
Interconnected
heterogeneous
SOA platform
models
Heterogeneous
SOA platforms
metamodels
Heterogeneous
SOA platforms
metamodels
Business
metamodels Business
metamodels flexible
Business Models
Business
metamodels
Semantically -
enabled
heterogeneous
SOA model
Unified and
standardised
metamodel for
SOA & SHA
Transformation
rules
Transformer
(engine)
according to
according to
transformation
engine
Transformation
rules
Transformer
(engine)
transformation
engine
Semantically -
enabled
heterogeneous
SOA platform
models
Semantically -
enabled
heterogeneous
SOA platform
metamodels
according to
EPC POP* BPDM, BPMN BMM …
Heterogeneous service platforms WSA JXTA OGSA JACK, JADE WSMO, WSMX …
Executable business 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
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
22
ICT 43
CIM-PIM-PSM Reference Matrix
ICT
SoaML Historikk
(Service oriented architecture
modeling language)
44
OMG RFP – September 2006
3 initial submissions – June 2007
Merge process in 2008 and 2009
SoaML 1.0 ferdigstilt desember 2009
SoaML 1.0 adopteres av OMG i mars 2010
FTF chairs: Arne J. Berre, SINTEF og Jim Amsden, IBM
http://www.soaml.org
23
ICT
VDM Metamodel
45
ICT
Value Network - Notations
46
24
ICT
VDM Metamodel
47
ICT 48
INF5120
”Modellbasert Systemutvikling”
”Modelbased System development”
Lecture 6: 28.02.2011 EPF, SPEM – Software Engineering Metamodels (Brian Elvesæter)
Lecture 7: 07.03.2011 BPMN 2.0
Arne-Jørgen Berre