Requirements Management
●
Once you have the initial
requirements for a body of work in hand, you must cope with the inevitable changes
during development.
●
Effective change management
demands a process for proposing changes and evaluating their potential cost and
impact on the project.
●
Tracking the status of each
requirement as it moves through development and system testing provides insight
into overall project status.
Good practices for requirements
management include:
●
Define a requirements
change-control process.
●
Establish a change
control board (team).
●
Perform
requirements-change impact analysis.
●
Establish a baseline and
control versions of requirements documents.
●
Maintain a history of
requirements changes.
●
Track the status of each
requirement. (e.g. proposed, approved, implemented, or verified),
●
Measure requirements
volatility. (e.g. the number of proposed and approved changes
(additions, modifications, deletions)
●
Use a requirements
management tool. Create a requirements traceability matrix.
