PowerPoint Presentation

The Road to Executable ArchitecturesThe Road to Executable Architectures

Dennis Wisnosky, Wizdom Systems Inc., Dennis Wisnosky, Wizdom Systems Inc.,

[email protected]

Joseph Vogel, Wizdom Systems Inc.,Joseph Vogel, Wizdom Systems Inc.,

[email protected]@wizdom.com

Steven Ring, Mitre Corporation, Steven Ring, Mitre Corporation, [email protected]

Mitre Approved for Public Release, Distribution Unlimited, Case #04-0351

©2004 The MITRE Corporation. All rights reserved

©2004 Wizdom Systems Inc., All rights reserved

** Activity-Based Methodology is a concept developed by The MITRE Corporation and Lockheed-Martin, Copyright Activity-Based Methodology is a concept developed by The MITRE Corporation and Lockheed-Martin, Copyright © © 2003 2003

** DoDAF Minimalist Methodology is a concept developed by Wizdom Systems Inc., Copyright DoDAF Minimalist Methodology is a concept developed by Wizdom Systems Inc., Copyright © © 2004 2004

© 2004 Wizdom Systems, Inc. All rights reserved © 2004 The MITRE Corporation. All rights reserved

2

AgendaAgendaAgendaAgenda

Start With Integrated DoDAF ArchitecturesStart With Integrated DoDAF Architectures

PresentPresent Activity-Based Methodology Activity-Based Methodology (ABM) (ABM)

Present ABM Architecture Specification Model – “ASM”Present ABM Architecture Specification Model – “ASM”

Show steps to integrated Operational and System Architecture Show steps to integrated Operational and System Architecture Descriptions- the “Descriptions- the “Art of ArchitectingArt of Architecting””

Show Transition To “Dynamic” Executable ModelsShow Transition To “Dynamic” Executable Models

Present Executable Architecture Model ParametersPresent Executable Architecture Model Parameters

Show “dynamic” methodologies for executable architecture Show “dynamic” methodologies for executable architecture analysis analysis

Present linking integrated and executable architecture analysis Present linking integrated and executable architecture analysis with investment portfolio strategies and selections with investment portfolio strategies and selections

3

What Are Executable Architectures?What Are Executable Architectures?What Are Executable Architectures?What Are Executable Architectures?

Static Operational Models only show that Activities“must be capable of” producing and consuming Information? No details on event sequencing? No details on how or what conditions information is produced/

consumed? No details on producers/ consumers themselves or other

resources used

Dynamic (over time) Executable Architecture Models go beyond“must be capable of” – “WHENWHEN”Defines precise sequential/ concurrent event modelDefines precisely under what conditions Information is produced/

consumedDefines details on producers/ consumers (number and process

ordering) and other resources (when [not] available)

Dynamic model of Activities and their event sequencing performed at an Operational Node by Roles (within Organizations) using

Resources (Systems) to produce and consume Information

Dynamic model of Activities and their event sequencing performed at an Operational Node by Roles (within Organizations) using

Resources (Systems) to produce and consume Information© 2004 The MITRE Corporation. All rights reserved

4

Agile Organizations Require Adaptable Integrated Agile Organizations Require Adaptable Integrated ArchitecturesArchitecturesAgile Organizations Require Adaptable Integrated Agile Organizations Require Adaptable Integrated ArchitecturesArchitectures

1980’s and earlier

•Organization Focus

•Mainframe centric

•Monolithic•Internal use

1990’s

•Business Process Focus

•Client/Server•Monolithic•Business-to-business via EDI -file transfer

•Virtual organizations•Distributed Functions•Service oriented•Componentized•Real-time•Nework Centric Warfare & E-commerce

New Millennium3rd party service providers

ExtranetInternet

Customers

Modified from Advisory Council Enterprise Architecture SIG, Succeeding with Component-based Architectures – Draft, 2002

How important will this be?How important will this be?

© 2004 Wizdom Systems, Inc. All rights reserved

5

Build Integrated/Dynamic ArchitecturesBuild Integrated/Dynamic ArchitecturesBuild Integrated/Dynamic ArchitecturesBuild Integrated/Dynamic Architectures

Before you can use architecture descriptions for any type of Before you can use architecture descriptions for any type of analysis purposes analysis purposes you must first have an architectureyou must first have an architecture that is that is

– Integrated, unambiguous, and consistentIntegrated, unambiguous, and consistent

What’s an Integrated Architecture?What’s an Integrated Architecture?1. Based on DOD Architecture Framework (DoDAF) products

AV-1, AV-2, OV-2, OV-3, OV-5, SV-1, and TV-1AV-1, AV-2, OV-2, OV-3, OV-5, SV-1, and TV-1 + OV-4 the forgotten product, key to DOTLMPF+ OV-4 the forgotten product, key to DOTLMPF

2.2. Defined by a conceptual Defined by a conceptual Architecture Specification Model (ASM)Architecture Specification Model (ASM)

Most DoDAF architectures are Most DoDAF architectures are staticstatic representations of activities, representations of activities, roles, systems, nodes, …roles, systems, nodes, …

Must supplement static representations with Must supplement static representations with Dynamic, Dynamic, time-dependenttime-dependent behavior models of processes, organizations, behavior models of processes, organizations, and resourcesand resources

Enables a more expanded and comprehensive analysisEnables a more expanded and comprehensive analysis Support funding decisions, acquisitions, system engineeringSupport funding decisions, acquisitions, system engineering

Before you can use architecture descriptions for any type of Before you can use architecture descriptions for any type of analysis purposes analysis purposes you must first have an architectureyou must first have an architecture that is that is

– Integrated, unambiguous, and consistentIntegrated, unambiguous, and consistent

What’s an Integrated Architecture?What’s an Integrated Architecture?1. Based on DOD Architecture Framework (DoDAF) products

AV-1, AV-2, OV-2, OV-3, OV-5, SV-1, and TV-1AV-1, AV-2, OV-2, OV-3, OV-5, SV-1, and TV-1 + OV-4 the forgotten product, key to DOTLMPF+ OV-4 the forgotten product, key to DOTLMPF

2.2. Defined by a conceptual Defined by a conceptual Architecture Specification Model (ASM)Architecture Specification Model (ASM)

Most DoDAF architectures are Most DoDAF architectures are staticstatic representations of activities, representations of activities, roles, systems, nodes, …roles, systems, nodes, …

Must supplement static representations with Must supplement static representations with Dynamic, Dynamic, time-dependenttime-dependent behavior models of processes, organizations, behavior models of processes, organizations, and resourcesand resources

Enables a more expanded and comprehensive analysisEnables a more expanded and comprehensive analysis Support funding decisions, acquisitions, system engineeringSupport funding decisions, acquisitions, system engineering

DoD Architecture Framework 1.0

DoDArchitecture

Framework v1.0

© 2004 The MITRE Corporation. All rights reserved

6

Approach To Dynamic ArchitectureApproach To Dynamic ArchitectureApproach To Dynamic ArchitectureApproach To Dynamic Architecture1.1. Develop fully Develop fully integrated, unambiguous, and consistentintegrated, unambiguous, and consistent DoDAF DoDAF

viewsviews– DoDAF Minimalist Methodology* DoDAF Minimalist Methodology* is a tool-independent is a tool-independent

approach to building DoDAF work productsapproach to building DoDAF work products 11 step process for building those work products necessary to support the 11 step process for building those work products necessary to support the

DoDAF “Integrated Architecture.”DoDAF “Integrated Architecture.” Includes steps for producing work products that support the Joint Includes steps for producing work products that support the Joint

Capabilities Integration Development System (JCIDS)Capabilities Integration Development System (JCIDS) Uses IDEF0, IDEF1X, and UML modeling approaches interchangeably to Uses IDEF0, IDEF1X, and UML modeling approaches interchangeably to

develop DoDAF work products.develop DoDAF work products.

– Activity-Based Methodology (ABM)*Activity-Based Methodology (ABM)* is a tool-independent is a tool-independent approach to integrated DoDAF architecturesapproach to integrated DoDAF architectures Enables both “As-Is” (now) and “To-Be” (future) architecture development, Enables both “As-Is” (now) and “To-Be” (future) architecture development,

gap-analysis, and assessmentgap-analysis, and assessment Uses data centric architecture elements and product renderings and cross-Uses data centric architecture elements and product renderings and cross-

product relationships based on core set of architecture elementsproduct relationships based on core set of architecture elements Captures sufficient representations of architectures to transition to Captures sufficient representations of architectures to transition to

“dynamic” executable process models“dynamic” executable process models



© 2004 The MITRE Corporation. All rights reserved © 2004 Wizdom Systems, Inc. All rights reserved

7

……. using Physical . using Physical Resources (systems) in Resources (systems) in producing & consuming producing & consuming information and datainformation and data

Characterized by Characterized by modelsmodelsof operations of operations (Activities) performed (Activities) performed by Human Resources by Human Resources (people) ….(people) ….

EnterpriseEnterprise

ProgramProgram(Operational/(Operational/System/Tech)System/Tech)

HardwareHardware

SoftwareSoftware

““Architecture View” StackArchitecture View” Stack““Architecture View” StackArchitecture View” Stack


8

Executable Architecture Modeling TechnologiesExecutable Architecture Modeling TechnologiesExecutable Architecture Modeling TechnologiesExecutable Architecture Modeling Technologies

Colored Colored Petri-Net Petri-Net

(CPN)(CPN)

Colored Colored Petri-Net Petri-Net

(CPN)(CPN)

Discrete Discrete EventEvent

Discrete Discrete EventEvent

BPMN/BPMN/BPELBPEL

BPMN/BPMN/BPELBPEL

ExecutablExecutable UMLe UML

ExecutablExecutable UMLe UML


9

DoD Framework ProductsDoD Framework ProductsDifferent Information ViewsDifferent Information ViewsDoD Framework ProductsDoD Framework ProductsDifferent Information ViewsDifferent Information Views

Rules, guidance, and product descriptions for developing and presenting architectures thatRules, guidance, and product descriptions for developing and presenting architectures thatensure a common denominator for understanding, comparing, and integrating architecturesensure a common denominator for understanding, comparing, and integrating architectures

OPERATIONAL (OV)OPERATIONAL (OV) SYSTEMS (SV)SYSTEMS (SV)

1: High-Level Operational Concept Graphic *1: High-Level Operational Concept Graphic *1: High-Level Operational Concept Graphic *1: High-Level Operational Concept Graphic *

2: Operational Node Connectivity Description *2: Operational Node Connectivity Description *2: Operational Node Connectivity Description *2: Operational Node Connectivity Description *

3: Operational Information Exchange Matrix *3: Operational Information Exchange Matrix *3: Operational Information Exchange Matrix *3: Operational Information Exchange Matrix *

4: Command Relationships Chart4: Command Relationships Chart4: Command Relationships Chart4: Command Relationships Chart

5: Activity Model *5: Activity Model *5: Activity Model *5: Activity Model *

6a: Operational Rules Model6a: Operational Rules Model6a: Operational Rules Model6a: Operational Rules Model

6b: Operational State Transition Description6b: Operational State Transition Description6b: Operational State Transition Description6b: Operational State Transition Description

6c: Operational Event/Trace Description6c: Operational Event/Trace Description6c: Operational Event/Trace Description6c: Operational Event/Trace Description

7: Logical Data Model7: Logical Data Model7: Logical Data Model7: Logical Data Model

1: System Interface Description *1: System Interface Description *1: System Interface Description *1: System Interface Description *

2: Systems Communications Desc.2: Systems Communications Desc.2: Systems Communications Desc.2: Systems Communications Desc.

3: Systems Matrix3: Systems Matrix3: Systems Matrix3: Systems Matrix

4: Systems Functionality Description4: Systems Functionality Description4: Systems Functionality Description4: Systems Functionality Description

5: Operational Activity to System5: Operational Activity to System Function Traceability Matrix Function Traceability Matrix5: Operational Activity to System5: Operational Activity to System Function Traceability Matrix Function Traceability Matrix

6: Sys Information Exchange Matrix6: Sys Information Exchange Matrix6: Sys Information Exchange Matrix6: Sys Information Exchange Matrix

7: Sys Performance Parameters Matrix7: Sys Performance Parameters Matrix7: Sys Performance Parameters Matrix7: Sys Performance Parameters Matrix

8: System Evolution Description8: System Evolution Description8: System Evolution Description8: System Evolution Description

9: System Technology Forecast9: System Technology Forecast9: System Technology Forecast9: System Technology Forecast

10a: Systems Rules Model10a: Systems Rules Model10a: Systems Rules Model10a: Systems Rules Model

10b: System State Transition Description10b: System State Transition Description10b: System State Transition Description10b: System State Transition Description

10c: Systems Event/Trace Description10c: Systems Event/Trace Description10c: Systems Event/Trace Description10c: Systems Event/Trace Description

11: Physical Data Model11: Physical Data Model11: Physical Data Model11: Physical Data Model

TECHNICAL (TV)TECHNICAL (TV)1: Technical 1: Technical ArchitectureArchitecture

Profile *Profile *

2: Standards2: StandardsTechnologyTechnology

ForecastForecast

CADM: Core Architecture Data Model CADM: Core Architecture Data Model

DynamicDynamicModelsModels

DynamicDynamicModelsModels

StaticStaticModelsModelsStaticStatic

ModelsModels

SpreadsheetsSpreadsheetsSpreadsheetsSpreadsheets

* Mandatory* Mandatory* Mandatory* Mandatory


10

Wizdom Minimalist Methodology


11

OAOA

SASA TATA

ProcessProcessViewView

ResourceResourceViewsViews

DoD Architecture Framework 1.0

Rules/ConstraintsRules/Constraints

Executable Architectures Consist of Reconfigured OA-Executable Architectures Consist of Reconfigured OA-SA-TA Views supported by KPP’s and KPI’sSA-TA Views supported by KPP’s and KPI’s

Executable Architectures Consist of Reconfigured OA-Executable Architectures Consist of Reconfigured OA-SA-TA Views supported by KPP’s and KPI’sSA-TA Views supported by KPP’s and KPI’s

But, Standards and Methods:But, Standards and Methods:Don’t Exist! Don’t Exist! And, is this important?And, is this important?


12

WhereWhere

HowHow

WhatWhat

Generated ObjectsGenerated Objects

Core ObjectsCore Objects

Container

Asset

Function

Product

WhoWho

Operational SystemEntities

RelationshipsAttributes

RelationshipsAttributes

Entities

Org

Org

NetworkNetwork

KnowledgeSkills & Abilities

KnowledgeSkills & Abilities PerformancePerformance

Symmetrically Aligned DoDAF Architecture Symmetrically Aligned DoDAF Architecture Objects are Building Blocks of ABM Objects are Building Blocks of ABM

Integrated ArchitecturesIntegrated Architectures

Symmetrically Aligned DoDAF Architecture Symmetrically Aligned DoDAF Architecture Objects are Building Blocks of ABM Objects are Building Blocks of ABM

Integrated ArchitecturesIntegrated Architectures

ActivityActivity

InfoInfo

CONOPS

(rules)

CONOPS

(rules)

RoleRole

DataData

DesignRules

DesignRules

SystemSystem

Transfer

Link

Characteristic

Structure

WhyStrategy

CyclesCycles CyclesCyclesWhenBehavior

Need Line

Need Line

InfoExchange

InfoExchange

InterfaceInterface

DataExchange

DataExchange

SystemFunctionSystem

Function

OpNodeOp

NodeSystemNode

SystemNode

PerformerPerformerPerformerPerformer AssetAssetAssetAsset© 2004 The MITRE Corporation. All rights reserved

13

Op NodeOp NodeOperation

alActivity

InfoInfo InfoInfo

Sys NodeSys NodeSystem

FunctionDataData DataData

Role Role SystemSystem

Org Unit Org Unit Role Role System SystemOrg Unit Org Unit Role Role System System

OrgUnitOrgUnit

OV-4

ABM Triple 3-Way Associations ABM Triple 3-Way Associations between Core Entitiesbetween Core Entities

ABM Triple 3-Way Associations ABM Triple 3-Way Associations between Core Entitiesbetween Core Entities

ProducedConsumed

Activity Activity Op Node Op Node RoleRole

Activity Activity Op Node Op Node RoleRole

Op Node Op Node RoleRoleRole Role ActivityActivity

ActivityActivityOV-5

Op Node Op Node ActivityActivity

RoleRoleOV-4

InfoInfoOV-5

ProducedConsumed

Function Function Sys Node Sys Node System SystemFunction Function Sys Node Sys Node System System

Sys Node Sys Node SystemSystem

FunctionFunctionSV-4

System System FunctionFunction

Sys Node Sys Node FunctionFunction

SysteSystemmSV-7

DataDataSV-4

SV-SV-55

SV-SV-55

OpNodeOp

NodeOV-2

SysNodeSys

NodeSV-1


14

ABM Intersections of Core Entities ABM Intersections of Core Entities ABM Intersections of Core Entities ABM Intersections of Core Entities

ActivityActivity

Role

Op Nodes

Op

Act

ivit

ies

RoleRoleRoleRole

RoleRoleRoleRole

Sys Nodes

Sys

Fu

nct

ion

sSysSysSysSys

SysSysSysSys

System

Function

System

Function

SystemSystemOrg UnitOrg Unit

SystemSystemRole

System

Ro

le

OrgOrgOrgOrg

OrgOrgOrgOrg

SystemNode

SystemNode

OpNodeOp

Node


15

Integrated ArchitectureIntegrated Architecture Represented as Represented as Conceptual Conceptual AArchitecture rchitecture SSpecification pecification MModel – odel –

“ASM”“ASM”

Integrated ArchitectureIntegrated Architecture Represented as Represented as Conceptual Conceptual AArchitecture rchitecture SSpecification pecification MModel – odel –

“ASM”“ASM”

SupportsSupportsSupportsSupports

SupportsSupportsSupportsSupportsPerformePerforme

d Atd At

PerformePerforme

d Atd AtPerformePerforme

d Atd At

PerformePerforme

d Atd At

LocatedLocatedAtAt

LocatedLocatedAtAt

LocatedLocatedAtAt

LocatedLocatedAtAt

PerformsPerformsPerformsPerforms PerformsPerformsPerformsPerformsSupportsSupportsSupportsSupports

ConsistsConsistsOfOf




FunctionFunctionActivityActivity

InfoInfo DataData

RoleRole SysteSystemm

OrgUnitOrgUnit

OpNodeOp

NodeSys

NodeSys

Node


16

eadershipeadership

raininrainingg

octrinoctrinee

ateriaterialal

ersonnersonnelel

rganizatirganizationon

acilitiacilitieses

Mapping ASM to DOTMLPF Mapping ASM to DOTMLPF Mapping ASM to DOTMLPF Mapping ASM to DOTMLPF

OrgUnitOrgUnit

FunctionFunctionActivityActivity

InfoInfo DataData

RoleRole SysteSystemm

OpNodeOp

NodeSys

NodeSys

Node


17

InfoExchange

InfoExchange

Render Render InformationInformationExchanges Exchanges

Render Render InformationInformationExchanges Exchanges

Render 3-way Render 3-way associations associations Render 3-way Render 3-way associations associations

NodeANodeA““Act1~RoleX””

NodeANodeA““Act1~RoleX””

RoleX“NodeA~Act1”

Act1

“NodeA~RoleX”

Act1

“NodeA~RoleX”

OV-2OV-2

OV-2OV-2

Need Line

Need Line

Complete OV-2Complete OV-2Complete OV-2Complete OV-2 Generate OV-3Generate OV-3Generate OV-3Generate OV-3

AutomatioAutomationnAutomatioAutomationn

Op Nodes

Op

Act

ivit

ies

Manual 3-Manual 3-way way

AssociationAssociationss



RoleRole

RoleRole

Op Nod

e

Op Nod

eActivityActivity

RoleRole

Steps to an Integrated Operational Steps to an Integrated Operational Architecture - DetailedArchitecture - Detailed

Steps to an Integrated Operational Steps to an Integrated Operational Architecture - DetailedArchitecture - Detailed

OV-5OV-5

OV-2 OV-2 NodesNodes

OV-4 OV-4 RolesRoles

Data Data EntryEntryData Data EntryEntry RoleRoleActivityActivity InfoInfo Op

NodeOp

Node


18

AutomatioAutomationnAutomatioAutomationn

Complete SV-1Complete SV-1Complete SV-1Complete SV-1

InterfaceInterfaceRender 3-way Render 3-way associations associations Render 3-way Render 3-way associations associations

NodeANodeA“Func1“Func1~SysX””

NodeANodeA“Func1“Func1~SysX””

SysX“NodeA~Func1”

Func1

“NodeA~SysX”

Func1

“NodeA~SysX”

DataExchange

DataExchange

Render Render System DataSystem DataExchanges Exchanges

Render Render System DataSystem DataExchanges Exchanges Generate SV-6Generate SV-6Generate SV-6Generate SV-6

SV-6SV-6





Sys Nodes

Sys

Fu

nct

ion

s SystemSystemSystemSystem

SystemSystem

Function

Function

SysNod

e

SysNod

e

SysteSystemm

Steps to an Integrated Systems Steps to an Integrated Systems Architecture - DetailedArchitecture - Detailed

Steps to an Integrated Systems Steps to an Integrated Systems Architecture - DetailedArchitecture - Detailed

SV-7 SystemsSV-7 SystemsSV-1 SV-1 NodesNodes

Data Data EntryEntryData Data EntryEntry

SV-4SV-4

SystemSystemSystem FunctionSystem FunctionDataData SystemNode

SystemNode


19

ChainedChained Leaf Activities Leaf Activities Produce Candidate Produce Candidate Activity Thread (Scenario) Models Of Sequenced Activity Thread (Scenario) Models Of Sequenced

ActionsActions

ChainedChained Leaf Activities Leaf Activities Produce Candidate Produce Candidate Activity Thread (Scenario) Models Of Sequenced Activity Thread (Scenario) Models Of Sequenced

ActionsActions External Activities/ Nodes External Activities/ Nodes PINKPINK

Lowest activities in node tree Lowest activities in node tree chain (No further chain (No further decomposition)decomposition)

Leaf activities signified by Leaf activities signified by Blue Blue BoxesBoxes

OV-6 generationOV-6 generation

Information Exchanges and Information Exchanges and Need Lines built only from Leaf Need Lines built only from Leaf ActivitiesActivities

Use Cases/ System Functions/ Use Cases/ System Functions/ BPMN Message Flows (**)BPMN Message Flows (**)

Act 11“Wash DC”

Act 11“Wash DC”

Act 121“Boston”Act 121

“Boston”Act 122

“LA”Act 122

“LA”

Act 21“Cleveland”


Act 221“Miami”Act 221“Miami”

Act 222“New York”


Act 14“KC”

Act 14“KC”

Act 13“Chicago”

Act 13“Chicago”

Act 11“Wash DC”

Act 11“Wash DC”

Act 121“Boston”Act 121

“Boston”Act 122

“LA”Act 122

“LA”



Act 221“Miami”Act 221“Miami”



Act 14“KC”

Act 14“KC”

Act 13“Chicago”

Act 13“Chicago”

Ordering of Leaf ActivitiesOrdering of Leaf ActivitiesFollows OV-5 Information FlowFollows OV-5 Information Flow

Gets us to!Gets us to!


20

ResourcesResources InfoInfo

ContainersContainersActivitiesActivities

InformationInformation Applications, Applications, Databases,Databases,

Servers,Servers,Networks Networks

Systems, W/S, Systems, W/S, Satellites, Satellites,

Equipment, Equipment, Techniques, Tools, Techniques, Tools,

ATM, NetworksATM, Networks

Call for Fire, Produce ATO Call for Fire, Produce ATO Conduct Mission Planning,Conduct Mission Planning,Process Loan ApplicationProcess Loan Application

Inputs/OutputsInputs/OutputsTriggersTriggersInputs/OutputsInputs/Outputs

Process ModelProcess Model

Anatomy of an Executable Operational Anatomy of an Executable Operational ArchitectureArchitectureAnatomy of an Executable Operational Anatomy of an Executable Operational ArchitectureArchitecture

Organization ChartOrganization Chart

Actual Organization Unit -Actual Organization Unit -1-8 Armor BN, Widget Fin Dept1-8 Armor BN, Widget Fin Dept

Job TitlesJob Titles Business EntitiesBusiness Entities

Human Roles, Jobs:Human Roles, Jobs:

- Wing Cdr, S3, XO,- Wing Cdr, S3, XO,VP, clerkVP, clerk

Organizational StructureOrganizational Structure- BN, Wing, Fleet,- BN, Wing, Fleet,

Finance Dept Finance Dept

But we need But we need KPPs and KPIs!KPPs and KPIs!

21

Transition To Executable Models Transition To Executable Models Transition To Executable Models Transition To Executable Models

Processing time and its statistical time Processing time and its statistical time distribution + average wait time before distribution + average wait time before processing + continuation strategy + processing + continuation strategy + cost$cost$+ Input conditions + Output conditions+ Input conditions + Output conditions

InformationInformationExchangesExchanges

Transport time and its statistical time Transport time and its statistical time distribution + quantity + distribution + quantity + cost$cost$

Hourly and fixed Hourly and fixed cost$cost$ + single/periodic + single/periodic unavailability times + set up time + capacity unavailability times + set up time + capacity (quantity) + processing strategy (FIFO, etc.)(quantity) + processing strategy (FIFO, etc.)

““Static-Static-Land”Land”

““Dynamic-Dynamic-Land”Land”KPPs and KPisKPPs and KPis

ConnectionsConnectionsbetweenbetween

ProcessesProcessesIEXIEXIEXIEX

LeafOperation

alActivity

LeafOperation

alActivity

ProcessProcess+ + + +

+ + + +

+ + + + Roles, Roles,

SystemsSystems ResourcesResources

Sends InfoSends Info

Resources, Resources, Job TitlesJob Titles

Activity, Activity, TaskTask

NodeNode IEX IEX IEX IEX ProcessProcess

IEX IEX IEX IEX

ProcessProcess

+ + + +


22

Transformation to Dynamic Process Models Transformation to Dynamic Process Models Transformation to Dynamic Process Models Transformation to Dynamic Process Models

OV-5 Leaf ActivitiesOV-5 Leaf ActivitiesRearranged to Match OV-2Rearranged to Match OV-2

OV-3 Info ExchOV-3 Info Exch

+ +

ArchitectuArchitecturere

ToolsTools

ArchitectuArchitecturere

ToolsToolsMappingMapping

StaticStatic-to_-to_

DynamicDynamic

MappingMappingStaticStatic-to_-to_

DynamicDynamicOV-4 Org/ OV-4 Org/ RolesRoles

ExecutableExecutableModelingModeling

ToolsTools

ExecutableExecutableModelingModeling

ToolsTools

Integrated Integrated ArchitecturArchitectur

eses

Integrated Integrated ArchitecturArchitectur

eses

ExecutableExecutableArchitectureArchitecture

ss

ExecutableExecutableArchitectureArchitecture

ss

Generated OV-6aGenerated OV-6a


23

Three Attributes of Analysis for Executable Three Attributes of Analysis for Executable Models: Constraints Within/Without BoundsModels: Constraints Within/Without BoundsThree Attributes of Analysis for Executable Three Attributes of Analysis for Executable Models: Constraints Within/Without BoundsModels: Constraints Within/Without Bounds

Activities - Processes

Roles – Human Resources

Systems – Physical Resources

Tim

eTim

eTim

eTim

e Cap

acit

y

Cap

acit

y

(#)

(#)

Cap

acit

y

Cap

acit

y

(#)

(#)

Cost

($)

Cost

($)

Cost

($)

Cost

($)

Comms

Measures of Merit - Performance Related - Resource related - Reliability related

TimeTime: Activity - clock time to perform Role – availability over 24 hrs

CapacityCapacity: # of Resource elements (Roles, systems)

CostCost: Dollar cost associated with usage of resource element

TimeTime: Activity - clock time to perform Role – availability over 24 hrs

CapacityCapacity: # of Resource elements (Roles, systems)

CostCost: Dollar cost associated with usage of resource element

TimeTime

CapacityCapacity CostCost

11

22 nn

Examine and optimize(?) operational attributes ofExamine and optimize(?) operational attributes of Time, Capacity and Co$t Time, Capacity and Co$t


24

Three Measures of MeritThree Measures of MeritThree Measures of MeritThree Measures of Merit

Performance

Performance

Resources

Resources

Reliability

Reliability

Time to perform Activity…delays due to bottlenecks – resource not availableTime to perform Activity…delays due to bottlenecks – resource not available Increase number of resources Have resources available more often

Time to Send information…delays due to comm’s network or task interdependencyTime to Send information…delays due to comm’s network or task interdependency Alternate ways of communicating information among resources Automate manual tasks

Time to perform Activity…delays due to bottlenecks – resource not availableTime to perform Activity…delays due to bottlenecks – resource not available Increase number of resources Have resources available more often

Time to Send information…delays due to comm’s network or task interdependencyTime to Send information…delays due to comm’s network or task interdependency Alternate ways of communicating information among resources Automate manual tasks

Utilization of Resources (Human or Mechanical)Utilization of Resources (Human or Mechanical)– Bottlenecks (Over-utilized), Idle (Under-utilized)Bottlenecks (Over-utilized), Idle (Under-utilized)

Cost of ResourcesCost of Resources– Static (Price tag), Dynamic (Operating Cost)Static (Price tag), Dynamic (Operating Cost)

Marginal Utility of Additional ResourceMarginal Utility of Additional Resource– Benefit gained by adding additional resourceBenefit gained by adding additional resource

Utilization of Resources (Human or Mechanical)Utilization of Resources (Human or Mechanical)– Bottlenecks (Over-utilized), Idle (Under-utilized)Bottlenecks (Over-utilized), Idle (Under-utilized)

Cost of ResourcesCost of Resources– Static (Price tag), Dynamic (Operating Cost)Static (Price tag), Dynamic (Operating Cost)

Marginal Utility of Additional ResourceMarginal Utility of Additional Resource– Benefit gained by adding additional resourceBenefit gained by adding additional resource

Health of the OperationHealth of the Operation– Impact of single point of failureImpact of single point of failure

Mission Failure, Loss of Life, Task Failure, Minimal ImpactMission Failure, Loss of Life, Task Failure, Minimal Impact– Availability of alternate/back-up resources when they’re neededAvailability of alternate/back-up resources when they’re needed

RecoverabilityRecoverability– Time to recover from a failureTime to recover from a failure– Adaptability to changes in environmentAdaptability to changes in environment

Time, Quality, Mission Success, LossesTime, Quality, Mission Success, Losses– Graceful degradation Graceful degradation

Mission tasks completed prior to shutdownMission tasks completed prior to shutdown Mission accomplished prior to status changed to combat ineffectiveMission accomplished prior to status changed to combat ineffective

Health of the OperationHealth of the Operation– Impact of single point of failureImpact of single point of failure

Mission Failure, Loss of Life, Task Failure, Minimal ImpactMission Failure, Loss of Life, Task Failure, Minimal Impact– Availability of alternate/back-up resources when they’re neededAvailability of alternate/back-up resources when they’re needed

RecoverabilityRecoverability– Time to recover from a failureTime to recover from a failure– Adaptability to changes in environmentAdaptability to changes in environment

Time, Quality, Mission Success, LossesTime, Quality, Mission Success, Losses– Graceful degradation Graceful degradation

Mission tasks completed prior to shutdownMission tasks completed prior to shutdown Mission accomplished prior to status changed to combat ineffectiveMission accomplished prior to status changed to combat ineffective


25

Executable Architecture Modeling Parameters & RulesExecutable Architecture Modeling Parameters & RulesExecutable Architecture Modeling Parameters & RulesExecutable Architecture Modeling Parameters & Rules

Resources – human producers/consumers and physical systemsResources – human producers/consumers and physical systems– CapacityCapacity - how many of each? - how many of each?– AssignmentAssignment - who does what? - who does what?– Time allocationTime allocation and when [not] available (24 hour clock)? and when [not] available (24 hour clock)?– OrderingOrdering - when multiple resources do same activity together – who is - when multiple resources do same activity together – who is

first up-to-bat?first up-to-bat?– ConcurrencyConcurrency - when multiple resources do same activity - when multiple resources do same activity

simultaneously?simultaneously?– CostsCosts – direct and indirect? – direct and indirect?

ActivityActivity– Time durationTime duration (how long to accomplish) (how long to accomplish)– Sequential/ concurrentSequential/ concurrent activity event process ordering activity event process ordering– Input/Output ConditionsInput/Output Conditions under which information is under which information is

produced/consumedproduced/consumed– CostsCosts – direct and indirect? – direct and indirect?

Information FlowInformation Flow– Transfer timesTransfer times and information flows and information flows

26

Executable Architecture Sub-Process ModelExecutable Architecture Sub-Process ModelExecutable Architecture Sub-Process ModelExecutable Architecture Sub-Process Model

Jobs (Tokens)Jobs (Tokens)– Enter at topEnter at top– Exit at bottomExit at bottom– Four end-end Four end-end

pathspaths

Act A16Act A16

I1I1I1I1

O2O2Act 17Act 17

Act A18Act A18

Act A11Act A11

Act A12Act A12 Act A13Act A13

Act A15Act A15Act A14Act A14

O1O1

I1I1I1I1

O2O2

O1O1


27

Act A11Act A11

Act A13Act A13

Act 17Act 17

O2O2O2O2

Act A11Act A11

Act A13Act A13

Act 17Act 17

O1O1O1O1

Act A18Act A18

Act A11Act A11

Act A12Act A12

Act A15Act A15

Act A16Act A16

O1O1O1O1

Act A18Act A18

Act A11Act A11

Act A12Act A12

Act A14Act A14

Act A16Act A16

Act A18Act A18

O1O1O1O1

I1I1I1I1I1I1I1I1I1I1I1I1 I1I1I1I1

Individual Mission Paths – In Context Of…Individual Mission Paths – In Context Of…Individual Mission Paths – In Context Of…Individual Mission Paths – In Context Of…


28

Dynamic Analysis CycleDynamic Analysis CycleDynamic Analysis CycleDynamic Analysis Cycle

EditEditProcessProcessModelModel

EditEditProcessProcessModelModel

RunRunProcessProcessModelModel

RunRunProcessProcessModelModel

Maintain sameevent triggers for each run/ analysis cycle

RunRunCombatCombat

SimulationSimulationModelModel

RunRunCombatCombat


EventsEventsEventsEvents

Edit combat model when only process models analysis is complete

Capture newnew event Trigger times when Combat model changes

RunRunCombatCombat


RunRunCombatCombat


EventsEventsEventsEvents

AnalyzeAnalyzeAnalyzeAnalyze


29

Emerging Technical Issues (1 of 2)Emerging Technical Issues (1 of 2)Emerging Technical Issues (1 of 2)Emerging Technical Issues (1 of 2)

Stale (duplicate) information in the business process modelStale (duplicate) information in the business process model

Fault analysis - major changes to process flow (e.g., staff cell or Fault analysis - major changes to process flow (e.g., staff cell or sensor destroyed, or system fails, network fails) – how to reroute sensor destroyed, or system fails, network fails) – how to reroute information flowinformation flow

Applying contextual updates among combat simulation, business Applying contextual updates among combat simulation, business process model and network communications modelprocess model and network communications model– Combat simulation updates node locations in comms modelCombat simulation updates node locations in comms model– Combat simulation updates node status (destroyed, non-Combat simulation updates node status (destroyed, non-

operational) in process model and comms modeloperational) in process model and comms model– Process model sends orders to specific unit in combat Process model sends orders to specific unit in combat

simulationsimulation

Allocating activities in mission thread to the appropriate Allocating activities in mission thread to the appropriate simulationsimulation– Some activities represent physical actions – more appropriate Some activities represent physical actions – more appropriate

for the combat simulation to executefor the combat simulation to execute– Some activities represent information processing actions – Some activities represent information processing actions –

more appropriate to stay in the business process modelmore appropriate to stay in the business process model© 2004 The MITRE Corporation. All rights reserved

30

Emerging Technical Issues (2 of 2)Emerging Technical Issues (2 of 2)Emerging Technical Issues (2 of 2)Emerging Technical Issues (2 of 2)

Incorporating dynamic cost analysis to address operational costs Incorporating dynamic cost analysis to address operational costs of a resourcesof a resources

How to adjust interactions in mission threads (business How to adjust interactions in mission threads (business processes) to better separate command/staff activities & processes) to better separate command/staff activities & unit/system activities ?unit/system activities ?– Currently defined mission threads intertwine activities Currently defined mission threads intertwine activities

represented in process model and combat modelrepresented in process model and combat model– Need to modify mission threads to handle actions between Need to modify mission threads to handle actions between

process model and combat simulationprocess model and combat simulation

How to create interactions between combat simulation and How to create interactions between combat simulation and process models ?process models ?– Mapping Key Events to start of a Mission ThreadMapping Key Events to start of a Mission Thread

Standards for Models and ProductsStandards for Models and Products

How to define the measures of merit that we want and then get the How to define the measures of merit that we want and then get the models to provide them ?models to provide them ?


31

Integrated Integrated Architectures + Architectures + Executable Executable Architectures + Architectures + Analytical Tools and Analytical Tools and Methods Render Methods Render Quantative Actionable Quantative Actionable ArchitecturesArchitectures

To be used for Funding decisions, To be used for Funding decisions, acquisitions, system engineering, acquisitions, system engineering, investment strategy,…investment strategy,…

++ ++

AnalysisMethodsAnalysisMethods

AnalyticalTools

AnalyticalTools

ActionableActionableArchitecturesArchitectures

ActionableActionableArchitecturesArchitectures

IntegratedIntegratedArchitecturArchitectur

eses


eses

Architecture ToolsArchitecture Tools

The Road ReviewedThe Road ReviewedThe Road ReviewedThe Road Reviewed

++DoDAFDoDAF

CADMCADMActivity-BasedMethodology

Activity-BasedMethodology

Guidance + Compliant Guidance + Compliant Tools and Methodology Tools and Methodology Render Render Integrated Integrated ArchitecturesArchitectures


eses


esesScenariosScenarios

ExecutableModeling Tools

ExecutableModeling Tools

Integrated Integrated Architectures + Architectures + Simulation Tools and Simulation Tools and Scenarios (context) Scenarios (context) Render Render Executable Executable ArchitecturesArchitectures

++

ExecutableExecutableArchitecturArchitectur

eses

ExecutableExecutableArchitecturArchitectur

eses

32

Issue 1: For CCA Business Case Need Key Performance Indicators (KPI)

Chapter 6 of DoDAF Wizdom

SUMMARY

Issue 2: Because the world is not stoppingNeed Dynamic Models

This PresentationAnd in Conclusion!And in Conclusion!


33

DoDAF does not provide answers DoDAF does not provide answers questions such as:questions such as:

DoDAF does not provide answers DoDAF does not provide answers questions such as:questions such as:

What Direction to go?

How to Build what I want?

How to not get Hurt?


Dennis Wisnosky, Wizdom Systems Inc., Dennis Wisnosky, Wizdom Systems Inc.,

[email protected]

Joseph Vogel, Wizdom Systems Inc.,Joseph Vogel, Wizdom Systems Inc.,

[email protected]@wizdom.com

Steve Ring, Mitre Corporation, Steve Ring, Mitre Corporation, [email protected]

Presented by:Presented by:Presented by:Presented by:

The Road to Executable ArchitecturesThe Road to Executable ArchitecturesNovember 2004November 2004November 2004November 2004

Wizdom Systems Inc., and MITRE Approved for Public Release

Distribution Unlimited, Case #04-0351

©2004 The MITRE Corporation. All rights reserved

©2004 Wizdom Systems Inc., All rights reserved

