Artifact: Requirements Management Process Description |
This artifact is used capture the requirements strategy for a project or for multiple projects with a similar profile within an organization.
Domains: Requirements
Purpose
To document decisions made by the organization on how to document and manage their project requirements To reuse on future projects with a similar profile. To promote standardization of the requirements management process within the project team and the organization as a whole
Relationships
Roles | Responsible: Analyst | Modified By: Analyst
Tasks | Input To: Organize Requirements | Output From: Plan Requirements Management Strategy
Description
Main Description | The Requirements Management Process Description describes the requirements artifacts, requirement types, their respective requirements attributes, how requirements traceability will be managed, and specifies the information to be collected and tracked. It also specifies how requirements changes will be managed, as well as addressing requirements organization, tool automation, the necessary reports, views, and queries that will be generated and the related processes for requirements and requirements change management.
Illustrations
Templates | Requirements Management Process Description
Examples | Requirements Management Process Description
Tailoring
Impact of not having | Inconsistency in documenting and managing requirements within the project team and the organization. Inconsistent organization of requirements and tool use. Poorly understood requirements and change management process. Incorrect use of various requirement and document types in a large complex requirement set.
Reasons for not needing | A lengthy and formal Requirements Management Plan might not be necessary for small projects with a simple requirements set and a well-defined requirements management strategy and process. This is particularly true if the analyst team is very familiar with the process.
Representation Options | Most of the information in this artifact can captured as a word document. It is also possible to capture all or part of this information as an extension of the requirements management practice. Dynamic processes, which can be depicted effectively by using activity and workflow diagrams, could use the Rational Method Composer. If this is not feasible, the processes can be included in the word document along with all related information.
More Information
Checklists | Requirements Management Process Description
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.