Principles of Quality Architecture and

Moving Forward Towards a Unified Common Approach

5 January 2012

Walt Okon

Senior Architect Engineer Architecture & Infrastructure Directorate

(571) 372-4685Walt.Okon@osd.mil

UNCLASSIFIED 1

Defense is our MissionDefense is our MissionArchitecture; Then and NowArchitecture; Then and Now

Common Architecture Framework

Unalienable Rights: Life, Liberty and pursuit of Happiness

Elements of Quality Architecture

Common Architecture Framework Approach

• Single Architecture Framework

• Policy, Direction, Guidance

• Architecture Exchange

• Architecture Tools

• Certified Architects

Enabling efficient and effective

acquisition of hardware, software and

services used by DoD in missions

deliverables.

Single Architecture Framework

Architecture viewpoints are composed of data that has been organized to facilitate understanding. 4

All V

iewp

oin

tO

ve

rarc

hin

g a

sp

ec

ts o

f arc

hite

ctu

re c

on

tex

t tha

t rela

te to

a

ll mo

de

ls

Data an

d In

form

ation

View

po

int

Artic

ula

te th

e d

ata

rela

tion

sh

ips

an

d a

lign

me

nt s

truc

ture

s

in th

e a

rch

itec

ture

co

nte

nt

Stan

dard

s View

po

int

Artic

ula

te a

pp

lica

ble

Op

era

tion

al, B

us

ine

ss

, Te

ch

nic

al,

an

d In

du

stry

po

licy

, sta

nd

ard

s, g

uid

an

ce

, co

ns

train

ts, a

nd

fo

rec

as

ts

Systems Viewpoint

Articulate the legacy systems or independent systems, their composition,

interconnectivity, and context providing for, or supporting, DoD functions

Services Viewpoint

Articulate the performers, activities, services, and their exchanges providing

for, or supporting, DoD functions

Operational Viewpoint

Articulate operational scenarios, processes, activities & requirements

Capability Viewpoint Articulate the capability requirement,

delivery timing, and deployed capability

Pro

ject View

po

int

De

sc

ribe

s th

e re

latio

ns

hip

s b

etw

ee

n o

pe

ratio

na

l an

d

ca

pa

bility

req

uire

me

nts

an

d th

e v

ario

us

pro

jec

ts b

ein

g

imp

lem

en

ted

; De

tails

de

pe

nd

en

cie

s b

etw

ee

n c

ap

ab

ility

ma

na

ge

me

nt a

nd

the

De

fen

se

Ac

qu

isitio

n S

ys

tem

p

roc

es

s.

Policy, Direction, Guidance http://www.dodcio.defense.gov/sites/diea/

6

Architecture Exchange UPDM – Unified Profile for DoDAF/MODAFUPDM – Unified Profile for DoDAF/MODAF

AdaptiveAdaptive

Artisan SoftwareArtisan Software

ASMGASMG

BAE SystemsBAE Systems

DoDDoD

DNDDND

embeddedPlusembeddedPlus

GenericGeneric

IBMIBM

ThalesThales

Lockheed Martin CoLockheed Martin CoMitreMitreL3 CommsL3 CommsMODMOD

NoMagicNoMagic

RaytheonRaytheon

Rolls RoyceRolls Royce

Sparx SystemsSparx Systems

VisumPointVisumPoint

SelexSelex

UPDM RFC GroupUPDM RFC Group

Walt OkonWalt OkonDoD SupportDoD Support

Defense-Industry Challenge: Synchronization of DoDAF-UPDM

Lifecycles

2. Industry Produces Develops Generic

Modeling &EngineeringStandards

3. Vendors Produce Product

VersionsDefense Domain Tools

“Just-In-Time”

1. GovernmentsProduce BaselinesDevelop, Evolve &

HarmonizeDefense Enterprise

ArchitectureFrameworks

For Acquisition

Leverages Vendors Standards-Based Tools & Government Frameworks

Core Architecture Data Model

All View

Syst

ems/S

ervi

ces

View

Technical StandardsV

iew

Operational View

RFC

class Class Model

Capabilities Serv ices

Projects

PerformersObject Exchanges

RulesMeasures

Foundation

according-to according-toto-meet

meet

satisfy follow

lead-to lead-to

meet comply-with

result-inresult-in

conduct

class Capability

Type

Capability

TemporalType

Effect

TemporalType

CapabilityConfiguration

Type

Measure

TemporalType

Condition

Performer

Organization

ExchangeObject

Materiel

TemporalType

Skill

ExchangeObjectPerformer

PersonnelType

InterfaceTypeTemporalType

Activ ity

TemporalType

RealProperty

Performer

System

real izes

1..*

is-part-of

0..*

is-a-part-of

0..*

is-a-part-of

is-a-part-of

0..*

is-a-part-of

0..*

is-a-part-of

0..*

results-in

0..*

0..*

is-a-part-of

0..*

applies-to

0..*

1..*

is-performed-under

class Serv ices

TemporalType

Effect

Type

Measure

TemporalType

Condition

Organization

ExchangeObject

Materiel

TemporalType

Skill

ExchangeObject

PersonnelType

InterfaceTypeTemporalType

Activ ity

TemporalType

RealProperty

System

Serv iceRequirement

Serv iceImplementation

Rule

Standard

PerformerState

Performer

SoftwareServ ice

is-a-part-of

0..*

results-in

0..*

0..*

applies-to 0..*

0..*

performs1..*is-performed-by

class ExhangeObjectFlow

PerformerState

Performer

TemporalType

ExchangeObject

Data

Materiel

Information

InterfaceTypeTemporalType

Activ ity

Rule

Standard

according-

to

PersonnelType

1..*

is-performed-by

0..*

performs

0..*

is-produced-by

0..*

0..*

is-consumed-by0..*

is-a-part-of

class Project

Ev ent

Type

Vision

TemporalType

Project

TemporalType

Goal

Cost

Plan

Rule

Means

InterfaceTypeTemporalType

Activ ity

TemporalType

Condition

TemporalType

PerformerState

TemporalType

EffectType

Measure

1..*

initiates-stimulates

0..*

is-realized-by

0..*

directs

0..*

1..*

is-realized-by

initiatesis-necessary-for

0..*

seeksChangeTo

1..*

0..*

changes

1..*

0..*

results-in

0..*

0..*

applies-to

0..*

class Rule

Type

Rule

Standard

Agreement

FunctionalStandard TechnicalStandard

Guidance

Constraint

TemporalType

Condition

Means

UCORE IC-ISM-v2::SecurityAttributesGroup

0..*

is-valid-under

1..*

class Measure - WIP

Cost

Type

Baseline::Measure

Timeliness

RateThroughput

Capacity

AccuracyPrecision

Dependability

NeedsSatisfactionMeasure

PerformanceMeasure

MaintainabilityMeasure

AdaptabilityMeasure

OrganizationalMeasure

Interoperability

Trustworthiness

Reliability

Security

class Performer

Performer

ExchangeObject

PersonnelType

System

SoftwareServ ice

Organization

TemporalType

Skill

ExchangeObject

Materiel

InterfaceTypeTemporalType

Activ ity

Rule

StandardTemporalType

Network

TemporalType

PerformerState

according-

to

AbstractFeatureType

GeoFeature

Location

1..*

is-performed-by

is-a-part-of

0..*

performs

is at

2..*

is-part-of

Architecture Tools

• Guidance– DoDAF v2.0 – Federated Architecture Strategy

• DoD Tools– DoD Architecture Registry System (DARS)– DoD IT Standards Registry (DISR)– GIG Technical Guidance (GTG) Tool– Meta Data Repository (MDR)

Vendor Tools are Necessary

DoDAF V 2.0 Delivery

DoDAF V2.0 is available at:

http://dodcio.defense.gov/sites/dodaf20/

Architecture Education & Training

Defense Architecture Framework

DoD Certified Architects delivering quality Architectures

Certified Enterprise Architects

design the information

technology architecture

structure enabling the efficient

and effective acquisition of

hardware, software and services

utilized by the DoD in missions

supporting the warfighters.Architect Career Plan

Architect’s Competency Framework

Elements of Quality Architecture

Common Architecture Framework Approach

• Single Architecture Framework

• Policy, Direction, Guidance

• Architecture Exchange

• Architecture Tools

• Certified Architects

Enabling efficient and effective

acquisition of hardware, software and

services used by DoD in missions

deliverables.

Office of Management and Budget

Common Approach Federal Enterprise Architecture (CA-FEA)

05 January 2012

“Build to Share”

Walt OkonSenior Architect Engineer

Architecture & Infrastructure (703) 607-0502

walt.okon@osd.mil

UNCLASSIFIED 14

• Mr. Scott Bernard, Chief Architect at OMB

• Reorganization of the Architecture Infrastructure Committee (AIC)

• Unified Architecture Framework (DoDAF Version 2.0) with

• New FEA alignment is his focus

• Organizations both Federal and Industrial (IAC) will be able to contribute to the EA community.

Architecture at Federal Level

Strategic Direction from Federal Chief Architect

“The Federal Enterprise Architecture (EA) community is at a crossroad regarding the way that architects individually and collectively contribute to Administration and Agency initiatives”

Mission Statement. Federal enterprise architects provide leading-edge analysis and design services that align strategic priorities with mission capabilities and technology solutions.

Vision Statement. To be a trusted, knowledgeable resource that helps to accomplish mission goals, drive change, and optimize resources through proven enterprise architecture methods.

2

Objectives of CA-FEA

To Describe: “…the need for changes in purpose, direction, and goals [of the EA practice in government].”

To Identify: areas that need improvement with respect to deriving more value from the practice of EA by senior decision makers responsible for agency strategy

To Change: how Architects at all levels (Enterprise, Segment, Solution) provide a support to the “business” of government

To Improve the Practice of EA: through development of a “common approach”

• To support decision makers• To improve interoperability across organizations• To improve the quality of architectural solutions

New - Common Approach

Move EA from academic exercise to an applied management discipline

Focused on business performance Integrates strategic, business, technology domains Agile, scalable, and repeatable Emphasizes the future, not the past Part of TechStat reviews Produces tangible, measurable results Cloud-based shared service orientation

Common Approach

EA Program needs to be “in-place” before agility can be reached Enhance awareness on expanding the use of EA to serve as a

strategy and business tool Recommend reference architecture, profiles, and standards to

align the elements EA in a common way to insure cross-domain interoperability.

Describe the mature practice of EA profession through identifying requirements for education/training.

Identify the relevance of stakeholders, their requirements, and means to provide traceability to the EA.

Provide education and training to develop foundational architecture skills as well as those specific to support U.S. Government EA process requirements.

Common Approach

Common Approach” -- being more prescriptive will:– Reduce the variety and standardize a Federal EA

framework and methodology:

1. Reduces the number of EA variations to be supported by Tool manufactures

2. Supports repeatable practice by architects and provide common education to grow new Federal Enterprise Architects

3. “Common Approach” will address EA development, methodology, and maintenance

Updated FEA Approach

More agile approach Primary outcome objectives Levels of scope Agency EA program elements Repeatable process for solution architecture Core / elective models Analysis guide

Context and Status

21

IT Reform Agenda

Shared Services Strategy Cloud Computing Strategy

Common Approach to Federal EA

IaaS PaaS SaaS Light Apps Security

Cloud Computing Reference Architecture (NIST)

Shared Services / Cloud Solutions

FEAF-II / FEAv2 DODAFv2.0 Other EA

Polic

yAp

proa

chD

eliv

ery

Data Center Consolidation

Shared Service/Cloud Computing Implementation Architecture

Common Approach and FEA

Strategic Goals

Enabling Applications

BusinessServices

Host Infrastructure

Data and Information

Secu

rity

Co

ntr

ols

(SR

M) (PRM)

(BRM)

(DRM)

(TRM)Curr

ent V

iew

s Future Views

Enterprise Plan

Transition Plan

Governance

Standards

Framew

ork

Use

MissionSuccess

AuthoritativeReference

Reso

urce

Opti

miz

ation Functional

Integration

•Primary Outcome•Levels of Scope•Basic Elements•Repeatable process•Sub-Architecture Areas•Core Artifacts

Methodology

23

Reference Model Updates

24

Business Reference Model (BRM)• Intra- and inter-agency shared services• Agencies, customers, partners, providers

Infrastructure Reference Model (IRM)• Hardware providing functionality• Hosting, data centers, cloud, virtualization

Application Reference Model (ARM)

• Business-focused data standardization • Cross-agency information exchanges

Performance Reference Model (PRM)

• Inputs, outputs, and outcomes• Uniquely tailored performance indicators

Secu

rity R

efe

ren

ce M

od

el (S

RM

)

Data Reference Model (DRM)

• Software providing functionality • Enterprise service bus

Questions

UNCLASSIFIED 25