INF5120 ”Modelbased System development” · UML 2.0 – what is new in version 2 VDML – Value...

INF5120INF5120”Modelbased System development”

Lecture 1: 14.01.2013Arne-Jørgen Berre

[email protected] and [email protected]@ @

Telecom and Informatics 1

Welcome to INF5120 “Model based System development” Model based System Development Model based System Development

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

L t Lecturers: Arne-Jørgen Berre Guest lecturers Email: [email protected]

Responsible for Obligatory exercises:g y Yannick Lew, Tore Vatnan Email: [email protected]


3 parts of the course3 parts of the course

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

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

MDI II (Model Driven system architecture and realisation)


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) U i d T h i /UI D i B l i (A l K h i ) 4 (4/2): User experience and Touchpoints/UI Design – Balsamiq – (Amela Karahasanovic) 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 engineering – Metamodels, DSL, UML Profiles etc.( ) g g 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 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) C l i d S f INF5120 P ti f E 16(13/5): Conclusion and Summary for INF5120 - Preparation for Exam

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


ObligsObligs

Partially individual partially group in 3 parts Partially individual, partially group - in 3 parts

Will b t d i d t il J 28th Will be presented in more detail on January 28th


Course literature – available on web Material from all lectures and OBLIG 1 and 2 a/b 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 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


http://INF5120 modelbased nethttp://INF5120.modelbased.net


UML 2 0UML 2.0

UML 2 0 and SysML Background and Reference material UML 2.0 and SysML Background and Reference material See www.uml-forum.com/specs.htm

Også hos OMG: htt // / l/ (UML) http://www.omg.org/uml/ (UML) http://www.omg.org/mda/ (MDA)

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


UML 2.0 recommend books:

UML 2.0 in a Nutshellby Dan Pilone (Author), Neil Pitman (Author)

The Unified Modeling Language User Guide Second edition (ISBN 0-321-26797-4)(G, Booch, J. Rumbaugh, Jacobsson)


Agile Service Development (1/3)Agile Service Development (1/3)New book – published 2012, Springer.

We will use a publication preprint initiallyWe will use a publication preprint initially


Agile Service Development (2/3)Agile Service Development (2/3)


Agile Service Development (1/3)Agile Service Development (1/3)


Open Services Innovationp

Book:

Telecom and Informatics

January 2011

Supporting literature Book: Model-Driven Software Development: Technology, Engineering,

Management (Paperback) by Thomas Stahl Markus Voelter Krzysztof Czarneckiby Thomas Stahl, Markus Voelter, Krzysztof CzarneckiISBN: 978-0-470-02570-3

Engineering Service Oriented Systems: A Model Driven Approach, Karakostas, Bill; Zorgios, YannisISBN10: 1599049686 ISBN13: 9781599049687Cover: Hardcover A il 2008


April 2008

Supporting literature – EMF and GMF Book: Eclipse Modeling Framework (2nd Edition) (Paperback) Dave Steinberg (Author), Frank Budinsky (Author), Marcelo Paternostrog ( ), y ( ),

(Author), Ed Merks (Author)

Book: Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit Book: Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit (Paperback)

Richard C. Gronback


Value Network AnalysisValue Network Analysis

http://www valuenetworksandcollaboration comhttp://www.valuenetworksandcollaboration.com


Kermeta – www kermeta orgKermeta www.kermeta.org


Software engineering practices and methods modelbased net modelbased.net practices.modelbased.net

A ti f k SEMAT t A practices framework, SEMAT, www.semat.org


Book is available now – Safaribooksonline/Addison Wesley

19

The Kernel

A stripped-down, lightweight set of definitions that captures h f ff ithe essence of effective,

scalable software engineering in a practice independent way

The Kernel is described using a small subset of the Language

20independent way.Language.

Alphas: The Essential Things to Work With

Customer

Solution

Endeavor

21

Alphas: ExampleRequirementsDescriptionWhat the software system must do to address the opportunity and satisfy the stakeholders.y pp y y

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.

Associationsscopes and constrains : Workscopes and constrains : Work

22

Activity Spaces: The Essential Things to Do

Explore Ensure Stakeholder Use the SystemUnderstand Explore Possibilities

Ensure Stakeholder Satisfaction

Use the SystemStakeholder Needs

Shape the System

Implement the System

Test the System

Deploy the System

Operate the System

Understand the Requirements

23Prepare to do

the WorkCoordinate

ActivitySupport the Team Stop the WorkTrack Progress

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 UMLcompared with UML

We will make the second part on Model Driven Engineering smaller and practical – i e make an editorEngineering 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 thedevelopment with UML and UML profiles and with the transformations to platform environments for service oriented architecture (SOA) and cloud computing.


New content started in 2012, ti d i 2013continued in 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


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.org26

Which tools/environments will you learn ?learn ? UML modeling tools AT ONE – Service Design VNA – Value Network Analysis BMI B i M d l I ti /G ti BMI – Business Model Innovation/Generation Balsamiq – UI Mockups – for further UI modeling MagicDraw with UML and BPMNMagicDraw 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, …


Requirements for the courseRequirements for the course

Student at UIO Student at UIO

O l ti i b i k l d f UML d J Only assumption is basic knowledge of UML and Java (but not necessarily UML 2.0)


ExamExam

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

4 hours

Monday June 3rd, 2013, 4 hours


OMG Model-Driven Architecture (MDA)

www.omg.org/mda


Automation in Software DevelopmentAutomation in Software DevelopmentRequirements Requirements Requirements

High level spec

Manuallyimplement

Manuallyimplement

Manuallyimplement

High-level spec(functional andnonfunctional) Implement

withInteractive,

Source indomain-specificlanguage (DSL)

Source indomain-specificlanguage (DSL)

,automatedsupport

Source in ageneral-purpose (may generate

g g ( )

(may generate

g g ( )

Compile Compile

general-purposelanguage, e.g.,

Java or C++

code inJava or C++)

code inJava or C++)

Compile Compile Compile


Implementation Implementation Implementation

MDA CIM, PIM

BPMN, POP*, ARIS,

CIM, PIM and PSM/Code

CIM

ATL

BPMN, POP , ARIS,ArchiMate,

GERAM, GRAI, Zachman, UEML, B.Rules

ComputationalIndependent

Model

PSM/Code

PIMBPDM, SBVR, EDOC,UPMS,

ATL

Platform EDOC,UPMS, PIM4SOA, ODM

MOFScript ADM

PlatformIndependent

Model

PSMUML profiles and

metamodels for Java JEE, BPEL, WSDL,

XML, XPDL,OWL S WSML WSDL S

PlatformSpecific

BPEL, WSDL, XML, XPDL,

ADMOWL-S, WSML, WSDL-S

Code, Java JEE,

Model/Code


OWL-S, WSML, WSDL-S, ,

….

What is Enterprise Modelling?

E t i M d lli (EM) i bilit

What is Enterprise Modelling?

Enterprise Modelling (EM) is a capabilityfor externalising, making and sharingenterprise knowledge.

EM tools can either be:• used stand-alone to produce variouskinds of model viewskinds of model views,• integrated as front-ends to othersystems,• part of an environment providing a• part of an environment providing acontextual user-environment.


Why Enterprise Architecture?Why Enterprise Architecture?

??How can I use best

practices to ensure ??How can Iinvolve my peoplein improving the

the success of the business?

in improving theperformance of thebusiness

??How can I

ensure that the IS technology ???? technology

helps the work of my people?

??


Representations of Architecturep

ARIS ZACHMAN GERAM

EKA -POPSEKA -POPSEKA -POPS

EN/ISO 19439


NISTAthena OEA

Three Views in DOD A hi F k d C4ISR AFDOD Architecture Framework and C4ISR-AF


Zachman Framework – for Enterprise

Based on work by John A. Zachman

VA Enterprise Architecture

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Based on work by John A. Zachman

VA Enterprise Architecture

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

Architecture (IBM, 1987)SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

Things Important to the Business

Entity = Class of Business Thing

Processes Performed

Function = Class of Business Process

Semantic Model Business Process Business Logistics Work Flow Model Master Schedule Business Plan

ImportantOrganizations

People = Major Organizations

Business locations

Node = Major Business Locations

Ev ents Significantto the Business

Time = MajorBusiness Event

Business Goalsand Strategy

Ends/Means =Major Business Goals

SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

SCOPE(CONTEXTUAL)

Planner

ENTERPRISE

Things Important to the Business

Entity = Class of Business Thing

Processes Performed

Function = Class of Business Process

Semantic Model Business Process Business Logistics Work Flow Model Master Schedule Business Plan

ImportantOrganizations

People = Major Organizations

Business locations

Node = Major Business Locations

Ev ents Significantto the Business

Time = MajorBusiness Event

Business Goalsand Strategy

Ends/Means =Major Business Goals

MODEL(CONCEPTU AL)

Owner

SYSTEM MODEL(LOGICAL)

MODEL(CONCEPTU AL)

Owner


Ent = Business Entity Rel = Business Relationship

Model

Proc = Business Process I/O = Business Resources

gSystem

Node = Business Location Link = Business Linkage

People = Organization Unit Work = Work Product

Time = Business Event Cycle = Business Cycle

End = Business Objectiv e Means = Business Strategy

Logical DataModel

Application Architecture

Distributed SystemArchitecture

Human InterfaceArchitecture

ProcessingStructure

Business RuleModel

MODEL(CONCEPTU AL)

Owner


MODEL(CONCEPTU AL)

Owner


Ent = Business Entity Rel = Business Relationship

Model

Proc = Business Process I/O = Business Resources

gSystem

Node = Business Location Link = Business Linkage

People = Organization Unit Work = Work Product

Time = Business Event Cycle = Business Cycle

End = Business Objectiv e Means = Business Strategy

Logical DataModel

Application Architecture

Distributed SystemArchitecture

Human InterfaceArchitecture

ProcessingStructure

Business RuleModel

Designer

TECHNOLOGYMODEL(PHYSICAL)

Designer

TECHNOLOGYMODEL

(PHYSICAL)

Ent = Data Entity Rel = Data Relationship

Proc = Application Function I/O = User Views

Node = IS Function Link = Line Characteristics

People = Role Work = Deliv erable

Time = System Event Cycle = Processing Cycle

End = Structural Assertion Means = Action Assertion

Physical DataModel

SystemDesign

TechnologyArchitecture

PresentationArchitecture

ControlStructure

RuleDesign

Designer

TECHNOLOGYMODEL(PHYSICAL)

Designer

TECHNOLOGYMODEL

(PHYSICAL)

Ent = Data Entity Rel = Data Relationship

Proc = Application Function I/O = User Views

Node = IS Function Link = Line Characteristics

People = Role Work = Deliv erable

Time = System Event Cycle = Processing Cycle

End = Structural Assertion Means = Action Assertion

Physical DataModel

SystemDesign


PresentationArchitecture

ControlStructure

RuleDesign

Builder

DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)

S b C t t

Builder


S b C t t

Ent = Segment/Table Rel = Pointer/Key

Proc = Computer Function I/O = Data Elements/Sets

Node = Hardware/Softw are Link = Line Specifications

People = User Work = Screen Format

Time = Ex ecute Cycle = Component Cycle

End = Condition Means = Action

DataDefinition

Ent = Field

Program

Proc = Language Statement

Netw orkArchitecture

Node = Addresses

SecurityArchitecture

People = Identity

Timing Definition

Time = Interrupt

RuleDesign

End = Sub Condition

Builder


S b C t t

Builder


S b C t t

Ent = Segment/Table Rel = Pointer/Key

Proc = Computer Function I/O = Data Elements/Sets

Node = Hardware/Softw are Link = Line Specifications

People = User Work = Screen Format

Time = Ex ecute Cycle = Component Cycle

End = Condition Means = Action

DataDefinition

Ent = Field

Program

Proc = Language Statement

Netw orkArchitecture

Node = Addresses


People = Identity

Timing Definition

Time = Interrupt

RuleDesign

End = Sub Condition Sub-Contractor

FUNCTIONINGENTERPRISE

Sub-Contractor


Ent = Field Rel = Address

Proc = Language Statement I/O = Control Block

Node = Addresses Link = Protocols

People = IdentityWork = Job

Time = InterruptCycle = Machine Cycle

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 =

Sub-Contractor


Sub-Contractor


Ent = Field Rel = Address

Proc = Language Statement I/O = Control Block

Node = Addresses Link = Protocols

People = IdentityWork = Job

Time = InterruptCycle = Machine Cycle

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 =


DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

y

DATAWhat

FUNCTIONHow

NETWORKWhere

PEOPLEWho

TIMEWhen

MOTIVATIONWhy

y

IT/Business architecture transformation


TOGAF 9TOGAF 9


UPDM RFC - Domain Meta Model SummaryUPDM RFC Domain Meta Model Summary


Zachman with OMG standardsZachman with OMG standardsData Function Network People Time Motivation

(What) (How) (Where) (Who) (When) (Why)

Scope(Contexts)

List of things importantto business

SBVR

List of processes thatthe business performs

VDM

List of locations whichthe business operates

VDM

List of organizationsimportant to the business

OSM

List of events/cyclesimportant to the business

DTFV

List of businessgoals/strategies

BMM

Business(Concepts)

System

Semantic ModelODM,

IMM (CWM)

Business ProcessModel

BPMN, CMPM

Business LogisticsSystem

BPMN, CMPM

Workflow ModelOSM, BPMN,

CMPM

Master ScheduleBPMN, CMPM,

DTFV

BusinessPlan

SBVR

Logical Data Model Application Distributed Human Interface Process Structure Business RuleSystem(Logic)

Technology(Physics)

gODM,

IMM (CWM), UML

ppArchitecture

SoaML, UMLSystem Architecture

SoaML, UMLArchitecture

BPMN, CMPMBPMN, CMPM,

DTFVModel

SBVR

Physical Data ModelIMM (CWM), UML

System DesignSoaML, UML


SoaML UMLPresentationArchitecture

Control StructureBPMN, CMPM,

DTFV

RuleDesignSBVR(Physics)

Component(Assemblies)

( ) SoaML, UML DTFV SBVR

Data DefinitionIMM (CWM), UML

ProgramUML

NetworkArchitecture

UMLSecurity

Architecture

TimingDefinitionDTFV

RuleDefinitionSBVR

Operation(Instances)

Data Function Network Organization Schedule Strategy


OMG standards coverageOMG standards coverageData Function Network People Time MotivationData

(What)Function

(How)Network(Where)

People(Who)

Time(When)

Motivation(Why)

Scope(Contexts)

List of thingsimportant

to business

List of processesthat the business

performs

List of locationswhich the business

operates

List of organizationsimportant to the

business

List of events/cyclesimportant to the

business

List of businessgoals/strategies

BMMVDM OSMSBVR( )

Business(Concepts)

p p

Semantic ModelBusinessProcessModel

BusinessLogisticsSystem

WorkflowModel

MasterSchedule

BusinessPlan

BPMN

CMPMODM

System(Logic)

Technology

Logical Data Model ApplicationArchitecture

DistributedSystem

Architecture

HumanInterface

Architecture

ProcessStructure

Business RuleModel

Physical Data Model System Design Technology Presentation Control Rule

SBVR

DTFVUMLIMM

CMPM

SoaML(Physics)

Component(Assemblies)

Physical Data Model System Design Architecture Architecture Structure Design

Data Definition Program NetworkArchitecture


TimingDefinition

RuleDefinition

DTFV(CWM)

Operation(Instances)

Data Function Network Organization Schedule Strategy


Models on Different Abstraction LevelsModels on Different Abstraction Levels


Agile Service Development FrameworkAgile Service Development Framework


CSI Norway – Center for Service Innovationled by Norwegian Business School, Bergen, SINTEF, AOH, Telenor,..(N ti l C t f R h D i I ti (SFI) 20 M(National Center for Research Driven Innovation (SFI) – 20 Meuro budget, 8 years 2011 – 2018)


CSI planned ActivitiesCSI planned Activities


Businss Model Innovation

The Alexander Osterwalder canvas


Strategyzer (Osterwalder)Strategyzer (Osterwalder)


BMI – Canvases/ModelsBMI Canvases/Models


VDML – Value Modeling St d d l N 2012Standard proposal, Nov. 2012


ServiceML EditorServiceML Editor

Web based modelling editor Web-based modelling editor http://tomcat.thingml.org/backend/poem/repository

User guide

A

http://epf.thingml.org/wikis/neffics/practice.business.service_modelling.base-sintef/guidances/toolmentors/neffics_service_modelling_editor_user_guide_D29F2B87.html

T

Currently being extended to support AT ONE Method (i.e., the Service Innovation practice)

OInnovation practice) http://epf.thingml.org/wikis/neffics/practice.innovatio

n.service_innovation.base-sintef/guidances/practices/service_innovation_F3FED330 html

ND330.html

E


A – Actors Services Architecture (SoaML)A ActorsValue Network (VDML)

Services Architecture (Business-SoaML)Services Architecture (Business-SoaML)

Hybrid notation• Participants (from Value Network)• Conversation (from BPMN 2.0)

• Groups a set of Flows


• Groups a set of Flows

T – TouchpointsT TouchpointsService Journey Mapy p• Service Journey:

Chronological mapping (from the customer point of pview) of a service

encounter.• Model as "Stages"

• Attach touchpoints to pthe different stages

• Library of differenttypes of touchpoints

to select from.


O – OfferingsO Offerings

Service ContractD ili f h• Detailing of the conversation.

• Conversation is the grouping of

fl ( )flows (messages).• Service Contract

defines the interfaces on both

id ( t t )side (structure) and the protocol (behaviour) for

how to use these i t finterfaces.


N – NeedsN Needs

Goals and Objectives• We have not yet implemented

modelling support for needs.• One idea is to use a very small

Example of Goals and Objectives diagram

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


E – ExperiencesE 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 p p

journey (seen from a Service Provider side).

Ref. alsoS i F ll h


myServiceFellow smart phone app

Business Motivation Model (BMM) with MeansRealizations


What is BPMN (Business Process Modeling Notation) ?


BPMN exampleBPMN example


A (1

)Enterprise

Model

UML Profile for POP*• Process• Organisation• Product• …

Business

annotated with

or S

OA

Service Oriented

Architecture Specification

UML Profile for SOA• Information• Service

Prenc

e O

ntol

ogy

annotated with

Model to ModelTransformation

Business Requirements

Analysis

ET fo

Service-OrientedArchitecture Model

UML Profile for Web Services

Model Transformation

• Process• QoSR

efe

Model to Model Transformation

t t d

CO

M

Web ServiceSpecification Model

Agent SpecificationModel

BPEL SpecificationModel

P2P SpecificationModel

Model Transformation

UML Profile for Web ServicesUML Profile for AgentsUML Profile for BPELUML Profile for P2P

Model to Text

annotatedwith

ndin

g

Web ServiceE ti A t f t

Agent BPEL P2P

Model TransformationTransformation

OWL

annotatedwith

Exte

n Execution Artefacts Execution Artefacts Execution Artefacts Execution Artefacts

ATHENA IntegratedRegistry

RepositoryService Wrappers (Enterprise A)

Evaluation & Negotiation of Available Functionality

Cross-org.

Intra-org.

PublicInfrastructure Services

Service Wrappers(Enterprise X)

Service Wrappers(Enterprise Y)

InternalInfrastructure Services

Process Execution Platform(BPEL)

Goal-orientedAdaptive ExecutionPlatform

Goal-orientedAdaptive ExecutionPlatform

ActiveModel Platform(AKMii)

ActiveModel Platform(AKMii)

ComposedWebServicePlatform(WebServices)

Deployment

Ontology


E SemanticSpace

Execution Infrastructure Enhanced Service Interconnection Bus

Existing Enterprise Applications

(BPEL) (Agents)(Agents) (AKMii)(AKMii)

Legend

Message-OrientedPlatform(MQSeries)

Message-OrientedPlatform(MQSeries)

Server-side Component Platform(.NET, J2EE)

Server-side Component Platform(.NET, J2EE)

(WebServices)

Business Process/Agent

Active (Business) Model

Web/Server Component

Middleware Process/Agent

Middleware Component

Adaptive Distributed Resource Mgt Platform (P2P)

EPF ComposerEPF Composer

EPF Composer is EPF Composer isa tool platform for process engineers,project leads projectproject leads, projectand program managerswho are responsiblefor mainteining andfor mainteining and implementing processesfor development organizations or individual projects

Aims to: 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 provide process engineering capabilities by supporting processe

engineers and project managers in selecting, tailoring, and rapidly assembling processes for their concrete development process.


System and objectsy jy jA system is a part of the real world which we choose to regard as a whole separated from the rest of the world during someas a whole, separated from the rest of the world during some period of consideration.

A h l h h id ll i f bjA whole that we choose to consider as a collection of objects, each object being characterized by attributes and by actionswhich may involve itself and other objectswhich may involve itself and other objects.

Mental modell

Manifest ModelReal-Worldphenomenon


Next Lecture, January 21, 2013 Service Innovation and Service Designg

Guest lecture: Marika Lüders Guest lecture: Marika Lüders

AT ONE AT ONE

S i I ti d S i D i Service Innovation and Service Design


INF5120 ”Modelbased System development” · UML 2.0 – what is new in version 2 VDML – Value...

Documents

Transcript of INF5120 ”Modelbased System development” · UML 2.0 – what is new in version 2 VDML – Value...