Checklist: Requirements Management Process Description |
Ensure that the team's Requirements Management Process Description is complete and can be used effectively by team members.
Relationships
Related Elements | Requirements Requirements Management Process Description
Check Items
Are similar requirements management plans leveraged?
If your project is similar to others in your organization that already have well-defined requirements management strategies, use those strategies. If they are not documented clearly, document them for use in your project as well as future projects.
Has the representation for the requirements management process been clearly identified?
Extending the Requirements Management practice is an ideal way to capture the requirements management process description. This requires knowledge of the IBM® Rational® Method Composer tool, and the Unified Method Framework. Alternatively, you can record the process in the document and diagramming tools used to capture the workflows. See Example: Requirements Management Process Description.
Has automation (tooling) been described in the plan?
Capture the tools and methods used for automation as part of the strategy.
Are multiple requirement and document types identified and captured?
Specify what the various document types are, and what types of requirements are captured in each document. Define the differences between the different requirement types, and when and how they would be used.
Are all properties and tracking information about each requirement captured in the plan, and is only the minimum information maintained?
Be careful not to define attributes that will never be used. because they introduce unnecessary overhead. Keep the attribute set to the absolute essentials if the requirements management process is not automated.
Is it clear how all the requirements will be tracked and managed?
Are all reports, queries, charts, and so on that will be used by managers and team members clearly defined?
Does the team understand the requirements management process?
Make sure that the entire process is captured in the plan, or is referenced by the plan, so that it can be easily located (for instance, if the process is captured in a published practice). Make sure that the process is described at the right level of detail, so that it is complete but still understandable.
More Information
Examples | Requirements Management Process Description
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.