Overview

Each FSW package has a file ("cmt/requirements") that contains lines of the form "use <package>". CMT and CMX use these files to control (recursively) which packages a given package can access.

The FSW Document Mechanization system harvests these files each morning, then uses the information to generate diagrams called "use" trees. Actually, the phrase is a bit misleading; the diagrams are Directed Acyclic Graphs (DAGs), rather than simple hierarchies.

In any case, the diagram allows the user to see the "use" relationships in a set of packages, click on a node to go to a package page, etc. "use" trees appear in several formats and locations:

• Global

  This page shows most FSW packages, excluding only some commonly used packages (e.g., CMX, ITC, MSG, PBI, PBS, VXW) that are part of the FSW infrastructure. In an alternate version, nodes are colored to indicate their Projects. Both pages include a Legend, giving descriptions and other information on each FSW package.

  Showing the manner in which the FSW development effort is coming together, there is a set of QuickTime animations (fast, medium, and slow), based on the colored "use" tree diagram. The Package Version Timelines show another view of FSW progress.

• ISIS

  Although the ISIS software borrows heavily from the mainline FSW code base, it differs in many respects. This page eliminates packages which are not used by ISIS.

• Package-specific (e.g., FILE) Most package pages include a package-specific "use" tree, depicting the package and all of its direct ancestors and descendents.

• Project-specific (e.g., SVC) Most project pages include a project-specific "use" tree, depicting the packages in the project and all of their direct ancestors and descendents.

• Task-specific (e.g., Configuration, Housekeeping, Instrument Physics)

  These pages eliminate packages which are not used in flight, highlighting items which are of particular relevance to the task in question.