Newsletter
Step-by-step instructions for creating a new requirement
Watch the video or follow these easy steps:
The custom identifier is an id that is automatically generated but it can be modified by the user. The ID must be unique within the project.
Brief description of the requirement. For example, “Word report”.
Details for the requirement. For example, “The system shall support Word reports.”
Select where in the table of contents the requirement should be stored. For example, “general requirements”.
Select the users you would like to be linked with this requirement.
Select a status for the requirement. The status values are used to control what response is required from the end-user. If you specify “pending approval of final requirement”, the stakeholder can select “Yes”, “No” or “Yes if” and provide a comment. If pending more information is specified, they can provide a comment. The detailed behaviour of the status transitions can be configured for each specification.
Any additional information you may want to specify.
When the requirement has been saved, you can add links to other requirements that this requirement depend on and specify the relationship between the two as "parent", "child" or "bi-directional".
You can add one or more notes to the various note categories.
You can upload one or more files. Each attachment should have a name and description specified.
You can select values for the various attributes that you have configured for this specification.
If the requirement was created as a result of a questionnaire from the Questionnaire module, a link to that questionnaire is shown.
If the requirement has been saved at least once, you can check “Minor change”. Minor changes can then be excluded when making reports or doing analysis.
The change history for each requirement keeps a log of all changes to all values for each requirement. The changes are categorized and are shown when a "change type" is selected.