DoD Enterprise Architecture Embracing Tiered Accountability and Federation

This Presentation Courtesy of the
International SOA Symposium
October 7-8, 2008 Amsterdam Arena
www.soasymposium.com
info@soasymposium.com

Founding Sponsors

Platinum Sponsors

Gold 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
Reach of the Business Mission Area

"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.”

DWiz DoD BMA CTO/CA
2

The Challenge

DWiz DoD BMA CTO/CA
3

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

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.
DWiz DoD BMA CTO/CA
5

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

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

Mission 

Opera,ons 

Tiered Accountability End-to-End Alignment
Processes 

Tasks 

    
    
  
Procedures       
    
    
    
…. …. .. …..  …. …. .. …..  …. …. .. …..  …. …. .. ….. 
…. …. .. ….. …. …. .. …..  …. …. .. …..  …. …. .. ….. …. …. .. ….. 
…. …. .. …..  …. …. .. ….. 
…. …. .. ….. …. …. .. …..  …. …. .. ….. …. …. .. …..  …. …. .. ….. …. …. .. ….. 
…. …. .. ….. …. …. .. …..  …. …. .. …..  …. …. .. ….. 
…. …. .. ….. 
…. …. .. …..  …. …. .. …..  …. …. .. …..  …. …. .. ….. 
…. …. .. …..  …. …. .. ….. 
…. …. .. …..  ….. ….. …..  …. …. .. …..  ….. ….. ….. ….. ….. ….. 
Data  ….. ….. ….. 
….. ….. …..  ….. ….. …..  ….. ….. …..  ….. ….. ….. ….. ….. ….. 
….. ….. …..  ….. ….. ….. ….. ….. …..  ….. ….. …..  ….. ….. ….. ….. ….. …..  ….. ….. ….. 
….. ….. …..  ….. ….. …..  ….. ….. ….. 
….. ….. …..  ….. ….. …..  ….. ….. …..  ….. ….. ….. 
… ….. ….. …  … ….. ….. …  … ….. ….. …  … ….. ….. …  ….. ….. ….. 
….. ….. ….. ….. ….. …..  … ….. ….. … ….. ….. …..  … ….. ….. …  … ….. ….. … 
….. ….. ….. 
… ….. ….. …  … ….. ….. … 
….. ….. …..  ….. ….. …..  … ….. ….. … 
… ….. ….. …  … ….. ….. …  … ….. ….. … 
… ….. ….. … 
… ….. ….. …  … ….. ….. …  … ….. ….. …  … ….. ….. …  … ….. ….. … 
… ….. ….. … 
… ….. ….. … 
… ….. ….. …  … ….. ….. … 
… ….. ….. … 
… ….. ….. …  … ….. ….. … 
… ….. ….. …  … ….. ….. …  … ….. ….. … 
… ….. ….. … 
DWiz DoD BMA CTO/CA 7

and federation.
Current Architecture Federation Map
Prioritized,
Functions Delivered
Warfighter
Operational
Capabilities
Programming Acquisition Policy Requirements
Planning
Warfighter High-Level Architecture

Force Application

Command & Control
Global C2 Architecture

Battlespace Awareness Intel Enterprise Architecture
Capabilities

Enterprise-Level Rules and
Constraints
Influence
Architecture (Notional)
includes Defense
Information Enterprise
Protection Architecture

Net-Centric NII Comms and Transport Architecture
Global Collaborative Manufacturing Architecture
Corporate Management & Support
Expeditionary Business
Systems Architecture
Logistics Business Enterprise Architecture

Force Support

DWiz DoD BMA CTO/CA How will we do Federation? 8

and federation.

Building Common Vocabularies
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;
Step 5. Deploy Enterprise vocabulary definitions.
resulting in human-readable documentation and formal Services
People users access the vocabularies and Services through web browsers to
Step 3: Share anddocumentation, to navigate formal relationships and
view natural language Reuse
to determine the availability of services becomes the repository for the
-The Business Enterprise Architecture (BEA)
Common Business Vocabularies.
Machine users download vocabularies and services from the Metadata &
Services Registries
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.

DWiz DoD BMA CTO/CA
9

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

2. Stop using Architecture for administering things, and start using Architecture
for delivering value.
Current State and Future Vision: Its Happening Now

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


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

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

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?
DWiz DoD BMA CTO/CA
13

In Electrical Engineering, Consider ........
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…
And!

In Music, Consider ........
Music Scale symbols

Notes symbols

This agreed upon representation
of music allows a common
understanding…
But in Architecture!

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

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: Round-Tripping
DWiz DoD BMA CTO/CA
16


Round-Tripping: Model to Execution
Tool A  Tool B  Tool C 

Process Modeling (BPMN)  Process Modeling (EPC) 
Process Simulation 

Load Model in Process Modeling Tool for further refinement

Store Model w/ Sim Data
Store Model

Process Model Repository 

Standard Standard Standard Standard Standard
Process Process Process Process Process
Model Model Model Model Model
Tool B, Ext Attr. Tool B, Ext Attr. Tool B, Ext Attr. Tool B, Ext Attr.

Tool D Ext. Attr. Tool D Ext. Attr. Tool D Ext. Attr.

Load Model
Tool C Ext.Attr. Tool C Ext.Attr.

Store w/ SOA Details
Tool D 

Extended Attributes allow SOA Design 
Executable Model 
Any-to-Any Round Trip: Repository  
(Tool-Specific, extended 
1.  From Tool to Tool XPDL, BPEL or similar) 

2.  From Tool to Execution
Engine Process Execution – Web Service Calls 

At the very least!
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
There must be standard formats for reuse content data
use them to integrate and diagrams, and for
thatacross views
represents the diagrams, and for data that moves within
and between the reality that diagrams represent.
  Value Proposition: An Unambiguous
Definitions of Architecture Concepts for
Developers and Users Engineered Architecting
The Goal: An
Framework – A Discipline!
DWiz DoD BMA CTO/CA
18


We must make sense out of this!

Primitives
Standard 
Standards
Symbols 

Architecture Primitives
Best Practices
Music Language and
Symbols:

influences
informed
Engineering Language

by
and Symbols:

Architecture Primitives PriMo
Modeling Guide

foundation
for

PrOnto
Ontology (Lexicon)

• DoDAF 2.0 serves as the
foundation for architecture
input for

primitives
• Use Cases being developed and Standard 
used to drive pilots
Different Language (terms 
Frameworks We need a discipline?
and deﬁni,ons) 


An Engineered Architecting Framework – 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?


Agile, Adaptive, Net-Centric Organizations

Stove Pipes Tiered Global Collaboration
Accountability
Service
providers Contractors
In DoD
Allies

Was IS
Primitives Enable
the “To Be”

How will we get there?
DWiz DoD BMA CTO/CA
22

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?

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!

Any Questions?

Dennis.Wisnosky@osd.mil

DWiz DoD BMA CTO/CA

DoD Enterprise Architecture Embracing Tiered Accountability and Federation

Recommandé

Recommandé

Contenu connexe

Similaire à DoD Enterprise Architecture Embracing Tiered Accountability and Federation

Similaire à DoD Enterprise Architecture Embracing Tiered Accountability and Federation (20)

Plus de SOA Symposium

Plus de SOA Symposium (20)

Dernier

Dernier (20)

DoD Enterprise Architecture Embracing Tiered Accountability and Federation