Semantic Enterprise Architecture

Michael zur Muehlen, Ph.D.Stevens Institute of TechnologyHowe School of Technology ManagementCenter for Business Process InnovationHoboken, New [email protected]

Semantic Enterprise Architecture

1

2

“Vision without execution is hallucination” Thomas Alva Edison

A Story in 3 Parts

3

4

“If it doesn’t make three people angry, it is not a process”

Beyond Reengineering (Michael Hammer, 1996)

Enterprise

Management System

Operational System

5

Operational Information System

Suppliers

Goods and Services

Money

Custo-mers

Planning and Control System

Mgt. Information

Dir

ecti

ve

Management Information

SystemR

eportin

g

Business as a System

6

“All models are wrong, some are useful”George P.E. Box

7

Why Model?

past present future

explain

predict

constrain

guide

8

What are Good Models?

Correct Relevant Economical

Clear Comparable Systematically Designed

ModelQuality

Source: Becker, Rosemann, von Uthmann

9Source: xkcd.com

Understanding Process Modeling

BPMN is a standard notation for business processes, but it is complex (50+ symbols)

Questions:

How expressive is BPMN in theory?

Which parts of BPMN are used in practice?

Which parts of BPMN should be used in practice?

11

BPMN Features

Modeling Practice

BPMN Best Practice

What can BPMN express?

Which BPMN subset do people

use?

How should you use BPMN?

Δ = untapped potential OR unnecessary features Δ = skill deficit

Δ = standard design flaws

12

Normal FlowTask

End EventStart Event / Event

PoolData-Based XOR

Start MessageText Annotation

Message FlowParallel Fork/Join

LanesGateway

Sub-Process (Collapsed)AssociationData Object

Intermediate TimerIntermediate Message

End TerminateSub-Process (Expanded)

End LinkDefault Flow

Inclusive Decision/MergeActivity LoopingException Task

Start LinkEnd Message

End ExceptionComplex Decision/Merge

Event-Based XORMultiple Instance

GroupTransaction

Intermediate EventEnd Cancel

CompensationIntermediate Compensation

Conditional FlowException Flow

Intermediate LinkStart Timer

Off-page connectorStart Rule

Intermediate RuleIntermediate Multiple

End CompensationStart Multiple

Intermediate ExceptionIntermediate Cancel

End MultipleCompensation Association

source: zur Muehlen, Recker (2007)

How to Improve a Standard

13

Analyze BPMN Use

2007

Define BPMN Subset

2008

Engage BPMN

Standards Body

2009

Issue BPMN 2.0 w/

Conformance Classes

2010

Develop Skilled

Workforce

Develop BPMN 2.0

training program

Issue Policy Memo

mandating BPMN 2.0 Use

Add BPMN 2.0 to

Enterprise Standards Registry

While keeping the vendor community continually informed...

enterprise architecture |ˈentəәrˌprīz ˈärkiˌtekCHəәr|

Terminology and composition of enterprise components, their relationships with the external environment, and the guiding principles for the analysis, design, and evolution of an enterprise.

Source: Wikipedia

14

Why Enterprise Architecture?

To Understand

Analyze what already exist

Assess what will be

Main purpose: People Integration/Conversation

To Build

Design what will be within today’s constraints

Set objectives and constraints for detailed speci!cations

Main purpose: Instruction/Guideline

To Verify

Provide a framework for others

Evaluate current practice against existing guidelines

Main purpose: Compliance/Control 15

16

Enterprise Architecture is primarily about People talking to each other...

17

...so we can buildSystems and Services that talk to each other

Enterprise

Management System

Operational System

18


Suppliers

Goods and Services

Money

Custo-mers


Mgt. Information

Dir

ecti

ve


SystemR

eportin

g


19

20

Enterprise

Management System

Operational System

21


Suppliers

Goods and Services

Money

Custo-mers


Mgt. Information

Dir

ecti

ve


SystemR

eportin

g


Problem: Information Quality

1

Problem: Information Overload

2

Problem: Decision Quality

3

Enterprise Architecture IssuesDifferent Framworks

Multiple Views

Many Techniques

UML, IDEF, BPMN, RAD, EPC, PowerPoint and many, many others...

22

<<TupleType>>Activities::PerformerRuleConstrainsActivityOverlap

<<TupleType>>ResourceFlows::PersonnelTypePartOfSystem

<<TupleType>>Activities::ActivityWholeConsumingPartOfActivity

<<TupleType>>ResourceFlows::SkillPartOfPersonnelType

<<TupleType>>Rules::RuleGuidanceOfActivityValidUnitorCondition

<<TupleType>>Activities::ActivityWholeProducingPartOfActivity

<<powertype>>ResourceFlows::ArchitectureOverviewAndPurpose

<<type>>Locations::IntentionallyConstructedInd

ividual

<<TupleType>>Goals::VisionsRealizedByDesiredEff

ect

<<powertype>>ResourceFlows::Information

<<TupleType>>ResourceFlows::PerformerLocationOverlap

<<type>>ResourceFlows::Resource

<<powertype>>ResourceFlows::ResourceType

<<powertype>>Activities::ConsumingPartOfActivity

<<powertype>>ResourceFlows::PerformerType

<<TupleType>>Activities::ActivityPerformedByPerformer

<<TupleType>>Activities::ActivityResultsInEffect

<<TupleType>>ResourceFlows::MaterielPartOfSystem

<<type>>ResourceFlows::EffectObject

<<TupleType>>Capability::CapabilityPerformerManifestation

<<TupleType>>Goals::EffectPartOfCapability

<<TupleType>>Locations::FacilityPartOfSite

<<powertype>>Measures::Measure Type

<<powertype>>ResourceFlows::DomainInformation

<<powertype>>ResourceFlows::ServiceDescription

<<TupleType>>InformationAndData::DescribedBy

<<TupleType>>ResourceFlows::DataPartOfInformation

<<TupleType>>Services::ServiceEnablesAccessTo

<<powertype>>Activities::ProducingPartOfActivity

<<TupleType>>Activities::ActivityChangesEffectObject

<<IndividualType>>Locations::GeoPoliticalExtent

<<TupleType>>ResourceFlows::nameTypeInstance

<<IndividualType>>ResourceFlows::IndividualResou

rce

<<IndividualType>>Locations::PlanerSurface

<<TupleType>>Activities::PerformerSupportingActivity

<<TupleType>>Activities::ActivityPerformerOverlap

<<IndividualType>>ResourceFlows::IndividualPerfo

rmer

<<type>>ResourceFlows::Means

<<type>>ResourceFlows::Performer

<<powertype>>ResourceFlows::Service

<<powertype>>ResourceFlows::PersonnelTyp

e

<<TupleType>>Activities::ActivityResourceOverlap

<<powertype>>ResourceFlows::NameType

<<powertype>>TrainingSkillEducation::Skill

<<TupleType>>Activities::ActivityConditionOverlap

<<TupleType>>Rules::RuleConstrainsActivity

<<type>>Measures::NeedsSatisfaction

Measure

<<powertype>>ResourceFlows::Materiel

<<TupleType>>InformationAndData::namedBy

<<powertype>>ResourceFlows::Data

<<IndividualType>>ResourceFlows::Organizatio

n

<<TupleType>>Activities::ActivityPartOCapability

<<powertype>>ResourceFlows::System

<<TupleType>>Goals::DesiredEffectDirectsActivity

<<IndividualType>>Locations::Location

<<type>>Services::ServicePort

<<TupleType>>Services::PortPartOfPerformer

<<type>>Measures::Maintainability

Measure

<<IndividualType>>Locations::Site

<<type>>Measures::Organizational

Measure

<<IndividualType>>Locations::Facility

<<TupleType>>Project::GoalsRealizedByProject

<<TupleType>>InformationAndData::tuple

<<NameType>>ResourceFlows::Address

<<TupleType>>InformationAndData::DataAss

ociation

<<powerType>>Services::ServiceChannel

<<type>>Measures::PhysicalMe

asure

<<type>>Measures::SpatialMea

sure

<<type>>Measures::Performanc

eMeasure

<<type>>Measures::AccuracyPr

ecision

<<type>>Measures::RateThroug

hput

<<type>>Measures::Capacity

<<type>>Measures::Dependabili

ty

<<type>>Measures::Trustworthi

ness

<<type>>Measures::Reliability

<<type>>Measures::Security

<<type>>Measures::ServiceLev

el

<<type>>Measures::Adaptability

Measure

<<type>>Measures::Interoperabi

lity

<<type>>Measures::EffectsMea

sure

<<type>>Measures::Cost

<<IndividualType>>Locations::GeoFeature

<<IndividualType>>Locations::Surface

<<IndividualType>>Locations::Line

<<IndividualType>>Locations::Point

<<IndividualType>>Locations::Country

<<IndividualType>>Locations::RegionOfCo

untry

<<IndividualType>>Locations::SolidVolum

e

<<IndividualType>>Locations::Installation

<<TupleType>>Locations::SitePartOfIn

stallation

<<IndividualType>>Locations::RealPropert

y

<<IndividualType>>Goals::Vision

<<IndividualType>>Goals::Goal

<<powertype>>ResourceFlows::Organ

izationType

<<type>>Services::Port

<<IndividualType>>Measures::Measure

<<powerType>>Rules::TechnicalStandard

<<type>>InformationAndData::Thing

<<type>>Measures::Timeliness

<<NameType>>ResourceFlows::Name

<<powerType>>Activities::ServiceFunction

<<individualType>>Rules::FunctionalStandard

<<TupleType>>Services::InterfaceType

<<individualType>>Rules::Guidance

<<type>>Capability::Capability

<<powertype>>Activities::Activity

<<individualType>>Rules::SecurityAttributes

Group

<<individualType>>Rules::Constraint

<<powerType>>Rules::ServicePolicy

<<IndividualType>>Project::Project

<<powertype>>Activities::Condition

<<individualType>>Rules::Rule

<<individualType>>Rules::Agreement

<<powertype>>Goals::DesiredEffect

<<individualType>>Rules::Standard

<<powerType>>Activities::Event

<<powertype>>Project::Plan

10..*

place2Type

place1TypenameType

place2TypenameInstance

place1Type

wholeInformation

place2Type

dataPart

place2Type

place1Type

place1Type

place2Type

2pointOnLine

place2Typeplace1Type

place2Type

place1Type

place2Type

1..*

place1Type

place1Typeplace2Type0..1

place1Type

nameType

place4Type

place2TypeassociateOne

place3Typerelationship

place1TypeassociateTwo

place1TypethingDescribed

place2Type

tuplePlace2

place1Type

tuplePlace1

place1Typeplace2Type

place1Type

place2Type

place2Typedescription

place2Type

place2Type

place1Type

place1Type

thingBeingDescribed

place2Type

place1Type

place2Type place1Type

place1Type

place2Type

place1Type

place2Type

place1Type

place2Type

place2Type

place1Type

place1Type

place1Type

place1Type

place1Type

place2Type0..*

place3Type

place2Type

place3Type

place1Type

place2Type

place2Type

place2Type

place1Type

place1Type

place2Type

place1Type

place2Type

place1Type place3Type

place2Type0..*

Dependencies (DoDAF 2.0 Spec)

23

OV-1

AV-1

NOTE1

NOTE 1: Developed iteratively as the Architecture Description is developed.NOTE 2: The AV-2 presents all the metadata used in an architecture. An AV-2 shows elements from the DoDAF Meta-model that have been described in the Architectural Description and new elements (i.e., not in the DM2) that have been introduced by the Architectural Description.

AV-2

NOTE2

OV-5b

DIV-1

OV-6c

DIV-2

StdV-2

OV-6a

StdV-1

DIV-3

SV-4

SV-6

SV-10b

SvcV-4

SvcV-6

SvcV-10b

SV-10c

SvcV-10c

OV-2

SV-1

SvcV-1

OV-5a

OV-3

OV-4

CV-x

PV-1

OV-6b

CV-6

SV-9

SvcV-9

SV-2

SvcV-2

SV-8

SvcV-8

parallel relationship

completion order

Viewpoint may/may not be required

NOT a JCIDS Requirement

SV-3

SV-5a

SV-5b

Example: Capability Meta Model

24

Core Description

25

CapabilityActivity/Process/Function

Resource(Data)

realized through

input/output

Resource(Person/System)

performed by

Relationships

26

Activity(Process)

realized through

Sub-Activity(Activity)

In/Out

Decom

posed

Resource

De!ne Capabilities

De!ne Resources

De!ne Activities

De!ne Performers

Capability PerformerPerforms

Vocabulary-driven Architecture

De!ne Capabilities

What is the architecture supposed to

achieve?

Items:

• Objectives

• Features

• Services

De!ne Resources

Which data/resources will be consumed or produced?

Items:

•Nouns

De!ne Activities

Which processes/

activities will provide the capabilities?

Items:

• Verbs

De!ne Performers

Who/What will be

involved?

Items:

• Roles

• Systems

• Actors

C A R P

CARP Baseline

28

Milestones (Process)

29

Use Case (Capabilities)

30

From CARP

Class Diagram (Data)

31

From CARP

Implement

ModelSimulate

Modeling & Simulation

32

Shared Concepts

semantics |səәˈmantiks|

the meaning of a word, phrase, sentence, or text: such quibbling over semantics may seem petty stuff.

Source: Merriam-Webster

33

Enterprise Architecture

34

Model

Architecture

ModelModelModel

described by

Separate Content and Representation

35

ModelStructure

DomainContent

Model

Architecture

ModelModelModel

Defined by Modeling Language

Organized by Domain

Ontology

described bycaptures

captures

Storing Content and Representation

36

ModelStructure

DomainContent

Model

Architecture

ModelModelModel


Organized by Domain

Ontology


captures

saved as

saved as

Model Data

Vocabulary

Example

This part describes the content of the process(the business logic)

This part describes the layout of the process

(tool-speci!c rendering information)

Target Audience: Domain Expert

Target Audience: Engineer/Implementer

38

ModelStructure

DomainContent

Model

Architecture

ModelModelModel


captures

saved as

saved as

Model Data

Vocabulary

Consistent Rendering from Requirements Capture to

Implementation

Fit-for-Purpose Rendering based on Stakeholder

Needs

Focus

Organizing Domain Content

39

ModelStructure

DomainContent

Model

Architecture

ModelModelModel


Organized by Domain Ontology


captures

contains

containsTerms & Concepts

Constraints

apply to

Semantic Example

40Source: Moran (2011)

2

Design Time

Run Time

Process Semantics (e.g., activity labels)

BPMN Semantics (e.g., objects +

connectors) Payload Semantics (e.g., data objects +

messages)

Payload Instance Semantics (e.g.,

case data + messages)

Processing Behavior (e.g., audit trail)

Layout (placement of objects)

Metadata (e.g. author, version, validity)

42

SO WHAT?

43

So what?

Semantic approach leverages ontologies to describe domains and content

Need upper ontology to provide primitives

For elementary concepts (capability, activity, resource, performer, event, ...)

For elementary properties (metric, objective, condition, ...)

Need domain ontologies to provide context

Domain-speci!c context (key data elements, processes, actors, ...)

Domain ontologies map to concepts in the upper ontology

Need system ontologies to provide architecture details

System-speci!c content

Map to domain ontology or directly to upper ontology

Integration via mapping of shared concepts, not rede!nition

44

Semantics....

45

Thank You - Questions?

Michael zur Muehlen, Ph.D.

Center for Business Process Innovation

Howe School of Technology Management

Stevens Institute of Technology

Castle Point on the Hudson

Hoboken, NJ 07030

Phone: +1 (201) 216-8293

Fax: +1 (201) 216-5385

E-mail: [email protected]

Web: http://www.stevens.edu/bpm

slides: www.slideshare.net/mzurmuehlen

46