Requirement Properties

Parent

Name of the parent requirement. For root requirements (directly linked to the Requirements folder), it is the requirements model name

Title ID

Read-only number expressing the place of the requirement in the requirements hierarchy. For example: 1.3.2

Title

Name of the requirement

Code

Code of the requirement, which can be computed or user-defined. The computed value comes from a user-defined GTL template that you specify in the Model Options dialog box. See Customizing Requirement Codes

Description

Full description of the requirement. You can use the RTF editor toolbar. The text is displayed simultaneously in the Description tab of the Notes tab

Comment

Any comment on the requirement

Stereotype

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

Type

Type of requirement from the process point of view (See Customizing a list of values)

Status

Validation level for a requirement (See Customizing a list of values)

Priority

Priority level attached to a 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

If checked, the requirement is retained for the project. If cleared, the requirement is excluded from the project and the sum of workloads

Risk

Level of risk, would a requirement not be satisfied (See Customizing a list of values)

Verification

Test level for a requirement (See Customizing a list of values)

Workload 1-4

Record workloads assigned to four individuals or groups. Workflows for requirements with sub-requirements are read-only fields calculated as the sums of all requirement workloads. For more information, see Assigning Workloads.