Understand Documentation-Graph Catalog
scitools.com

← Graph catalog

Dependencies is one of the interactive graphs Understand can draw of your code — call trees, dependencies, control flow, and more.

Open a graph · Which graph should I use?

Dependencies

Languages: Any
Targets: Architectures
Variants: Butterfly, Depended On By, Depends On, Internal

Show dependencies for the selected architecture.

Dependencies map references to their owning file, class, or architecture. So a file's dependencies are the other files that own entities it references. For example, if a function defined in fileA calls a function defined in fileB, then fileA depends on fileB. References that contribute to dependencies vary by language, but generally include call, set, use, modify, and type references.

Dependencies always stay at the same grouping: file will only depend on other files, classes on other classes, and architectures on other architectures within the same root architecture.

See File Dependencies for an alternate view of architecture dependencies.

Dependencies - Butterfly

The Butterfly variant shows both directions, architectures the selected architecture depends on and is depended on by.

The sample project below is split into three architectures:

See Graph Architecture for a graphical view of the architecture organization.

Rooted at api, the graph shows that api is depended on by ui through 22 references, and depends on lib through 27 references. In the GUI, architectures can be expanded to show the entities for each reference, and edges can be right clicked to directly view the references.


Back to Dependencies

Dependencies - Depended On By

The Depended On By variant shows architectures the selected architecture is depended on by.

The sample project below is split into three architectures:

See Graph Architecture for a graphical view of the architecture organization.

Rooted at api, the graph shows that api is depended on by ui through 22 references. In the GUI, architectures can be expanded to show the entities for each reference, and edges can be right clicked to directly view the references.


Back to Dependencies

Dependencies - Depends On

The Depends On variant shows architectures the selected architecture depends on.

The sample project below is split into three architectures:

See Graph Architecture for a graphical view of the architecture organization.

Rooted at api, the graph shows that api depends on lib through 27 references. In the GUI, architectures can be expanded to show the entities for each reference, and edges can be right clicked to directly view the references.


Back to Dependencies

Dependencies - Internal

The Internal variant shows dependencies between the architecture's contents, both entities directly in the architecture and any nested architectures.

The sample project below is split into three architectures:

See Graph Architecture for a graphical view of the architecture organization.

Rooted at api, the graph shows dependencies between the files in the folder. If api contained folders, those would be shown too. In the GUI, architectures can be expanded to show the entities for each reference, and edges can be right clicked to directly view the references.


Back to Dependencies