Creating Requirements

There are four steps necessary to create a requirement:

  • Create a requirement
  • Define the requirement information
  • Define the requirement attribute values
  • Assign responsible users
Note: In addition, you can link reference documents, create traceability links, and define the validation procedure.
Note: You can create requirements in the scenario and simulations integrated from Caliber Visualize. However, in Visualizations, they will appear as notes.
CAUTION:
Security is enforced while creating a new requirement, so you are not able to modify fields that your security profile does not allow. Only fields that are enabled are available for you to change.

To create a requirement

  1. Click Home.
  2. Click Create Requirement.

    This creates a new requirement in the requirement tree.

    1. Insert Above: Creates a new requirement at the same hierarchical level and before the currently selected requirement.
    2. Insert Below: Creates a new requirement at the same hierarchical level and after the currently selected requirement.
    3. Drag-and-Drop New Requirement: Creates a new requirement anywhere in the tree (that you have permission to create requirements) by allowing you to “drop” the requirement in place.
    Note: The Above and Below options are disabled when you create a requirement starting from a requirement type in the tree.
    Note: When creating a new requirement, the view does not shift from the current tab.
  3. Define the requirement information as described below.
  4. Define the requirement attribute values. See Related Procedures below for details.
  5. Assign responsible users as described below.
  6. Save the requirement by selecting Requirement > Save Changes from the menu.
    Note: The first time you save a requirement, that requirement is entered into the Caliber database and a creation entry (Rev. 1.0) is made in the change history record. Each time you change a requirement and save it, you may be prompted to enter a comment about the change. The change and the comment are entered in the change history record. See Related Procedures below for details.
    Tip: To avoid unwanted change history data, fully define the requirement before saving it. You can turn the Comment dialog window on or off through the Options dialog window.