This process describes how you can create, edit, commit, and implement IT requirements. By using this process and the documentation of all related tasks, you can find out at any time where an IT requirement originated, who implemented it, and when the change was implemented in a production environment.
IT requirements are processed by solution architects and IT managers.
You have the business role SOLMANPRO
(also see Authorizations).
The graphic below shows how the solution architect and the IT requirements management can process an IT requirement.
Processing an IT Requirement
The solution architect receives an IT requirement and enters information such as the change cycle in which the requirement is to be implemented, the potential risks, and any related problems or incidents.
The IT department uses a checklist to analyze the feasibility of the requirement and chooses the action Submit for Approval
.
The IT manager checks the requirement and commits the scope. The requirement is then returned to the business department for final commitment.
Note
A requirement can be implemented only if it is committed by both the business department and the IT department.
When the requirement has been committed, the IT department begins to implement it in one of the following ways:
By starting a project in Project Management, where the IT requirement is assigned to a change document
By creating change documents from the IT requirement scope
By handling the requirement as part of maintenance by creating a request for change