Lecture 4.4: DoDAF Overview (Vol. II, Chs 1 & 2) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
Agenda <ul><li>Overview </li></ul>
Overview (1.1) and Purpose (1.2) <ul><li>DoDAF provides a “common approach for DoD architecture description development, p...
Architecture Views (2.1) <ul><li>The Framework defines three views: </li></ul><ul><ul><li>Operational View (OV) : describe...
Architecture Products (2.2)
Architecture Products (2.2) : All Views, Operational Views and Technical Views
Architecture Products (2.2) :  Systems Views
Architecture Data Elements (2.3) <ul><li>Architecture Data Elements (ADEs) are the underlying basic elements that comprise...
Architecture Product Development (2.4) <ul><li>Supports both Structured Analysis (IDEF) and UML methodologies </li></ul><u...
Integrated Dictionary Legend <ul><li>Entry Types:  </li></ul><ul><ul><li>Operational Node (ON) </li></ul></ul><ul><ul><li>...
AV-2: Integrated Dictionary - WBRS Example
Conclusions <ul><li>AV-1 and AV-2 are essential products for every architecture </li></ul><ul><li>AV-1 is usually develope...
Upcoming SlideShare
Loading in …5
×

Lecture_4.4-DoDAF_Ov..

573 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
573
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Lecture_4.4-DoDAF_Ov..

  1. 1. Lecture 4.4: DoDAF Overview (Vol. II, Chs 1 & 2) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
  2. 2. Agenda <ul><li>Overview </li></ul>
  3. 3. Overview (1.1) and Purpose (1.2) <ul><li>DoDAF provides a “common approach for DoD architecture description development, presentation, and integration” </li></ul><ul><ul><li>Supports Requirements Development </li></ul></ul><ul><ul><ul><li>Complete </li></ul></ul></ul><ul><ul><ul><li>Consistent </li></ul></ul></ul><ul><ul><ul><li>Allocated to Components </li></ul></ul></ul><ul><ul><li>Supports Design Development </li></ul></ul><ul><ul><ul><li>Complete </li></ul></ul></ul><ul><ul><ul><li>Consistent </li></ul></ul></ul><ul><ul><ul><li>Meets Requirements </li></ul></ul></ul><ul><li>Definitions </li></ul><ul><ul><li>Architecture refers to both: </li></ul></ul><ul><ul><ul><li>An architecture description </li></ul></ul></ul><ul><ul><ul><li>An architecture implementation </li></ul></ul></ul><ul><ul><li>Architecture Description is “a representation of a defined domain … in terms of constituent parts, what those parts do, how the parts relate to each other and to the environment and the rules and constraints governing them” </li></ul></ul><ul><ul><li>Architecture Implementation is “a real implementation of capabilities and assets in the field” </li></ul></ul><ul><ul><li>Integrated Architecture is “an architecture description that ahs integrated OVs, SVs and TVs” </li></ul></ul>
  4. 4. Architecture Views (2.1) <ul><li>The Framework defines three views: </li></ul><ul><ul><li>Operational View (OV) : describes tasks, activities, operational elements, and information exchanges required to accomplish DoD Missions, i.e., “enterprise” mission aspects. </li></ul></ul><ul><ul><li>System View (SV) : describes systems and interconnections providing for, or supporting, DoD functions. It associates systems resources to the OV. </li></ul></ul><ul><ul><li>Technical Standards View (TV) : provides the technical systems implementation guidelines upon which engineering specifications are based, common building blocks are established, and product lines are developed, e.g., policies and technical standards. </li></ul></ul><ul><li>“ All View (AV)” products are those provide overarching information describing the architecture plans, scope, and definitions </li></ul><ul><li>Each View is composed of sets of architecture data elements that are depicted via graphic, tabular, and textual products. </li></ul><ul><li>The Core Architecture Data Model (CADM) defines the entities and relationships for architecture data. </li></ul><ul><li>DoDAF recognizes that the term “Architecture” is overloaded. As such, it divides the term into different views and products (for each view). </li></ul>
  5. 5. Architecture Products (2.2)
  6. 6. Architecture Products (2.2) : All Views, Operational Views and Technical Views
  7. 7. Architecture Products (2.2) : Systems Views
  8. 8. Architecture Data Elements (2.3) <ul><li>Architecture Data Elements (ADEs) are the underlying basic elements that comprise the architecture (examples will be provided later) </li></ul><ul><li>These ADEs are captured in the a Architecture Data Model that is specific to each AV, OV, SV, or TV graphics (examples will be provided later) </li></ul><ul><li>The All-DoD Core Architecture Data Model (CADM) specifies the ADE fields for each View </li></ul>
  9. 9. Architecture Product Development (2.4) <ul><li>Supports both Structured Analysis (IDEF) and UML methodologies </li></ul><ul><li>Most products may be decomposed to multiple levels </li></ul><ul><li>Decomposition should be to the level required for the stated objective (user) </li></ul><ul><li>Products should be developed iteratively (per SE Process) </li></ul><ul><li>Templates should be developed </li></ul>
  10. 10. Integrated Dictionary Legend <ul><li>Entry Types: </li></ul><ul><ul><li>Operational Node (ON) </li></ul></ul><ul><ul><li>Operational Element (OE) </li></ul></ul><ul><ul><li>System (Sys) </li></ul></ul><ul><ul><li>Subsystem Element (SE) </li></ul></ul><ul><ul><li>Actor (Actor) </li></ul></ul><ul><ul><li>External System (ES) </li></ul></ul><ul><ul><li>External Subsystem Element (ESE) </li></ul></ul><ul><ul><li>Function/Activity (Fnc) </li></ul></ul><ul><ul><li>Rule Model (RM) </li></ul></ul><ul><ul><li>State (State) </li></ul></ul><ul><ul><li>Data Entity (DE) </li></ul></ul><ul><ul><li>Data Attribute (DA) </li></ul></ul><ul><li>Reference ID: </li></ul><ul><ul><li>Function/Activity: A1.X.y </li></ul></ul><ul><ul><li>System/Subsystem Element: C1.X.y </li></ul></ul><ul><ul><li>External System/Subsystem Element: ESX.Y </li></ul></ul><ul><ul><li>Rule Model: RM1.X.y </li></ul></ul><ul><ul><li>Data Entity (DE): DEX.y </li></ul></ul><ul><li>Acronym </li></ul><ul><li>Term </li></ul><ul><li>Definitions </li></ul><ul><ul><li>Functions should indicate I/O Des and Rule Models </li></ul></ul><ul><ul><li>System/Subsystem Elements should include alllocated Functions </li></ul></ul><ul><ul><li>DEs should include list of DAs </li></ul></ul><ul><ul><li>DAs should include data type, visibility, and ranges. </li></ul></ul><ul><ul><li>RMs should include reference to functions and DEs </li></ul></ul>
  11. 11. AV-2: Integrated Dictionary - WBRS Example
  12. 12. Conclusions <ul><li>AV-1 and AV-2 are essential products for every architecture </li></ul><ul><li>AV-1 is usually developed in a Word document </li></ul><ul><li>Initially one may want to develop the AV-2 in Word or Excel until you figure out the desired format or until a CASE Architecture Tool is selected. </li></ul>

×