If RCM is not enabled, the requirement owner can create an approved version.
Follow these steps:
Specifies that the updates are small changes, such as editorial changes or field changes such as entering the Actual Effort. The version changes by one point (0.1).
Specifies that the updates are significant, such as changing the release associated with the requirement, or changing the scope of the requirement. The version changes by one full version number (1.0).
A new version of the requirement is created. The following fields or sections have updated values:
The value changes from Draft to Approved.
The value increases by a decimal point or whole number, which is specified by a minor or major version type.
A record is added to the Versions section, with the new version number and a time stamp.
| Copyright © 2012 CA. All rights reserved. |
|