DoD Architecture Framework Version 2.0 Models & Illustrative View Examples

1. DoD Architecture FrameworkVersion 2.0 Models & Illustrative View Examples USSOCOM Mr. Charles Thornburg Enterprise Architecture & Standards Directorate Office of the DoD Deputy Chief Information Officer (703) 412-7937 Thornburg_Charles@bah.com

2. Before After Overlap Super Sub Type Whole Part Temporal Performer Activity Organization System Measure Service . . . Foundational Concepts in DM2

3. Concepts in AV-1 Overview and Summary • Activity • Constraint • Guidance • Information • Measure • Organization • Performer • Project • Resource • Rule • Vision

4. AV-1 Overview and Summary Information - DARS Registration Example

5. AV-1 Overview and Summary Information - DARS Registration Example (Cont.)

6. AV-1 Overview and Summary Information - DARS Registration Example (Cont.) Architecture Model(s) Models

7. AV-1 Overview and Summary Information - DARS Registration Example (Cont.)

8. AV-1 Overview and Summary Information - DARS Registration Example (Cont.)

9. AV-1 Overview and Summary Information - DARS Registration Example (Cont.)

10. AV-1 Overview and Summary Information – Example 2 AV-1 Overview and Summary Information • Architecture Project Identification • Name: Engineering Developing Center Enterprise • Architect: • Organization Developing the Architecture: Air Force Engineering Developing Center • Assumptions and Constraints: • Date Completed: 03/01/2009 • Scope: Architecture Models Identification • Model Developed: OV-1, OV-2, OV-3, OV-4, OV-5a, OV-6c, SV-1, SV-2, SV-3, SV-5a, SV-8, SV-9, StdV-1, StdV-2 • Time Frames Addressed: Current Baseline, 07/01/2004 – 07/31/2004 • Organizations Involved: Command Group, CIO, Operational Divisions

11. AV-1 Overview and Summary Information – Example 2 (Cont.) AV-1 Overview and Summary Information • Purpose and Viewpoint • Purpose of the Architecture: Reengineering Major Processes • From whose viewpoint the Architecture is Developed: Commander • Context • Mission: Improved Analysis & Evaluation • Tasking for Architecture Process and linkages to Other Architectures: • Tool and File Formats Used: System Architect tool, Formats: System Architect, Excel, Visio

12. Activity Agreement Capability Condition Constraint Data Information Guidance Information Location Materiel Measure Organization Performer Person Type Rule Service Skill Standard System Vision Concepts in AV-2 Integrated Dictionary

13. AV-2 Integrated Dictionary Example

14. AV-2 Integrated Dictionary Example 2

15. Capability Viewpoint Articulate the capability requirement, delivery timing, and deployed capability • Describes the scope and vision for the capability • The delivery phasing and dependencies of the capability • The deployment of the capability in a solution

16. Capability Performer May include: Activity Condition Data Desired Effect Guidance Location Measure Organization Concepts in CV-4 Capability Dependencies • Person Type • Project • Resource • Rule • Service • Skill • System

17. CV-4 Capability Dependencies Example

18. Guidance Measure Information Materiel Organization Performer Resource Concepts in OV-2 Operational Resource Flow Description Concepts that could be what used to be “Node”

19. OV-2 Operational Resource Flow Description Example (Traditional) –This example also depicts Command Relationships

20. OV-2 Operational Resource Flow Description Example (Net-Centric) - Does not depict Command Relationships This can be high level (Network Resources) or detailed. Correspondingly, on the SV-2 or SvcV-2 that supports the OV-2, it can have more details (a website URL) or have several layers, additional layers with more details (specific server names that support a website)

21. OV-2 Comparison

22. Activity Concepts in OV-5a Activity Decomposition Tree Whole Part

23. OV-5a Activity Decomposition Tree Example This is the decomposition of activities, e.g., a tire is part of a car. It does not indicate a Supertype-Subtype relationship (“IS-A”), e.g., a car is a vehicle, a truck is a vehicle.

24. Project Viewpoint Describes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process. • Associates the Programs, Portfolios, Projects, or Initiatives to requirements • Describes a timeline with milestones and dependencies • Describes an Organizations’ effort to acquire and deliver Capabilities

25. Activity Constraint Project May Include: Measure Organization Performer Resource Rule Vision Concepts in PV-1 Project Portfolio Relationships

26. PV-1 Project Portfolio Relationships Examples

27. Activity Constraint Project Performer May Include: Condition Location Materiel Measure Organization Person Type Resource Rule Service Skill System Vision Major Concepts in PV-2 Project Timelines Temporal

28. PV-2 Project Timelines Example Forward Thrust Testing Vertical Engine Testing Multi-Engine Concurrent Testing 3Q 2Q 4Q 1Q This is High Level, geared toward Decision-makers and associated with activities and capabilities. It does NOT replace day-to-day project management.

29. Activity Condition Data Guidance Information Location Materiel Measure Performer Resource Rule Service Standard Major Concepts in SvcV-6 Services Resource Flow Matrix

30. SvcV-6 Services Resource Flow Matrix Example

31. Standards Viewpoint Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts • Renamed from Technical Standards View • Adds the Operational, Business and Industry standards to the Technical Standards

32. Activity Agreement Condition Constraint Data Guidance Location Materiel Measure Organization Performer Project Resource Rule Service Skill Standard System Vision Concepts in StdV-1 Standards Profile

33. StdV-1 Standards Profile Example Financial Data Standard Financial Information Structure is a "common business language" that supports information requirements for budgeting, financial accounting, and cost/performance management. It is available at http://www.bta.mil/SFIS/SFIS_%20Matrix_BEA%206%200.xls Information Exchange SFIS Web Services The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics.It is available at http://www.w3.org/TR/owl-features/ Information Exchange OWL

34. Activity Agreement Condition Constraint Data Guidance Location Materiel Measure Organization Performer Project Resource Rule Service Skill Standard System Vision Concepts in StdV-2 Standards Forecast Temporal

35. StdV-2 Standards Forecast Example

36. Guidance Information Location Materiel Measure Performer Person Type Resource Rule Standard System Concepts in SV-1 Systems Interface Description

37. SV-1 Systems Interface Description Example

38. Activity Performer May Include: Capability Guidance Information Location Resource Rule System Concepts in SV-5a Operational Activity to System Function Traceability Matrix Temporal

39. SV-5a Operational Activity to System Function Traceability Matrix Example A Date, or a “Stoplight” could be at the intersection

40. VDC-400 TACLINK 2000 C2 GCCS-J CPOF AFATDS F.P. GCSS-MC IOS(V)2 IOW MSIDS LOG. FIRES DNS Exchange IOS(V)1 IOW INTEL C2PC MAN. TSM Print Server Router Switch AN/PRC-150 PRC-117 EPLRS AN/MRC-142 SATCOM A “Fit-for-Purpose” View - The Cube Has Three Dimensions of Interfaces in DM2’s Concept of System - from USMC EAWG Across WF Functions – an interaction amongst Systems, itself a SoS which is a System. Abstracting the actual Network and Transport systems. As a “vertical” stack that provides the complete means for end-devices to communicate down to transport layer systems (e.g., through MODEM’s, gateways). This “system” is a type of dynamic or ad-hoc system, e.g., dynamic routing Within device-compatible “networks”, e.g., EPRLS. A network is a type of system in DM2 because it is a bunch of systems working together. As another “Fit-for-Purpose” variation, organizational dependencies can be added to this view.

41. Observations • DoDAF V2.0 does not provide examples of the Views. • DoDAF V2.0 states the focus is about the data. • View examples have been asked of DoD CIO Enterprise Architecture & Standards. • Based on questions that have been asked by others, it seems the questions are based on the DoDAF V1.5 paradigm • The message about DoDAF V2.0 has to be clarified: • Focus should be on the data needed for the Decision-makers and the appropriate Decision Support Systems (or Services). • The format of Views are up to the Decision-makers.

42. Questions? 42