Mapping requirements
 |
 |
 |
Prerequisites
• Access to the File > Requirement mapping (DC029) menu;
• Requirement released;
• Requirement mapping created.
Introduction
The requirement mapping can be considered a traceability method, as it displays exactly where the compliance must be applied and if or how it is met.
See below how to map the requirements after finishing the mapping creation.
Mapping requirements
See the steps to map requirements in the video below:
Extra information about the Map field
• The options to associate Departments and Processes will only be available if the mapping is by business unit or department;
• Upon associating a Control, the processes and controls related to them will be displayed;
• Only the departments related to the business unit associated with the mapping will be available for selection. To check if the business unit has departments, access the File > Organization structure: Organizational unit (AD003) menu of SoftExpert Administration;
• For the processes to be available for selection, they must be released and have the same business unit as the mapping. Remember that the business unit must be associated with the general process data;
• For risks and controls to be available for association, it is necessary for the risk plan business unit to be the same as the mapping one, and the plan must have risks and controls associated and be released. Remember that the business unit must be associated with the plan data.
Requirements that are not checked as applicable will not be considered for the calculations of the implementation in requirement monitoring.
For the associations to work correctly in the Map and Associate fields, it is necessary for the Process, Risk, Action plan, and Workflow components to be part of the solutions acquired by your organization.
Conclusion
Once the requirement mapping is performed, it is necessary to release the record. To do so, follow the steps displayed in the Finishing a mapping article.