13
Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer [email protected] Delivering an Information Advantage Architecture Policy, Processes and Tools Integrated EA Conference 2009

Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer [email protected] Delivering

Embed Size (px)

Citation preview

Page 1: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

Brian WilczynskiDirector

Enterprise Architecture and StandardsOffice of the DoD Deputy Chief Information Officer

[email protected]

Delivering an Information AdvantageArchitecture Policy, Processes and Tools

Integrated EA Conference 2009

Delivering an Information AdvantageArchitecture Policy, Processes and Tools

Integrated EA Conference 2009

Page 2: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

DoD CIO IM/IT Strategic PlanDelivering an Information Advantage

VisionLead The DoD Enterprise To Achieve An Information Advantage For

Our People And Mission Partners

MissionLead the information age transformation to enhance the Department

of Defense’s effectiveness and efficiency

Strategic EndAn agile enterprise empowered by access to and sharing of timely and

trusted information

2

http://www.defenselink.mil/cio-nii/docs/DoDCIO_Strat_Plan.pdf

Page 3: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

Integrated Enterprise ArchitectureArchitecture Policy/Mandates

Integrated Enterprise ArchitectureArchitecture Policy/Mandates

“Develop, maintain, and facilitate theimplementation of a sound and integratedIT architecture for the executive agency” – Clinger-Cohen Act

3

Office of Management and Budget Circular A-130“Management of Federal Information Resources”

DoD Directive 8000.01“Management of the DoD Information Enterprise”

DoD Directive 8210.x“Architecture in the Department of Defense”

Defense Acquisition System

Joint Capability Integration

Interoperability and Supportability

DoD Directive 5144.1“ASD NII / DoD CIO”

Page 4: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

Net-Centric Transformation

Information as a Strategic Asset

Interoperable Infrastructure

Assured Information Access

Return on Investment

IT Work Force Development

CIO Strategic Goals

CIO Vision &Mission

Enterprise Architecture & StandardsSupporting the CIO Mission

Lead The DoD Enterprise To Achieve An Information Advantage For Our People And Mission Partners

Initiatives

4

Page 5: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

Delivering an Information AdvantageArchitectural and Decision Making Processes

Delivering an Information AdvantageArchitectural and Decision Making Processes

5

IT Architecturesare required and areessential parts of each decision-making process

Interoperability andSupportability

BUILDDODD 7045.14,

DODI 7045.7

BUILDDODD 5000.1,DODI 5000.2

DODD 4630.5, DODI 4630.8, CJCSI 6212.01E

Assess and Certify System Interoperability

PlanningProgrammingBudgetingExecution(PPBE)

DefenseAcquisition

JointCapabilities

Integration andDevelopment

(JCIDS)

Acquire and Equipthe Force and

Force Capabilities

Allocate Resources forthe Force and

Force Capabilities

Define the Force andForce Capabilities

DEFINECJCSI 3170.01C, CJCSM 3170.01

Page 6: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

Delivering an Information AdvantageProvide an Integrated Compliance Toolset

Delivering an Information AdvantageProvide an Integrated Compliance Toolset

Data StandardsData Standards Data MiningData Mining Modeling Tools Modeling Tools Exchange StandardsExchange Standards

USMCUSMC

ARMYARMY

NAVYNAVY

DISRDISRUSAFUSAF

Web Services

Web Services

JCMEJCME(JFCOM)

DoDAF

DoDAF

FEA

FEA

OO / UML, UPDM, IDEF

OO / UML, UPDM, IDEF

DataDataTagsTags XM

L, XMI

XML, XM

I

Tools

Databases

Federal &Local Govt

Data Sources

DoD

Coalition

External DITPRDITPR FSAMFSAM E-ISPE-ISP VUE-ITVUE-IT

IDEASIDEAS

DARSFederated Catalog

DARSFederated Catalog

Exchange

Tuple Type

Obj Exchg

Tuple Type

DoDAFMetaModel (DM2)

Specification

6

Page 7: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

“Fit for Purpose” Architecture Descriptions

Page 8: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

DoDAF 2.0 Viewpoints

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

all v

iew

s

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

the

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, a

nd

Ind

us

try

po

licy

, sta

nd

ard

s, g

uid

an

ce

, co

ns

train

ts, a

nd

fore

ca

sts

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 ViewpointArticulate 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 c

ap

ab

ility

req

uire

me

nts

an

d th

e v

ario

us

pro

jec

ts b

ein

g im

ple

me

nte

d; D

eta

ils

de

pe

nd

en

cie

s b

etw

ee

n c

ap

ab

ility m

an

ag

em

en

t an

d th

e D

efe

ns

e

Ac

qu

isitio

n S

ys

tem

pro

ce

ss

.

Page 9: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

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

realizes

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-v 2::SecurityAttributesGroup

0..*

is-valid-under

1..*

class Measure - WIP

Cost

Type

Baseline::Measure

Timeliness

RateThroughput

Capacity

AccuracyPrecision

Dependability

NeedsSatisfactionMeasure

PerformanceMeasure

MaintainabilityMeasure

AdaptabilityMeasure

OrganizationalMeasure

Interoperability

Trustw orthiness

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

DoDAF Metamodel (DM2)

Page 10: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

www.defenselink.mil/cio-nii/sites/diea

Page 11: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

IEA Priorities Data and Services Deployment (DSD) – Decouple data and

services from the applications and systems that provide them, allowing them to be visible, accessible, understandable and trusted. Lay the foundation for moving the DoD to a Service-Oriented Architecture (SOA).

Secured Availability (SA) – Ensure data and services are secured and trusted across DoD. Allow users to discover data and services and access them based upon their authorization.

Computing Infrastructure Readiness (CIR) – Provide the necessary computing infrastructure and related services to allow the DoD to dynamically respond to computing needs and to balance loads across the infrastructure.

Communications Readiness (CR) – Ensure that an evolvable transport infrastructure is in place that provides adequate bandwidth and end-to-end, seamless net-centric communications capability across all GIG assets.

NetOps Agility (NOA) – Enable the continuous ability to easily access, manipulate, manage and share any information, from any location at any time.

Page 12: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

DoD Architecture Federation

Force Application Force Application

Building PartnershipsBuilding Partnerships

Command & ControlCommand & Control

ProtectionProtection

LogisticsLogistics

Force Support Force Support

Corporate Management & SupportCorporate Management & Support

Net-centricNet-centric

Battlespace AwarenessBattlespace Awareness

IEA

GLOBAL C2GLOBAL C2 JIAMDO C2JIAMDO C2

JDDA-E

TAMD

GIG

IA

Arc

hit

ectu

re

HRM Architecture

Dept of Army Dept of Navy Dept of Air Force

Army Architecture

DON Architecture

Air Force Architecture

Join

t C

apab

ilit

y A

reas

DoD Enterprise Architecture

Ref Models Tech Stds Arch Guidance Laws, Regs, and Policy

DISR DODAF LawsDoD EA RM

Tools

DITPR Regs Policy

SO

CO

M

DIS

A

DL

A

NS

A

NR

O

NG

A

DIA

Oth

er

Solution Architectures

NC CPM ArchNC CPM Arch

BE

A

WSLM FM

HRM

RP&ILM MS&SM

Page 13: Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian.wilczynski@osd.mil Delivering

Lessons Learned

Architecture must be a senior-level leadership priority.

Architecture becomes relevant when it is integrated into the major decision-making processes of an organization.

Architecture needs to be described within the terms of the consumer.

Complexity needs to be understood and managed.