“The Department of Defense (DoD) Architecture Framework (DoDAF), Version 1.0, defines a common approach for DoD architecture description development, presentation, and integration. The Framework enables architecture descriptions to be compared and related across organizational boundaries, including Joint and multinational boundaries.
The Framework supports the development of interoperating and interacting architectures as referenced in DoD issuances.” [DoDAF, v1.0, Deskbook] It defines three related views of architecture: Operational View (OV), Systems View (SV), and Technical Standards View (TV) as depicted in Figure 1.
Figure 1 Linkages Among Views [DoDAF, v1.0, Deskbook]
“The term integrated architecture refers to an architecture description that has an Operational View (OV), Systems View (SV), and Technical Standards View (TV), and the views are integrated (i.e., there are common points of reference linking the OV and SV and also linking the SV and TV). The Operational Activity to Systems Functions Traceability Matrix (SV-5), for example, relates operational activities from the Operational Activity Model (OV-5) to system functions from the Systems Functionality Description (SV-4); the SV-4 system functions are related to systems in the Systems Interface Description (SV-1); thus bridging the OV and SV. An architecture is defined to be an integrated architecture when products and their constituent architecture data elements are developed such that architecture data elements defined in one view are the same (i.e., same names, definitions, and values) as architecture data elements referenced in another view.” [DoDAF, v.10, Vol. II]
“The OV is a description of the tasks and activities, operational elements, and information exchanges required to accomplish DoD missions. DoD missions include both warfighting missions and business processes. The OV contains graphical and textual products that comprise an identification of the operational nodes and elements, assigned tasks and activities, and information flows required between nodes. It defines the types of information exchanged, the frequency of exchange, which tasks and activities are supported by the information exchanges, and the nature of information exchanges.” [DoDAF, v.10, Vol. II]
“The SV is a set of graphical and textual products that describes systems and interconnections providing for, or supporting, DoD functions. DoD functions include both warfighting and business functions. The SV associates system resources to the OV. These system resources support the operational activities and facilitate the exchange of information among operational nodes.” [DoDAF, v.10, Vol. II]
“The TV is the minimal set of rules governing the arrangement, interaction, and interdependence of system parts or elements. Its purpose is to ensure that a system satisfies a specified set of operational requirements. The TV provides the technical systems implementation guidelines upon which engineering specifications are based, common building blocks are established, and product lines are developed. The TV includes a collection of the technical standards, implementation conventions, standards options, rules, and criteria organized into profile(s) that govern systems and system elements for a given architecture. ” [DoDAF, v.10, Vol. II]
“There are some overarching aspects of an architecture that relate to all three views. These overarching aspects are captured in the All-Views (AV) products. The AV products provide information pertinent to the entire architecture but do not represent a distinct view of the architecture. AV products set the scope and context of the architecture. The scope includes the subject area and time frame for the architecture. The setting in which the architecture exists comprises the interrelated conditions that compose the context for the architecture. These conditions include doctrine; tactics, techniques, and procedures; relevant goals and vision statements; concepts of operations (CONOPS); scenarios; and environmental conditions.” [DoDAF, v.10, Vol. II]
MagicDraw UML offers full support of all DoDAF products. It is easy to create integrated DoDAF products and maintain their inter-relationships. MagicDraw will create integrated architecture [DoDAF, v1.0, Desktop, page 2-1], supporting all types of relationships between elements in separate products or views. Modification of the model will result in the automatic updates of the referenced elements.
There are 4 major DoDAF product types distinguished in MagicDraw:
UML based
diagrams. User is provided with a set of UML and SysML diagrams
extended to meet DoDAF products. Diagrams will be equipped with DoDAF
specific diagram toolbar for the usability sake.
Any regular UML, SysML, or BPMN diagram can also be added to the DoDAF
project as any DoDAF product.
Dependency matrixes*. Read-only tables with model elements as columns and rows showing if there is a relationship between them. A dependency matrix is a view showing existing model information.
Tables*. A writable table made specifically to meet some DoDAF products, TV-1 for example. Modifying the table will change the related model element, so model integrity will be maintained.
Generated
documents (reports). MagicDraw will generate PDF or RTF
documents from the DoDAF model. Go to Tool->Report and pick the report
templates for the DoDAF products.
MagicDraw will have possibility to link any external document to the DoDAF model.
In order to meet specific DoDAF needs, a UML profile extending UML and SysML was created. The UML profile is explained in detail for every DoDAF product.
Notes
Only DoDAF specific properties will be listed in the detailed description.
All standard UML properties will accessible to the modeler, e.g. Name, Owner, etc.
The products of each of the views and their form in MagicDraw are listed below.
DoDAF Product |
Name |
Diagram (diagram type) |
Matrix |
Report |
Table |
AV-1 |
Overview and Summary Information |
- |
- |
Ö |
- |
AV-2 |
Integrated Dictionary |
- |
- |
Ö |
|
OV-1 |
High-Level Operational Concept Graphic |
UML Class |
- |
- |
- |
OV-2 |
Operational Node Connectivity Description |
UML Class UML Composite structure |
- |
- |
- |
OV-3 |
Operational Information Exchange Matrix |
- |
- |
Ö |
- |
OV-4 |
Organizational Relationships Chart |
UML Class |
- |
- |
- |
OV-5 |
Operational Activity Model |
UML Class UML Activity |
- |
- |
- |
OV-6a |
Operational Rules Model |
- |
- |
Ö |
- |
OV-6b |
Operational State Transition Description |
UML State Machine |
- |
- |
- |
OV-6c |
Operational Event-Trace Description |
UML Sequence |
- |
- |
- |
OV-7 |
Logical Data Model |
UML Class |
- |
- |
- |
SV-1 |
Systems Interface Description |
UML Class UML Composite structure |
- |
- |
- |
SV-2 |
Systems Communications Description |
UML Class UML Composite structure |
- |
- |
- |
SV-3 |
Systems-Systems Matrix |
- |
Ö |
- |
- |
SV-4 |
Systems Functionality Description |
UML Class UML Activity |
- |
- |
- |
SV-5 |
Operational Activity to Systems Function Traceability Matrix |
- |
Ö |
- |
- |
SV-6 |
Systems Data Exchange Matrix |
- |
- |
Ö |
- |
SV-7 |
Systems Performance Parameters Matrix |
- |
- |
- |
Ö |
SV-8 |
Systems Evolution Description |
UML State Machine |
- |
- |
- |
SV-9 |
Systems Technology Forecast |
- |
- |
- |
Ö |
SV-10a |
Systems Rules Model |
- |
- |
Ö |
- |
SV-10b |
Systems State Transition Description |
UML State Machine |
- |
- |
- |
SV-10c |
Systems Event-Trace Description |
UML Sequence |
- |
- |
- |
SV-11 |
Physical Schema |
UML Class |
- |
- |
- |
TV-1 |
Technical Standards Profile |
- |
- |
- |
Ö |
TV-2 |
Technical Standards Forecast |
- |
- |
- |
Ö |
Figure 2 Product taxonomy