...
- Requirement Id: A unique identification of the requirement. This field is non editable.
- Requirement Version : A requirement can have multiple versions and each version is a requirement committed in space and time. A complete description of requirement versioning is available at Details of Requirement Version Management
- It is displayed next to the Requirement Id, within braces.
- A parent requirement is treated as a container and it's version cannot be saved. These requirements will have Version # 1, throughout their lifetime.
- Requirement Summary: This is a brief description of the requirement.
- Description: This is a field to capture details of a requirement. However it is not visible in the tabular view (by default).
- Attachments: Any number of documents or links can be attached to the requirement. For attaching a document or link against a requirement, just click on "Attachments" column (
) and row corresponding to the requirement. After a panel appears, enter details of document or link.
- Categories: A requirement can be classified in user defined categories.
- A category can be created by clicking on "Categories" column in any row of the table. After a category panel appears, click on "Create New Category" to create a new category.
- After a category is created, it can be associated with any requirement in the table (planned or unplanned).
- A category can be edited by clicking on edit category image
- A category can be deleted by clicking on delete category image
...
- 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.
- 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
...