As for all other diagram types, you can create Constraint diagrams which provide a high-level or overview perspective, and then magnify that perspective by creating child constraint diagrams from the symbols you have used. The diagram in which the symbol is contained becomes the parent diagram.

This process is called decomposition, and the resulting child constraint diagrams are also called decomposition diagrams. Decomposition is the dividing of a modeled function into component functions. In OV-5, you decompose Operational Activities on Activity Model diagrams with Activity Model child diagrams. When you do this, you create a constraint or decomposition diagram.

The three Balance commands (Reports menu: Balance Parent, Balance Child(ren), and Balance Horizontal) invoke the System Architect balancing algorithms. System Architect checks Balance violations, as well as rule violations that prevent proper balancing, during execution of these commands. The diagram being checked is annotated with error indicators. Multiple errors are indicated with an asterisk. The Clear Errors command removes the error indicators from the diagram after you are done inspecting them.

The Balance Child(ren) command balances the child diagrams of any parent processes selected in the currently displayed diagram. Click to select the process, and then click Reports > Balance Child(ren).

When you decompose a single function on an Constraint diagram with a child Constraint diagram, you model the major subfunctions on the child diagram. To show increasing detail, you can create child diagrams for the subfunctions on the child diagram, and so on. You should keep the overall scope of each child diagram in the scope of the parent Operational activities at all times.