Duplicating a Specification

You can duplicate the complete or partial structure of a selected requirement specification.

Required responsibilities:

  • Baseline: Leader (when the object is in the Frozen state) or Author


Before you begin: View the list of requirement specifications. See Requirement Specifications Page.
  1. Select the requirement specification that you want to duplicate.
  2. From the toolbar, select Actions > Duplicate .
    The Duplicate Requirement Specification - Options dialog box opens.
  3. In the Copy or Reference field, select the scope of the other specification's structure that you want to duplicate:
    • Select Complete Structure from another Requirement Specification to duplicate the complete specification structure.
    • Select Partial Structure from another Requirement Specification to specify which parts of the specification's structure (chapters, requirements, and so on) you want to duplicate.
  4. In the Copy with link field, select Create clone relation if you want to create a cloned relationship link to objects copied from the other specification's structure.
  5. For each type of specification object, specify how to import them into the target specification:

    OptionMeaning
    DuplicateThis type of object will be duplicated in the specification structure. It will have a new name.
    ReferenceThis type of object will be referenced in the specification structure. it will have the same name.
    NoneThis type of object will not be imported into the specification structure.

    If you choose to duplicate, the types, policies, and vault of the copied objects will be the same as the original object. Each of the duplicated object's state will be its first state in the policy as if it were a new object.

  6. For copied objects, type the Prefix for Copied Objects or select AutoName.

    A prefix is required for copied objects to ensure all objects in the database have a unique name. The default value is "Copy of". If you do not select Autoname, the app will assign the prefix repeatedly until any name collision is resolved. If the name collision cannot be resolved using the prefix, when the maximum length of 128 bytes is reached, autonaming will be used to create a copy of the object to be imported to avoid extremely long names.

  7. Click OK.
    The duplicate specification is listed on the Requirement Specifications page.