In the DesignSync environment, object versions have fixed names that can map to model version revision names in the Defect Management and Collaboration environment. DesignSync versions can also have tags, which can be moved from one version to another. For example, version 1.4.1.2 of an object can be tagged Gold to indicate that this is currently the best version. At a later point in the development cyle, this tag may be moved to a more recent version, for example 1.5, to indicate that a new best (Gold) version is available. In Defect Management, you can also add tags to a model version revision, then move these tags between model version revisions to dynamically manage the model version hierarchy. If you move a tag from one revision of a model version revision to another and that tag is being used as part of a model version hierarchy definition, then the model version hierarchy itself automatically updates to include the model version revision now associated with the tag because tags are resolved during hierarchical operations to determine model version hierarchies. For example, if CHIP revision 1.4 has a hierarchical reference to ALU revision 1.6, which currently has the tag Gold, the Gold tag resolves to ALU revision 1.6 during hierarchical operations. Since the Gold tag currently resolves to model version revision 1.6, ALU revision 1.6 is currently included in the CHIP model version hierarchy. If the Gold tag were subsequently moved to ALU revision 1.8, subsequent hierarchical operations would resolve the Gold tag to ALU revision 1.8, which would then be included in the CHIP model version hierarchy instead of ALU revision 1.6. | |||||||||||