Requirement Properties

You can modify an object's properties from its property sheet. To open a requirement property sheet, double-click its Browser entry in the Requirements folder.

The General tab contains the following properties:

Property

Description

Parent

[read-only] Displays the name of the parent requirement. For top-level requirements this is the model name.

Title ID

[read-only] Displays the number expressing the place of the requirement in the requirements hierarchy. For example: 1.3.2.

Title

Specifies the name of the requirement.

Code

Generates a unique code for the requirement. You can override an individual requirement code by typing in the Code field. You can also modify the template used to generate the codes (see Customizing Requirement Codes).

Description

Specifies a detailed description of the requirement. This field is also available on (and synchronized with) the Notes tab.

The Detail tab contains the following properties:

Property

Description

Comment

Provides space for any comment on the requirement.

Stereotype

Specifies a sub-classification used to extend the semantics of an object without changing its structure. It can be predefined or user-defined

Type

Specifies the type of requirement, as viewed from the process point of view. You can specify your own types (see Customizing a List of Values).

Status

Specifies the present validation status for the requirement. You can specify your own status levels (see Customizing a List of Values).

Priority

Specifies the priority level attached to the requirement. Select a value in the list or type a value. The value cannot be null or negative, and is limited to one decimal (for example: 1.9).

Selected

Specifies that the requirement has been selected to be implemented in the project. If this checkbox is cleared, the requirement is excluded from the project and the sum of workloads.

Risk

Specifies the level of risk associated with implementing the requirement. You can specify your own risk levels (see Customizing a List of Values).

Verification

Specifies the type of testing to be applied to the development of the requirement. You can specify your own verification types (see Customizing a List of Values).

Workload 1-4

Specifies the workloads assigned to four individuals or groups (see Assigning Workloads). Workflows for requirements with sub-requirements are read-only fields calculated as the sums of all sub-requirement workloads.

The following tabs are also available: