background image
<< Why Work with Use Cases | How Does RequisitePro Handle Requirements? >>
The RequisitePro toolbar
<< Why Work with Use Cases | How Does RequisitePro Handle Requirements? >>
68
Chapter 5 - Creating Requirements
The RequisitePro Word document appears and displays the Arrange Shipment use
case. This document is based on a template provided with RUP. (In Chapter 3, you
saw, and may have clicked on, a link to this template.)
The RequisitePro toolbar also appears (see Figure 19). This is a standard Microsoft
Word toolbar that can float or be anchored. The default setting for this toolbar is
floating.
Figure 19
Working with Use Case Documents Using RequisitePro
2
In the document, scroll to page 4,
Use Case Specification: Arrange Shipment
.
Text with double-underlining identifies use case requirements. Identified by the
prefix UC, use case requirements are high-level requirements that describe the
system's behavior.
3
Read the Brief Description and Flow of Events. Notice that the shipping date
feature was part of the original use case (it's at the bottom of the page and it starts
with "The warehouse...") but it has not yet been identified as a requirement.
This is a typical way of starting requirements work. You use the familiar
environment of Word to document your requirements. You use RequisitePro to
identify and elaborate on your project requirements. You also indicate which
requirements are related. RequisitePro then tracks how changes to the system
affect your requirements and how changes to requirements affect your system.
4
If Rose is not installed on your computer, minimize Word and RequisitePro. If
Rose is installed, quit Word, then click No if prompted to save your changes. Also
quit RequisitePro. When prompted to close the project, click Yes.