Often the set of design states that can be defined for a given design is significantly larger than the number of state configurations actually needed to test the design (this is particularly true if design states have been generated automatically using the Auto-Create Design States operation).If these design states are inherited hierarchically, they will produce an unnecessarily large number of hierarchical states and output functions on the upper-level assembly (for a detailed discussion of this, see the topic "Output Functions and Hierarchical States"). It is important that the Analyst be able to reduce the number of inherited design states to the minimal set that achieves the diagnostic goals for the given design. This can be done by generating diagnostics using path-based tests defined for all possible design states.
This process can, of course, be desirable in and of itself—for certain types of designs, Analysts are often confronted with the need to determine the total number of design configurations that are needed to diagnose a system. Whereas this task can sometimes take weeks to accomplish using conventional methods, the diagnostics can often be used to solve this same problem in significantly less time.
How to Use Diagnostics to Minimize the Set of Design State Definitions
Review the generated test sequence and determine which design states are required by the tests that are utilized.
5
Either delete the superfluous (unused) design states or set their usage to "Unused".
6
Optional: For design states generated using the Auto-Create operation, rename the states to reflect the corresponding operational configuration. This will greatly improve "understandability" not only at this level of the design, but also at higher design levels.
