SoftExpert Requirement tasks
Introduction
Tasks are pending system activities for which the user is responsible. They are divided into two categories: Execution and Tracking.
Tracking tasks are tasks for which the user is responsible, but that are executed by another user.
Execution tasks are pending tasks that the user must execute within a deadline or defined period.
In SoftExpert Requirement, no tracking tasks are generated.
See further details on these execution tasks:
Execution tasks
Revalidation approval
Requirements that have validity control configured in its type will be regularly revalidated.
Depending on the configurations made in the validity control, after the revalidation is closed, the revalidation approval task is generated.
Who receives it | Users defined as members of the responsibility route for the approval associated with the validity configuration or revalidation of the requirement in question. |
When | When a revalidation is sent for approval. |
Where | My tasks menu. |
Purpose | To approve or reject a requirement revalidation. |
Requirement mapping revalidation approval
Requirement mappings that have validity control configured in its type will be regularly revalidated.
Depending on the configurations made in the validity control, after the revalidation is closed, the requirement mapping revalidation approval task is generated.
Who receives it | Users defined as members of the responsibility route for the approval associated with the validity configuration or revalidation of the requirement mapping in question. |
When | When a revalidation is sent for approval. |
Where | My tasks menu. |
Purpose | To approve or reject a requirement mapping revalidation. |
Requirement revision
When requirements created in the system are configured to go through revision processes based on the ISO9000 standards or via workflow, the requirement revision task is generated.
Such configuration is established in the type that classifies the requirement.
Who receives it |
ISO9000 based: Users defined as participants in the revision route associated with the requirement. Workflow: Users defined as executors of the workflow activity. These users should have the Edit control enabled in the requirement security list. |
When |
ISO9000 based:
Workflow: When a new revision starts and when, in the process flow, the activity should be executed. |
Where | My tasks menu or Management > Revision > Requirement (REQ022) menu. |
Purpose | To control the changes and versions of the requirements added to the system. |
Requirement mapping revision
When requirement mappings created in the system are configured to go through revision processes based on the ISO9000 standards or via workflow, the requirement mapping revision task is generated.
Such configuration is established in the type that classifies the mapping.
Who receives it |
ISO9000 based: Users defined as participants in the revision route associated with the requirement mapping. Workflow: Users defined as executors of the workflow activity. These users should have the Edit control enabled in the requirement mapping security list. |
When |
ISO9000 based:
Workflow: When a new revision starts and when, in the process flow, the activity should be executed. |
Where | My tasks menu or Management > Revision > Requirement mapping (REQ025) menu. |
Purpose | To control the changes and versions of the requirement mappings added to the system. |
Requirement due date
Certain requirements remain current, that is, valid, for a specific period.
According to the validity configurations associated with the requirement type, due date tasks are generated to allow managing the validity deadline of those requirements more effectively.
Who receives it | Users who have the Edit or Revise controls enabled in the security list of the pending requirement. |
When | When the default time set in the validity configuration associated with the type of the pending requirement expires. |
Where | My tasks menu. |
Purpose | To allow the responsible users to revise or revalidate the pending requirement and to allow deleting requirements that are no longer necessary for the organization. |
Requirement mapping due date
Certain requirement mappings remain current, that is, valid, for a specific period.
According to the validity configurations associated with the requirement type, due date tasks are generated to allow managing the validity deadline of those mappings more effectively.
Who receives it | Users who have the Edit or Revise controls enabled in the security list of the pending requirement mapping. |
When | When the default time set in the validity configuration associated with the type of the pending mapping expires. |
Where | My tasks menu. |
Purpose | To allow the responsible users to revise or revalidate the pending mapping and to allow deleting mappings that are no longer necessary for the organization. |
Requirement test execution
When the requirement test option is enabled in the requirement data, a task is generated for the responsible parties.
Who receives it |
Responsible user or members of the responsible team for tests by test case, defined in the requirement data. Responsible user or members of the responsible team for tests by sample, defined in the requirement structure. |
When | When the next requirement test execution has been set for within the next 10 days.* |
Where | My tasks menu or Execution > Requirement test (REQ040) menu. |
Purpose | To execute the requirement tests, both by test case and by sample. |
*The task is only generated when the next test execution is within 10 days. For example, if the test execution is defined for 15 days from now, the task will not be generated.
Additional information
• Tasks can also be executed through the button available in the notification e-mail related to them.
• For further details on the revalidation process, refer to the What is a revalidation? article.
• For further details on the revision configuration and execution, refer to the What is a revision? article.
Conclusion
As tasks are executed and closed, they are no longer displayed in the list of pending records in the Task menu.