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