Page Comparison

...

• Size: The field specifies the estimated size of the functionality in the chosen units.
• Effort: This field specifies estimated effort required for the requirement in man days.
• Priority: This field specifies priority of the requirement. Possible values for this field are "Blocker", "Critical", "Major", "Minor" and "Trivial".
• Criticality: This field specifies criticality of the requirement. Possible values for this field are "Low", "Medium" and "High".
• Feasibility: This field specifies technical and business feasibility of the requirement. Possible values for this field are "Yes", "No" and "Investigate".
• Technical Risk: This field specifies technical risk of the requirement. Possible values for this field are "Very High", "High", "Average", "Low" and "Very Low".
• Created On
• Updated On
• Reporter: Reporter of this Requirement.
• Votes
  
  • From 1.5.1 onwards, RMsis supports voting for the Planned Requirements.
  • The current Vote Count is always displayed in the cell.
  • A user can cast a positive vote by clicking on the cell corresponding to a requirement.
  • A second click toggles the state of the vote.
• Comments: Any comment related to the requirement can be entered into this field. The latest comment will be shown in "Comments" column against any requirement. After clicking on that cell, all the comments related to the requirements will be shown. Reply can be given to the comment by clicking on "reply to comments" image .
• Watchers : This field identifies the watcher of the requirement. If mail notifications are enabled, the watchers will receive mails for requirement state change events and general Requirement attribute update events. (available from RMsis 1.8.9.2 and later versions)
• Requirement Sources: Both Internal and External sources of Requirements can be specified.

Image Removed

Specific to Planned Requirements

• Baselines: All baselines associated with the requirement are shown in this column.
• Baseline Indicator: This is the "BL" column and displays the baseline status of a requirement.
  
  • Not Baselined
  • Marked for Baseline
  • Marked for Baseline and changed
  • Baselined
  • A detailed description of Baseline States is available at Details of Requirements Baselining.
Depends on
Depends on
• Depends on (from RMsis 1.8.9.4, the Depends On and Dependents columns are available for both Planned and UnPlanned Requirements)
  Depends on establishes forward Traceability to a Lower Level Requirement.
  • For example,
a
• • a Product Goal x depends on a Product Function y.
  • Requirement dependency can be created by clicking the cell corresponding to the requirement in "Depends On" column.
  • After clicking on this column, a panel will appear.
  • Check the requirements on which dependencies needs to be created.
  • RMsis checks for and prevents cyclic dependencies.
  • Creation of a "Depends On" relationship, automatically updates the Dependents relationship.
• Dependents
  Dependents show the reverse traceability of a Lower Level Requirement to a Higher Level Requirement.
  
  • For example,
the
• • the dependents of Product Function zare Product Goal x and Product Goal y.
.
• • Requirement dependency can be created by clicking the cell corresponding to the requirement in "Dependents" column.
  • After clicking on this column, a panel will appear.
  • Check the requirements on which dependencies needs to be created.
  • RMsis checks for and prevents cyclic dependencies.

...

• Image Added

• Linked/ Not Linked Filters in Depends On/ Dependents panels :
  Image Removed
  • • Image Added
    • "Linked" filter can be applied in the Depends On/ Dependents panel to see only those requirements which are linked with the requirement.
    • "Not Linked" filter can be applied in the Depends On/ Dependents panel to see only those requirements which are not linked with the requirement.
      Image Added

  Image Added

  Specific to Planned Requirements

  Image Removed
  • Baselines: All baselines associated with the requirement are shown in this column.
  • Baseline Indicator: This is the "BL" column and displays the baseline status of a requirement.
  • 
    
    • Not Baselined
    • Marked for Baseline
    • Marked for Baseline and changed
    • Baselined
    • A detailed description of Baseline States is available at Details of Requirements Baselining.
  • Actual Effort : This field specifies actual effort for the requirement in man days.
  • Release Id: This field identifies the release id associated with the requirement. A release can be created in "Releases" tab.
  • Status: This field specifies status of the requirement. Possible values for this field are
    
    • Open
    • Closed
    • Completed
  • External ID (Available from RMsis 1.8.7 and later versions) : 
    • This field identifies the ID of requirement which is managed in external systems (tools/ systems other than RMsis).
    • The value in this field can not be edited and its value is populated only via CSV import mechanism (during import of externally managed requirements).
    • External-ID cannot be used for cross referencing within RMsis (for traceability purposes).
    • The value of External ID will be same for multiple versions of same requirement. 

  • Assignee: This field identifies the assignee of the requirement.

  • Custom ID: This column displays configurable Custom ID for requirement. The Custom ID can be configured from Project Configuration tab in RMsis.

  ...