INF5120 ”Modelbased System development”

Lecture 1: 14.01.2013 Arne-Jørgen Berre

[email protected] and [email protected]

Telecom and Informatics 1 Welcome to INF5120 “Model based System development”

 Model based System Development  http://www.uio.no/studier/emner/matnat/ifi/INF5120/v13/

 LtLecturers:  Arne-Jørgen Berre  Guest lecturers  Email: [email protected]

 Responsible for Obliggyatory exercises:  Yannick Lew, Tore Vatnan  Email: [email protected]

Telecom and Informatics 2 3 parts of the course

 MDI I (Model Driven Enterprise and business architecture, with service innovation and design)

 MDE II (Model Driven Engineering) – Design of domain specific languages and editors

 MDI II (Model Driven system architecture and realisation)

Telecom and Informatics 3 INF5120 - Lecture plan - 2013

 1 (14/1): Introduction – overview Enterprise Architecture with UML and BPMN and DSLs  2 (21/1): Service Innovation and Design, AT ONE method/workshop – myServiceFellow (Marika Lüders)  3: (28/1): Value Networks/VDML BPMN, vs. UML Activity diagrams - Oryx  4 (4/2): User exper ience an d Touc hpo ints /UI Des iign – BlBalsami q – (Ame la K arah asanovi c)  5 (11/2): UML and Req.Modeling –Agile User stories versus Use cases  6 (18/2): UML 2.0 and Service Modeling – SoaML and System architecture

 7 (()25/2): Model driven en gineerin g – Metamodels, DSL, UML Profiles etc.  8 (4/3): Model driven engineering EMF, Eclipse, GMF  9 (11/3): Model driven engineering , transformation technologies (Franck Fleurey)

 10(18/3): UML Service Modeling – Service composition, USDL, ISO 19119, etc.  11(8/4): BPMN and Business Process Management and CMMN and Case Management  12(15/4): UML and Entity and Information modeling, UML, ISO 19103  13(22/4): UML and Semantic models, Facts, SBVR, Ontologies, Rules  14(29/4): UML and Platform models, realisation, migration, Java, Apps, CloudML  15(6/5): Software Process modeling frameworks – SPEM/EPF, ISO 24744, FACESEM/ESSENCE  16(13/5): Conc lus ion an d Summary for INF5120 - PtifEPreparation for Exam

 Exam: Monday June 3rd, 2013, (4 hours)

Telecom and Informatics 4 Obligs

 Partially individual, partially group - in 3 parts

 Will be presen te d in more de ta il on January 28th

Telecom and Informatics 5 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 - will be updated  Web site for practices:  Inf5120.modelbased . net

 Practical use of tools (OBLIG, part 2)

 Oryx - Cloud based UML, BPMN (and ServiceML) editor

 EMF - http://www.eclipse.org/modeling/emf/

 GMF - http://www.eclipse.org/gmf/

 Eugenia – http://www.eclipse.org/gmt/epsilon/doc/eugenia/  See also: http://live.eclipse.org/node/575

 BPMN – http://www.eclipse.org/stp/bpmn  SoaML - www.soaml.org

Telecom and Informatics 6 http://INF5120. modelbased. net

Telecom and Informatics 7 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)  h//http://www.omg.org/ cwm/ (MOF, XMI , CWM)

Telecom and Informatics 8 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)

Telecom and Informatics 9 Agile Service Development (1/3) New book – published 2012, Springer. We will use a publication preprint initially

Telecom and Informatics 10 Agile Service Development (2/3)

Telecom and Informatics 11 Agile Service Development (1/3)

Telecom and Informatics 12 Open Services Innovation

Book: January 2011

Telecom and Informatics 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 14 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

Telecom and Informatics 15 Value Network Analysis

http://www. valuenetworksandcollaboration.com

Telecom and Informatics 16 Kermeta – www. kermeta. org

Telecom and Informatics 17 Software engineering practices and methods

 modelbased. net  practices.modelbased.net

 A practi ces f ramework , SEMAT , www.semat.org

Telecom and Informatics 18 Book is available now – Safaribooksonline/Addison Wesley

19 The Kernel

A stripped-down, lightweight set of definitions that captures thfffihe essence of effective, The Kernel is described scalable software using a small subset of the engineering in a practice Language. independent way . 20 Alphas: The Essential Things to Work With

Customer

Solution

Endeavor

21 Alphas: Example

Requirements Description What the software syyppyystem must do to address the opportunity and satisfy the stakeholders. It is important to discover what is needed from the software system, share this understanding among the stakeholders and the team members, and use it to drive the development and testing of the new system. Associations scopes and constrains : Work

22 Activity Spaces: The Essential Things to Do

Explore Understand Ensure Stakeholder Use the System Possibilities Stakeholder Needs Satisfaction

Understand the Shape Implement the Test Deploy Operate Requirements the System System the System the System the System

Prepare to do Coordinate Support the Team Track Progress Stop the Work the Work Activity 23 Update to the course in 2013

 We will start with a focus on enterprise architeture and business architecture and service innovation and business process modeling, illustrated with various modeling tools - compared with UML  We will make the second part on Model Driven Engineering smaller and practical – i. e. make an editor  In part three we will focus on practical model driven development with UML and UML profiles and with the transformations to platform environments for service oriented architecture (SOA) and cloud computing.

Telecom and Informatics 24 New content started in 2012, continued i n 2013

 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

Telecom and Informatics 25 Which OMG modeling standards will you learn ?

 UML 2.0 – what is new in version 2  VDML – Value Delivery Modeling Language – with VNA  SoaML – SOA Modeling Language  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

Telecom and Informatics 26 Which tools/environments will you learn ?

 UML modeling tools  AT ONE – Service Design  VNA – Value Network Analysis  BMI – Bus iness Mo de l Innova tion /Generati on  Balsamiq – UI Mockups – for further UI modeling  MagicDraw with UML and BPMN  Eclipse EMF and XMI, Principles of GMF  EuGENia – for GMF  EPF/SPEM Software Process Modeler  Overview of ATL, KerMeta, OpenArchitectureWare-OAW, …

Telecom and Informatics 27 Requirements for the course

 Student at UIO

 OlOnly assumpti on i s b as ic know ldledge o fUMLf UML an dJd Java (but not necessarily UML 2.0)

Telecom and Informatics 28 Exam

 Case-based (ref. earlier exams)  All written material can be used

 4 hours

 Monday June 3rd, 2013, 4 hours

Telecom and Informatics 29 OMG Model-Driven Architecture (MDA)

www.omg.org/mda

Telecom and Informatics 30 Automation in Software Development

Requirements Requirements Requirements

Manually Manually Manually implement implement implement

High-level spec (functional and nonfunctional) Implement with Interactive, automated Source in Source in support domain-specific domain-specific langgg(uage (DSL ) langgg(uage (DSL )

Compile Compile Source in a (may generate (may generate general-purpose code in code in language, e.g., Java or C++) Java or C++) Java or C++ Compile Compile Compile

Implementation Implementation Implementation

Telecom and Informatics 31 MDA CIM, PIM and BPMN,POP, POP* ,,ARIS, ARIS, Computational ArchiMate, PSM/Code CIM GERAM, GRAI, Zachman, Independent UEML, B.Rules Model ATL

BPDM, SBVR, Platform PIM EDOC,UPMS, Independent PIM4SOA, ODM Model MOFScript ADM

UML profiles and Platform metamodels for Java PSM JEE, BPEL, WSDL, Specific XML, XPDL, Model/Code OWL-S, WSML, WSDL -S ADM

BPEL, WSDL, XML, XPDL, Code, Java JEE, OWL-S, WSML, WSDL-S ….

Telecom and Informatics 32 What is ?

EtEnterpri se Mo delli ng (EM) isacapability 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.

Telecom and Informatics 33 Why Enterprise Architecture?

How can I use best practices to ensure How can I ? the success of the involve my people business? in improving the performance of the business How can I ensure that the IS ? technology ? helps the work of my people?

Telecom and Informatics 34 Representations of Architecture

ARIS ZACHMAN GERAM

EKA - POPS

EN/ISO 19439 Athena OEA NIST

Telecom and Informatics 35 Three Views in DOD A rchi tecture F ramework and C4ISR -AF

Telecom and Informatics 36 Zachman Framework – for Enterprise Architecture (IBM, 1987)

VA Enterprise DATA FUNCTION NETWORK PEOPLE TIME MOTIVATION Based on work by Architecture What How Where Who When Why John A. Zachman SCOPE Things Important Processes Business Important Events Significant Business Goals SCOPE (CONTEXTUAL) to the Business Performed locations Organizations to the Business and Strategy (CONTEXTUAL)

Planner Entity = Class of F unc tion = C lass of Node = Major People = Major Time = Major Ends/Means = Planner Business Thing Business Process Business Locations Organizations Business Event Major Business Goals ENTERPRISE Semantic Model Business Process Business Logistics Work Flow Model Master Schedule Business Plan ENTERPRISE MODEL Model System MODEL (CONCEPTUAL) (CONCEPTUAL)

Owner Ent = Business Entity Proc = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Rel = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy SYSTEM MODEL Logical Data Application Distributed System Human Interface Processing Business Rule SYSTEM MODEL (LOGICAL) Model Architecture Architecture Architecture Structure Model (LOGICAL)

Designer Ent = Data Entity Proc = Application Function Node = IS Function People = Role T ime = System Ev ent End = Structural Assertion Designer Rel = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliverable Cyc le = Proc ess ing Cycle M eans = Ac tion As sertion TECHNOLOGY Physical Data System Technology Presentation Control Rule TECHNOLOGY MODEL Model Design Architecture Architecture Structure Design MODEL (PHYSICAL) (PHYSICAL)

Builder Ent = Segment/Table Proc = Computer Function Node = Hardware/Software People = User Time = Execute End = Condition Builder Rel = Pointer/Key I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED Data Program Network Security Timing Rule DETAILED REPRESENTATIONS Definition Architecture Architecture Definition Design REPRESENTATIONS (OUT-OF-CONTEXT) (OUT-OF-CONTEXT)

SbSub-CtContract or Ent = Field Proc = Language Statement Node = Addresses People = Identity Time = Interrupt End = Sub-Condition SbSub-CtContract or Rel = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step FUNCTIONING Data Function Network Organization Schedule Strategy FUNCTIONING ENTERPRISE ENTERPRISE

Ent = Proc = Node = People = Time = End = Rel = I/O = Link = Work = Cycle = Means = DATA FUNCTION NETWORK PEOPLE TIME MOTIVATION What How Where Who When Why

Telecom and Informatics 37 IT/Business architecture transformation

Telecom and Informatics TOGAF 9

Telecom and Informatics 39 UPDM RFC - Domain Meta Model Summary

Telecom and Informatics Zachman with OMG standards

Data Function Network People Time Motivation (What) (How) (Where) (Who) (When) (Why)

List of things important List of processes that List of locations which List of organizations List of events/cycles List of business Scope to business the business performs the business operates important to the businessimportant to the business goals/strategies (Contexts) SBVR VDM VDM OSM DTFV BMM

Semantic Model Business Process Business Logistics Workflow Model Master Schedule Business Business ODM, Model System OSM, BPMN, BPMN, CMPM, Plan (Concepts) IMM (CWM) BPMN, CMPM BPMN, CMPM CMPM DTFV SBVR

System Logical Data Model Application Distributed Human Interface Process Structure Business Rule ODM, Architecture System Architecture Architecture BPMN, CMPM, Model (Logic) IMM (CWM), UML SoaML, UML SoaML, UML BPMN, CMPM DTFV SBVR

Technology Control Structure Rule Technology Physical Data Model System Design Presentation Architecture BPMN, CMPM, Design IMM (()CWM), UML SoaML, UML Architecture (Physics) SoaML, UML DTFV SBVR

Network Timing Rule Data Definition Program Component Architecture Security Definition Definition Architecture (Assemblies) IMM (CWM), UML UML UML DTFV SBVR

Operation Data Function Network Organization Schedule Strategy (Instances)

Telecom and Informatics 41 OMG standards coverage

Data Function Network People Time Motivation (What) (How) (Where) (Who) (When) (Why)

List of things List of processes List of locations List of organizations List of events/cycles Scope SBVR VDM OSM ListBMM of business important that the business which the business important to the important to the goals/strategies (()Contexts) to business performs operates business business

Business Business Business BPMN Workflow Master Business Semantic Model Process Logistics Model Schedule Plan (Concepts) ODM Model System

Distributed CMPM Human System Application Process Business Rule Logical Data Model System Interface Architecture Structure SBVRModel (Logic) Architecture Architecture

Technology SoaML TechnologyUML Presentation Control Rule PhysicalIMM Data Model System Design Architecture Architecture DTFVStructure Design (Physics) (CWM)

Component Network Security Timing Rule Data Definition Program (Assemblies) Architecture Architecture Definition Definition

Operation Data Function Network Organization Schedule Strategy (Instances)

Telecom and Informatics 42 Models on Different Abstraction Levels

Telecom and Informatics 43 Agile Service Development Framework

Telecom and Informatics 44 CSI Norway – Center for Service Innovation led by Norwegian Business School, Bergen, SINTEF, AOH, Telenor,.. (Na tiona l C en ter for Researc h Dr iven Innova tion (SFI) – 20 Meuro budget, 8 years 2011 – 2018)

Telecom and Informatics CSI planned Activities

Telecom and Informatics Businss Model Innovation

The Alexander Osterwalder canvas

Telecom and Informatics Strategyzer (Osterwalder)

Telecom and Informatics 48 BMI – Canvases/Models

Telecom and Informatics 49 Telecom and Informatics VDML – Value Modeling Stand ard proposal , N ov. 2012

Telecom and Informatics 51 ServiceML Editor

A  Web-based modelling editor  http://tomcat.thingml.org/backend/poem/repository  User guide  http://epf.thingml.org/wikis/neffics/practice.business. T service_modelling.base- sintef/guidances/toolmentors/neffics_service_modell ing_editor_user_guide_D29F2B87. O  Currently being extended to support AT ONE Method (i.e., the Service Innovation practice) N  http://epf.thingml.org/wikis/neffics/practice.innovatio n.service_innovation.base- sintef/guidances/practices/service_innovation_F3FE D330.html E

Telecom and Informatics 52 A – Actors Services Architecture (SoaML)

Value Network (VDML)

Services Architecture (Business-SoaML)

Hybrid notation • Participants (from Value Network) • Conversation (from BPMN 2.0) • Groups a set of Flows

Telecom and Informatics 53 T – Touchpoints

Service Journeyyp Map • Service Journey: Chronological mapping (from the customer point of view) of a service encounter. • Model as "Stages" • Attach touchpoints to the different stages • Library of different types of touchpoints to select from.

Telecom and Informatics 54 O – Offerings

Service Contract • Deta iling o f t he conversation. • Conversation is the grouping of flows ( messages) . • Service Contract defines the interfaces on both sid(tt)ide (structure) and the protocol (behaviour) for how to use these itinterf aces.

Telecom and Informatics 55 N – Needs

Goals and Objectives • We have not yet implemented Example of Goals and Objectives diagram modelling support for needs. • One idea is to use a very small subset of BMM (Business Motivation Model) standard. • Goal: a statement about a state or condition of the enterprise to be brought about or sustained through appropriate Means (i.e., Offerings expressed as Service Contracts). • Objective: An Objective is a statement of an attainable, time- targeted, and measurable target that the enterprise seeks to meet in order to achieve its Goals

Telecom and Informatics 56 E – Experiences

Experiences • The idea is to extend the Service Journey Map. • Each user/customer capture experiences (emotional icons) related to each touchpoints and deviations in the ideal/expected journey (seen from a Service Provider side). Ref. also mySiFllServiceFellow smart ph one app

Telecom and Informatics 57 Business Motivation Model (BMM) with MeansRealizations

Telecom and Informatics What is BPMN (Business Process Modeling Notation) ?

Telecom and Informatics BPMN example

Telecom and Informatics Extending COMET for SOA (1)

Space Semantic Reference Ontology Ontology OWL annotated anno with with ttd t a Specification Model EtiAtftE Execution Infrastructure ATHENA Integrated t e xecu d Web Service Web Service ti on A r annotated with annotated with t e f ac t s Agent Specification Execution Artefacts Execution Artefacts Execution Artefacts Execution Artefacts Execution Artefacts Execution Requirements ModelModel to Transformation Model Business gn PLP2P BPEL Agent Analysis Legend Architecture Model Middleware Component Middleware Process/Agent Web/Server Component Active (Business) Model Business Process/Agent Infrastructure Services Repository Service Transformation Registry Internal ModelText to Enterprise

Model (P2P) PlatformResource Mgt Adaptive Distributed (BPEL) Platform Execution Process Service WrappersService (.NET, J2EE) (.NET, Platform Component Server-side (Enterprise X) (Enterprise Evaluation & Negotiation of Available Functionality Available of Negotiation & Evaluation - (Agents) PlatformPlatform Execution Execution AdaptiveAdaptive Goal-oriented Oriented (MQSeries) Platform Oriented Message- Service Wrappers (Enterprise A) (Enterprise Wrappers Service Service Wrappers (Enterprise Y) (Enterprise Enhanced Service Interconnection Bus Interconnection Service Enhanced Transformation ModelMode to ( Platform Model Active AKMii BPEL Specification BPEL ) Existing Enterprise Applications Infrastructure Services Infrastructure ( Platform WebService Composed WebServices Public ) org. Intra- org. Cross- Model Telecom and Informatics Telecom and l P2P Specification Model oe Transformation Model Model Transformation Model Deployment Specification Architecture

Transformation • • • • ProfileUML for SOA UML ProfileUML for P2P ProfileUML for BPEL ProfileAgentsUML for Services Web for Profile UML • • • • ProfileUML for POP* QoS P Service Information … Product Organisation Process rocess

Profile

for

Web

Services 61 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.

Telecom and Informatics Syyjstem 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. AhlhA whole that we ch oose to cons ider as a coll lliection of fbj objects, each object being characterized by attributes and by actions which may involve itself and other objects .

Mental modell

Real-World Manifest Model phenomenon

Telecom and Informatics 63 Next Lecture, January 21, 2013 Service Innovation and Service Design

 Guest lecture: Marika Lüders

 AT ONE

 SiIService Innova tidSiDition and Service Design

Telecom and Informatics 64