View DNDAF:DNDCF Architecture Data Model
Introduction
...
Background
From Volume 3 of DND/CF Architecture Framework (DNDAF) Version 1.6:
The DND/CF Architecture Data Model (DADM) provides the logical basis for moving architectures from compendiums of documents, spreadsheets, and graphics to architecture data that can be stored in architecture data repositories and manipulated with automated tools. Multiple commercial tools may be used to manipulate the architecture data and generate architecture descriptions and products. The DADM establishes the conditions for a data-centric enterprise architecture that is executable and actionable.
The DADM therefore makes it possible to store architecture descriptions (models) in a way that can be manipulated using software tools.
The DND/CF Architecture Framework (DNDAF) provides guidance on producing views and architecture descriptions via a set of sub-views. The resulting products are visual and textual representations of an architecture consisting of sets of data entities. Because a given architecture data entity frequently occurs in more than one sub-view, each architecture must be built on a set of common architecture data entity definitions, otherwise data entered in support of one sub-view will not be accessible in another. The DADM template for each sub-view provides definitions of the entities and attributes, i.e., the architecture data that are updated in the creation of the information content of each sub-view. The attribute definitions provide added detail about the data characteristics.
The architecture data entities are defined in the DADM and provide the structure for storing data about a given architecture that will be captured in the sub-views and stored in an integrated repository. The DADM forms the underlying schema for the repository by defining the entities, the relationships between the entities and the attributes of the entities.
...
The DNDAF subviews therefore populate the underlying data model and each of the DNDAF subviews defines which DADM entities it creates.
The DADM
The DADM (Figure 4.2 of Volume 3 of DND/CF Architecture Framework (DNDAF) Version 1.6) is represented as an entity-relationship diagram. It consists of
218 entities and 1691 attributes that describe the information needed to describe the DND/CF Enterprise Architecture. Of the entities, 174 are used to support the DNDAF version 1.6. The remainder will be used in future releases of the DNDAF.
Other Frameworks
Although each of the frameworks discussed on this site has a standardised set of elements underlying each of the architecture views there is a difference in purpose and emphasis.
The DADM is most like the Core Architecture Data Model (CADM) underlying DODAF 1.5 which has since been replaced in DODAF 2 by the DODAF Metamodel (DM2). Both are represented by entity-relationship diagrams and in both the emphasis is on using the views to populate the data model.
- DODAF 2 Metamodel (DM2)
- MODAF Metamodel (M3)
- NATO Architecture Framework Metamodel (NMM)
- TRAK Metamodel
There is also a comparison of the architecture frameworks which looks at more than just the underlying data model / metamodel..
References
- DND/CF Architecture Framework (DNDAF) Version 1.6, Volume 3: DND/CF Architecture Data Model (DADM) https://www.img.forces.gc.ca/pub/af-ca/vol-03/index-eng.asp