Page Comparison

...

• 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 establishes forward Traceability to a Lower Level Requirement.
    • For example, 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 dependents of Product Function z are 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 Modified

• Actual Effort : This field specifies actual effort for the requirement in man days.
• Technical Risk: This field specifies technical risk of the requirement. Possible values for this field are "Very High", "High", "Average", "Low" and "Very Low".
• 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

...