Architecting and designing > DoDAF > DoDAF 1.5 Activity Based Methodology (ABM) > Developing operational views with DoDAF ABM > ABM syntax rules > Decomposing OV-5 input and output flows (branching and joining)
  
Decomposing OV-5 input and output flows (branching and joining)
Like activities that are decomposed into child sub-activities and nodes that are decomposed into sub-Nodes, input/output information flows are decomposed into their component information subparts. At higher levels of an activity model, an input/output information flow can be considered as a “bundle” or “pipeline” while at the lower levels the inputs/outputs consists of the “bundled/pipelined” component information parts. This bundled or pipelined information flow is usually graphically depicted as “branches/joins”.
For example, Intel Data could be made up of Target Data, Weather Data, and Unit Locations:
This graphic is described in the surrounding text.
One way of decomposing input/output information flow would be as shown below:
This graphic is described in the surrounding text.
Another approach would be to think of Intel Data as a pipeline between two parent activities that gets decomposed at lower levels as shown below:
This graphic is described in the surrounding text.
See also
ABM syntax rules