The analysis dependencies can be easily viewed by clicking the Details
display tab at the bottom of the file list window for a file or analysis, then expanding the
Dependencies section. For example, consider a flow analysis that has a
geometry file (wing.sat) as an input. The geometry file has a manually
specified upstream dependency to the original CAD geometry from which it was created
(wing-original.sat). The following image shows the dependency diagram of
the analysis.

In the diagram, the current object being viewed (Flow Analysis in this
case) is shown in a white box and the upstream and downstream dependencies are shown in shaded
ovals. The objects to the left of the current object are the upstream dependencies and the
objects to the right are downstream dependencies. If any object is a stored version, its version
number will be displayed next to its name (for example wing.sat [1.3]). To
view the full path to the object, simply hover over its diagram node with your mouse. You can
click on the diagram node to go directly to that object.
All levels of upstream dependencies are shown in the diagram, but only the first level of downstream dependencies is displayed. The reason for this is twofold. First, you need to look at all of the upstream dependencies to determine whether the current object is out-of-date or not. Second, an object will typically have a small number of upstream dependencies that can be shown easily in a diagram. However, it is possible for an object to have numerous downstream dependencies which may in turn have numerous downstream dependencies of their own. Therefore, if all levels of downstream dependencies are visible, it may make the diagram too large and unwieldy to display it given the constraints of the window.
In the example provided above, the diagram and table show that the Flow Analysis object is
dependent on version 1.3 of wing.sat, which is dependent on version 1.2 of
wing-original.sat. The analysis also has two outputs (downstream
dependencies): airfoil-2.cas and airfoil-2.dat.
If a new version of wing-original.sat is created (version 1.3), and
that version contains changes, the file's diagram node is marked with an asterisk (*), and its
status in the table becomes New version exists. All other boxes are marked
with an 'attention required' icon
and their status is reported as Out of date. This helps
you easily verify which files have changed, and which ones need updating.

To update the analysis, there are two things you need to do:
Update wing.sat. To do this, you can create a new version of
wing.sat using the latest version of
wing-original.sat and update the upstream dependency of
wing.sat to point to the latest version of
wing-original.sat. As an example, suppose the new version of
wing.sat is 1.4.
Re-execute the Flow Analysis using the latest version of
wing.sat.
Once you have performed these steps, the dependency table will look like this:
