This functionality has been introduced from RMsis 1.4.0 onwards and can significantly reduce the effort required to map Requirements / Test Cases to a Release.
Implementation Overview
In RMsis context, a Release relates of a set of requirements, artifacts and a set of test cases. These are associated as follows:
- Requirements
- Requirements Mapped to the previous Release + Requirements implemented for the current Release - Requirements excluded in the current lrease
- OR Requirements mapped to a set of Baselines - Excluded Requirements + Additional Requirements included
- JIRA Artifacts are directly associated with the Release by virtue of their association with JIRA Versions
- Test Cases
- Test Cases mapped to the Requirements, which are further mapped to the Releases
- Test Cases directly associated with a Release
User Interface
- Provide a A Configure Release
option on the Releases Tab is provided for all releases. - Clicking on this, opens up a panel, where user can
Select the release, which needs to be configured.- Select options to map it to a set of Requirements include
- One or more of the Previous Releases
- One or more of the Baselines
- Once the user validates the selection, the entire set of Requirements appears, with the mapped requirements shown as selected.
- Subsequently the user has the ability to
- select (additional) individual Requirements
- deselect any of the requirements already mapped
- Select options to map it to a set of Requirements include
- Exceptions
- The system will show a warning, if different versions of the same requirement get included in the release.
- The user can change the configuration till the time of Release.
- Once Released, the mapping cannot be altered.