Enterprise Architecture - DoDAF

4,824 views

Published on

Published in: Education, News & Politics
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,824
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
208
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Enterprise Architecture - DoDAF

  1. 1. Enterprise Architecture - DoDAF Capturing a DODAF Architecture in CORE Clifford Levine Vitech Corporation © 2006 Vitech Corporation. All rights reserved.
  2. 2. Presentation Objectives • Demonstrate how to implement MBSE methodology to build a DoDAF Architecture using CORE® • Solve a sample problem while at the same time, generate a complete set of DoDAF views • Provide you the knowledge and skills to take back to your team and organization 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 2
  3. 3. Presentation Outline – Using Model-based systems engineering concepts – The CORE® Environment – Introduction to Tactical Image Management System example – Capturing the Architecture – Generating DoDAF Views – Summary and review 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 3
  4. 4. Model Base Systems Engineering 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 4
  5. 5. Model Base Systems Engineering Problem Behavioral Architecture Definition Analysis Synthesis Source DoDAF Material Views Integrated, Consistent Analysis: Complete Specifications, Project Documentation, Queries & Models 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 5
  6. 6. Why MBSE? • Convergent • Model-based • Concurrent engineering • Layered, hierarchical solution • Central engineering repository – Incorporating system definition language • With graphical control constructs • Executable, dynamic validation of system logic • Context free • Automated artifact generation 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 6
  7. 7. CORE Environment 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 7
  8. 8. CORE System Definition Language CORE English CORE Example Language Equivalent Element Noun • Operational Node Brigade Level • Operational Activity Receive Orders • Component Troop Carrier Relationship Verb • Operational Activity are allocated to Operational Node Attribute Adjective • Description • Number Attribute of Adverb Resource consumed by Function Relationship • Amount Structure N/A • Viewed as Enhanced FFBD or FFBD SDL is an Extended Natural Language in ERA Format 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 8
  9. 9. A Partial ERA Example Architecture comprised of •Description comprised of (member of) •Number (member of) Operational Activity Component •Description Implemented by •Description •Number (implements) •Number •Structure •Structure performs performs (allocated to) (allocated to) Operational Node Function •Description Implemented by •Description •Number •Number (implements) •Structure •Structure Operational Elements System Domain 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 9
  10. 10. CORE Project Explorer 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 10
  11. 11. Tactical Image Management Architecture 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 11
  12. 12. TIM Context View Description: The Tactical Image Management Architecture is composed of both an operational element and an image management system which supports the architecture. 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 12
  13. 13. Operational Behavior This diagram becomes an OV-6 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 13
  14. 14. Data to be Collected 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 14
  15. 15. DoDAF Views 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 15
  16. 16. OV-3 Operational Information Exchange Matrix • Description: – Information exchanged between nodes and the relevant attributes of that exchange • CORE Implementation – Outputs the information exchange requirements for the OperationalNodes that comprise the user selected Architecture or OperationalNode. Optionally outputs an Elements Definitions Table. 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 16
  17. 17. Operational Information Exchange Matrix (OV-3) 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 17
  18. 18. Operational Information Exchange Matrix (OV-3) 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 18
  19. 19. SV-1 System Interface Diagram • Description – Identification of systems nodes, systems, system items, services, and service items and their interconnections, within and between nodes • CORE Implementation – Outputs a Physical Block Diagram for the user selected Component or a user selected ExternalFile for the Component. 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 19
  20. 20. System Interface Diagram (SV-1) 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 20
  21. 21. Summary 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 21
  22. 22. Impleting DoDAF in CORE • Extended the underlying systems engineering design language to embrace operational architecture development • Apply the MBSE approach to integrated operational and system architectures – DoDAF views are by-products architecture development – Integrated architecture data and views are always synchronized • Ability to identify critical decision elements that are part of the architecture and be able to ‘tune’ them for decision support 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 22
  23. 23. Benefits of Integrated Repository Viewgraph Engineering Model-Based SE Independent drawings Consistent views Static diagrams Executable behavior[1] Data storage Linked repository Stored views Dynamic view generation Ad hoc process (inconsistent Repeatable process (consistent results) results) Manual change propagation across Automatic change propagation all affected products (by the system across all current and future engineer) products (by the engineering environment) [1] Executable behavior eliminates structural or dynamic inconsistencies from the requirements. 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 23
  24. 24. Summation • A way to produce architecture view artifacts (OV, SV, and TV’s) that meet the wants and desires of the DoD customer • A way to deliver System and Architecture views to users, stakeholders, and customers that support each of their analytical tasks • A way to produce Integrated Architectures • A way to produce ‘Executable Architectures’ • A methodology to do the above 12/2008 © 2006 Vitech Corporation. All rights reserved. DoDAF- 24
  25. 25. clevine@vitechcorp.com MM DDD YYYY © 2006 Vitech Corporation. All rights reserved. Brief Title - 25

×