Requirement

Description

Package: com.ibm.rpm.scopemanagement.containers

Extends: AbstractScope

Usage

Requirements allow managers to break the project scope into manageable and trackable elements.

In their simplest form requirements can be defined as project scope elements and deliverables. When these requirements are contained in other point solutions or applications, the tracking of project delivery is usually a manual process. Managers are forced to report project performance in different ways because project work breakdown structures do not necessarily map directly to project or business requirements.

IBM Rational Portfolio Manager offers the unique ability to create project requirements and to map the project work breakdown structure to these requirements. Furthermore, as IBM Rational Portfolio Manager project artifacts; requirements can be subjected to the same rigorous processes used to manage such elements as project documents.

A requirement cannot exist unless a folder exists.

Parent is mandatory, allowed parent types are ScopeFolder, Action, Issue, ChangeRequest, Defect, Requirement, Risk and ServiceRequest.

Supported API Calls

Security Restrictions

N/A

Fields

The following table lists the fields for this object.

Table 1. Requirement Field Description
Field Detail
approvedCostBenefits

Type: ApprovedCostBenefits

Default value: N/A

Description:The approved costs and benefits of the requirement, which are used to identify the approved schedule impact, effort required as well as the costs and benefits..

Field validation description: N/A

Additional field security restrictions: N/A

Inherited Fields

Click on object for list of inherited fields:

From RPMObject

From ScopeElement

From AggregateScope

From AbstractAggregateScope

From AbstractScope

Related Objects

N/A