INF5120 Model based System Development 16.01.2012
1
Telecom and Informatics 1
INF5120
”Modellbasert Systemutvikling”
”Modelbased System development”
Lecture 1: 16.01.2012 Arne-Jørgen Berre
[email protected] and [email protected]
Telecom and Informatics 2
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
Guest lecturers
Email: [email protected]
Responsible for Obligatory exercises:
Tore Vatnan, Weiqing Zhang, …
Email: [email protected]
INF5120 Model based System Development 16.01.2012
2
Telecom and Informatics
3 parts of the course
SSI (Service Innovation and Service Engineering)
MDE I-V (Model Driven Engineering)
MDI I-II (Model Driven Interoperability)
Each part will have separate handbook/material
3
Telecom and Informatics 4
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: Service Innovation, Enterprise Architecture and Value Networks – Verna Allee (VNA)
3: 30/1: SIE II:: Business Architecture and Business Process Modeling with BPMN 2.0 - 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: MDE I: Metamodels, Domain specific languages and UML profiles
6: 20/2: SIE IV: Service modeling with SoaML – Service modeling - Design, patterns
7: 27/2:SIE V: Information Modeling with UML and Design with DCI - Design, patterns
8: 5/3: MDE II: Metamodeling, MDLE and DSL Tools (EMF, GMF, ATL, Kermeta)
9: 12/3: MDE III: Model transformations - MOFScript, QVT
10: 19/3: MDE IV: ThingML and CloudML with examples
11: 26/3: MDE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud
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)
INF5120 Model based System Development 16.01.2012
3
Telecom and Informatics 5
Next Lecture – Enterprise Architecture and
Value Networks. January 23rd, 2012
Enterprise Architecture
Business Architecture
IT Architecture
VNA – Value Network Analysis (Guest lecture by Verna
Allee)
See online book: Value Netwoks and the true value of
Collaboration – by Verna Allee (chapter 1 and 2)
http://www.valuenetworksandcollaboration.com
Telecom and Informatics 6
Exam
Case-based (ref. earlier exams)
All written material can be used
1330-1830 (4 hours) –
Monday June 4th, 2012
INF5120 Model based System Development 16.01.2012
4
Telecom and Informatics 7
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
Telecom and Informatics 8
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.
INF5120 Model based System Development 16.01.2012
5
Telecom and Informatics 9
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)
Telecom and Informatics 10
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)
INF5120 Model based System Development 16.01.2012
6
Telecom and Informatics
Value Network Analysis
11
http://www.valuenetworksandcollaboration.com
Telecom and Informatics
Agile Service Development (1/3)
12
New book – in the publishing process until April 2012, Springer.
We will use a publication preprint initially
INF5120 Model based System Development 16.01.2012
7
Telecom and Informatics
Agile Service Development (2/3)
13
Telecom and Informatics
Agile Service Development (1/3)
14
INF5120 Model based System Development 16.01.2012
8
Telecom and Informatics
Open Services Innovation
Book:
January 2011
Telecom and Informatics
Software engineering practices and
methods
modelbased.net
practices.modelbased.net
A practices framework, SEMAT, www.semat.org
16
INF5120 Model based System Development 16.01.2012
9
Telecom and Informatics 17
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
Telecom and Informatics 18
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
INF5120 Model based System Development 16.01.2012
10
Telecom and Informatics
Kermeta – www.kermeta.org
19
Telecom and Informatics 20
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
INF5120 Model based System Development 16.01.2012
11
Telecom and Informatics
Change in course in 2012 We will now start with the practical modeling part, Agile
Service Engineering – before focusing on the MDE –
Model Driven Engineering part – giving the introduction to
modeling earlier in the course.
We will continue with the use of the Kermet Metamodel
environment, on top of EMF, instead of only focusing on
GMF.
In March we will focus on Model Driven Engineering, and
in April we will introduce the additional topics of Semantic
Web/services and Model Driven Interoperability (MDI) –
and Architecture Driven Modernisation (ADM) – before a
final conclusion of the course
21
Telecom and Informatics
New in 2012 Continued focus on “Service Science” – with Service
Innovation (with BI/NHH), Service Design (OAH) and
Service Engineering (UIO)
VNA – Value Network Analysis, Verna Allee
New standard: OMG MDA standard: VDML, FACESEM
Service Design: AT ONE
Business Model Innovation: Osterwalder/Lindgren
22
INF5120 Model based System Development 16.01.2012
12
Telecom and Informatics
New in 2011
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.
23
Telecom and Informatics
Which OMG modeling standards will
you learn ?
VDML – Value Delivery Modeling Language – with VNA
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
24
INF5120 Model based System Development 16.01.2012
13
Telecom and Informatics
Which tools/environments will you
learn ? VNA – Value Network Analysis
BMI – Business Model Innovation/Generation
AT ONE – Service Design
Modelio UML Modeler (BPMN, UML 2, SysML)
Modelio SOA Solution (SoaML)
Eclipse EMF and XMI, Principles of GMF
EuGENia – for GMF
MOFScript (Model2Text, Model2Model)
EPF/SPEM Software Process Modeler
Overview of ATL, KerMeta, OpenArchitectureWare-OAW,
Microsoft OSLO
Ref. also IBM RSA/RSM, Enterprise Architect, Magic Draw
supporting SoaML and BPMN 25
Telecom and Informatics
OBLIG 1: – “Service Analysis and Design
for University of Oslo – Institute for
Informatics” – with group presentations
Value Network Analysis
Business Model Innovation
AT ONE – Service Design
Business Process Modeling – BPMN
Select Service Innovation area with potential IT support
Design and Specify Service
Service Modeling with SoaML
26
INF5120 Model based System Development 16.01.2012
14
Telecom and Informatics
OBLIGS: – “MDE tools in practice”
Oblig 2 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
27
Telecom and Informatics
OBLIG 2a: – “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
28
INF5120 Model based System Development 16.01.2012
15
Telecom and Informatics
OBLIG 2b – “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
29
MOFScript transformations to Java and potentially to
different technologies/platforms
Discussion on Model Driven Interoperability
Telecom and Informatics 30
Requirements for the course
Student at UIO
Only assumption is basic knowledge of UML and Java
(but not necessarily UML 2.0)
INF5120 Model based System Development 16.01.2012
16
Telecom and Informatics 31
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 – to be updated
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
Practical use of tools (OBLIG):
Modelio - http://www.modeliosoft.com/
MOFScript -http://www.eclipse.org/gmt/mofscript/
BPMN – http://www.eclipse.org/stp/bpmn
EMF - http://www.eclipse.org/modeling/emf/
GMF - http://www.eclipse.org/gmf/
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/
Telecom and Informatics 32
Exam
Case-based (ref. earlier exams)
All written material can be used
4 hours – (Note, extended from 3 from previous years,
we will, however, still keep the same amonunt of work)
Monday June 4th, 2012, 1430-1830
INF5120 Model based System Development 16.01.2012
17
Telecom and Informatics 33
OMG Model-Driven Architecture (MDA)
www.omg.org/mda
Telecom and Informatics 34
Automation in Software Development Requirements 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
INF5120 Model based System Development 16.01.2012
18
Telecom and Informatics 35
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
Telecom and Informatics 36
Ex
ten
din
g C
OM
ET
fo
r S
OA
(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
INF5120 Model based System Development 16.01.2012
19
Telecom and Informatics
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
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
target output
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
serv
ice-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
Telecom and Informatics
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
INF5120 Model based System Development 16.01.2012
20
Telecom and Informatics 39
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,
GERAM, GRAI, Zachman,
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
Telecom and Informatics
Technologies/Realisation
Information Services Process
XML,, Metro/WSDL BPEL/XPDL
OWL,WSML OWL-S/WSML SA/WSML ASM
ODM,
Concepts
BPMN CIM
PIM
Persistence API EJB 3.0, Java,
SoaML
Jack, JADE Jack, JADE Jack, JADE
SAP SAP SAP
BMM
INF5120 OMG standard focus
PSM
INF5120 Model based System Development 16.01.2012
21
Telecom and Informatics 41
SHAPE Solution
Overview
SoaML
Core
Service
Variability
PIM4 SWS
PIM4 Agents
P2P/Grid/ Components/…
SHA-ML
WSDL, WSMO, OWL S, JACK, JADE, JXTA, OGSA, CORBA, …
J2EE, NetWeaver , .Net, …
Flexible Business Modelling
BPMN EPC BMM
PIMs for different
Architectural Styles
Execution Environments
PSM Implementation Models
CIM Business Models
PIM System Models
…
2nd EC Review, Brussels, January 28th
2010
Telecom and Informatics
Models on Different Abstraction Levels
42
INF5120 Model based System Development 16.01.2012
22
Telecom and Informatics
Agile Service Development Framework
43
Telecom and Informatics 44
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
INF5120 Model based System Development 16.01.2012
23
Telecom and Informatics 45
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)
Telecom and Informatics 46
CIM-PIM-PSM Reference Matrix
INF5120 Model based System Development 16.01.2012
24
Telecom and Informatics 47
PIM-K
CIM-K
BPDM, SBVR,
EDOC,UPMS,
PIM4SOA, ODM
TR/QVT
PSM-K
TR/QVT
BPMN, POP*, ARIS,
ArchiMate,
GERAM, GRAI, Zachman,
UEML, B.Rules
BPEL, WSDL, XML, XPDL,
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
BPEL, WSDL, XML, XPDL,
OWL-S, WSML, WSDL-S
TR/M2T ADM
ADM
ADM
Code
Semantic
Interoperability
Part 4: MDI
Model Driven
Interoperabtiliy
Organisational
Interoperability
Technical
Interoperability
Telecom and Informatics
EPF Composer
EPF Composer is a tool platform for process engineers, project leads, project and program managers who are responsible for mainteining and implementing processes for 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.
INF5120 Model based System Development 16.01.2012
25
Telecom and Informatics
SEMAT – Software Engineering
Methods and Theory
49
www.semat.org
Telecom and Informatics 50
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?
INF5120 Model based System Development 16.01.2012
26
Telecom and Informatics 51
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?
?
Telecom and Informatics 52
Representations of Architecture
ARIS ZACHMAN GERAM
EN/ISO 19439
NIST
EKA - POPS EKA - POPS EKA - POPS
Athena OEA
INF5120 Model based System Development 16.01.2012
27
Telecom and Informatics 53
Three Views in
DOD Architecture Framework and C4ISR-AF
Telecom and Informatics 54
To-be Operational DoDAF
As is To be architecture
Target
architecture
Architectural models supported
by the necessary tools.
Organisation
Hub
Current
Architectural Standards
New Form of Service-Team Organization
To-Be
INF5120 Model based System Development 16.01.2012
28
Telecom and Informatics 55
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
Telecom and Informatics
CSI Norway – Center for Service Innovation led by Norwegian Business School, Bergen, SINTEF, AOH, Telenor,..
(National Center for Research Driven Innovation (SFI) – 20 Meuro
budget, 8 years 2011 – 2018)
INF5120 Model based System Development 16.01.2012
29
Telecom and Informatics
CSI planned Activities
Telecom and Informatics
Business Motivation Model (BMM) with
MeansRealizations
INF5120 Model based System Development 16.01.2012
30
Telecom and Informatics
What is BPMN (Business Process
Modeling Notation) ?
Telecom and Informatics
BPMN example
INF5120 Model based System Development 16.01.2012
31
Telecom and Informatics 61
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 Model Real-World
phenomenon
Telecom and Informatics 62
Next Lecture – Enterprise Architecture and
Value Networks. January 23rd, 2012
Enterprise Architecture
Business Architecture
IT Architecture
VNA – Value Network Analysis (Guest lecture by Verna
Allee)
See online book: Value Netwoks and the true value of
Collaboration – by Verna Allee (chapter 1 and 2)
http://www.valuenetworksandcollaboration.com