Previous Topic: Create a Child Requirement

Next Topic: Associate a Requirement with a Product Release

Edit Child Requirement Details

Follow these steps:

  1. Open the requirements list page and click Edit in the Actions column of the child requirement you want to edit.
  2. On the Requirement Edit page, complete or edit the following fields as necessary:
    Title

    Specifies the name of the requirement.

    Financial Benefits

    Specifies the amount of potential profit the requirement can provide.

    Planned Cost

    Specifies the planned cost for the requirement. When CA Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten.

    Planned Effort

    Specifies the planned effort for the requirement in labor hours. When CA Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten.

    Actual Cost

    Displays the actual cost of the requirement. When CA Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten.

    Actual Effort

    Displays the actual effort in labor hours charged to the requirement. When CA Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only. If you are integrated with CA Clarity PPM, manual edits will be overwritten.

    Remaining Cost

    Displays the amount of planned cost that remains. When CA Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only.

    Remaining Effort

    Displays the amount of planned effort hours that are left. When CA Product Vision is integrated with CA Clarity PPM, this data comes from CA Clarity PPM and is read-only.

    Planned vs Actual Cost

    Displays the difference between the planned cost and the actual cost. This field is read-only.

    Planned vs Actual Effort

    Displays the difference between the planned effort and the actual effort. This field is read-only.

    Complexity

    Specifies the degree of difficulty that can be expected in completing the requirement.

    Values: High, Medium, Low

    Priority

    Specifies the precedence of the requirement over other requirements.

    Values: Very High, High, Medium, Low, Very Low, Not Prioritized

    State

    This field is defined by your company. Typically, this field is used to label different workflow stages for a requirement.

    Labor Estimate

    Specifies the estimated labor cost for the requirement.

    Planned Cost

    Specifies the estimated expense of the requirement.

    Confidence Level

    Specifies the level of confidence the owner has in the organization's understanding of the requirement and the organization's ability to deliver the requirement.

    Values: High, Medium, and Low.

    Category

    Specifies a way to group requirements that is defined by your company. Select one of the options from the drop-down.

    Parent Requirement

    Specifies the requirement that is the parent of the current requirement. This field applies only to child requirements

    Is Active

    Specifies that the requirement is active and can be assigned to releases and features. Inactive requirements do not appear in the list views or hierarchy views.

    Default: Selected

    Products

    Specifies the product or products to which the requirement applies. You can select more than one product to associate with the requirement.

    Features

    Specifies the features to which the requirement is assigned.

    Releases

    Specifies the releases to which the requirement is assigned. You can assign the requirement to more than one release.

    Sources

    Specifies the sources associated with the requirement. You can assign the requirement to more than one source.

    Requirement Owner

    Specifies the name of the owner or owners of the requirement.

    Personas

    Specifies the personas associated with the requirement. You can associate more than one persona with a requirement.

    Description

    Provides a description of the item being created or edited.

    Problem

    Specifies the problem the requirement addresses or solves.

  3. Click Save.
  4. Click Back to List.

How to View CA Software Change Manager Package Information

You can integrate with CA Software Change Manager (CA Software Change Manager) to view information about packages related to requirements.

Important:

To integrate with CA Software Change Manager, the system administrator must enable integration with CA Software Change Manager.

After the integration has been enabled, you can perform the following tasks from a requirement:

View CA Software Change Manager Packages

If the system administrator has enabled integration with CA Software Change Manager, you can view a list of packages related to a requirement. Packages appear in CA Software Change Manager section of the detail page.

The CA Software Change Manager section displays a list of packages with the following information:

Package Name

The name of the package associated with a requirement. The name has a link to the CA Software Change Manager Package Detail page for the package.

Click on the package name to view more detail about the package.

SCM Project

The name of the related project in CA Software Change Manager

Broker

The CA Software Change Manager broker

Created By

The user ID that created the package

View CA Software Change Manager Package Detail

The CA Software Change Manager Package Details page displays package history and code changes associated with a requirement. The information on this page is read-only.

You can link to this page from the CA Software Change Manager section in the detail page for the requirement.

The CA SCM Package History table displays the following information:
Action

The most recent activity performed on the package

State

The current phase in the development lifecycle, such as "Development"

Modified By

The name of the user that last modified the module

Date Changed

The date on which the module was last changed

The Code Changes table displays the following information:
Item Name

The name of the created item that is checked in to a CA Software Change Manager repository

Path

The path of the item in the repository

Version number

The iteration of an item in the repository

Date Changed

The date on which the module was last changed

Modified By

The name of the user that last modified the item