Creating a reference requirement
 |
 |
 |
Prerequisites
• Access to the File > Requirement (REQ021) menu;
• Previously created requirement type.
Introduction
This step will teach you to create a requirement. It is a record used to catalog the compliances of the organization.
For this article, we will create the "ISO9000" type, which is part of the example seen in the Learn about SoftExpert Requirement article.
Creating a reference requirement
1. To add a requirement, access the File > Requirement (REQ021) menu.
2. Click on the 
button.
3. Select a previously created requirement type.
4. Click on the 
button.
5. On the screen that will be opened, enter an ID # and a name.
6. The Requirement type field is filled out by the system with the previously selected type, but it is possible to edit it.
7. To do so, use the 
button to search for previously created types or the 
button to create a new type.
8. The Responsibility field will be filled out by the system with the data of the user that is creating the requirement; however, it is possible to edit it.
9. Then, fill out the Responsible team field with the team that will be responsible for the requirement.
10. In the Reference document field, use the button to search for the document to which the requirement refers. For example, the quality manual of the organization.
11. In the URL field, enter the URL where you can find the documentation to which the requirement refers. For example, an article with the ISO9000 standards.
12. Lastly, use the content field to describe the requirement being created.
13. Use the 
button to save the record for the first time and enable the other configurations.
If attributes have been associated in the Requirement type to complement requirement information, the Attribute tab will be displayed for the completion of the fields.
For further details on attribute completion, refer to the Attribute completion article.
After finishing the initial requirement configurations and saving the record for the first time, new tabs are enabled.
The Audit criterion tab will only be available if, in the Requirement type, the Allow requirement audit option is checked. For further details on this tab and how to configure it, watch this video:
• The evaluation criteria associated with the Audit criterion tab must have been previously created in the Audit component. If SoftExpert Audit is not part of the solutions acquired by your organization, this feature may not be applied.
• It is mandatory to fill out the evaluation criterion. If this field is not filled out, it will not be possible to close the requirement revision.
In the Workflow tab, it is possible to add and/or associate workflows related to the requirement being created.
To add workflows, follow the steps below:
1. In the Workflow tab, click on the button to instantiate a process.
2. Select the desired process or workflow type.
3. Enter the instance title.
4. If necessary, enter a description.
5. Click on .
Once the workflow is instantiated, the activity execution screen will be displayed. For further details on this operation, refer to the SoftExpert Workflow documentation.
On the Documentation tab, it is possible to associate documents from SoftExpert Document or attachments related to the requirement. For further details on this operation, refer to the Adding attachments and associating documents article.
The Associations tab allows associating records from other components with the requirement.
Some of the options for the association are assets, suppliers, supplies, items, action plans, and isolated actions.
For further details on the creation of action plans and isolated actions, refer to the Learn about SoftExpert Action plan article.
To be able to associate documents in the Documentation tab and add or associate records from other components in the Associations tab, it is necessary for the respective components to be part of the solutions acquired by your organization.
Once all configurations are set for the reference requirement, click on to close the record.
Conclusion
After creating the reference requirement, the next step is assembling the requirement structure.
For further details on this operation, refer to the Configuring the requirement structure article.