Simplified DODAF_pre..

1,092 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,092
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
34
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Simplified DODAF_pre..

  1. 1. DoDAF Enterprise Architecture Framework Basics
  2. 2. 3. Overview of the Core Products * * Core products are those that are recommended for most architectures, and/or those that have been adopted by other frameworks
  3. 3. “ All Views” Products Capture Information That Applies to the Architecture Overall <ul><ul><ul><li>Identification </li></ul></ul></ul><ul><ul><ul><ul><li>Name </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Architect </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Organizations Involved </li></ul></ul></ul></ul><ul><ul><ul><ul><li>When Developed </li></ul></ul></ul></ul><ul><ul><ul><li>Purpose </li></ul></ul></ul><ul><ul><ul><ul><li>Analysis Needs </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Decision Support Needs </li></ul></ul></ul></ul><ul><ul><ul><li>Scope </li></ul></ul></ul><ul><ul><ul><ul><li>Views and Products Used </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Time Frames Addressed </li></ul></ul></ul></ul><ul><ul><ul><li>Context </li></ul></ul></ul><ul><ul><ul><ul><li>Mission </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Geographical </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Rules, Criteria, and Conventions Followed </li></ul></ul></ul></ul><ul><ul><ul><li>Findings: Results, Recommendations </li></ul></ul></ul><ul><ul><ul><li>Tools and File Formats </li></ul></ul></ul>Overview and Summary Information Integrated Dictionary At a minimum, the integrated Dictionary is a glossary with definitions of terms used in the given architecture description. Each labeled graphical item in the graphical representations should have a corresponding entry in the Integrated Dictionary. Integrated Dictionary Core Products
  4. 4. The Operational View Captures the Critical Mission Relationships and Information Exchanges Core Products Node A Node B Activity 1 Activity 2 Node C Activity 3 Activity 2 Activity 3 <ul><li>Information Description </li></ul><ul><ul><li>Name/Identifier </li></ul></ul><ul><ul><li>Definition </li></ul></ul><ul><ul><li>Media </li></ul></ul><ul><ul><li>Size </li></ul></ul><ul><ul><li>Units </li></ul></ul><ul><li>Information Exchange Attributes </li></ul><ul><ul><li>Frequency, Timeliness, Throughput </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Interoperability Requirements </li></ul></ul><ul><li>Information Source </li></ul><ul><li>Information Destination </li></ul>Information Exchange 1 High-Level Operational Concept Description Operational Node Connectivity Description Operational Information Exchange Matrix High-level graphical description of the operational concept of interest Operational nodes, activities performed at each node, node-to-node relationships, and information needlines Information exchanged between nodes and the relevant attributes of the exchanges To External Node From External Node Activity Model Operational activities performed and their input/output relationships OPERATIONAL INFORMATION ELEMENT DESCRIPTION MEDIA SIZE UNITS NAME/IDENTIFIER DEFINITION DIGITAL, VOICE, TEXT, IMAGE, ETC. RANGE LIMITS FEET, LITERS, INCHES, ETC. OPERATIONAL ELEMENT & ACTIVITY OPERATIONAL ELEMENT & ACTIVITY IDENTIFIER OF PRODUCING OE PRODUCING ACTIVITY IDENTIFIER OF CONSUMING OE CONSUMING ACTIVITY INFORMATION SOURCE INFORMATION DESTINATION FREQUENCY, TIMELINESS, THROUGHPUT SECURITY INTEROPER- ABILITY REQUIREMENTS INFORMATION EXCHANGE ATTRIBUTES INFORMATION DESCRIPTION
  5. 5. A Closer Look at the Operational Node Connectivity Description OV-2 Showing Physical Nodes Shows that Node C needs information of type X, and that Node B is tasked with providing that information.
  6. 6. A Closer Look at the Operational Node Connectivity Description OV-2 continued Showing Logical Nodes
  7. 7. A Closer Look at the Operational Information Exchange Matrix OV-3 And their attributes For each needline ... There is a listing of distinct information exchanges ...
  8. 8. What About the Case in Which All Nodes Get All Information - “Everyone Sees Everything?” <ul><li>Architectures should be built with a specific purpose and scope in mind (more on that later) </li></ul><ul><li>Even when everyone can see everything, it is usually not the case that everyone needs to see everything for every purpose </li></ul><ul><li>Needlines on the Node Connectivity Description show which nodes need to be connected for the purposes being addressed in the architecture </li></ul><ul><li>The Information Exchange Matrix shows attributes of those exchanges that are relevant to the purposes being addressed in the architecture </li></ul><ul><li>If in fact all nodes do need to be connected to all other nodes, this can be shown graphically in a shorthand way, but the Integrated Dictionary must capture each individual connection. An automated tool is essential for this. </li></ul><ul><li>This universal connectivity can be shown also in the System Interface Description and System Communications Description (see later example) </li></ul>
  9. 9. The Systems View Examines Current and Postulated IS Capabilities in Context with Mission Operations Internodal System-to-System Intranodal Intrasystem Core Product: System Interface Description Internodal Node-Edge-to-Node-Edge NODES COMMUNICATIONS NETWORK FROM/TO OTHER SYSTEM 3 NODE B COMMUNICATIONS NETWORK Interface 1 Interface 2 SYSTEM 1 SYSTEM 2 FROM/TO OTHER NODES
  10. 10. Web-based Example (All Nodes Can Get All Information): Federal Commons System Interface Description “ Web” grid indicates that all nodes can receive all information Color coded lines indicate which nodes need which information
  11. 11. The Technical View Identifies the Implementation Criteria That Govern the Given Architecture Core Product: Technical Standards Profile Services View Interfaces View
  12. 12. The Framework Specifies Common Architecture Data Core Products - Operational View Entities and Attributes The Framework provides a description of the data that must be captured in each architecture product. This product data is listed in Product Data Element Tables. Core Product - Technical View Entities and Attributes Core Product - Systems View Entities and Attributes
  13. 13. Example - Data Element Table for the Operational Node Connectivity Description (Extract)
  14. 14. The Core Products Link to Each Other HIGH-LEVEL OPERATIONALCONCEPT DESCRIPTION (OV-1) VALUE ADDED : SUMMARY LEVEL REPRESENTATION OF ORGANIZATIONS/ROLES, MISSION, AND CONTEXT FOR THE ARCHITECTURE OPERATIONAL CONCEPT ROLES & MISSIONS SET SCOPE FOR ACTIVITY MODEL OPERATIONAL INFORMATION EXCHANGE MATRIX (OV-3) VALUE ADDED : INDIVIDUAL INFORMATION EXCHANGES ASSOCIATED WITH EACH NEEDLINE, PERFORMANCE REQUIREMENTS FOR OPERATIONAL INFORMA- TION EXCHANGES OPERATIONAL NODE CONNECTIVITY DESCRIPTION (OV-2) VALUE ADDED : STATEMENT OF OPERATIONAL NODES, ACTIVITIES, AND CRITICAL INFORMATION NEEDS (NEEDLINES & SUMMARY INFORMATION EXCHANGED) <ul><li>OPERATIONAL NODES ARE ASSOCIATEAD WITH SYSTEMS AND SYSTEMS NODES </li></ul><ul><li>EACH OPERATIONAL NEEDLINE MAPS TO ONE OR MORE SYSTEMS LINKS </li></ul>SYSTEMS INTERFACE DESCRIPTION (SV-1) VALUE ADDED : STATEMENT OF SYSTEMS NODES, SYSTEMS, LINKS & COMPONENT INTERFACES; SUMMARIZED SYSTEM INFORMATION EXCHANGES STANDARDS APPLY AT SYSTEM TO SYSTEM INTERFACES TECHNICAL STANDARDS PROFILE (TV-1) VALUE ADDED : COMPLETE LIST OF RELEVANT STANDARDS WITH OPTIONS & PARAMETERS INFORMATION EXCHANGES ASSOCIATED WITH EACH NEEDLINE ARE DETAILED IN OV-3 <ul><li>ACTIVITIES MAP TO OPERATIONAL NODES </li></ul><ul><li>I/OS MAP TO NEEDLINES </li></ul><ul><li>PERFORMERS OF ACTIVITIES, IF SHOWN ON 0V-5, MAP TO OPERATIONAL NODES </li></ul>VALUE ADDED : BUSINESS/MISSION PROCESS & RELATIONSHIPS AMONG ACTIVITIES AND OPERATIONAL INFORMATION EXCHANGED ACTIVITY MODEL (OV-5) OPERATIONAL CONCEPT CONNECTIVITY & INFORMATION EXCHANGES, IF SHOWN ON 0V-1, MAP TO OPERATIONAL NODE CONNECTIVITYDESCRIPTION NEEDLINES & INFORMATION EXCHANGES INNPUT/OUTPUT LABELS MAP TO OPERATIONAL INFORMATION EXCHANGES (NOT ALWAYS ONE-TO-ONE) Overview and Summary Information and Integrated Dictionary are not shown because they relate to all other products
  15. 15. Some Other Important Product Linkages … And the sending and receiving systems used to implement the interface are indicated... OV-3 Operational Information Exchange Matrix SV-1 System Interface Description SV-6 System Data Exchange Matrix Nature of Transaction Data Source Data Destination Content Size Media Format LISI Level Achievable ID of Source System ID of Receiving System Source System Function (from S-4) Receiving System Function (from S-4) Operational Node(s) Where System Is Resident Operational Node(s) Where System Is Resident Protocols Used Identifier/ Name of Operational Needline Supported (from OV-2) Identifier/ Name of Operational Information Exchange Supported (from OV-3) e.g., 1-a e.g., 1-b e.g., 1-c Identifier/ Name of Corresponding System Interface(s) (from SV-1) e .g., Interface 1 e .g., Interface 2 . . . e .g., Interface n Needline 1 Needline 2 Needline n . . . e.g., 1-d e.g., 1-e e.g., 1-f 1 3 … The individual information exchanges are assigned to the appropriate system interface... 2 Each needline is decomposed into one or more system interfaces ...
  16. 16. Architecture Product Linkages Provide the “Audit Trail” That Relates Technology to Mission Operations What Information Must Be Captured? <ul><li>Implementation Criteria </li></ul><ul><li>Standards, Conventions </li></ul><ul><li>Operating Environment </li></ul>What Performance Measures? Where Captured? Audit Trail Mission Effectiveness <ul><li>Players, activities, interactions, ... </li></ul><ul><li>Information exchanges </li></ul><ul><li>Execution environment </li></ul><ul><li>Projected risks </li></ul><ul><li>Applications and products </li></ul><ul><li>Platform, operating system </li></ul>Operational Mission Requirements Systems Capabilities Implementation Criteria <ul><li>System Requirements </li></ul><ul><li>Functions/capabilities </li></ul><ul><li>Information exchanges </li></ul><ul><li>Performance </li></ul><ul><li>Threat/security protection </li></ul><ul><li>Functions supported </li></ul><ul><li>Interoperability level </li></ul><ul><li>Performance characteristics </li></ul><ul><li>Info Assurance/IO measures </li></ul>Operational Node Connectivity Description Technical Standards Profile System Interface Description Mission Operations System Attributes/Metrics System Implementations TARGETS KILLED SAUDI ARABIA PFP SITES DETECTED IRAQ TIMELY INTERDICTION BOLIVIA PIT RAID COUNTERDRUG COUNTER- PROLIFERATION SUPPORT TO MILITARY OPS O P E R A T I O N S S Y S T E M S T E C H N I C A L
  17. 17. 4. Overview of the Supporting Products* of the DoD Architecture Framework * Supporting Products are those products, other than the core products, that you may need to build for your architecture
  18. 18. “ AV-3” Capability Maturity Profile (Not an official part of the Framework document, but a technique many architects are using) <ul><li>Provides a structure for enterprise-wide planning to </li></ul><ul><ul><li>Rationalize investment strategies </li></ul></ul><ul><ul><li>Promote increasing capability levels </li></ul></ul><ul><ul><li>Assure that $$ spent address capability needs </li></ul></ul><ul><ul><li>Move from As-Is to To-Be architectures </li></ul></ul>
  19. 19. Components of the Capability Roadmap - Select the components you need and create new ones as needed SCI SECRET UNCLASSIFIED IT Competency Email/Messaging Collaboration Directory Services Domain Applications Search & Access Administrative Applications Information Assurance Computing Platform Infrastructure Management Infrastructure Knowledge Management Resourcing Governance Network Subscription & Delivery Services Information Storage & Management IT Service Delivery Multiple Security Level Interconnection Process
  20. 20. Standard Capability Scale 1 2 Interactions focused on separate objectives using organization-unique systems and databases Ad-hoc Rudimentary, secure information exchanges between some organizations on common intranet, with unpredictable reliability Minimal 3 Limited Secure multimedia collaboration within interest groups using partially integrated networks, limited data sharing, and interoperable applications and services 4 Structured Established enterprise management and reliable operations focused on improved customer satisfaction, collaborative core business processes, enterprise-wide, secure information and applications sharing, and the timely exploitation of enabling technologies 5 Optimizing i Continuously optimized management, operations, and external partnerships focused on mission effectiveness and the agility to extract and reassemble information from multiple domains securely and adaptively Increasing capabilities, availability, reliability, and global reach
  21. 21. OV-4 Organizational Relationships Chart
  22. 22. OV-6 Operational Timing and Sequencing Products OV-6bOperational State Transition Description OV-6a Operational Rules Model: no graphic OV-6cOperational Event/Trace Description S U B S T A T E 1 S U B S T A T E 2 S U B S T A T E 3 S U B S T A T E 4 EVENT 3 EVENT 4 EVENT 1 EVENT 2
  23. 23. OV-7 Logical Data Model Entity Name Relationship Attributes • ..... • ..... • .....
  24. 24. SV-2 System Communications Description Intranodal Perspective Internodal Perspective NODE A Local Area Net System 1 System 2 System 3 System 4 System 5 EXTERNAL CONNECTION (OUTSIDE THE NODES OF INTEREST) CONNECTION TO NODE B CONNECTION TO NODE B CONNECTION TO NODE C Two-Way Communications Paths One-Way Communi - cations Path
  25. 25. SV-3 System-System Matrix
  26. 26. SV-4 Systems Functionality Description System Function 1 DATA REPOSITORY DATA FLOW 1 DATA FLOW 2 DATA FLOW 3 DATA FLOW 4 DATA FLOW 5 DATA FLOW 6 DATA FLOW 7 DATA FLOW 8 DATA FLOW 9 DATA FLOW 10 EXTERNAL SOURCE 1 EXTERNAL SOURCE 2 EXTERNAL SINK 1 EXTERNAL SINK 2 System Function 3 System Function 4 System Function 2
  27. 27. SV-5 Operational Activity to System Function Traceability Matrix 1 1.1 1.1.1 1.1.1.1 1.1.1.2 1.1.1.3 1.1.2 1.1.2.1 1.1.2.2 1.1.2.3 1.1.3 1.1.3.1 1.1.3.2 1.1.3.3 1.1.3.4 3.11 3.11.3 3.12 3.12.1 3.12.2 3.12.3 3.13 3.14 3.14.1 3.14.2 3.14.3 3.14.4 3.15 3.16 3.17 3.17.1 System Functions .. .. Operational Activities X X X X X X X X X X X X X X X
  28. 28. SV-6 System Data Exchange Matrix Nature of Transaction Data Source Data Destination Content Size Format LISI Level Achievable Source System Name Receiving System Name Source System Component Receiving System Component Other Protocols Identifier/Name of Operational Needline Supported (from OV-2) Identifier/ Name of Operational Information Exchange Supported (from OV-3) e.g., 1-a e.g., 1-b Identifier/Name of Corresponding System Interface(s) (from SV-1) e.g., Interface 1 e.g., Interface 2 . . . e.g., Interface n Needline 1 Needline 2 Needline n . . . e.g., 1-c e.g., 1-d Identifier/ System Data Exchange e.g., 1-a (1) e.g., 1-a (n) . . . Performance Attributes Information Assurance Attributes Physical Environment Frequency Timeliness Throughput Threats Physical Electronic Aerospace Sea Land Political/ Economic Classification Criticality/ Priority Encryption Authentication Other . . . Identifier/Name of Operational Information Exchange Supported (from OV-3) e.g., 1-a e.g., 1-b e.g., Interface 1 e.g., Interface 2 . . . e.g., Interface n Needline 1 Needline 2 Needline n . . . e.g., 1-c e.g., 1-d e.g., 1-a (1) Identifier/ System Data Exchange e.g., 1-a (n) . . . Identifier/Name of Operational Needline Supported (from OV-2) Identifier/Name of Corresponding System Interface(s) (from SV-1) * * * * * * * * * * * * * * * Indicates minimum recommended entries C O N T I N U E D
  29. 29. SV-7 System Performance Parameters Matrix
  30. 30. SV-8 System Evolution Description Migration Example Evolution Example
  31. 31. SV-9 System Technology Forecast - Fragment -
  32. 32. SV-10 Systems Timing and Sequencing Products SV-10b Systems State Transition Description SV-10c Systems Event/Trace Description S U B S T A T E 1 S U B S T A T E 2 S U B S T A T E 3 S U B S T A T E 4 EVENT 3 EVENT 4 EVENT 1 EVENT 2 COMPLEX TRANSITIONS (SYNCHRONIZATION OF CONTROL ) SV-10a Systems Rules Model: no graphic
  33. 33. SV-11 Physical Schema
  34. 34. TV-2 Standards Technology Forecast- Fragment

×