Once the Requirements are created. You may want to copy the Requirements to other projects or to the same project which use the some similar requirements. While copying the requirements in ALM you got to know the following
- Root folder cannot be copied.
- Test coverage is not copied.
- Defect linkage is not copied.
- Risk Based Quality Management ( RBQM) is not copied.
When the requirement is copied the following will be copied
- Traceability.
- Associated Requirements.
When you name the copied requirement with the existing requirement name
Suffix_Copy will be added automatically.
Example:
When you are trying to name the copied requirement with Login which is already exsist in your project. So ALM will be automatically add Login_Copy to the name of the copied requirement.
Moving a Requirement
Once you created your requirement sometimes you may want to move the requirement from one folder to another. While following the requirement also moves the following items
Moving a Requirement
Once you created your requirement sometimes you may want to move the requirement from one folder to another. While following the requirement also moves the following items
- Child Requirements.
- Test Coverage.
- Requirement Traceability link.
- Defect linkage.
Root folder cannot be moved. You can drag the requirement other than a root folder to its new location.
Delete a Requirement
While deleting a created requirement also deltas the following items
- Child requirements.
- Test coverage.
- Requirement traceability.
- Defect linkage.
Root folder cannot be deleted. Deleting a requirement, deletes all the previous versions in version controlled projects.
Naming the requirement
While naming the requirement the following special characters cannot be included.
\ ^ *
While naming the requirement the following special characters cannot be included.
\ ^ *
No comments:
Post a Comment