inf5120 ”modellbasert systemutvikling” ”modelbased …...ontologies bus.process bus.rules...

INF5120 Modellbasert Systemutvikling 05.03.2007

1

1Telecom and Informatics

INF5120”Modellbasert Systemutvikling”

”Modelbased System development”

Forelesning F7 05.03.2007

Arne-Jørgen Berre


INF5120 - Forelesninger - 2007

AJB: ArneAJB: Arne--JJøørgenrgen Berre, Berre, BRE: Brian ElvesBRE: Brian Elvesææterter GKOGKO: : GGøøran K. Olsenran K. Olsen

� MDSU (Bok 1 – part 1 og 2) – fra 22/1� 1 22/1: Introduction to MBSU, MDA, OO and modeling (M1-M5)� 2: Metamodeling and UML profiles, MDA technologies (Eclipse technologies) (M2, M4, M6)� 3: Language Engineering and DSL (M8)� 4: Model transformations with ATL and other technologies (M10, M11� 5: Code generation with MOFScript and other technologies (M9

� COMET – New development (Bok 1 part 3, Bok 2 COMET) – fra 26/2� 6 26/2: Method Engineering and Process – and COMET overview (M13)� 7: 5/3: Enterprise Architecture and Modeling (EA) � 8: COMET Business Modeling and Requirements Modeling� 9: SOA Architectures and platforms (SOA) and COMET Architecture Modeling and PIM4SOA and UPMS� 10: PIM and Web Services teknologi (PSM) med WSDL/XML/BPEL,

� MDI (Bok 3 - MDI) - fra 16/4� 11 16/4: Interoperability and MDI – EIF and EIM� 12: Ontologies and Semantic web and Modeling� 13. NFA, OCL and QoS - ?� 14. MDA, SOA and MDI in practice – Trends and future� 15. 14/5 Course summary


2


Enterprise Architecture and Enterprise Modeling

� Enterprise Architecture

� Systems Architecture

� Methodologies (e5, p111-140, SEI/CMM, Zachman)

� Architectural Frameworks (C4ISR-AF, RM-ODP, MAF, TOGAF/DODAF, ….

� Enterprise Unified Process

� Enterprise Modeling

� ATHENA POP*

� ArchiMate example

� Next: COMET Methodology


PIM + Semantics

CIM + Semantics

TR/QVT

PSM + Semantics

TR/QVT

BPEL, WSDL, XML, XPDL,

OWL-S, WSML, WSDL-S

TR/M2T ADM

ADM

ADM

Model-Driven

Business-oriented

Semantic

Service Architectures

and Engineering

Enterprise

Modeling

Enterprise

Architecture


3


Enterprise Architecture and Enterprise Modeling

� Enterprise Architecture

� Systems Architecture

� Methodologies (SEI/CMM, Zachman)

� Architectural Frameworks (C4ISR-AF, RM-ODP, MAF, TOGAF/DODAF, ….

� Enterprise Unified Process

� Enterprise Modeling

� Next: COMET Methodology


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?


4


PIM-K

CIM-K

Ontologies Bus.Process Bus.Rules Goals NFA/Qualities Org

BPDM, SBVR,

EDOC,UPMS,

PIM4SOA, ODM

PSM-K

BPMN, POP*, ARIS,

ArchiMate,

GERAM, GRAI, Zachman,

UEML, B.Rules. ..

Technologies/Realisation-K

UML profiles and

metamodels for BPEL, WSDL, XML,

XPDL,

OWL-S, WSML, WSDL-S

Technology

Reliastion

Code

Information Process Services Rules NFA UI

Data Wflow/Comp Interfaces Rules NFA UI

XML, BPEL/XPDL, WSDL, SWRL, Security, AJAX

OWL, OWL-S/WSML WSDL-S, Induction, … QoS

Legacy and New systems/services, ERPs/ESAs


PIM-K

CIM-K

BPDM, SBVR,

EDOC,UPMS,

PIM4SOA, ODM

TR/QVT

PSM-K

TR/QVT

BPMN, POP*, ARIS,

ArchiMate,

GERAM, GRAI, Zachman,

UEML, B.Rules


OWL-S, WSML, WSDL-S

TR/M2T ADM

ADM

ADM

UML profiles and

metamodels for BPEL, WSDL, XML,

XPDL,

OWL-S, WSML, WSDL-S

Code

PIM-K

CIM-K

TR/QVT

PSM-K

TR/QVT


OWL-S, WSML, WSDL-S

TR/M2T ADM

ADM

ADM

Code

Semantic

Interoperability

Part 3: MDI

Model Driven

Interoperabtiliy

Organisational

Interoperability

Technical

Interoperability


5


Some references

� Enterprise Unified Process: http://www.enterpriseunifiedprocess.info/

� SEI (CMM) etc: http://www.sei.cmu.edu/sei-home.html

� EA: http://www.enterprise-architecture.info/

� Software Architecture: www.wwisa.org

� Archimate: www.archimate.com


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?

??


6


What is Enterprise Architecture

� Enterprise Architecture (EA) is a generic, abstracted and aggregated representation of the core structures and competencesof an enterprise.

� EA supports laying out the main characteristics of the enterprise to be analysed and agreed before detailed technical design is started.

� It is shared and discussed enterprise-wide between all stakeholders as a common description forms, functions and features, components, properties and relationships.


Industrial Definition

EA is the holistic expression of the enterprise’s key business

knowledge, information, application and technology strategies and

their impact on business functions and processes, that:

• Guides investment strategies & decisions • Provides the framework needed to innovate the business• Consists of the current targeted Active Knowledge Models (AKM):

EBA : Enterprise Business ArchitectureEKA : Enterprise Knowledge ArchitectureEIA : Enterprise information ArchitectureEAA : Enterprise Application Architecture

ETA : Enterprise Technology Architecture • Oversees integration across the core architectures provides a synchronized set of EA artifacts that needs to be created, collected, organized, & communicated to enable adaptation to change (business & technology)• Is defined and deployed through the Companywide Process Councils


7


“Architecture”…what is it anyway?

1) “Architecture” Definitionsa. The design, structure, or pattern of anything.

b. A unifying or coherent form or structure<the novel lacks architecture>.

c. Design, the way components fit together.

d. The manner in which the components of a computer or computer system are organized and integrated.

e. The manner of construction of something and the disposition of its parts.

f. Formation or construction as (or as if) the result of conscious act <the architecture of the garden>.

2) “Architecture” is not:a. Just a list of standards and predefined views (product, process,

technical)…


Enterprise architecture

Business

Information

Operational

Organisational

Architectural

Infrastructure


8


Architecture agility

Enterprise

Architecture

Organisational

Business Goals

Qualities

Processes

Practices

- systems


ICT and Software Domains of All Spaces

Enterprise Spaces and Knowledge Dimensions

System vs. Enterprise Architecture

Knowledge

Competence

Signals

Data

Information

Experience

Wisdom

Signals

Data

Information

Knowledge

Experience

Competence

Wisdom


9


Representations of Architecture

ARISZACHMAN GERAM

EN/ISO 19439

NIST

EKA -POPSEKA -POPSEKA -POPS

Athena OEA


Three Views in DOD Architecture Framework and C4ISR-AF


10


To-be Operational DoDAF

As is To bearchitecture

Target

architecture

Architectural models supportedby the necessary tools.

Organisation

Hub

Current

Architectural Standards

New Form of Service-Team Organization

To-Be


Enterprise Architecture Viewpoints

Enterprise

Business

Architecture(EBA)

En

terp

rise

Arc

hite

ctu

re

Enterprise

KnowledgeArchitecture

(EKA)

EnterpriseApplication &

Architecture

(EAA)

Enterprise

TechnicalArchitecture

(ETA)

(EA)

• Business Processes

• Information Flows (between

Processes)

• People, Teams, RAA

• Business Policy & Strategy

• Business Information

• Information Policy & Strategy

• Applications

• Application Data

• Data Flows (between Apps)

• Application Policy & Strategy

• IS Platform and Infrastructure

• Hardware & OS

• SW Services & Middleware

• Productivity Apps.

• Technical Policy & Strategy

• Integrates AcrossEBA,EKA,EIA, EAA


11


Different kinds of Architecture

Business architectureIntegrating Infrastructure

Conceptual architecture

Architecture framework

Logical architecture

Knowledge architecture

Information architecture

Realisation architecture

Functional architecture

ICT architecture


User’s Problems

� A lot of enterprise architecture proposals on the ‘market’

� However, it is usually difficult to

� understand

� compare

� choose

� It is not easy for anyone to survive in the “jungle” of Enterprise Architectures


12


Researcher’s Problems

� There is no justification, nor evaluation of existing enterprisearchitectures

� No adequate architecture representation language, too many different views and levels of detail

� Confusing notions between Enterprise Architecture, Enterprise Model, Enterprise Infrastructure (platform)

� Lack of standardized terminology and collaboration between different EA communities (system engineers, software engineering,…).


Engineer’s Problems

� There is no ‘architecture continuity’, it is difficult to transform an architecture from conceptual to implementation levels, and vice versa;

� There is no ‘architecture interoperability’, enterprise applications built on different architectures are not interoperable;

� There is no scientific ‘architecture principles’ like we have in the construction or shipbuilding domains, enterprise architecting is still a matter of experience.


13


Enterprise Architecture as a ‘skeleton’

� An architecture is a description of the basic arrangement and connectivity of parts of a system

� have properties that can be verified with respect to user needs (ex. open or closed architecture, interoperable or not, centralised or decentralised…).

� be simple so that business people can easily understand, check, analyse, discuss as a ‘language’ shared at corporate level.

� have a style (by comparison with construction where architecture can represent some particular characteristics of a building such as ‘gothic’, ‘romaine’…). EA should be able to characterise enterprise systems (ex. ‘fractal’, ‘holonic’, or ‘agile’...).


Concluding Summary

There is a need to develop commonly accepted architecture representation and specification languages – EKM models !

To describe and represent a common point of departure for families of enterprise solutions – the deliverables of EA

To support managers and project leaders in their strategic and business operational decisions

To answer a key problem: architecture continuity along the wholelife cycle (requirements, design, implementation)

To amplify features of various architectures so that comparison and choice become easier for users

To ensure interoperability between applications built from various architectures

To support new approaches and methodologies to most engineering disciplines.


14


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


Platform

Model

Component implementationmodel

Bu

sin

ess D

om

ain

Syste

m D

om

ain

Model world Real world

Concepts& Artifacts

Processes

Actors

Business (Context)

Model Goal Model

ComponentModel

Visionfor change

Context statement

Risk analysis

Business Process & RoleModel -> WARM

Business Resource Model

Deployment

User ServiceTier

User ResourceService Tier

LS

Legacy

Business

ServiceTier

ResourceService

Tier

Presentation Tier

UserDialog Tier Co

mp

on

en

t Infra

stru

ctu

re

&W

ork

flow

En

gin

e (M

icro

wo

rkflo

w)

User

Serv

ice

Do

main

Bu

sin

es

s S

erv

ice

Do

main

UserInterface

Tier

RARA

LA

Workflow Service Domain

Component structure

Interface and interaction specification

Busines domain to system domain

mapping

•Work element analysis•Use case refinement and BCE

Work Element Analysis Model

Use case model

RequirementsModel

Use case Scenario Model

PrototypeSystem Boundary

*BCE Model

COMET


15


Enterprise Unified Process (EUP)

� The Enterprise Unified Process : Extending the Rational Unified Processby Scott W. Ambler, John Nalbone, Michael J. Vizdos

� Chapter 6

� and book to be published (early 2005)


EUP Lifecycle


16



Next

� ArchiMate Enterprise Architecture example

� Report: ArchiMate Language Primer (27 pages)

� 12/3: COMET – Business Modeling, ….


17


OBLIG 2a – Gruppe oppgave

� Dann grupper nå (3-5 per gruppe)

� Levering onsdag 11. april

� Gjennomgang mandag 16.april

� Oppgave 2a: Modellbasert utvikling av Nettbutikk system med tjenester for video/MP3 salg

� Bruk COMET metodikken og RSM med COMET UML profil, Lag Business Modell, Krav Modell og Arkitekturmodell, og MOFScript for ågenerere WSDL spesifikasjoner for tjenester fra arkitekturmodellen uttrykt i henhold til COMET metodikken

� Oppgave 2b – med utvidelse, kommer senere, levering onsdag 2. mai, gjennomgang mandag 7. mai

inf5120 ”modellbasert systemutvikling” ”modelbased …...ontologies bus.process bus.rules...

Documents