ddafv20dodaf v2.0 oioverview
TRANSCRIPT
D DAF V2 0 O iDoDAF V2.0 Overview28 April 2010
Mr. Shelton LeeArchitecture, Standards, and Interoperability Directorate
1
, , p yOffice of the DoD Deputy Chief Information Officer
(703) 916-7340 [email protected]
Report Documentation Page Form ApprovedOMB No. 0704-0188
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.
1. REPORT DATE 28 APR 2010 2. REPORT TYPE
3. DATES COVERED 00-00-2010 to 00-00-2010
4. TITLE AND SUBTITLE DoDAF V2.0 Overview
5a. CONTRACT NUMBER
5b. GRANT NUMBER
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) 5d. PROJECT NUMBER
5e. TASK NUMBER
5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Lockheed Martin ,Office of the DoD Deputy Chief InformationOfficer,Architecture, Standards, and Interoperability Directorate,Washington,DC,20301
8. PERFORMING ORGANIZATIONREPORT NUMBER
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)
11. SPONSOR/MONITOR’S REPORT NUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited
13. SUPPLEMENTARY NOTES Presented at the 22nd Systems and Software Technology Conference (SSTC), 26-29 April 2010, Salt LakeCity, UT. Sponsored in part by the USAF. U.S. Government or Federal Rights License
14. ABSTRACT
15. SUBJECT TERMS
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as
Report (SAR)
18. NUMBEROF PAGES
38
19a. NAME OFRESPONSIBLE PERSON
a. REPORT unclassified
b. ABSTRACT unclassified
c. THIS PAGE unclassified
Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18
IntroductionIntroduction
• DoDAF is prescribed for the use and development of Architectural Descriptions in the DepartmentArchitectural Descriptions in the Department
• DoDAF V2.0 provides an overarching set of architecture concepts guidance best practices and methods toconcepts, guidance, best practices, and methods to enable and facilitate architecture development
• Explicit Roles & ResponsibilitiesExplicit Roles & Responsibilities– Managers guidance for use and management of architecture– Architects guidance for development of architecture, meta-
model and data exchange requirements– Developers guidance defines the DM2 Physical Exchange
SpecificationSpecification2
Goal: Support Core ProcessesGoal: Support Core Processes
1. Capabilities Integration and Development (JCIDS)
2. Planning, Programming, Budgeting, and Execution (PPBE)
3. Acquisition System (DAS)
4 Systems Engineering (SE)4. Systems Engineering (SE)
5 Operations Planning5. Operations Planning
6. Capabilities Portfolio Management (CPM)p g ( )3
Promulgation MemoPromulgation Memo
• Version 2.0 is the prescribed framework for all Department architectures and represents a substantial shift in approach.– Don’t redo current architecture
• Architectures shall comply with DoDAF V2.0 in their next major release.– Update only in the next release– Does not prevent early adoption of DoDAF V2.0
4
DoDAF V2 0 ConformanceDoDAF V2.0 Conformance
• The data in an architectural description is defined according to the DoDAF meta-model (DM2) concepts, associations, and attributes.
f– The information captured in an architecture tool is consistent with the DM2 concepts, associations, and attributes.
– Architectural data should be stored in a recognized commercial garchitecture tool that conforms to industry standards.
– Tools, preferably data-driven, can be used for the presentation of architectural data but must be based on DATAof architectural data, but must be based on DATA.
• The architecture data is capable of transfer in accordance with the Physical Exchange Specification (PES).– Architectures that will exchange information need to comply with
DM2 PES (for the appropriate architectural data).
5
DoDAF V2 0 Key ConceptsDoDAF V2.0 Key Concepts
• Data-centric v. Product Centric• DoDAF V2.0 Meta-Model (DM2)DoDAF V2.0 Meta Model (DM2)• DoDAF V2.0 Method
DoDAF Described Models s Presentation Vie s• DoDAF Described Models vs. Presentation Views• “Fit-for-Purpose”
7
Data Centric ParadigmData-Centric Paradigm
• Prior versions of DoDAF emphasized ‘products’ (i.e., graphical representations or documents).
• DoDAF V2.0 emphasizes the capture and analysis of data and its relationships, rather than the creation of products.– Emphasizes on utilizing architectural data to support analysis
and decision-making.– Greatly expands the types of graphical representations that can– Greatly expands the types of graphical representations that can
be used to support decision-making activities.– Supports innovative and flexible presentation of the
architectural data in a meaningful, useful, and understandable manner.
9
DM2 IntroductionDM2 Introduction
• Constrained vocabulary for DoDAFF h d i i d di f d l– For the description and discourse of models
• Federated EA data exchange specification– For interoperability of EA data between tools, DBs
• Supports the Net Centric Data Strategypp gy– Discovery and understandability of EA data
• Precision semantics for EA analysisPrecision semantics for EA analysis– Provides mathematical rigor to the data
11
What is the DM2What is the DM2
• The DM2 is made up of three parts:– Conceptual Data Model
Key Concepts and Relationships in Non Technical Terms-- Key Concepts and Relationships in Non-Technical Terms– Logical Data Model
-- UML Class models that adds technical context to the CDMPh i l E h S ifi ti (PES)– Physical Exchange Specification (PES)
-- Implementation model and XSD Schemas
• Built upon the IDEAS Foundation– International Defense Enterprise Architecture Specification
Fo ndational objects (“Thing” “Indi id al” “T pe” etc )– Foundational objects (“Thing”, “Individual”, “Type”, etc.)– Relationship types (aka “Tuple” types)
-- “Whole/Part”, “Before-After”, Temporal, etc.”12
Th L l f th DM2Three Levels of the DM2
Conceptual Data ModelData Model
(CDM)Concepts and concept
relationshipsrelationships
Logical Data Model (LDM)Reified and Formalized relationshipsReified and Formalized relationships
Physical Exchange Schema (PES)13
Physical Exchange Schema (PES)XML encoding of LDM
C t l D t M d lConceptual Data Model
MeasureTypeActivity
ProjectRule
Measure
Guidance
123 4
56
DesiredEffect
Vision78
9
1011
1312
Condition18
13
16 1720
1922
14
21Capability
Agreement
Standard
Resource
152221
24
23
25
26
27
2829
23 (+ 24 &25)20 (+ 21 & 22)
30
SkillLocation
Agreement
Constraint
Information
Performer
PersonnelType
Thing
31
3233
30
34
Person
14Data
Organization
Materiel
System
Service
PersonnelType
ArchitectureDescription
36
35
37
Person Type
Logical Data ModelLogical Data Model (sample)
Resource Flow
Property
OverlapTypeactivityPerformedByPerformer
i.e., RoleResource Flow
IndividualTypeMeasure
+ numericValue: string
measureOfTypemeasureOfTypeActivityPerformedByPerformer
OverlapTyperuleConstrainsActivityPerformedByPerformer
measureOfTypemeasureOfTypeResource
IndividualType
LocationType
WholePartTyperesourceInLocationType
wholeType
IndividualType
Resource
IndividualType
Activity
Guidance
Rule
measureOfTypemeasureOfTypeActivityResourceOverlap
yp
partType
MaterielPerformer
Rule
Individual
IndividualResourceS i
superSubtypeactivityResourceOverlapSuperSubtypeOfRule
consumer
producer
OverlapTypeactivityResourceOverlap
Location
GeoPoliticalExtent
Representation
System
Organization
Service
IndividualPerformer
OverlapTypeactivityPerformableUnderCondition
15
Data
PersonType
Representation
Information
OrganizationType
Organization
IndividualType
Condition
activityPerformableUnderCondition
Physical Exchange SpecificationPhysical Exchange Specification
16
~ -~d-.;~~o;t~ -~ I r_-_--=------.:..;::_..._ ___ :J
0 .. 00
"capabilities" accessed are Resources -- Infotmation, Data, Materiel, Petfotmers, and Geo-political Extents,
r--
1 ideas:lndividuaiType (extension)
[±I attributes
ThP m.:liJnitllrlP nf ~nmP attribute of an individual,
1 - { any http:/lpurl.org/dc/elements/1.1 / ~ I - ---- - ---- ----- -=-------------=---=-------------=-----=-----"-;-~
0 .. 00
I
: r- ~-M-.;~~~;~p~j~ -1±1 : -------- : •r-_--------=--------------~:--J 1/ ~~ Ooo -- ... measures - -- ..../•3- - -1 •·
.... ,.._-________ ;S: ___ ~ • :
o. -~ ~- ~-M-.;~~~;~~~g-.; -1±1 I r---------_:__-_----------"':-:-""--;---·
0 .. 00 _________ ___J
---------------------------- - -~-~~~=~~~ .... ~~~0~~~~~~~~-:~- ~
seruiceEnablesAccess T oResou ... .:1-
An overlap between the Service mechanism and the Petfotmer capabilities it provides access to
DM2 in Practice
O i ti
DM2 in Practice
Desired Effect
Produces
Organization
Person TypeIs A
RealizesVision
At
Location
Performer Performer
PerformsP f d b
Capability
E blIs A
At
Activity Activity
Produces
Performed byEnablesSystem
Service
Resource
ProducesConsumed by
Service
ResourceConsumes
Which IsConditions Standards
Subject To Requires
MaterielInformation OrMeasures
Rules
Projects
Skills
IDEAS FoundationIDEAS Foundation
D l d b i t ti l f t i ti t i• Developed by an international group of computer scientists, engineers, mathematicians, and philosophers under defense sponsorship.
• See http://www.ideasgroup.org or http://en.wikipedia.org/wiki/IDEAS_Group
Thing
Type
wholePart
Indiv idual
typeInstance
tuple
instance
part
wholetype
superSubType
wholeParttypeInstance
temporalWholePartov erlapsubtype
supertype
part
beforeAfter
Indiv idualType
after
before
18
Methodology: DoDAF V2.0 Six-Step Architecture Development Process
• Determine Use, Scope, and Data Requirements of Architecture
• Architect (build models) analyze and present (report)Architect (build models), analyze, and present (report)20
DoD
AF
20
Vie
wpo
ints
DoD
AF
2.0
Vie
wpo
ints
21
~
f'
Project Viewpoint Describes the ~elation ships between operational and capability
requirements and the various projects being implemented; Details dependencies between capability management and the Defense
Acquisition System process.
.;, c ·e
·.;::::
~ Cl> .i::
--8 ·= ~ .~ 0'2:::: c.l-g 3: G> c. Q) ·= ~ ·- :::J > g-] > ... ~ :: ~Q. :a :a -8 ca m "tJ c. c. c ca acu U~~>
.c -.! Gl '3 u ~ ct
~-
• ~ ~ :il •
- I c • ·- 8 0 0 a. .. ~ Q.. I; tG '! ·- 0. > ·c 1: - •! ca c ·c 3 :I .2 ! r - •e~ ca c ... 0
&1 0 l
0
.! .. :I u
1! ..
--ac c 0 me 0c:n Cl> c u ,_ ·- t: ~ 0
- ~ 8: c ~ :::J ·- ~ ~ 0 .9!! .. c. .~ 0 3: ·~ .:~ Q) u 0 c ·- ca - 0 > ~ 01 '.;::::
1:!.5 g U) Cl> ., Q) E ·:;:.a u o e ·- 't: s:: Cl> ~ Q) Q. g., (J) Cl> c
.S a~ Al ..c ca ~ :i ll> .2.~ t:.c ct-
Standards Viewpoint
• '! c -- .sa c ... -. ~ ~ "'tJ,_ :I c ... _ &.·Iii c 1 0
- ~ c c c c ..II. c ·- 0 "' ·c; 25e.E a. • .! t:
·~ E .5 8. ID CQ. .a o i > r; ...
·- 25 ~ i[.: a» g,E.S ... .I 0 U)
~ • u .5 en =·i l
J= .. :::J . Q. u E 'SC 'f!! .I .. t8
Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts
I
~~---- _______J
Data and Information Viewpoint Articulate the data relationships and alignment structures in the
architecture content
All Viewpoint Overarching aspects of architecture context that relate to all v iews
DoDAF V2.0 Exemplarso 0 e p a s
• What are they– Collections of architectural views and their corresponding DM2
PES XML document examplesPES XML document examples– From coherent datasets, e.g., UPDM S&R, NCES ISP
• How are we doing them 1.DoDAF Journal2 DoDAF Outreach Brief Viewsg
Discuss Candidate
Datasets with
Conform Diagram to
2.DoDAF Outreach Brief - Views
1.DoDAF Outreach Brief – DM2 Developers / Analyst / I t tDatasets with
Process Owners
gDoDAF 2 and Add Legends
Add Additi l
Integrator2.DM2 Description Document –
PES3.DoD MDR4.DM2 Collaboration Site
DM2 PES
Additional Markups for
DM2
Enter Into Review22
DM2 DBDM2 PES XML Document
Enter Into DM2
Database
Review With
DM2 WG
Model ExamplesModel Examples
CV-1 SAR Vision ) f------------_______/
Desired Effect Fulfill International Obligations
Capability Search and Rescue
Desired Effect Maintain US SAR Responsibility
Vision US SAR Vision
I Visions l Capabilities
desired Effects
Activities
Note Phase I lasts 35 months
startDate 2010-01-01 00:00:00
end Date 2014-06-01 00:00:00
4t Whole 1 Capability lasts
54 months
1 Temporal
WholePart1 Temporal
WholePart2 1
Capability SAR Phase 1
startDate 2010-01-01 00:00:00
end Date 2012-12-01 00:00:00
!Activities part of j Capabilty
Activities -~ Assist Recover Search
Capability SAR Phase 2
startDate 2012-12-01 00:00:00
end Date 2014-06-01 00:00:00
Activities~ Assist Recover Search
Vision US SAR Vision
Note Phase II lasts 19 months
Model ExamplesModel Examples
Bounding boxOV-2 [Architectural Description] Organizational Interactions
WO : warningOrder Place of Safety1Search
Legend:
Organization Types
PersonType
Location Type1
Bounding box means Resource at Location
Boat Radio Communications System2
Search Org Type
DS : distressSignalTsk : taskingStat : status
PoS Org Type
Boat
Organization Types
Information (Resource)
Resource Flows
Rescue Org TypePerson in Distress DS :
voiceDistressSignal
DS : distressSignal
speak
key
Boat Radio2
System2
Consume (Activity)
Produce (Activity)
Tsk : tasking
Ctrl : control
Rqst : request
key
DS : keyDistressSignal
Materiel2
System
SAR Asset Controller
Tactical C2Org Type Monitoring
Org Type
Rqst : request
TI : trackInfo
NOTE 1. Should generally not be shown in OV-2 unless an important constraint, i.e., not within the solution trade space.NOTE 2: Should never be in OV-2 but included here for illustrative purposes to show SV-1 “bridge”. Such a dataset could be defined as a “fit for purpose” dataset within a sub-COI.
Presentation ViewsPresentation Views
• DoDAF V2.0 enables architects to provide visualizations of the collected architecture information through a combination of DoDAF-collected architecture information through a combination of DoDAFdescribed Models and Fit-for-Purpose Views.
• DoDAF V2.0-described Models are templates for creating architecture views (i.e., OV-2, SysV-4) of the architecture data.
• Presentation Views allow the architect to present the data in views commonly used by information consumers.
26
“Fit for Purpose”Fit-for-Purpose
• Is an architectural view that is appropriately focused on supporting the stated goals and objectives.
• Is meaningful and useful in the decision-making process.
• Encourages the architect to focus on collecting data and creating views that are customized to the decision-maker’s value chain.
• Architectural data and views are aligned to the information• Architectural data and views are aligned to the information consumer’s needs.
29
DoDAF V2.0 Moved to Web-BasedCollaboration Environment
• DoDAF V2.0 will be promulgated via the DoD CIO/NII website and not published as document. p
– Promoting collaboration among the DoDAFcommunitycommunity
– Improved ability to locate informationImproved ability to locate information
– Facilitate changes & updates to DoDAF guidance
31
The official and most current DoDAF V2.0 content is located on the government websites.
D DAF V2 0 W b it O iDoDAF V2.0 Website Overview
• Public DoDAF Website– Open to public – Hosted on the DoD CIO/NII website– http://cio-nii.defense.gov/sites/dodaf20/
• Private DoDAF Website N d G t S– Need Government Sponsor
– Need Account – Change Request SubmissionChange Request Submission – Hosted on DKO Homepage– https://www.us.army.mil/suite/page/454707
32
Public Websitehttp://cio-nii.defense.gov/sites/dodaf20
33
e ... liJ http:/Jcio-nii .defense.gov/sites/dodaf20/index .html v j +t X I Live Search
File Edit View Favorites Tools Help
What is New in DoDAF V2.0
Navigate by Content
Vision for DoDAF V2.0
Architecture Resources
DoDAF Vl.S Support
Relationships to other Frameworks
Background
Architecture Development
Viewpoints
Models
DM2
Navigate by Role
Manager Role
Architect Role
Developer Role
DoD Architecture Framework Version 2.0 DoD Deputy Chieflnformation Officer
Home Models DoOAF Journal links Archives
The DoDAF Architecture Framework Version 2.0
Welcome to the DoDAF web site! This website is the online documentation for the Department of Defense Architecture Framework.
The Promulgation Memo was signed on 28 May 2009 and is the prescribed framework for all Department architectures. The Department of Defense Archit ecture Framework (DoDAF), Version 2.0 serves as the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of Department of Defense (DoD) managers at all levels t o make key
Search
decisions more effectively through organized information sharing across the Department, Joint Capability Areas (JCAs), Mission, Component , and Program boundaries. The DoDAF serves as one of the principal pillars supporting the DoD Chief Information Officer (CIO) in his responsibilities fo r development and maintenance of architectures required under the Clinger-Cohen Act. It also reflects guidance from the Office of Management and Budget (OMB) Circular A-130, and other Departmental directives and instructions. This version of the Framework provides extensive guidance on the development of architectures supporting the adoption and execution of Net-{;entric services within the Department .
DoDAF Conformance criteria is listed here.
Version 2.0
Internet !t'._ IOO% ~
~ 7 1nternetExplorer ~ r13DoDAF2PienaryOutl .. . ~ fij ': l'~fe~ !0:48AM
Private DoDAF Website – DKOate o ebs te Ohttps://www.us.army.mil/suite/page/454707
34
(5 Army Knowledge Online - shelton. lee - Windows Internet Explorer ~~L8]
~ • Iii!! htt))s: Jiw........, ,us .~rmy.mil/suite/))ort~l/index .js)) I v ~ ~' Certific~te E~ +.,. ~ luve SeMch I& Eile !;.dit l(iew F~vorites I ools ttelp
~ IM
Do OAF Home page (Related Content • ) Op!Jon$ •
AKO lfome > DoD Orgaruza110ns > OSD > ASD (till) I DoD CIO > DCIOIDASD tnforma1Jon Management, lntegratron and Technology > Directorate . Enterprrse Archotecture and Standards > OoDAF Homepage > OoDAF Homepage
Welcome to the DoDAF Homepage Optoons
The DoDAF Homepage contains: • The formal DoD Architecture Framework documentation (V2.0, V1.5, and V1.0) • The DoDAF Journal, an area for support ing files. It will includes the fi les that support the DoOAF V2.0 Volumes, which will include examples. best pract ices, and community input. • The DoDAF Configurat ion Management process • Provides a channel to submit Change Requests. Change Requests and requests to add files to the DoDAF Journal will be processed in accordance with the Configuration Management process. Change Requests can be submitted for DoDAF and the DoDAF Journal below in the "DoDAF and DoDAF Journal Change Requests". Files can be uploaded by users in the "DoDAF Journal Knowledge Center Channel". This will initate the CM process. however, the files will need to be approved before they will be visible.
OoDAF Announc.ements Optoons
DoDAF V2.0 has been posted to Oefenselink and is available to the pubic. » DoDAFV2.0
Current « Pre"ous 1 l<ext • A rchrved
DoDAF Oocumentatoon Optoons
DoD Architecture Framework (DoDAF) l5 Personal and Teams
Show 1 0 20 (50] 1 00
Internet fit 100%
))
v
. . . (5 7 I nternet Explorer • f t:l DoDAF 2Pienary .. . ~~ Mocrosoft PowerPo.. . ~~ PowerPoont Slode 5 ... lrij ':' ~fe~ 11:06 AM
Ch R t I f tiChange Request Information
• DKO DoDAF V2.0 Homepage, https://www.us.army.mil/suite/page/454707,
• Under the “DoDAF and DoDAF Journal Change Requests” channel– Select “Open a Topic” to initiate a Change Request– Select Open a Topic to initiate a Change Request– Initiated Change Requests will be reviewed and adjudicated
monthly by DoDAF and DM2 Working Groups– Approved Change Requests will be updated in DoDAF 2.01
35
DKO DoDAF V2.0 Homepagep ghttps://www.us.army.mil/suite/page/454707
36
(5 Army Knowledge Online - shelton. lee -Windows Internet Explorer ~@][E) e .. li:i ht tps:J/www.us.army.milf suite{portal(ondex .jsp
File Edit View Favorites Tools Help
e» Remove from favontes
Q VIdeos of OoDAF V2.0 Sess1ons
Q Change management Pages
Q Training Resources
Q UJTLS in AV-2
Q ActNtJes and Functions
Archdecture Evaluation 4 files
Other Information
16 files
~ Last Message
16 Feb 2010 14:52 Gf.IT By: Q charles.thornburg
16 Feb 2010 12:S2 Gf.IT By: (l charles.lhornburg
16 Feb 2010 12:50 Gf.IT
By: Q charles.thornburg
12 Feb 2010 15:07 Gf.IT By: Q charles.thornburg
12 Feb 2010 15:04 Gf.IT
By: ~ charles.thornburg
1 - 5011 2 J.;j ~ [1] 2 3 v C-1
v I ~ Certificate Error ' t rx I Go~le
Archlecture Process 3 files
~···
Conf~guratlon llanagement
I p l.
Opt iOns
lnsode AKO 1 Hel p 1 Te<msof Use ®2001 -20 10 Un1ted StatesAsmy
Done Internet &, 100% ~---------------------------------------------------------------------------------------------------------~
•l _start ~~~ {5 Army Knowledge OniJ .. . rv...· ~~ 4:37 Pf'l
DoD Enterprise Architecture ConferenceDoD Enterprise Architecture Conference
San Antonio, TXMay 10-14, 2010Register at:Register at: WWW.DODENTERPRISEARCHITECTURE.ORGCo-hosted by Architecture, Standards, and Interoperability Directorate, DoD Deputy CIO and
37
p y , p yJoint Staff