Section: Purpose and Context Primary Use Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Primary Use The intended primary use of the architecture (when not included as part of description) Recommended Mission Name Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Mission Name (when not included as part of description) Recommended Concept of Operations Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Concept of Operations Name of CONOP document Recommended IA Requirement Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Info Assurance (IA) Requirement Textual description of the IA requirement Required (if applicable) Related Architecture(s) Names of related architecture(s) Required (if applicable) Section: Findings and Recommendations Issue(s) Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Issue(s) Textual description of issues relevant to doctrine, organization, training, materiel, leadership and education, personnel, and facilities (rationale: maintain DOTMLPF as prescribed in JP1-02) and/or the Warfighter Conclusion(s) Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable)
Conclusion(s) Textual description of issues relevant to doctrine, organization, training, materiel, leadership and education, personnel, and facilities (rationale: maintain DOTMLPF as prescribed in JP1-02) and/or the Warfighter Recommendation(s) Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Recommendation(s) Textual description of issues relevant to doctrine, organization, training, materiel, leadership and education, personnel, and facilities (rationale: maintain DOTMLPF as prescribed in JP1-02) and/or the Warfighter Constraint(s) Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Constraint(s) Textual description of issues relevant to doctrine, organization, training, materiel, leadership and education, personnel, and facilities (rationale: maintain DOTMLPF as prescribed in JP1-02) and/or the Warfighter Vulnerability(ies) Security Classification Marking IAW this appendix, Paragraph 2. and Reference XX Required (if Applicable) Vulnerability(ies) Textual description of issues relevant to doctrine, organization, training, materiel, leadership and education, personnel, and facilities (rationale: maintain DOTMLPF as prescribed in JP1-02) and/or the Warfighter Table - AV-1 Data Fields Integrated Dictionary (AV-2). The AV-2 presents all the metadata used in architecture. The AV-2 enables the set of architecture models to stand alone, allowing them to be read and understood with minimal reference to outside resources. It provides the metadata for the entire architecture. A simple "dictionary of terms" is not sufficient to meet the AV-2 requirements. () . AV-2 Structure: Tabular. The AV-2 presents all the data in the architecture as a hierarchy along with a text definition and its authoritative
Data Field Data field definition Recommend / Required Product Name Matches the name on the Products tab Required Service List Number Hierarchy number of the Service. This number should match any numbering on the Service Views Recommended Service Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Service Name Name of the Service. This name should match any numbering on the Service Views Required Capability List Number Hierarchy number of the capability. This number matches the CV-2 Recommended Capability Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Capability Name Matches the name on the CV-2 tab Required Service to Capability Relationship Type Name Security Classification markings IAW this appendix, Paragraph 2. and Reference XX Required (If Applicable) Service to Capability Relationship Type Name Name of the type of relationship between the Service and Capability. Provides context to the relationship. Recommended Table - CV-7 Data Fields
Product: DIV-3 Data Field Data field definition Recommended / Required Product Name Matches the name on the Products tab Required Parent Data Object Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Parent Data Object Name Matches the name on the DIV-1 and DIV-3 tab Required Data Object Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Data Object Name Matches the name on the DIV-1 and DIV-3 tab Required Data Object Attribute Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Data Object Attribute Data Field names assigned to the Entity Required Data Object Attribute Format Format for the data field Required Data Object Relationship Type Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Data Object Relationship Type Name Name of the type of relationship between the entity objects. Provides context to the relationship. Required Table - DIV-3 Data Fields
ANNEX D TO APPENDIX C TO ENCLOSURE D WMA ARCHITECTURE DATA FORMATS AND STANDARDS OPERATIONAL VIEWS (OV) High Level Operational Concept Graphic (OV-1). The OV-1 provides a graphical depiction of what the architecture is about and an idea of the performers and operations involved. It is intended for presentation to high-level decision-makers. () OV-1 Structure: Graphical, Document. DoDAF does not endorse a specific data modeling methodology. There are no standard elements or conventions identified for the OV-1. However the title, purpose, and description of the model shall be included in its description. OV-1 Data Fields. Table XX shows the required and recommended data fields that architects submit as part of an OV-1. Product: OV-1 Data Field Data field definition Recommended / Required Product Name Matches the name on the Products tab Required Image Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Image Location File Location and Type Recommended Image Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Image Name Name or title of the graphic. May match the OV-1 title. Required Image Description Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Image Description Text description, typically a paragraph or two describing the CONOP depicted in the image. Required
Producing Activity Business process that triggers the resource flow from the performer Required Consuming Activity Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Activity Business process that receives the resource flow for the consuming performer Required Consuming Performer Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Performer Performer receiving the resource flow from the OV-2 Required Consuming Organization Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Organization Organization receiving the resource flow from the OV-2. (Optional) Recommended Resource Element Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Resource Element Name Name of the resource (information) element Required Resource Element Description Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Resource Element Description Longer text description of the resource (information) element. May include specific information fields or AS Recommended Measure Type Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required
Data Field Data field definition Recommended / Required Product Name Matches the name on the Products tab Required Sort Order A unique ID that sorts the events in a logical temporal sequence. Recommended Producing Performer Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Producing Performer Name Performer initiating the resource flow Required Producing Activity List Number Unique identifier for the activity from the OV-5a Recommended Producing Activity Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Producing Activity Name Matches the name on the OV-5A and B tab Required Information Element Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required (if applicable) Information Element Name Name of the information element passed between two performers. This element name should match the OV-3 and/or OV-5B Recommended Consuming Activity List Number Unique identifier for the activity from the OV-5a Recommended Consuming Activity Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Activity Name Matches the name on the OV-5A and B tab Required Consuming Performer Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Performer receiving the resource flow Required
Project Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Project Name Name of the project found in the AV-1 Required Capability List Number A unique number of the capability found from the CV-2 Recommended Capability Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Capability Name Name of the capability found from the CV-2 Required Table - PV-3 Data Dictionary Fields
System Event-Trace Description (SV-10c). The SV-10c provides a examination of the interactions between functional resources. Each event-trace diagram should have an accompanying description that defines the particular scenario or situation. The SV-10c is valuable for moving to the next level of detail from the initial solution design, to help define a sequence of functions and system data interfaces, and to ensure that each participating resource or System Port role has the necessary information it needs, at the right time, to perform its assigned functionality. Specific points in time can be identified. The Resource Flow from one resource/port to another can be labeled with events and their timing. The System Event-Trace Description provides a time-ordered examination of the Resource Flow elements exchanged between participating resources (external and internal) or system ports. Each Event/Trace diagram should have an accompanying description that defines the particular scenario or situation. SV-10c Structure: Various. DoDAF does not endorse a specific data modeling methodology. There are no standard elements or conventions identified for the SV-10c. SV-10c Data Fields. Table XX shows the required and recommended data fields that architects submit as part of a SV-10c. Product: SV-10c Data Field Data field definition Recommended / Required Product Name Matches the name on the Products tab Required Producing System Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Producing System Name Performer initiating the resource flow. Must match SV-1 Required Consuming System Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming System Name Performer receiving the resource flow. Must match SV-1 Required
Description May include AS. JCSF List Number The List Number of the JCSF that the system function maps to. Functions must be mapped to JCSFL. Recommended. (See Annex E) JCSF Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required JCSF Name Mapped JCSF name from the JCSFL Required The following additional properties are used for Sequence Flow of Service Functions Diagram Producing Service Function Name Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required (if applicable) Producing Service Function Name In sequencing the system functions, this is the function that initiates a data exchange Recommended Consuming Service Function Name Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required (if applicable) Consuming Service Function Name In sequencing the system functions, this is the function that receives a data exchange Recommended Data Element Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required (if applicable) Data Element Name The data exchange name Recommended System Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required (if applicable)
Service Name data exchange. Found from the SvcV-1 Producing Service Function Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Producing Service Function Name Name of the system function (action) that initiates the data exchange from the SvcV-4 Required Consuming System Function Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Service Function Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Service Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Consuming Service Name Name of the Service that houses the receiving system function. Found from the SvcV-1 Required Data Element Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Data Element Name Name, title, or primary key of the data element. This should relate to the DIV-1 models Required
Data Element Description Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Data Element Description Text description of the data element. Recommended Data Content Data fields from the DIV-2 or DIV-3. Required Data Content Security Classification Markings Classification of the Content of the data being transmitted IAW this appendix, Paragraph 2. and Reference XX Required Data Format Format of the message traffic moving from system function to system function. Examples include XML, ASCII, "Message Traffic" Required Data Standard The transmission standard for the data exchange. This should come from the StdV-1 Recommended Transaction Type Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Transaction Type Information about the nature of the transaction. E.g., Text, Data Required Triggering Event Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Triggering Event The operational activity that triggers this event. This data should come from the SV-5a. Required Measure Type Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required
Standard Name Security Classification Markings IAW this appendix, Paragraph 2. and Reference XX Required Standard Name Name of the Standard. Required Current DISR Standard Identifier Matches the unique ID for the standard as found on DISR Required (If available) Current DISR Standard Expiration Date MM/DD/YYYY that the DISR Standard expires Recommended Transition Start Date MM/DD/YYYY that the architecture project plans to begin transitioning to the new standard Required Transition End Date MM/DD/YYYY that the architecture project plans to complete transitioning to the new standard Required New DISR Standard Identifier Matches the unique ID for the standard as found on DISR Recommended New DISR Standard Start Date MM/DD/YYYY that the DISR Standard goes into effect. Recommended Table - StdV-2 Data Dictionary fields