DoD Architecture Framework Version 1.0, Volume 2 - AcqNotes.com

• SYSTEM Identifier in ACTIVITY-MODEL-INFORMATION-ELEMENT-ROLE-MECHANISM-SYSTEM (a subtype of ACTIVITY-MODEL-INFORMATION-ELEMENT-ROLE-MECHANISM)• FACILITY Identifier in ACTIVITY-MODEL-INFORMATION-ELEMENT-ROLE-MECHANISM-FACILITY (a subtype of ACTIVITY-MODEL-INFORMATION-ELEMENT-ROLE-MECHANISM)• FACILITY-TYPE Identifier in ACTIVITY-MODEL-INFORMATION-ELEMENT-ROLE-MECHANISM-FACILITY (a subtype of ACTIVITY-MODEL-INFORMATION-ELEMENT-ROLE-MECHANISM)It is optional to incorporate some or all of the details of an activity model into a CADMstructureddatabase. At a minimum, both INFORMATION-ELEMENT and PROCESS-ACTIVITYshould be populated, so that the information flows and operational activities required for OV-3and SV-5, respectively, are available for cross reference. Because system functions are specifiedby use of SYSTEM -FUNCTION, a subtype of PROCESS-ACTIVITY, the entity PROCESS-ACTIVITY-ASSOCIATION is used to record the cross reference of SYSTEM -FUNCTION instances to otherinstances of PROCESS-ACTIVITY.A key element of operational requirement traceability is the relation of instances ofPROCESS-ACTIVITY to TASK instances such as those included in the UJTL [CJCSM 3500.04C,2002], the UJTL extensions for tactical tasks, and mission essential tasks. This traceability isprovided by populating PROCESS-ACTIVITY-TASK.Documents cited for details of an ACTIVITY-MODEL (or other subtypes of INFORMATION-ASSET) are stored as instances of INFORMATION-ASSET-DOCUMENT.Expanding on the core entities shown in Figure 4-18, Figure 4-19 provides a high-leveldiagram from the CADM showing key entities that are used to store architecture data for OV-5in a CADM-conformant database.4-41