What is Requirement Management

Requirement management is the process of documenting analyzing tracing and reviewing and then agreeing on the valid requirements and then applying the requirement change process and communicating to all relevant stakeholders requirement change process in which users can change the requirement technology can change the requirement environment can change the requirement (Here we have requirement baseline which has two parts correct baseline and review baseline) Requirement baseline is the process in which when we do work on iteration and that step we work on set of approved requirement that makes requirement baseline.

The requirement baseline provides ease in changing the requirement.

Why set a requirement baseline?

Answer: Requirement baseline specifies the set of requirements approved by all the stakeholders for the specification iteration.

The requirement baseline evaluates the impact of change on the system.

The requirement baseline reflects change throughout the requirement process.

Importance of Requirement Management

The importance of requirement management is to ensure that an organization's document verifies and validate the requirement and expectations of its customers and all stakeholders. Requirement management begins with analysis and elicitation of the objectives and constraints of the organization.

The requirement management process supports the traceability of the requirements which is very important to meet the customer expectations.
The traceability also supports the requirement change process.
The requirement management process includes planning for requirements, integrating requirements, and organizing for working with them.
Requirement management involves communication between the project team and stakeholders of a software project.

Why Project Fails

If the organization's concerns are not clear about the requirement management process, then software product/project leads to failing reason of project failures are.

In Complete Planning

A big project requires more efficient planning for making the project successful likewise a small project also requires planning but if at the start of the project you made a mistake and miss any prerequisites then your project will require two to three times revision this is the worst part of development.

Inefficiently define the project scope

In the Requirement Engineering process defining the project, the scope is very much important because if you define the scope of the project poorly or incompletely scope your project led to unsuccessful.

Ineffective leadership

In software development the if project leader is ineffective and poorly manages the project improperly defines the iteration of completion of the project is unsuccessful and useless at the end of the project.

Not Successfully identifying the assumptions

In software development, if you failed to define the assumption about the project then your project in the end will be useless.

Example

The project will work on Android Based Mobile Technology
The project will work in presence of Wi-Fi, 3G, or 4G technology.
Not Tracking the project progress
In software development, if you failed to track the full progress of the project then your project, in the end, will be useless.

No Detailed documentation

In software development, documentation is a very important phase in which we write software documents like SRS document Design Document in later stages of development we use reverse engineering techniques then we use these documents for the updating the software product.

No track requirements

Software requirement engineering is a very important phase of the software development process or simply Software development life cycle (SDLC). This phase is used to translate the unclear and incomplete idea of the customer into complete precise and formal specification this document is very must important and act as a bridge between the Customer, User, and Developers. Therefore, the importance of software requirement engineering is very much important for the development of effective and efficient software products.

Not Selection of the right technology.

In software development, if you failed in the selection of technology which technology is best for the development of the project then it may also lead to the project being unsuccessful.

Not Accurate measurement of time and budget.

If the time exceeds the completion of the project, then your project and development process leads to an unsuccessful project.
If the budget exceeds the completion of the project, then your project and development process leads to an unsuccessful project.

Not Detailed project planning.

A big project requires more efficient planning for making the project successful likewise a small project also requires planning but if at the start of the project you made a mistake and miss any prerequisites then your project will require two to three times revision this is the worst part of development.
Incomplete Requirements may lead a project to be Unsuccessful.
Before the Beginning of any project, we must be sure about prerequisites and after checking that all the permits have been obtained and make sure that all the requirements are obtained then move to the next step of the software development life cycle (SDLC) if you forget something in the first stage of software development then your project may lead to an unsuccessful project.

How we can Manage Software Requirements

We can manage requirements in the following ways.

By Documenting all the project progress ? By Detailed Documentation.
Software Requirement Specification (SRS) Documentation.
By Writing Design Documentation
By Writing All project reports from the project proposal to the end of the project.

Reference

Software Requirements Engineering Complete Book Practical Approach By Sardar Mudassar Ali Khan