About Revision

You can revise Traceable Requirements Management objects outside of the context of other objects in three ways—1) from the top of a specification, specifications folder, or requirements structure, 2) from a list of that type of object (specifications and requirements) or 3) from the object's Revisions page.

You can revise any object at the top of a structure using the Revision command. You can also revise an object in a list of that type of object (such as on the Requirement Specifications and Requirements pages) using the Revision command. You can revise any object, other than a specification, from its Revisions page using the Create Revision command. You can revise a specification without its files or revise a specification and upload all of the files to the new revision on its Revisions page using the Revise and Revise With Files commands, respectively.

When you revise an object at the top level of a structure, from a list, or outside of any other context, there is no change in the object's relationship to other objects after revision. You have created a new revision with all of the existing parent and child relationships that the previous revision of the object had.

You can revise all Traceable Requirements Management objects in the context of a structure, including requirements and specifications that are not at the top level of the structure, using the Replace By New Revision and Replace By Last Revision commands.

When you use the Replace by New Revision command to revise the latest revision of an object, the new revision is added to the structure in place of the previous revision.

If a newer revision of an object exists ( appears in the Revisions column), when you use the Replace By Last Revision command to revise a previous revision of the object, the latest revision of the object is added to the structure in place of the previous revision.

When you revise an object in a context of a structure, the revised object (revision B) maintains its child relationship to its parent object in the structure, whereas the previous revision (revision A) is no longer associated with the parent object and is no longer in the structure. The previous revision of the object (revision A) maintains its child relationship to any other parent objects in any other contexts, such as in other specification structures. Both revisions (revision A and revision B) maintain all of the same parent relationships to their child objects in all contexts after revision.