Defining quality objectives

About this task

During the planning process, the test team defines quality objectives. First, the test manager examines the predefined quality objectives in the project properties and evaluates whether they are suitable for the test team. Later, test leads implement the objectives in individual test plans, where the test team can track whether or not each objective has been met.

To define new objectives, you can open the Managing Quality Objectives editor from the Project Properties page or from an individual test plan. Any edits that you make are available to all test plans in the project area.

In the following example, you log in as Tammy, the test manager for the JKE Banking project, and review the project-level quality objectives.

Procedure

  1. Log in as the test manager by typing tammy for both the user ID and password. If you are prompted with a project login window, select the JKE Banking (Engineering Test Management) project. The quality dashboard opens.
    To modify and save project properties, a user must have the necessary permissions. This can be any one of the following:
    • A user granted permission to save and modify a project area in the process configuration.
    • A user who is an administrator of the project area.
    • A user who is granted either the JazzProjectAdmins or JazzAdmins repository group permissions.
  2. Click the Administration (Administration) icon in the banner and select Manage Project Properties. Then select Quality Objectives.
    The Manage Quality Objectives section of Project properties.

    Each quality objective includes a Name and Description, as well as a Condition and a Target.

  3. After reviewing the current project quality objectives, Tammy decides to modify the settings of some of the predefined quality objectives and also create some new, user-defined ones.

    For example, one of the predefined quality objectives states that the Percentage of Blocked Execution Records must be less than 10%. Tammy believes that the target should be less than 5%.

    1. In the Name column, find the row containing Percentage of Blocked Execution Records.
    2. In the Target column for that row, double-click the value 10.
    3. Specify a small target value by typing 5; then press Enter.
  4. Now, Tammy adds a new quality objective.
    1. Click the Add Row icon (Add table row).
      A blank row is added to the end of the table.
    2. In the Name column of the new row, type Number of Customer-Submitted Defects Open; in Description, type Objective stating that all customer-submitted defects must be closed.
    3. In Condition, choose =, and in Target, type 0.
    Remember: Both the predefined and user-defined quality objectives can be used in any test plan within that project area. However, only predefined quality objectives that are known by the application can be used in computations. User-defined quality objectives are informational only and do not contain computed values.
  5. Click Save.