Reference: Requirements definition
The first sections in the Details tab are used to define the requirement properly.
Section |
Field |
Description |
---|---|---|
Basic |
Related Specification |
Connect the requirement to an existing specification to retrieve a proper number, to set matching ownership and to enable reporting in context of given requirement specifications |
Basic |
ID |
The ID is automatically generated on Save; it reuses the selected requirement specification’s ID and adds a 4-digit numeric counter at the end, with the top-level requirement numbered as 0000. ![]() |
Basic |
Title |
The title must be defined and will be used for the Requirement descriptor |
Basic |
Description |
Use free text with formatting to define the given requirement details |
Basic |
Source |
Optionally select the source of the requirement for reporting and filtering purposes |
Basic |
Type |
Optionally select the requirement type for reporting and filtering purposes |
Graphics |
Upload images to describe the requirement and provide text comments along with each image |
|
Details |
Ideas |
If the Ideas Management template has been installed, this field can be added by the site administrator to enable references to ideas that drive the given requirement |
Details |
Keywords |
Provide a list of keywords to enable recognition of similar and related requirements |
Details |
Comments |
Add any comments helping to manage the requirement |
All fields in the Details section can be changed at any time, even if the Requirement was approved already as they do not impact the requirement contents and may be updated afterwards to capture Lessons Learned. Changes to these fields are still logged in the requirement’s Change Log tab.