background image
<< Working with RequisitePro | Why Work with Use Cases >>
Managing Requirements
<< Working with RequisitePro | Why Work with Use Cases >>
66
Chapter 5 - Creating Requirements
Managing Requirements
Managing requirements is a systematic approach to:
s
Finding, documenting, organizing, and tracking requirements.
s
Establishing and maintaining agreement between the customer and the project
team on the system's requirements.
Requirements management is challenging because requirements change throughout a
project. For example, users can change their minds about essential features, or they
may not have articulated their wishes clearly in the first place. Competitors can
release new versions of their software and you must respond by changing project
plans midstream. Changing laws can affect your software. When you don't manage
requirements, feature creep can slow down and complicate your project.
Using RequisitePro
RequisitePro makes it easy to write and manage requirements. It is integrated with
Microsoft Word and is packaged with Word templates to help you get started quickly.
RequisitePro is designed to work for your entire team:
s
Analysts use RequisitePro to document and maintain requirements.
s
Developers use requirements to design architecture and write more detailed
specifications.
s
Testers use requirements to design tests and check test coverage.
s
Project leaders and managers use RequisitePro to plan project work based on
available resources (for example, time, budget, and personnel).
Starting with a Use Case
In Chapter 2, About This Tutorial, you saw the enhancement request that was entered
in response to your feedback. One of your team members has started work on the use
case corresponding to the enhancement request.