Answer:
Hierarchy Diagram Flow Diagram
The hierarchy diagram represents the relationships between several layers of elements. There is no pre-defined semantic for a hierarchy, allowing the user to define the specific set of relationships to deliver the desired representation and insight in a traditional representation. Sample uses include functional, physical, and traceability hierarchy views. Part of the general representation set, hierarchy diagrams are available for all elements.
A hierarchy diagram is opened on the combination of an element and a hierarchy definition. The element defines the starting point for the diagram. The hierarchy definition specifies the relations (and optionally target classes) to traverse when building the hierarchy diagram. In building the diagram, CORE starts with the top-level element and checks to see if any of the specified relationships have targets of the specified target classes. If so, these targets become children of the top-level element and are displayed on the second level of the diagram. The children of the elements on the second level are then determined. This process continues until the lowest level elements have no targets in the specified set of relations. Individual elements are shown as nodes with the relationships between the elements shown as connecting lines.
