...
- 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.
- Depends on establishes forward Traceability to a Lower Level Requirement.
- 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.
- Dependents show the reverse traceability of a Lower Level Requirement to a Higher Level Requirement.
- Linked/ Not Linked Filters in Depends On/ Dependents panels :
- "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.
- Linked/ Not Linked Filters in Depends On/ Dependents panels :
- 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.
...