This process describes how a business department (line of business) can create, edit, and commit business requirements. By using this process and the documentation of all related tasks, you can find out at any time where a business requirement originated, who implemented it, and when the change was implemented in a production environment.
Business requirements are processed by business process experts and managers in the business department.
You have the business role REQUESTER
(also see Authorizations).
The graphic below shows how a business process expert can create and submit a business requirement for approval by the business manager. Once the business manager has approved the business requirement, it is submitted to the IT department in the form of an IT requirement.
Processing Business Requirements
A business process expert identifies a new requirement that is to be implemented by the IT department.
The business process expert creates a business requirement.
The business process expert submits the business requirement for approval by choosing
and saves the requirement.At this point, the business manager can reject the business requirement outright or return it to the requester for further clarification. To continue the process, however, the business manager chooses
and checks the requirement before deciding how to proceed:Manager's Decision | Action to Be Taken | Description |
---|---|---|
Approve the business requirement and submit it to the IT department for processing |
| The requirement is forwarded to the IT department in the form of an IT requirement. The link to the associated IT requirement is added to the |
Request further information about the business requirement from the business process expert |
| The status of the requirement is reset to |
Reject the business requirement |
| The requirement is closed. |
Postpone the business requirement until further notice |
| The requirement is postponed. |
When the IT department has approved the requirement and committed itself to implementing the requirement at a specific time and cost, the business requirement is assigned the status Committed by IT
. The business department (that is, the line of business) now approves the business requirement and commits itself to the time scale and cost. This is a “hard” commitment and can be equated with a purchase order.
Note
A requirement can be implemented only if it is committed by both the business department and the IT department.