< Previous | Next >

Lesson 2: Manage requirements related to the test plan

In this lesson, you learn about a new requirement that must be covered and you add it to the requirement collection. Also, a requirement is determined to be out of scope, so it is removed from the collection.

Before you begin

About this task

The test plan is the focal point for all testing activities for a particular test cycle; the plan can contain multiple test cases that describe the scenarios that you are going to test. Requirements help you to ensure lifecycle traceability because you can link the test cases with requirements in the test plan. Creating a link to the requirement from the test plan also creates a back link to the test plan in the Requirements Management application.


Log in as the product owner for the JKE solution, Ursula (Userid: ursula, Password: ursula) when prompted with the login dialog box. If you are prompted with a project login dialog box, select the JKE Banking (Requirements Management) project. The quality dashboard opens.

Add a new requirement

You recently learned that a requirement must be added to the release, so you will add the new requirement to the Release 1 Planning requirements collection.

About this task

A requirements collection is a high-level group of requirements that are targeted for a software release. Requirements and requirement collections are managed in the Requirements Management application. One quick way to access requirements from the Quality Management application is by opening a test plan that is associated with a requirements collection.


  1. Open the Development Test test plan by clicking Planning > Browse Test Plans. From the list of test plans, click Development Test in the Name column. The test plan opens in the test plan editor.
  2. Click Requirement Collection Links in the test plan table of contents.
  3. Click the Release 1 Planning link to open the requirement collection.
  4. When the requirement collection opens in the Requirements Management application, click the down arrow on the Add Artifact button; then click Feature.
    Adding new requirements
  5. In the Create Artifact window, type the following information:
    1. In Initial content field, type Add new functionality to allow users to allocate funds across multiple organizations.
    2. In the Name field, type (QM Tutorial) Donor can choose to support multiple organizations.
    3. Click the Add Tags button, click Core Functionality, and then click OK.
    4. Click OK.
      Creating an artifact
    The new requirement is created and is part of the Release 1 Planning requirement collection, which is linked to the test plan.
  6. Click Save to save the update to the requirements collection.

Remove a requirement from plan

During a planning review, project management has determined that a requirement is out of scope for this release. Ursula removes the requirement from the collection.


  1. While browsing the Release 1 Planning collection, find Donors Deposit Money in a Pooled Assistance Fund.
  2. In the requirement row, click the Action menu, select Remove Artifact, and then click Yes.
  3. Click Save.
  4. To return to the Quality Management application, open the Home menu and click Quality Management > JKE Banking (Quality Management).

    Home menu

  5. Log out as Ursula.

Lesson checkpoint

In this lesson, you learned the following:
  • How to navigate from a test plan to a requirement collection in the Requirements Management application.
  • How to add and remove requirements from a collection.
< Previous | Next >

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki