Creating requirements

You can use Rational® Quality Manager to create new requirements. Afterwards, you can add those requirements to a test plan.

About this task

To create new requirements:

Procedure

  1. Point to the Requirements (Requirements) icon, and click Create Requirement.

    This opens the Overview page of the Requirement work item editor.

    Restriction: The Requirement work item editor includes a button for moving or copying the requirement work item to another project area. This feature is not currently supported. Instead, you can use the Duplicate button while viewing a list of requirements.
  2. Complete the Overview page as needed. Your team might decide to complete only some of these fields.
    1. In the Summary field, type a statement that clearly summarizes the meaning of the requirement.
    2. In the Owned By field, select a user to own the requirement.

      The requirement owner will receive a notification in the My Tasks viewlet on his or her dashboard.

    3. In the Risk Assessment field, select the risk level of the requirement, ranging from Very Low to Very High.
    4. In the Severity field, select the severity level of the requirement, ranging from Minor to Blocker.

      Typically, Severity is a measurement of how important the requirement is to the originator of the requirement.

    5. In the Requirement Priority field, type a value for how important you consider the requirement to be.

      For example, even though the originator might consider the requirement to be of major importance, you might think differently when you compare this requirement to others. Your team might use priorities such as Must Have, Normal, and Minor. Priority is helpful when the team needs to decide which features must be cut from the release.

    6. In the Review Status field, type a value for the status of the requirement.

      For example, this field is often used to specify whether the requirement has been fully defined and whether it has been reviewed or approved. Typical values might include Draft, Under Review, Approved, Reviewed, or Draft.

    7. In the Tags field, type one or several tags that you can use to group or classify the requirement.

      For example, you can use tags such as performance, usability, accessibility, customer-must-have, and so on. You can also use tags as a filtering mechanism when viewing requirements in the View Builder.

    8. In the Description field, describe the requirement in as much detail as necessary.
    9. Afterwards, the entire team can add comments in the Discussion field.
  3. Complete the Links page as needed.
    1. To notify others about the requirement, click Links, and add other users as subscribers.
    2. In Attachments, click Add File, and attach a file to the requirement.
  4. Click Approvals to set up an approval process for the requirement.
  5. Click History to view the history the requirement.
  6. Click Save to save the requirement.
  7. Click Back to in the upper-left corner of the window to return to the Dashboard.

Feedback