The Activity Model describes the appropriate activities connected with the architecture, the data and/or information exchanged between activities, and the data and/or information exchanged with other activities that are outside the scope of the model, such as external exchanges.
The Activity Model is created by using the Integrated Computer-Aided Manufacturing (ICAM) DEFinition (IDEF) for Function Modeling (IDEF0) diagram.
The IDEF0 diagram is renamed in System Architect DoDAF support to the OV-5 Activity Model diagram (also referred to here as simply an OV-5 diagram). It reports to a model that is called an IDEF0 model (it has not been renamed).
The IDEF0 method used for OV-5
The IDEF0 method is designed to explain what happens in a business or specific activity area. Each activity is represented by a single box called an Operational Activity, with ICOM (Input, Control, Output, and Mechanism) arrows drawn into and out of the box. The ICOM arrows are identified by which part of the Operational Activity they flow in or out of. An ICOM arrow drawn into the left side of an Operational Activity box is an input, an ICOM arrow drawn into the top of a box is a control, an ICOM arrow drawn into the bottom of a box is a mechanism, and an ICOM arrow drawn out of a box is an output.
Working with models
The model is a grouping mechanism for OV-5 diagrams. You specify properties such as model viewpoint, purpose, and description for the model.
OV-5 Context diagrams
Every OV-5 Context Diagram must be associated with a model. System Architect forces you to define a Model Name for the diagram when you create it. This is in keeping with the IDEF0 specification.
A Context or A-O diagram is always the highest-level representation in the model and contains only one activity. It is included in every IDEF0 model. OV-5 modelers begin with the Context or A-0 diagram and then drill down into more detailed views of their enterprise. This diagram becomes the parent of the other OV-5 diagrams.