Figure 3.4

Fix is that OV-2 is an essential product.

It was not shown correctly on page 55 of the book.

View Figure 3.4 online, and "right click" to download

CADM

CADM

CADM
The All-DoD Core Architecture Data Model (CADM) defines the entities and relationships for architecture data elements. The CADM was developed cooperatively by representatives from the Office of the Secretary of Defense, Combatant Commands, Military Services, and Defense Agencies as the DoD standard architecture data model for Framework-based architecture data elements. [All-CADM, 200 3a, b, c] The CADM is built using the Integrated Definition for Data Modeling, IDEF1X [FIPS 184, 1993] methodology, notation, and forms. More than 95 percent of the entities and attributes from the CADM are approved as DoD architecture data standards. Using relational technology labels, for example, the entities from the CADM provide specifications for tables in a database, and the CADM attributes provide specifications for the fields (data elements) in the rows of such tables.

DoDAF

DoDAF
The Department of Defense (DoD) Architecture Framework (DoDAF), Version 1.0, defines a common approach for DoD architecture description development, presentation, and integration for both warfighting operations and business operations and processes. The Framework is intended to ensure that architecture descriptions can be compared and related across organizational boundaries, including Joint and multinational boundaries.

Figure 4.8

click figure to enlarge

Figure 4.8
Figure 4.8 in the book is technically correct based upon information shown, but a reader has pointed out that a more likely scenario would be that the Department contains 1 or more Employees who's identity is unknown.  Therefore, the line should be dashed rather than solid.  Wizdom agrees.

Figure 8.14

click figure to enlarge

Figure 8.14

Figure 8.14 page 185.  The diagram was changed after a reader point out that there is a many-to-many relationship between a  MANDROID Line Item and ARMAMENT.  An entity called MANDROID-ARMAMENT LINE ITEM  was added that captures the detail of the armament placed on a given MANDROID.  It should be pointed out here, that the business rules of the organization would be written at the same time the diagram is being created.  As captured in the OV-6a, these business rules may say that something strange is indeed going on.

Figure 8.16

Figure 8.16

Figure 8.16 page 187 could also be redrawn with the argument that it too should include a few many-to-many relationships.  In fact, a physical schema will be very detailed and at this level should have all many-to-many relationships resolved and ultimately be in third normal form (3NF) - because it will be used in the actual implementation of the systems itself.  To allow the diagram to fit on the page and still make sense, Wizdom purposely did not resolve these many-to-many relationships.

Normalization and (3NF)
 

Normalization and (3NF)
 
Normalization is used in IDEF1X.  In relational database management, normalization breaks down data into record groups for efficient processing. There are six stages. By the third stage (third normal form or 3NF), data are identified only by the key field in their record. For example, ordering information is identified by order number, and customer information, by customer number. A major goal of normalization is to eliminate redundancy by having a data element represented in only one place.