Distributed Collaborative Enterprise Modeling Tutorial @ CAiSE'07

inspired!IT Consulting Training Research Tools

Collaborative, Distributed Enterprise

Modelinga CAiSE 2007

Tutorial byGraham McLeod

inspired!IT Consulting Training Research ToolsCopyright 2007

Abstract

Collaborative, Distributed Modeling (1.5 hrs)

For too long the architecture effort in many organizations has been concentrated in the hands of a few experts, usually in a central location.This typically causes a bottleneck where architecture cannot keep pace with business change and where results are not effectively translated to action, making architecture an "ivory tower" exercise.

In other cases, where work is done by various groups (e.g. process, applications, data, technical) it is extremely difficult to integrate the outputs/models of the various groups meaningfully and to achieve a coherent "big picture". Problems include scope, notation, nomenclature, naming, timing, ownership and language.

This tutorial covers how these issues can be addressed by consistent, shared meta models, standards, education; distributing the architecture effort; and new tools which support distributed collaborative modeling.

Advantages include: higher quality input and models; acceleration of the architecture effort and higher levels of buy-in across the organization leading to higher architectural compliance and associated benefits.


AgendaChallenges for Architects/Architecture in the OrganizationA Vision of CollaborationEnabling Collaboration

ModelsMethodsTool Support

FuturesQuestions Ex

erci

ses a

nd

Dem

onst

ratio

n


BackgroundWork in Enterprise Architectures since 1990Linking Strategy, Architectures, Programme Management, Delivery MethodsMixed Industry and AcademicExperience with various frameworks, meta models and tools

Zachman, Inspired, DoDAF/C4ISR

Application in S.A., USA, UK, AustralasiaBanking, Assurance, Media, Healthcare, Retail, Communications, GovernmentParticularly in high deadline pressure, distributed organizations

Tool Support since 2000Archi


EA

SCOPE

MANAGEMENT

CO

VER

AGE

RIGOUR &

INTEGRATIO

N

TOOLS

INTEGRATEDPROGRAM MGMT

SCENARIOS

INDUSTRY STD PROCESS

VIA PROCESS

AD HOC

TECHNOLOGY

INFORMATION

APPLICATIONS

ENTERPRISE

INDUSTRY

QUALITY

RISK

COST

STRUCTURE

FORMAL MODELS

META MODEL

NONE

AD HOC

CASE TYPE

REPOSITORY

PROCESS

ARTIFACTS

COLLABORATIVEMODELING

AGENDA

TimeTime

How the EA Discipline has Evolved


The Oracle at DelphiAll knowledge collected at a central pointOne wise person who can provide answersLong trek to get there and long wait before you get an "answer"By the time you get back home you may have forgotten it, or it may no longer be the "correct" one! If you are the "oracle" it's a major stress

Challenges



Challenges

Rowing in CirclesTrying to do it all yourselfToo busy to get perspective and maintain directionToo much workVery slow progress, if any...



Challenges

Rowing in CirclesTrying to do it all yourselfToo busy to get perspective and maintain directionToo much workVery slow progress, if any... A better scenario..A better scenario..


Challenges..Multiple Lenses

The more eyes/hands/heads &formats information passes throughbefore it reaches us, the more inaccurate it is likely to be


Challenges..Multiple Lenses

The more eyes/hands/heads &formats information passes throughbefore it reaches us, the more inaccurate it is likely to be

Geography and Time Zones

Difficult to get information from all parts of the organizationDifficult to get people to communicate in real time


Integrating PerspectivesBusiness, process, data, application, technical, risk, cost...Complicated by different notations, semantics, naming, categorisation, tools, formats

Challenges...

??


Integrating PerspectivesBusiness, process, data, application, technical, risk, cost...Complicated by different notations, semantics, naming, categorisation, tools, formats

Challenges...

??

Identifying elements consistently

Debtors DB vs Deb0010Payroll vs QPac


ChallengeUsing the provided "framework" for a buildingAs an individual

Fill in the framework with the relevant information regarding your own home

Roof

DoorWindows

Walls

FoundationFloor

Electrical SupplyFood

HeatingDevice


ChallengeUsing the provided "framework" for a buildingAs an individual

Fill in the framework with the relevant information for this building

Roof

DoorWindows

Walls

FoundationFloor


Heating Device


ChallengeUsing the provided "framework" for a buildingAs a team

Fill in the framework with the relevant information for this building

Roof

DoorWindows

Walls

FoundationFloor


HeatingDevice


What can we learn from this?Seldom that one person has all the infoSometimes we just have a superficial understanding

But at least we know "about" something - that it exists!

Need a teamEach knowledgable about their own area / environment / responsibilityTo put the whole picture together

Can build the picture at various levels of detail..Just lists of thingsOr including relationshipsOr detailed information about things

Many attributesOr whole nested architectures

Relationships are equally important to thingsPicture could be built incrementally as we discovered thingsHelps if we have consistent naming

And access to what others have already done

Definitions are really importantWhat is a "Food Heating Device"?


Benefits of CollaborationInvolvement of more perspectives and subject expertsHigher quality input and modelsDistribution of effort and greater total effort appliedReduction of time to produce resultsHigher awareness and buy in of all relevant parts of the organization => higher architectural complianceGreater agility


The Web vs The LibraryLibrary

Central StoreOne way of organizing content

e.g. Dewey or AuthorSpecialist PersonnelLimited Access

LocationTimeAssistance

Single presentation formatLimited searchDated ContentCool for researching the past

WebDistributedn ways of organizing, indexing, linking contentDomain expert personnelVery Wide Access

AnywhereAnytimeUnaided

Multiple presentation formatsPowerful SearchDynamic, Current ContentBetter for building the future


Like a Central Nervous SystemMultiple sensory organs

Knowledgeable people in the organization and partners

FilteringBased upon models of what we need and how it fits

Storage & MemoryElements stored with rich content in repository

LinkingRich connections make every item more meaningful

AnalysisAnalysis adds meaning and new information

RecallRich query, search, reporting, formatting and output options

ActionInformation and insights available to all other organs to respond appropriately

FeedbackCommunication for how actions affect the world


Who to InvolveBusiness GoalsScope of Activity

Map onto FrameworkCoverage: ZachmanProcess: TOGAF

Map onto Meta ModelInspired, C4ISR

Depth (Abstraction vs Detail; Type vs Instance)Organization (& External)

ResponsibilityGeography

TimeframeArchitecture view (current, horizon)Project

Questions to be AnsweredDesired Outputs/Artifacts (Viewpoints)

Who has knowledge?needs to be committed to result?will be affected by the result?can trip us up?has skills?can take decisions?


Managed ChaosMeta ModelsVocabularyTaxonomy (Reference Frameworks)AuthorityResponsibilityReviewNotificationStatus

Cathedral of Saint Vitus by Josef Sudek 1928


StandardsNaming

Vital for consistency, searching, sorting, relating

Minimum documentation (e.g. Description)

One way to discourage "new" ones when they should be re-used

Agreed Meta ModelAbsolutely vital to ensure:

Coverage of required concepts and scopeAgreed types and their meaningRequired relationshipsDesired attributesScope of a particular effortIntegration of elements from diverse sources

Agreed ProcessE.g. TOGAF ADM

NotationE.g. Archimate; BPMN (we do not recommend UML, except for Data/Static Models)

Only ensure a "minimal achievement level"


VITAL Role of Meta Model

Architect = ConductorMeta Modeler = Arranger


FrameworkProvides

User Defined

ApplicationFunction

ApplicationType

Application Scenario

categorises provided by

part of

Status

Transactional

BankMaster

RetailBanking

2006 Optimistic

Upgrade to Rel 3

categorises provided by

part of

Meta Model

Logical

Physical

Content Model

Modeling at two levels of abstraction


Partners

BusinessCommunication

Location

Step Step Step Step Step Decision Decision Decision DecisionStakeholder

BusinessEvent

Business Process

Step Step Step Step Step

Decision Decision Decision Decision

govern

Business Rules

occurs at

triggers

includes

BusinessObject

responsiblefor

Organization

initiates

BusinessGoal

supports

uses/generates

uses/changesstate of

Product/Service

produces

Resource

usedby

provides

receivedby

KeyIndicators

monitoredby

SubProcess

Supportedby

Application

Deals

Business Unit

Model

Business Objective

Business Event

Resource Type

Business Function

Artifact

Business Goal

Data Collection

Application SystemResource Usage

Assessment

COBIT Domain

COBIT IT Resource Type

Location

Key Indicator

System Function

PersonRole

COBIT Information Criterion

Role

Architecture Scenario

Business Process

Activity Outcome

Activity Sequence

Business Communication

Product-Service Category

COBIT Control Objective

Process Activity

Business Rule

Model Item

Stakeholder Type

Risk Type

Activity Type

User Type

Partner

Person

ITIL Control

Business Object

Deal Type

Customer Type

dealor

dealee

dealee

dealor

works for

employs

is governed by governsis governed by

governs

is governed by

governs

is governed by

governs

is associated with

has associations

is associated withhas associations

is associated with

has associations

member of

has members

is part of

includes parts

is responsibility of

is responsible for


is responsible for

owned by

owns

owned by

owns

owned by

ownsis produced by

produces

triggered by

triggers

has

belongs to

supports

is supported by

relates to

is related to

outputs

output from

is supported by

supports

triggered by

triggers inputsinput to

relates to

is related to

supports

is supported by

supportsis supported by supports

is supported by

precedes

follows

relates tois related to

is part ofincludes parts

uses

is used by

accomodates

occurs at

implemented by

complies with

is part of

includes parts

is part of

includes parts

input to inputs

output fromoutputs

monitored bymonitors

writes

written by

included inincludes

precedes

follows

input to

inputs

output from

outputs

is used by

uses

owned byowns

is governed by

governs


is responsible for

monitored by

monitors

owned by

owns

is used by

uses

is responsible for


is affected by

affects

controls

has control controls

has control

controls

has controlis part of

includes parts

supports

is supported by

supportsis supported by

accomodates

occurs at

primary criterion forprimary criterionexhibited by

prone to

secondary criterion for

secondary criteria

applicable to

uses resource

is altered by

alters

application

initiates

relates to

is related to

quote

quote for

is part of

includes parts

inputs input to

assists in delivering

is partly produced by

prefers

is preferred by

outputs output fromsupplies

supplied by

is used by

uses

is part of

includes parts

categorisescategorised by

supports

is supported by

accomodates

occurs at

is governed by

governs

relates to

is related todealor

dealee

dealee

dealor

works for

employs

member of

has members

triggered by

triggers

owned by

owns

is used by uses


is responsible for

triggered by

triggers

fulf illed by

fulfills

is part of

includes parts

relates to

is related to

(partially) implements

maps to

acquired by

acquires

is part of includes parts relates to

is related to

dealor

dealee

dealee

dealor

works for

employs

member of

has members

triggered bytriggers

Bus ines s Unit

M ode l

Bus ine s s O bje ctiv e

Bus ines s Ev e nt

R e sour ce Ty pe

Bus ine s s Func tion

A rtifa c t

B usine s s Goa l

D ata Colle c tion

Applic ation Sy s te mR es ourc e Us a ge

A ss e s s m ent

CO BIT Dom a in

CO BIT IT Re s ourc e Ty pe

Loc a tion

Ke y Indica tor

Sy s te m Func tion

Pe rs onRole

C OB IT Inform a tion Cr it er ion

R ole

A rc hit ec ture Sc e na rio

Bus ine ss Proc e s s

Ac tiv ity O utc om e

Ac tiv it y Se que nc e

Bus ine s s C om munic a tion

P roduc t-Se rv ice C ate gory

C OBIT C ontrol Obje c tive

Proc e s s Ac tivity

Bus ine s s R ule

Mode l Ite m

St ak e holde r Ty pe

Ris k Type

A ct iv ity Ty pe

Us e r Ty pe

Pa rtne r

Pe rs on

ITIL C ontrol

Bus ine s s O bje ct

De a l Ty pe

Cus tom er Type

de a lo r

d e a lee

d e ale e

d e alo r

wo rks fo r

em p loy s

is g o ve rn e d b yg o ve rn s

is g o ve rn e d b y

g o v e rns


go v e rns

i s go v e rn ed b y

g ov e rn s

i s a s so c iate d wi th

h as a ss o cia ti on s

i s as s oc ia te d wi thh a s a ss o c ia ti on s

i s a ss o cia ted wi th

h as a ss o cia tio n s

m e mb e r o f

ha s m em b e rs

i s pa rt o f

i n clu d es p a rts

i s res p o ns ib il i ty o f

is re sp o n sib le fo r

i s r es p o ns ib il i ty o fis re s po n s ib le fo r

o wn e d b y

o wn s

o w ne d b y

o wn s

o wn e d b y

ow n sis p ro d uc e d by

p ro d uc e s

tr ig g e re d b y

tri g g ers

h as

b e lon g s to

su p p o rts

i s s u p p orte d b y

rela te s to

i s re late d to

o utp u ts

o utp u t from

is s u pp o rte d by

s u p po rts

tri g ge re d b y

tri g g ersin p u ts

in p u t to

r ela te s to

i s re late d to

s u pp o rts

i s su p p o rted b y

s u pp o rtsi s su p p o rte d b y s u pp o rts

i s s u pp o rte d b y

p re c ed e s

fo l l o ws

rela te s tois re la te d to

is p a rt o fin c lu d e s p a rts

u s e s

i s u se d by

a c c om o d ate s

o c cu rs a t

im ple m en te d b y

co m p lie s w ith

i s pa rt o f

in c lud e s pa rts

is p a rt o f

i n clu d e s p a rts

in p u t to in p u ts

ou tp u t fro mou tp u ts

m o n i to re d b ymo n i tors

wri tes

wri tte n b y

in c lu d e d i ninc lu de s

p re ce d e s

fo ll o ws

inp u t to

in p u ts

o utp u t fro m

ou tp u ts

i s u s ed b y

us e s

o wn e d byo wn s

is g o v ern e d b y

g o v ern s

i s re s po n s ib i l ity o f

i s res p o n sib le fo r

mo n i tor ed b y

m o n ito rs

o wn e d b y

ow ns

is u s e d b y

us e s

is re sp o n s ib le fo r

is re sp o n sib i li ty o f

i s a ffe cte d b y

affe c ts

c o ntro l s

h as co n tro lc on tro l s

h a s c o ntro l

c o n tr ol s

h a s co n tro li s p a rt o f

i n c lu d e s p a rts

s u p po rts


s u p p ortsis su p p o rted b y

a c c om o d ate s

o cc u rs a t

p rim ary c rite ri o n fo rp rim a ry cri te rio n

e xh ib ite d b y

p ro ne to

s e c on d a ry c ri ter io n fo r

se c on d a ry cri te ria

ap p l i ca b le to

u se s re so u rc e

is a lte re d b y

a l te rs

a pp l i ca ti on

ini ti a te s

r ela te s to

i s re late d to

q u o te

q uo te fo r

i s p a rt of


in pu ts in p u t to

a s si s ts i n d e l iv e ri n g

i s p a rtl y p ro d u ce d b y

p re fe rs

i s p re fe rre d b y

o u tpu ts ou tp u t fr omsu p p l ie s

s u p pl i e d b y

i s u s e d b y

u se s

i s p a rt o f

i nc lu de s p arts

ca te g o ris e sc a te g o ri se d b y

su p p orts


ac c o mo d a tes

o c cu rs at


g o v er ns

re la te s to

i s rela te d tod e a lo r

d e ale e

d e a lee

d e a lo r

wo rk s fo r

e m plo y s

me m b er o f

ha s me m b e rs

tr ig g e re d b y

tri g g er s

o w ne d b y

o wn s

is u se d b y u s es

i s re s p on s ibi l ity o f

i s re s p o ns ible fo r

tri g g e red b y

tri g g ers

fu l fil l e d b y

fu l fil l s

i s p art o f


re la te s to

i s re la te d to

(p a rtia l l y) im p le m e nts

m a p s to

a cq u i re d b y

a c qu i re s

i s pa rt o f i n clu d es p ar ts re late s to

i s re la te d to

d ea lo r

d ea le e

d e a lee

d ea lo r

w o rks fo r

e m plo y s

m e mb e r o f

h as m e mb e rs

tri gg e re d bytri gg e rs

Conceptual Picture Models

Class Diagrams

Fully Attributed Models Realised in EA Repository

Meta Models Exist at Several Levels


Business Architecture Excerpt

Business Process

includes parts

BusinessCommunication

inpu

ts

Project

is altered by

is part of

System Software Service

Application Service

is supported by

Locationoccurs at

Business Event

outp

uts

triggered bytriggers

Business Objectuses

Organisation Unit

owned by

Business Function/ Business Service

relates to

includes parts

includes parts

is supported by

includes parts

Business Goal

includes parts

is supported by


Information Architecture Excerpt

Business Object

Business Process

contains

specialisesis used by

Organisation Unit

governs

Subject Area

Data Collection

DBMS - File System

includes

implements

includes parts

is used by

Application System uses

Physical Platform hosts

Data Collection Type

is an instance of

Person/Role

is re

spon

sibl

e fo

r

references

role of

Application System


categorises

Application System

includes parts


requiresInterface

provided by

Application Type

is partly produced byis part of

Development Tool

is used by

Projectproduces

Person/Roleis responsible for

User Groupserved by

Locationoccurs at

Physical Platformruns on

Platform Type

Vendorsupplied by

provides

Business Object

Data Collection

DBMS - File System

used by

Organisation

Interface Type

categorises

Application Service

Applications Architecture Excerpt

owns


Technical Architecture Excerpt

Physical Platform

Application SystemData CollectionDevelopment Tool

accomm

odates

Person/Roleis responsibility of

Locationoccurs at

Organisation Unit

owns

Platform Type

host

s hostshosted by

DBMS - File SystemDevelopment Tool Type

cate

goris

es

System Software


provides

provides


Aspects of a Business BUSINESS OBJECTIVES

CLIENTS, MARKETS

PRODUCTS/SERVICES

PROCESSES

Hello, everyone!

Hello, everyone!

SYSTEMSINFORMATION

TECHNICALINFRASTRUCTURE

ORGANISATION/ CHANNELS


Aspects Coordinated

SYSTEMS

INFORMATION

PROCESSES

PRODUCTS/SERVICES

CLIENTS, MARKETS

BUSINESS OBJECTIVES

TECHNICALINFRASTRUCTURE

ORGANISATION/ CHANNELS


Role of Ontologies and Reference Models

Ontology..seeks to describe or posit the basic categories and relationships of being or existence to define entities and types of entities within its frameworkWikipedia

Reference Models (e.g. TOGAF TAM)Provide basic categories and interrelationships for organizing architecture knowledgee.g. Kinds of application systems; kinds of system software; kinds of data

Extremely useful in Providing (a relatively small number of) logical or abstract categoriesto help us understand the (relatively large numbers of) architecture elementsALSO to act as a check list when we are looking for architecture elements

e.g. What applications do we have for Supplier Management; What Multimedia data do we store; What Security Related system software do we have...

Can provide a language independent reference systemVery important in multi nationals with multiple language communities


ProcessIdentify Participants & RolesEducate ParticipantsDeploy Mechanism/ToolsCollect Lists

Use prepopulated taxonomies to accelerateUse pre-existing lists, models and documents Possible use of automated collection (but beware glut of meaningless data)

ABCDE...

CAiSE'08 OrganizationLeft side of room: List 5 Business Goals & 5 Business Events that you would need to deal withRight side of room: List 5 Business Objects & 5 Business Processes required


Process...Identify Participants & RolesEducateDeploy MechanismCollect Lists

Use prepopulated taxonomies to accelerateUse pre-existing lists, models and documents Possible use of automated collection (but beware glut of meaningless data)

Organize into HierarchiesDescribe

A..BC..D..E

CAiSE'08 OrganizationIn a small group, collect 10-12 Elements of a type (e.g. Business Process). See if it is meaningful to rationalise these and arrange in a hierarchy


Process...Identify Participants & RolesEducateDeploy MechanismCollect Lists

Use prepopulated taxonomies to accelerateUse pre-existing lists, models and documentsPossible use of automated collection (but beware glut of meaningless data)

Organize into HierarchiesDescribe

Link Across Types

A..BC..D..E

1..1.12..2.1..2.2

CAiSE'08 OrganizationOK, lets see how these could be related across the two groups..


Process...Identify Participants & RolesEducateDeploy MechanismCollect ListsOrganize into Hierarchies

Describe

Link Across TypesVerifyEnhance Detail

Expand AttributesDecompose

Enhance AbstractionPlan Forward

A..BC..D..E

1..1.12..2.1..2.2

2.2 NameProp1 xxxx Prop2 123 456Prop3 abc

CAiSE'08 Organization - Demonstrate


ExternalArtifacts Content Models

ModelTypes

Rep

osito

ry

Framework(FEAF)

Framework(Zachman)

UserInterfaces

Stakeholders

Artifacts

Guidance

EA Methode.g. TOGAF ADM

ModelTypes

Meta Model

Tool

FrameworkProvides lense thru which to view

Model TypesDefine structure, content and notation for artifacts/Viewpoints

Meta ModelDefines and relates all required concepts, drives capture and viewing interfaces

Content ModelsExpress the architecturecontent

EA Method Guides stakeholders and facilitates the process

ToolProvides facilities to capture, edit, store, relate, model, report, search, analyse and share

Role of Repository and Tooling


Product Architecture

User Models

Web Server

Archi/Webmodeler Server

Relational DBMS

Meta Model

System Settings

ManagedManagedManagedDocuments

ExternalPagesExternalPagesExternalPages

Strategist Program/Project Mgr Meta ModelerSystem Admin

Lan or WWWLan or WWW

Directories

CGI

SQL

HTMLHTMLHTTP/SHTTP/S

In BrowserGraphicalModeler

XMLXML

Desktop Productse.g. Visio

Requestor

COM+

Architects

WebClient

DESKTOPAPPLIC.DESKTOP

APPLIC.

e.g. Word, Excel

OLE

Analysts and Modelers

Templates

Graphical Modeling Interface


Tool SupportAdapt Meta Model

StandardEnhance for GoalsReduce for ScopeAlso as the project progresses...

Assign ResponsibilitiesPerson vs Model Fragment vs Role

Capture ListsWhat have we gotNaming Standards

Organize HierarchiesNatural e.g. Organization; GeographyAbstraction e.g. Process Hierarchy; Service Hierarchy; Application TypesCould be multiple for a type


Tool Support...Link Across Types

Relate, Cross ReferenceSearch/filter and linkMay be data about relationship too..Build Graphical Model

Enhance DetailPopulate required attributes per typeDecompose

Event NotificationWho has done something of interest to me?What data has arrived?

CommunicationNews ThreadsWiki Features

Difference IdentificationAcross Time (Delta Browser)Between Models (Difference Models in GM)


Tool Support...Sharing outputs

Browsing the "knowledge space"Reports, Generated DocumentsAnonymous Access, Portal, Web SitesFeed to other tools e.g. CSV to Excel, XML to analysis toolsStar Schema to DSS tools

Web + Repository + Meta Model + View Points

Capture Templates/FormsReportsMatricesGraphical Models

+ Security + Open Exchange


FuturesVirtual WhiteboardingVideo Conferencing3D Spaces

geoDecMiramarCroquet

ResearchAdvanced meta modeling techniquesCollaborative modeling in virtual spaces

What we can learn from online gamese.g. Spore from Will Wright

EmergenceWhere architectures connect themselves from elements endowed with behaviour and rules

"The best way to predict the future is to invent it" Alan Kay


ReferencesArchimate information at: http://www.telin.nl/index.cfm?project=ArchiMate&language=enCroquet Consortiumhttp://www.opencroquet.orgInspired, Enterprise Architecture Frameworkshttp://www.inspired.orgInspired, Archi Tool Architecture, internal documentationIntel, Miramar projecthttp://developer.intel.com/technology/itj/index.htm Open Group, Togaf 8.1.1 Enterprise Edition, http://www.opengroup.orgUniversity of Southern California, geoDec projecthttp://infolab.usc.edu/projects/geodec/index.jspWikipedia, http://www.wikipedia.comZachman Framework info, Zachman Institute for Framework Advancement, http://www.zifa.org


ContactGraham [email protected]+27 82 578 1834

Inspiredwww.inspired.org+27 21 531 5404