background image
<< The RequisitePro toolbar | Working with a Use Case Diagram >>
How Does RequisitePro Handle Requirements?
<< The RequisitePro toolbar | Working with a Use Case Diagram >>
Starting with a Use Case
69
How Does RequisitePro Handle Requirements?
RequisitePro is both document-centric and database-centric and relies on the
strengths of the following:
s
The document features provide a familiar environment (Word) for creating
descriptions and communicating your work to project stakeholders. You can start
a requirements document either by importing existing Word files into
RequisitePro or by working in a RequisitePro Word document.
s
The database features help you organize your requirements, prioritize your work,
track requirements changes, and share information with other Rational tools. To
work with database features, you use RequisitePro Views.
In the use case document, the requirements text (with double-underlined characters
by default) exists in the document. The database also stores the requirements text,
along with attributes (such as priority and assigned-to) that help track the requirement.
Later in this chapter, you will work with RequisitePro database features.
Learning More About Use Cases
You frequently start requirements work by developing use cases. When working with
use cases, you work in Rose to incorporate the use case in your visual model, then
work in RequisitePro to add textual descriptions, attributes, and links.
RUP describes how to write a use case. It includes details about the artifacts that you
need to get started and the artifacts that result from the activity. It then provides a
step-by-step description of the activity, and offers a template for creating use cases.
This template provides guidelines about how to structure a use case. You can use it as
a starting point for defining use case requirements. We recommend that you use this
template, or another template designed by your group, to ensure consistency and
completeness in use case development. This makes it easy for all stakeholders to
locate and understand important project information.