Dennis Wisnosky 3 Difficult Pieces

Founding Sponsors

This Presentation Courtesy of the

International SOA Symposium

October 7-8, 2008 Amsterdam Arena

www.soasymposium.com

[email protected]

Gold Sponsors

Platinum Sponsors

Silver Sponsors

The 3 Main Pillars of the DoD Go Forward Strategy

Three Difficult Pieces

October 8, 2008

Dennis E. Wisnosky, DoD BMA CTO & Chief Architect

Background

"The Secretary of Defense is responsible for a half-trillion dollar enterprise that is roughly an order of

magnitude larger than any commercial corporation that has ever existed. DoD estimates that business support

activities—the Defense Agencies and the business support operations within the Military Departments—

comprise 53% of the DoD enterprise.”

Reach of the Business Mission Area

DWiz DoD BMA CTO/CA 2

The Challenge


Transformation through SOA

“The DoD and IC [Intelligence Community] share a vision for a services-based environment that leverages technologies to provide access to information and business processes, and interoperable infrastructure and standards to enable discovery, availability and trust.” DoD Memorandum, 2007 DWiz DoD BMA CTO/CA 4

DWiz DoD BMA CTO/CA

BMA CTO & CA FY09 Objectives

1.  Build a top down DoD Enterprise Architecture embracing tiered accountability and federation.

2.  Stop using Architecture for administering things, and start using Architecture for delivering capabilities.

3.  Lead Government and Industry from costly dependence upon heroic Architecture building, to building Architectures based upon standards.

5

1. Build a top down DoD Enterprise Architecture Embracing Tiered Accountability and Federation.

Mission

Opera,ons

Processes

Tasks

Procedures

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

Data….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

….…...…..…..…..…..……..…..…

End-to-End Alignment Ti

ered

Acc

ount

abili

ty



1.  Build a top down DoD Enterprise Architecture embracing tiered accountability and federation. Current Architecture Federation Map

DWiz DoD BMA CTO/CA

Battlespace Awareness

Command & Control

Force Application

Influence

Force Support

Net-Centric

Corporate Management & Support

Protection

Logistics

Prioritized, Delivered Warfighter

Capabilities Operational Planning

Requirements Policy Acquisition Programming

NII Comms and Transport Architecture

Expeditionary Business Systems Architecture

Global Collaborative Manufacturing Architecture

Warfighter High-Level Architecture

Global C2 Architecture

Enterprise-Level Rules and Constraints

Architecture (Notional) includes Defense

Information Enterprise Architecture

Intel Enterprise Architecture

Business Enterprise Architecture

Functions

How will we do Federation?

Cap

abili

ties

8

DWiz DoD BMA CTO/CA

Step 1: Start at the bottom -Extract vocabularies from existing physical systems. -Software finds and displays matching data elements.

Step 2: Collaborate -The community documents, reviews, discusses and agrees; resulting in human-readable documentation and formal vocabulary definitions.

Step 3: Share and Reuse -The Business Enterprise Architecture (BEA) becomes the repository for the Common Business Vocabularies.

Step 4: Federate with the DoD Metadata & Service Registries

-Automate entry of metadata into the DoD Metadata Registry (MDR) and DoD Universal Description Discovery and Integration (UDDI) by federation with the BEA.

Building Common Vocabularies

Step 5. Deploy Enterprise Services People users access the vocabularies and Services through web browsers to

view natural language documentation, to navigate formal relationships and to determine the availability of services

Machine users download vocabularies and services from the Metadata & Services Registries


9

2. Stop using Architecture for administering things, and start

using Architecture for delivering capabilities.

DWiz DoD BMA CTO/CA

Current State and Future Vision: Its Happening Now

Systems will be Deployed as Services within a common Business Operating Environment

(BOE)

2. Stop using Architecture for administering things, and start using Architecture for delivering value.

11

3. Lead Government and Industry from costly dependence upon

heroic Architecture building, to building Architectures based upon

standards.

DWiz DoD BMA CTO/CA

We can build a standards-based Business Operating Environment , But developing for it is much harder

-As we build and use Architectures, we lack the standards so that we can go from planning and design tools, to development tools, to deployment and execution tools, and back again

-We need to be able to represent the same things the same way across all of our Architectures using any of our tools.

Are standards and a discipline important for communicating?

3. Provide Industry and DoD Leadership for Standards-based Architecture

13

Resistor symbol It’s Resistance is in Ohms, Ω It’s Power is in Watts, W

A value of resistance may be Ω = .01, with an example tolerance from ± 0.1% → ± 20%

Capacitor symbol Capacitance is in farads, F Voltage is in volts, V A range for capacitance may be from pico farads, pF, to mega farads, MF

This agreed upon representation of electrical engineering allows a common understanding…

In Electrical Engineering, Consider ........

And! 14 DWiz DoD BMA CTO/CA

DWiz DoD BMA CTO/CA

Music Scale symbols

Notes symbols

This agreed upon representation of music allows a common understanding…

In Music, Consider ........ 3. Provide Industry and DoD Leadership for Standards-based Architecture

But in Architecture! 15

DWiz DoD BMA CTO/CA

Architecture Standards – State of Practice

– Architecture is constructed through different views – DoDAF, ARIS, Zachman et al. provide collections of Views without

regard to conflicting requirements – Graphical Modeling Languages such as the IDEFs, BPMN, Class

Diagrams, Sequence Diagrams fill these views without regard to a methodology

– Models and the data that represents the models are stored for re-use in the format du jour

The Goal: Round-Tripping

There must be standard formats for diagrams, and for data that represents the diagrams, and for data that moves within and between the reality that diagrams represent.


16

DWiz DoD BMA CTO/CA

Round-Tripping: Model to Execution

ProcessModelRepository

ToolA

ProcessModeling(BPMN)

Standard Process Model

ToolB

ProcessModeling(EPC)


Tool B, Ext Attr.


Tool D Ext. Attr.

Tool B, Ext Attr.


Tool D Ext. Attr.

Tool B, Ext Attr.

Tool C Ext.Attr.


Tool D Ext. Attr.

Tool B, Ext Attr.

Tool C Ext.Attr.

Extended Attributes allow Any-to-Any Round Trip: 1.  From Tool to Tool 2.  From Tool to Execution

Engine

Store M

odel

Store M

odel w/ S

im D

ata

Load Model

ToolC

ProcessSimulation

Load Model in Process Modeling Tool for further refinement

ProcessExecution–WebServiceCalls

ToolD

SOADesignExecutableModelRepository

(Tool-Specific,extendedXPDL,BPELorsimilar)

Sto

re w

/ SO

A D

etai

ls

At the very least!


17 DWiz DoD BMA CTO/CA

DWiz DoD BMA CTO/CA

Shared Vocabulary   Architecting complex systems requires the use

of multiple views   Each view may be rendered in a different

technique   Yet the underlying concepts refer to the same

subject matter!   Goal: Capture terms and definitions at the

beginning of the architecture process and use them to integrate and reuse content across views

  Value Proposition: An Unambiguous Definitions of Architecture Concepts for Developers and Users


There must be standard formats for diagrams, and for data that represents the diagrams, and for data that moves within and between the reality that diagrams represent.

The Goal: An Engineered Architecting Framework – A Discipline!

18


DWiz DoD BMA CTO/CA We must make sense out of this!

19

Primitives

foun

datio

n fo

r

PrOnto Ontology (Lexicon)

PriMo Modeling Guide

Different Frameworks

inpu

t for

influ

ence

s

info

rmed

by

Standards Best Practices

StandardLanguage(termsanddefini,ons)

StandardSymbols

Engineering Language and Symbols:

Music Language and Symbols:

Arc

hite

ctur

e Pr

imiti

ves

Architecture Prim

itives

• DoDAF 2.0 serves as the foundation for architecture primitives • Use Cases being developed and used to drive pilots


DWiz DoD BMA CTO/CA 20 We need a discipline?

‣ Architecture = Collection of Views

‣ View = Perspective of Reality as a Model

‣ Model = Representation of Concept in Language

‣ Language = Combination of Vocabulary and Grammar

‣ Vocabulary = Collection of Terms

‣ Grammar = Rules for combination of Terms


Where will this take us?

An Engineered Architecting Framework – A Discipline!


DWiz DoD BMA CTO/CA

Stove Pipes Tiered Accountability

Allies

Global Collaboration

Service providers Contractors

In DoD

Agile, Adaptive, Net-Centric Organizations


Was IS Primitives Enable

the “To Be”

22 How will we get there?

DWiz DoD BMA CTO/CA

Global Collaboration

Object Management Group (OMG), Windows Workflow Foundation, Organization for the Advancement of Structured Information Standards (OASIS), Workflow Management Coalition (WFMC), World Wide Web Consortium (W3C) WS-C …WS-X


Where are we now? 23

Status of 3 Difficult Pieces 1.  Build a top down DoD Enterprise Architecture embracing tiered

accountability and federation. BEA 3.0 was the first DoD Capabilities based Architecture. BEA 5.0 was the first version to consider common vocabularies. This work is progressing through the use of COTS to map data between existing systems for insertion into the BEA and use of the new AV-2 for new capabilities. A memorandum is being staffed through DEPSECDEF to formalize this process.

2.  Stop using Architecture for administering things, and start using Architecture for delivering value.

The Business Operating Environment (BOE) which was first exposed in the BMA Enterprise Architecture Federation Strategy and Roadmap Based Upon SOA 2 years ago has evolved to inform the DKO and the NCES SOA Foundation Services and more as Services are deployed. Our challenge now is governance of this phenomenon.

3.  Lead Government and Industry from costly dependence upon heroic Architecture building to building Architectures based upon standards and discipline.

Our Primitives work has more acceptance and traction than we dared to hope. Externally results are being vetted to software vendors. Internally we are using primitives for the Global Collaborative Manufacturing Architecture (GCMA) and gearing up for BEA 7.0.


Thank You for Your Time!

DWiz DoD BMA CTO/CA

Any Questions?

[email protected]

Dennis Wisnosky 3 Difficult Pieces

Business

Transcript of Dennis Wisnosky 3 Difficult Pieces