Artifacts > Requirements Artifact Set > Stakeholder Requests
The purpose of this artifact is to capture all requests made on the project, as well as how these requests have been addressed. Although the system analyst is responsible for this artifact, many people will contribute to it: marketing people, end users, customers—anyone who is considered to be a stakeholder to the result of the project. This information may be collected in a document or automated tool and appropriate requests should be tracked and reported on following an approved Change Request Management (CRM) process.
Examples of sources for the Stakeholder Requests are:
Stakeholder Requests are mainly collected during the inception and elaboration phases, however you should continue to collect them throughout the project's lifecycle for planning enhancements and updates to the product. A change request tracking tool is useful for collecting and prioritizing these requests.
A system analyst is responsible for the integrity of the Stakeholder Requests artifact, ensuring that:
Stakeholder requests are best managed in a database, such as Rational
ClearQuest and/or Rational RequisitePro, in order to track status, prioritize,
generate reports, and establish traceability. See Tool
Mentor: Managing Stakeholder Requests using Rational ClearQuest® and Rational
RequisitePro®. Tailoring involves deciding on the information
(attributes) to be documented for each stakeholder and each stakeholder request.
See Artifact: Requirements Attributes.
Rational Unified Process