76
1 INF5120 ”Modelbased System development” Lecture 1: 14.01.2019 Arne-Jørgen Berre [email protected] and [email protected]

INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

  • Upload
    others

  • View
    9

  • Download
    0

Embed Size (px)

Citation preview

Page 1: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

1

INF5120”Modelbased System development”

Lecture 1: 14.01.2019

Arne-Jørgen Berre

[email protected] and [email protected]

Page 2: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 2

Welcome to INF5120

“Model based System development” ◼ Model based System Development - (with Platform based system

development)

◼ http://www.uio.no/studier/emner/matnat/ifi/INF5120/

◼ Lecturers:

◼ Arne-Jørgen Berre

◼ Guest lecturers

◼ Email: [email protected]

◼ Teaching Assistant responsible for Obligatory exercises and lab:

◼ Chaudhry Rehan Ikran

◼ Email: [email protected]

◼ Master student focusing on INF5120 course design and evolution◼ Ewa Kabza

Page 3: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

26-1-2019 3www.bdva.eu

Course INF5120 – Institute for Informatics, UiO – Model-based and

Platform-based System Development – Every Monday, 1400-1700 –

Starting Monday January 14th, 2019

Contact: [email protected], SINTEF Digital, Software and Service Innovation, Smart Data

Business Architecture – Modeling with Business Model Canvas, Lean Startup Canvas and VDML – Value Delivery

Modeling Language, Enterprise Architecture with TOGAF and ArchiMate 3.0 modeling

Project on Smart Home – using IoT Platforms – with usage of IBM Cloud, IBM Bluemix, IBM Watson IoT, and

comparisons with Microsoft Azure, Amazon Web services, Kongsberg KognifAI, DNV Veracity, GE Predix, …

System Architecture – Modeling HW/SW – with sensors/actuators, Raspberry Pi

Software Architecture – Modeling UI with IFML, Analytics/Machine Learning and Service Composition with Microservices

and SoaML, Big Data and Databases with UML – SQL and NoSQL databases

Software Engineering with Agile Development (Scrum/Lean/Kanban)

Model-driven Engineering – Creating and using Domain Specific Languages – Node-RED, ThingML, CloudML, …

StartUp project – Group project from Business Idea to Minimum Viable Product (MVP) during the course

Page 4: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Course parts – 2019 (tentative plan)

4

◼ Part I-a -(Introduction to Modeling): ◼ 14/1 - Start◼ 1-14/1: Introduction to INF5120◼ Part I-b -(Introduction to Modeling and Metamodeling and)◼ 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) ◼ 3-28/1: MDE with Eclipse EMF, Xtext and SIRIUS◼ Part II - (Business Architecture/Business Modeling Modeling + Server side – Node-RED + THingML + Sensors/IoT/Cloud -

and the Smart Home project): )◼ 4-4/2: Business Modeling – BMC, LSC, VDML/VDMBee, (w/meta model) - (Business Model Canvas, Value Proposition, Lean

Canvas - BPMN process - UML Activ.Diagram◼ 5-11/2: Node-RED/IBM Bluemix/Cloud– getting started + Individual Oblig + VDMBee/VDML◼ 6-18/2: Cognitive Services/AI – Watson services example (for Oblig 1 and 2) (IBM Cloud)◼ 7-25/2: ArchiMate 3.0 Modeling, TOGAF 9.0 + Design Thinking◼ 25/2 - Oblig 1: Individual - Metamodeling + Node-RED (pass / no-pass)◼ 8-4/3: Smart Home - Design Thinking ◼ 9-11/3: Service Modeling with UML 2.X Collaboration Models and Composite Models and SoaML◼ 10- 18/3: UML 2.x Sequence Diagrams, UML 2.x State Machines. ArchiMate ArchIsurance, ArhiMetal examples, ◼ 18/3 - Oblig 2: Specification Models Smart Home – Business Architecture – Business Canvases, ++, ArchiMate + IBM◼ Part IIi - (Modeling –Apps + EA/ArchiMate)◼ 11- 1/4 UI – Server, UI Start lecture – incl. IFML – EA with ArchiMate - Oblig 2 (3) discussion/presentation◼ Oblig 3: Smart Home – Realisation with Node-RED, IBM Watson/IoT services + ArchiMate/UML++ Application, Technology,

Physical models – 10%Part IV - (MDE – Creating Your own Domain Specific Language – Eclipse, Xtext/SIRIUS): ◼ 12-8/4: Model driven engineering - revisited◼ EASTER – 15/4 and 22/4 ◼ 29/4 - Oblig 3 - delivery◼ 13-29/4: MDE – Lexical (ThingML) and Graphical (CJML) DSLs and Transformations◼ 14-6/5 Lecture – Model Driven Engineering◼ 15-13/5 Lecture - Model Driven Engineering◼ 13/5 – Oblig 4- Smart Home demonstrations - 10%◼ 16-20/5: Summary of the course - Oblig 4 final discussions - Conclusions, Previous exams – group collaborations

Preparations for the Exam by old exams

◼ 3/6: Exam (4 hours), Mandag June 3rd, (0900-1300) - 70%

Page 5: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

5

Student

IndustryUniversity

Sweet spot

Formal learning vs industryHow to find a sweet spot for a student?

EWA

Page 6: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Student´s needs/motivation

CV boost

Tools, certifications

Voice from the industry

- Do you need modellers?

«We need modellers but we cannot find them. It seems there are not enough of good ones»

- How do you define a good modeller?

«It´s a person who understand business and technology; and can put elements together»

Interviews, Questionnaires, Observations, Document Analysis

Being catchy on a job market

Getting to know companies

Knowledge

Useful framworks

Page 7: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

7

www.bdva.eu

Page 8: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

26-1-2019 8www.bdva.eu

TF1: Programme

TF2: Impact

TF3: Community

TF4: Communication

TF5: Policy &

Societal

Policy &

Societal

TF6: Technical

TF6-SG1: Data Management

TF6-SG2: Data Processing

Architectures

TF6-SG3: Data Analytics

TF6-SG4: Data Protection and

PseudonymisationMechanismsTF6-SG5: Advanced

Visualisation and User Experience

TF6-SG6: Standardisati

on

TF7: Application

TF7-SG1: Emerging

Application AreasTF7-SG2: Telecom

TF7-SG3: Healthcare

TF7-SG4: MediaTF7-SG5: Earth observation &

geospatialTF7-SG6: Smart Manufacturing

IndustryTF7-SG7: Mobility

and Logistics

TF7-SG8: SmartCities

TF8: Business

TF8-SG1: Data

entrepreneurs

(SMEs and startups)TF8-SG2:

Transforming

traditional business

(Large Enterprise)TF8-SG3:

Observatory on Data Business Models

TF9:

Skills and Education

TF9.SG1: Skill

requirements from

European industriesTF9SG2: Analysis of

current curricula

related to data

scienceTF9.SG3: Liaison

with existing

educational projects

BDVA TF6 Technical Priorities

Dr. Arne J. BerreSINTEF Digital

Page 9: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

26-1-2019 9www.bdva.eu

BDV – Big Data and Analytics/Machine LearningReference Model

Page 10: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

26-1-2019 10www.bdva.eu

Big Data Value Reference Model

Time series,

IoT

GeoSpatioTemp

MediaImageAudio

TextNLP.

Genom

WebGraphMeta

Structdata/

BI

Standards

Data Processing Architectures and WorkflowsBatch, Interactive, Streaming/Real-time

Data Visualisation and User Interaction1D, 2D, 3D, 4D, VR/AR

Data Analytics Descriptive, Diagnostic, Predictive, Prescriptive

Machine Learning and AI, Deep Learning, Statistics, HYBRID ANALYTICS (Optim/Simulation)

j

Data ManagementCollection, Preparation, Curation, Linking, Access, Sharing – Data Market / Data Spaces

DB types: SQL, NoSQL (Document, Key-Value, Column, Array,Graph, …)

Cloud and High Performance Computing (HPC)

Big D

ata Prio

rity Tech

Are

as

Applications/Solutions: Manufacturing, Health, Energy, Transport, BioEco, Media, Telco, Finance, EO, SE, …

Data Protection, Anonymisation, …

Big dataTypes &semantics

Things/Assets, Sensors and Actuators (Edge, Fog, IoT, CPS)

Co

mm

un

ication

and

Co

nn

ectivity, in

cl. 5G

Cyb

erSe

curity

and

Trust

De

velo

pm

en

t -En

gine

erin

g and

De

vOp

s

Data sh

aring p

latform

s., Ind

ustrial/P

erson

al

Relevant technology platforms:

IBM Cloud/Bluemix/Watson, MS Azure/Machine learning,

Amazon Web services, Apache Hadoop.

Page 11: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

4 parts of the course

◼ Enterprise Architecture and Business Architecture –

Modeling context and Requirements – with BMC, LSC,

VDML, TOGAF and ArchiMate 3.0 and requirements

engineering

◼ MDE-Platform-Server: (System and Software Architecture

Engineering - Model Driven system architecture and

realization – with IBM Cloud/BlueMix/Watson technology

platform – with Node-RED, ThingML, CloudML, …

◼ MDE-Platform-Client: (Analytics, Processing and User

Interaction with Visualisation)

◼ MDE-DSL (Model Driven Engineering) – Modeling of

Structure and Behaviour in "systems"- Creation of domain

specific languages and editors

11

Page 12: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Enterprise Architecture and

Enterprise Engineering

Enterprise

Architecture

Business

Architecture

Systems

Architecture(System of

systems)

Systems

Engineering

Business

Engineering

Software

Hardware

Hardware

Engineering

Software

Engineering

Enterprise

Engineering

Page 13: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Course components

13

Model Driven

Engineering –

New DSL -3

Software Architecture with

Analytics and Visualisation

client -1

Software/System Architecture

Engineering for Technology

Platforms (Node-RED,

ThingML Server -2

"Smart Home "

3+1 OBLIGS

Enterprise Architecture

Business Architecture

(BMC,LSC,VDML)

Page 14: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 14

Course areas

Business ArchitectureSystem and Software

ArchitectureTechnology Architecture MDE and Metamodeling

ArchiMate 3.0 Motivation,

Strategy and Business,

Lean Canvas & Business

Model Canvas

VDML & CJML

ArchiMate 3.0

Application, UML 2.5 &

BPMN 2.0, Node-RED &

ThingML, ChatBot

conversation models

ArchiMate 3.0 Technology,

Raspberry PI, TJBot IBM

Watson Cognitive & IoT

services/API's, Wireless

sensors (Zwave, Zigbee)

Eclipse EMFXtext and SIRIUS

Requirement models User stories and Use cases, UI Mockups

ToolsModelio, VDMBee, Node-RED, IBM Cloud, Eclipse EMF Xtext/SIRIUS

From Object Management Group (OMG) historical use:CIM: Computational Independent Models -> Business ArchitecturePIM: Platform Indepenent Models -> System/Software ArchitecturePSM: Platform Specific Models -> Technology Architecture

EnterpriseArchitecture

TOGAF 9.2, ArchiMate 3.0Project challenge(From idea to MVP)

Page 15: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Update to the course in 2019◼ We have a project focus on "Smart Home for Keeping Aging people

longer at home" with focus on Platform based development with

Internet of Things for Smart Home – and also for applicable for

Industry 4.0

◼ We will use Business Model Canvas and Lean Startup Canvas in

combination with VDML (Value Delivery Modeling Language) and

CJML (Customer Journey Modeling Language)

◼ The core MDE part with metamodeling will be introduced earlier in the

course – to enable the student to understand the semantics of and

create their own modeling languages earlier in the course - their still

including the creation of Model Driven Engineering tools – and the

creation of tool support for new domain specific languages.

◼ We will introduce a stronger focus on IoT/Cyber Physical System/Big

Data support through the use of emerging platforms – with IBM Cloud

BlueMix as an example – with Node-RED, Watson IoT, - and also

ThingML domain specific language - and supporting Metamodels

◼ We will reduce the focus on App/Web Porta/Ul development with the

IFML/WebRatio and also have UIs with AngularJ, React Native, ….

15

Page 16: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Obligs

◼ Partially individual, partially group - in multiple, incremental parts

◼ Oblig 1, 2, 3 and 4 "Smart Home" – your "own" company to develop an IoT

solution with sensor system control for Smart Homes – will be presented in

more detail on January 21st

◼ Oblig 1, 2, 3 and 4 – Evaluation will count as part of your final grade

(10+10+10 = 30%) - One Obligatory as pass/no pass.

16

Page 17: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Architecture for "Smart Home " project

Spring 2019

17

Page 18: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 18

Technology Platform:

Node-RED, Raspberry Pi, IBM Cloud/Bluemix/Watson IoT

ThingML

IoT Hub,

- Analytics

- Visualisation

- Apps

Page 19: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Book on Model-Based system development

19

◼ Model-Driven Software Engineering in Practice

◼ ISBN 978-1-60845-882-0

◼ Morgan&Claypool Publishers, Synthesis lectures on Software Engineering

◼ 2012, 166 pages (new version 2017)

◼ Marco Brambilla, Jordi Cabot and Manuel Wimmer

Page 20: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 20

UML 2.0

◼ UML 2.0 and SysML Background and Reference material

◼ See www.uml-forum.com/specs.htm

◼ Also at OMG:

◼ http://www.omg.org/uml/ (UML)

◼ http://www.omg.org/mda/ (MDA)

◼ http://www.omg.org/cwm/ (MOF, XMI, CWM)

Page 21: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 21

UML 2.0 recommended 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)

Page 22: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 22

Requirements for the course

◼ Student at UIO

◼ Only assumption is basic knowledge of UML and Java (but not necessarily

UML 2.0) – we will use Model-based tools/languages – and JavaScript.

◼ Links to other courses on software engineering, entrepeneurship, user

interaction etc.

Page 23: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 23

Exam

◼ Oblig 1,2,3,4 (30%) – some pass/no-pass parts

◼ Case-based (ref. earlier exams) (70%)

◼ All written material can be used

◼ 4 hours

◼ Planned: Friday June 3rdth, 2019, 0900-1300 (4 hours)

◼ The grades from the OBLIGS count 30% as part of the

final grade of the course

Page 24: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 24

OMG Model-Driven Architecture (MDA)

www.omg.org/mda

Page 25: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 25

Automation in Software DevelopmentRequirements 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

Page 26: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 26

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

Page 27: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Which Modeling languages will you

learn ?

◼ UML 2.0 – what is new in version 2

◼ VDML – Value Delivery Modeling Language – with VNA

◼ TOGAF with ArchiMate 3.0

◼ Node-RED application workflow (not a standard)

◼ ThingML (State machine language for IoT, not standard)

◼ SoaML – SOA Modeling Language

◼ MDA – Model Driven Architecture

◼ BPMN 2.0 – Business Process Modeling Notation

◼ BMM _ Business Motivation Model

◼ SysML – Systems Engineering Modeling Language

◼ QVT, MOF2Text – Query, View, Transformation

◼ See www.omg.org27

Page 28: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Which tools/environments will you

learn ?

◼ WebRatio - IFML for Web and Mobile Apps

◼ Agile team support – Symphonical/Someone, Scrumwise

◼ BMI – Business Model Innovation/Generation - Strategyzer

◼ Balsamiq – UI Mockups – for further UI modeling

◼ UML and BPMN modeling tools - MagicDraw

◼ AT ONE – Service Design – use of Smaply

◼ MagicDraw with UML and BPMN

◼ Eclipse EMF and XMI, Principles of GMF

◼ Sirius for Eclipse

◼ EPF/SPEM Software Process Modeler

◼ Overview of ATL, MOFScript, KerMeta, OpenArchitectureWare-OAW,

28

Page 29: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Model Driven Engineering techniques

◼ Structure modeling: UML Class (Information) and Components –

MagicDraw/Cameo, http://www.nomagic.com/

◼ Behaviour modeling: UML Behaviour modeling, BPMN

◼ Node-RED

◼ ThingML

◼ Enterprise Architecture – TOGAF – with ArchiMate 3.0

◼ WebRatio with IFML – for UI and App/Server development, -

http://www.webratio.com/

◼ Non functional modeling: OCL and Planguage

◼ Metamodeling and DSLs: EMF and Sirius

◼ Business Model Canvas and Value Proposition Canvas – VDMBee

◼ Scrum/Agile Project Management User stories and Use cases –

29

Page 30: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Software engineering practices and methods

◼ modelbased.net

◼ practices.modelbased.net

◼ A practices framework, SEMAT, www.semat.org

30

Page 31: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Requirements and Agile development

31

The Agile Manifesto: http://agilemanifesto.org/

Page 32: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Upwave.io – for Scrum

32

Page 33: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Scrum – Scrumwise.com

33

Page 34: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 34

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?

Page 35: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 35

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?

?

Page 36: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 36

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)

Page 37: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 37

Enterprise Architecture

UAF - Unified Architecture Specification (2017)

Zachman (1987)

ArchiMate

TOGAF 9

Page 38: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Zachman with OMG standards

38

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

IFMLIFML

(ThingML)

Page 39: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 39

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 ModelReal-World

phenomenon

Page 40: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

ArchiMate 3.0

40

Page 41: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 41

> 1 million copies sold

30 languages

Page 42: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

42

Business ArchitectureVDML (OMG 2015)Value Delivery Modeling Language

Customer Journey Modeling Language (CJML)

Business Model Canvas& Lean Startup Canvas

ArchiMate 3.0Motivation, Strategy, Business

Page 43: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

The Business Model Canvas

Businss Model Innovation

Page 44: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Strategyzer (Osterwalder)

44

Page 45: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Business Model Canvas and Value Proposition

Canvas Resources

◼ www.strategyzer.com

◼ http://www.alexandercowan.com/business-model-canvas-

templates/

◼ BizCanvas App for the iPad

◼ …

45

Page 46: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Business Model (Definition)

◼A Business Model describes the rationale of

how an organization creates, delivers and

captures value.

46

Page 47: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Reference examples in the course

◼ Concierge: A company with a system/service that offers

advice and recommendations to people with respect to

current and upcoming events, concerts, exhibitions etc.

◼ TravelAdvisor: A company with a system/service that

offers advice and booking possibilities to travelers

◼ SenseIt: UV sensor measurements (from the course of

2015)

◼ BioCaching: Citizen Science for Biodiversity (2016)

◼ Project 2017: Smart Building

47

Page 48: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

SenseIt

48

Page 49: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 49

October, 2014

Page 50: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Value Proposition

Canvas

50

Value needsValue offer

(Opportunity) (Requirements)

Page 51: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Value Proposition Canvas

51

Page 52: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

BPMN and UML

◼ BPMN

◼ UML 2.0

52

Page 53: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

What is BPMN (Business Process Modeling

Notation) ?

Page 54: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

BPMN example

Page 55: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 55

Purchase

Process2

OrderInfo :

OrderInfo

Proceed

Purchase2

Handle invoice2

Order Process2

confInfo

Delivery

Process2

invoiceInfo

Seller2 : ISellerCustomer2 : ICustomer

Activity model

Information model

Interaction model

UML Activity model (or BPMN)

UML component diagram

(enhanced in UML 2.0), SoaML

UML Class diagram

LTB HPL

ICustomer ISeller

IProdOwn

LHH

IWareHouse

TRA

ITransportServ

OrderLine

+ nrOfProd : Int

<<entity>>

Invoice

- date : Date

- amount : Currency

<<entity>>

SellerEntity

- name : String

<<entity>>

Product

+ prodNr : Int

+ description : String

<<entity>>

Shipment

+ delivAddress : Address

<<entity>>

CustomerEntity

+ name : String

+ address : String

+ phonenr : String

<<entity>>

PurchaseOrder

- poNr : int

- date : Date

<<entity>>

Order

+ orderNr : Int

+ date : Date

<<entity>>

1..*1..*

Information

modeling

Semantic

Models

Page 56: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

56

Systems & Software Architecture

// PSM

connector tlstick.to_T1 => T1.initial

connector tlstick.to_gdg => gdg.show_gadgets

connector tlstick.to_onoff1 => onoff1.initial

connector T1.provide_val => pim.get_sensor

connector T1.timer => timer.timer

connector T1.show_values => tg.show_values

connector onoff1.show_val => onoffobs.show_onoff

// HMI

connector myself.send_cmd => pim.human_input

// PIM outwards

connector pim.request_sensor => T1.require_val

connector pim.request_actuator => onoff1.require_val

connector pim.human_output => myself.get_values

ThingML

Node-RED (2018)

UML/BPMN

ArchiMate 3.0 Application

(IFML 2015-2017)

Page 57: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

57

Technology and Platform Architecture

IBM Cloud (Bluemix)IBM Watson

TjBot, w/ Raspberry PI,camera, speaker, microphone ,led, servo, ….

Watson Cognitive services:Speach to textText to speachImage recognitionChatBot

Watson IoT services:Machine Learning

ArchiMate 3.0Technology

Page 59: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Parts of UML

Metamodel

Class

Attribute

initialValue : Expression

DataType

Operation

SpecificationisPolymorphic : Booleanconcurrency : CallConcurrencyKind

GeneralizableElement

Feature

BehaviouralFeatureStructuralFeature

Association

Classifier

0..*

+features

0..*

AssociationEnd

2..n2..n

0..*0..*

0..* 1

0..*

1

0..*

0..*

Page 60: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

UML Information Modeling

◼ Ref also ISO 19103 Standard for Conceptual Modeling

◼ The following material is for reference …..

60

Page 61: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Objects

Can represents

◼ One instance

◼ One type, interface

◼ One class

Ola :Person

Person

<<Interface>>

Person

Objekt modellering

Page 62: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Object and classes

- notation

Person

navn : string

personnr. : integer

adresse : string

gasje : money

stillingstittel : string

endre-stilling()

endre-adresse()

Example - object class

Objekt modellering

Page 63: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Page 64: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

User Story template

◼ I <in the role of XX> needs functionality <zzz> to achieve

the goal of <YYY>

64

Page 65: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Backlog metamodel

Page 66: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Use-Case Essentials◼ A way to establish the requirements of the system

◼ Use cases place requirements in context

◼ A way to establish the system boundary

◼ The model identifies who or what interacts with the system and what

the system should do

◼ A way to iteratively evolve the requirements

◼ A way to communicate the requirements to all the stakeholders

◼ The use cases provide a common thread through all project activities

◼ A way to focus the development efforts on delivering customer

value

◼ A way to verify that the requirements have been implemented

Introduction to The

Essentials / 03 -

66

A way to effectively gather requirements and ensure that

the system delivers real value to the customers and users

Page 67: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

What is a Use Case?

Introduction to The

Essentials / 03 -

67

◼ Use cases are

described in text

◼ They tell the story of the

interactions between

actors and the system

Withdraw CashBank Customer

• Use cases are shown in UML diagrams

A use case describes a sequence of actions a system performs that yields an observable result of value to a particular actor

Page 68: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

What do we need to produce?

Introduction to The

Essentials / 03 -

68

Page 69: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 69

http://thingml.org/

Page 71: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Xtext

71

Page 72: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Sirius

72

Page 73: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

Sirius

73

Page 74: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 74

MDSD

◼ 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

Page 75: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics

DSL Engineering

75

◼ DSL Engineering: Designing, Implementing and Using Domain-Specific

Languages Paperback– January 23, 2013 , 560 pages

◼ Markus Voelter

Page 76: INF5120 Modelbased System development · Part I-b -(Introduction to Modeling and Metamodeling and) 2-21/1: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) 3-28/1:

Telecom and Informatics 76

Next Lecture, January 21, 2018

Modeling structure and behaviour (UML and

UML 2.0)

Class models as a basis for meta modeling

First introduction to meta modeling