|
Gather information
Use various techniques to make gathering requirements easier. Face-to-face meetings with stakeholders is the most
effective way to understand stakeholder needs and to gather and validate requirements, but you must prepare in order
for these meetings to run efficiently.
Be prepared by gathering and reviewing information related to the problem domain, problem statement, business
environment and key stakeholders. Most of this information should be available in the Artifact: Vision. Review the Artifact: Work Items List for stakeholder requests.
See Guideline: Requirements Gathering Techniques for more information.
|
Identify and capture domain terms
| Collaborate with stakeholder to make sure that ambiguous or domain-specific terms are clearly defined in the Glossary and that you use these terms consistently. |
Identify the types of requirements relevant to your system
Requirements can be broadly classified as either functional or non-functional requirements. The former specify what the
system must do. The latter specify constraints on the solution such as usability, reliability, performance,
supportability, interfaces with legacy systems, etc. Depending upon the domain there may be regulatory requirements
that apply.
Collaborate with stakeholders to identify the types of requirements relevant to your system. This will help you assess
the completeness of your requirement set. For more information on types of requirements see Concept: Requirements and Concept: Supporting Requirements.
|
Identify and capture Use Case and Actors in a Use-Case Model
Identify and capture Supporting Requirements
Collaborate with stakeholders to identify and capture the other types of requirements relevant to your system. See
Guideline: Supporting Requirements for more information.
|
Achieve concurrence
Update the Work Items List
|
