Defining a Release Composition

Owned by Sanjay Sahani
Last updated: Jan 25, 2012
2 min read

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
    • OR Requirements mapped to a set of Baselines
  • 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

  • A Configure Releaseoption on the Releases Tab is provided for all releases.
  • Clicking on this, opens up a panel, where user can
    • Select options to include
      • One or more of the Previous Releases
      • One or more of the Baselines

  • 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.