Architecting and designing : MODAF : Creating Operational View products : Creating OV-5 activity models : Modeling OV-5 diagrams with IDEF : Creating and developing OV-5 child diagrams : Attaching ICOM arrows to child diagrams
  
Attaching ICOM arrows to child diagrams
When you create a child OV-5 diagram, untunneled ICOM arrows of the parent diagram are carried over to the new diagram. You must then attach the arrows to operational activities.
To attach a parent arrow to an activity, select the parent arrow; drag the line to the activity at which you want the line to end.
Note Deleting an arrow from a child diagram does not delete it from the parent activity. The arrow on the Parent will be tunneled the next time the parent diagram is opened.
An OV-5 diagram can have more than one of each type of ICOM arrow. Any output arrow can provide input, control, or mechanism data to one or more boxes. The child diagram also shows the constraining relationship of arrows, that is, a function that receives input or control from a previous function is constrained by that previous function.
An unconnected end of an arrow, in a child diagram, must have the ICOM code to specify its connection to the parent diagram or it must be tunneled.
See also
Creating and developing OV-5 child diagrams