Requirements Management Process
A Structured Approach



The Requirements Management Process is a structured approach for the capture, organization and management of Business Requirements. These steps are commonly known as the Analysis phase of the Systems Development Life-Cycle (SDLC).

The Requirements Management Process typically consists of the following four steps:
  • Gathering
  • Analyzing
  • Organizing
  • Approving
Gathering is those activities associated with the collection of the business requirements from the various sources including document and stakeholders.

Analyzing is those activities associated with the negotiation and determination of what the requirements actually mean and which stakeholders’ requirements take priority. It determines which requirements should be addressed in this project.

Organizing is the documentation and organizing of the requirements. Normally requirements can be classified into functional and non-functional requirements. The document created is the User Requirements Document.

Approving is the confirmation and signoff from the stakeholders that these are the requirements they want to be addressed in this project.

The IEEE “Guide to the Software Engineering Body of Knowledge” (SWEBOK) refers to these same phases as Elicitation, Analysis, Specification and Validation.



Clearly Put has developed a clear and simple Requirements Management Process. The Requirementing steps consists of Gather, Analyze, Organize and Approve. Two additional steps also included are Control and Manage.

Controlling is a valuable activity that aligns the Requirements Management activities with other Project Management activities.


Summary

The Requirements Management Process consists of 4 steps. These steps are typically known as 1) Gathering; 2) Analyzing; 3) Organizing; and 4) Approving.

Requirementing Steps