This activity addresses collecting and eliciting information from the Stakeholder in the project in order to understand what their needs really are. The
collected Stakeholder Requests can be regarded as a "wish list" that will be used as
primary input to defining the high-level features of your system, as described in the Vision (see Develop Technical Vision), which drive the specification of the Requirements, as described in the software requirements specification (which
may reference the Use-Case Model, Use Cases and System-Wide Requirements).
The main objective is to elicit stakeholder requests using such input as interviews, Enhancement Request, and requirements workshops. The primary outputs are
collection(s) of prioritized features and their critical attributes, which will be used in defining the system and
managing the scope of the system (see defining the system, managing system scope).
This information results in a refinement of the vision, as well as a better understanding of the Requirements Attributes. Also, during the enactment of this activity you may start
discussing the functional requirements of the system in terms of its Use Cases and Actors (see Identify and Outline Actors and Use Cases). Those requirements which do not
fit appropriately within the use cases should be documented in System-Wide Requirements (see Detail System-Wide Requirements).
As you define new requirements, it is important to document any dependencies (e.g., Traceability) between these requirements (see Requirements Traceability).
Another important output is an updated Glossary of
terms to facilitate communication through the use of a common vocabulary among team members.
|