Defining Requirements

To define requirement information

  1. Select a requirement near where you want to create the new requirement and select the appropriate option for creating a requirement from the context menu (Child, Above or Below), or click the appropriate Create Requirement button.
  2. Click the Details tab.
  3. Enter a name for the requirement in the Name field .
    Note: A requirement name can consist of 128 characters.
  4. Select the appropriate Owner, Status, and Priority from their respective drop-down lists.
    Note: The default Owner is the user who created the requirement. You may assign the requirement to someone else, but you may not be able to modify it again after it is saved if you do not have security privileges to do so.
  5. Enter a description for the requirement in the Description field.

    For more information on formatting description text, see related procedures on “Formatting requirements” and “Formatting fonts”.

    Note: The requirement description is visible at all times, in a pane below the tabs, and allows you to adjust the size of the description window. The size of the description window on the Details tab is independent from all other tabs. To add a picture, OLE object, table, or hyperlink to the requirement description, select Insert > Picture/ Object/Table/Hyperlink from the menu. The JPG format is the recommended format for inserted pictures. To edit an object, right-click it and select Edit Object.
    Note: In Document Factory, objects are represented as pictures. Inserted objects may be inserted as icon (ex: JPG, GIF) or image of the object (BMP), consistent with Microsoft Word OLE behavior.
  6. Save the requirement by selecting Requirement > Save Changes from the menu. To delete the requirement, select Requirement > Cancel Changes from the menu.

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 information on “Requirement History” .

To avoid unwanted change history data, fully define the requirement before saving it. You can turn the Comment dialog box on or off through the Options dialog box.