Information Technology Reference
In-Depth Information
2. The second connotation is as an ''art and a social science (process)'' practiced
by individuals to get things done by others without absolute authority or clarity
in the organizational processes.
3. The third connotation is as a ''body of knowledge'' about getting things done
It is the second connotation that is pertinent to the present context of require-
ments management. Management as a process consists of the following sub
processes:
1. Planning
2. Organizing
3. Staffing
4. Controlling
Therefore, requirements management includes the above four aspects. CMMI
Version 1.3 defines requirements management, as, ''The management of all
requirements received by or generated by the project or work group, including
both technical and non-technical requirements levied on the project or work group
by the organization''. Technical requirements are defined as ''properties of product
or service to be acquired or developed'' and non-technical requirements are
defined as ''requirements affecting product and service acquisition or development
that are not properties of the product or service'' .
This definition specifies that requirements can be of two varieties, namely
technical and non-technical requirements. It also states that requirements can be
received from external sources such as customers or can be generated within the
project team too. Especially in COTS (Commercial Off The Shelf) product sce-
nario, many, if not all, requirements are generated within the project team.
Wikipedia defines requirements management, as, ''Requirements management
is the process of documenting, analyzing, tracing, prioritizing, and agreeing on
requirements and then controlling and communicating to relevant stakeholders. It
is a continuous process throughout the project'' .
This definition enumerates the activities to be performed as part of requirements
management, namely,
1. Documenting requirements
2. Analyzing the requirements
3. Tracing the requirements through out the development life cycle
4. Prioritizing the requirements, especially their order of implementation
5. Agreeing upon the requirements, that is requirements are accepted for imple-
mentation by the project team and are approved by the stakeholders
6. Controlling the requirements, that is controlling the change to the agreed upon
requirements
7. Communicating the status and progress of implementation of requirements and
changes received thereon to all stakeholders.
This definition also states that the process of requirements management begins
with the starting of the projects and completes with the ending of the project.
Search WWH ::
Custom Search