Tool Mentor: Developing
a Vision Using Rational RequisitePro
Purpose
This tool mentor describes how to use Rational RequisitePro® to document
a project vision. The Vision document is a general statement of the core project's
requirements, and it provides the contractual basis for the technical requirements.
This section provides links to additional information related to this tool mentor.
Overview
The Vision document provides a high-level and sometimes contractual basis for
the technical requirements. There can also be a formal Requirements Specification.
The vision captures very high-level requirements and design constraints, to
give the reader an understanding of the system to be developed. It communicates
the fundamental "why's and what's" related to the project and is a
gauge against which all future decisions should be validated.
Tool Steps
To document the vision using RequisitePro:
- Create a Vision document
- Create requirements in
the Vision document
The Vision document contains the product features identified in the Activity:
Elicit Stakeholder Requests. If you create a RequisitePro project using
one of the default project templates (Use-Case, Traditional, or Composite),
your project already contains a Vision document in the Features and Vision package.
If your project does not contain a Vision document, perform the following procedure
to create one.
To create a Vision requirements document:
- Open the RequisitePro project.
- In the Explorer, select the package in which you want to place the Vision
document, and then click File > New > Document. The
Document Properties dialog box appears.
- Type a name, description, and file name for the document.
- In the Document Type list, select "Vision Document Type." Click OK. The outline for the Vision document opens in Microsoft® Word.
- Replace the default instructional text with project-specific information.
- Click RequisitePro > Document > Save.
For More Information
Refer to
the following topics in the RequisitePro online Help:
- Creating a RequisitePro project (Index: projects>creating)
- Creating requirements documents (Index: documents>creating)
Create requirements from product features outlined in the Product Features
section of the Vision document. This enables you to manage requirement attributes
in an Attribute Matrix and helps you track traceability links between product
features and software requirements.
To create requirements in the Vision document:
- In the Product Features section of the Vision document, select (highlight)
the text that defines the requirement.
- Do one of the following:
- Right-click and select New Requirement.
- Click RequisitePro > Requirement
> New.
The Requirement Properties dialog box appears.
- On the General tab, accept the feature (FEAT) requirement type and type a name for the requirement.
- Click the Attributes tab and set the Priority
attribute to one of the provided values (Must, Should, Could, Won't). It's a good
idea to record stakeholder priorities when you elicit stakeholder
requirement requests. (See Activity:
Elicit Stakeholder Requests.)
- Select the Origin attribute and select an entry that
represents the originator of that particular feature. This helps you keep
track of the requestors of specific product features, so that you know who
to contact if you need to clarify or negotiate a request.
- Click OK.
- You can repeat these steps for each product feature outlined in the
Product Features section of the Vision document. When you have finished,
click RequisitePro > Document > Save.
To view the requirements and attributes:
- In the RequisitePro window, select the package in which you want to create a view.
- Click File > New > View. The View Properties dialog
box appears.
- Type a name for the view, select the Attribute Matrix
view type, and select the FEAT requirement type, which you
used in your Vision document.
- Click OK. Review your feature requirements and their
attribute values.
For More Information
Refer to the following
topics in the RequisitePro online Help:
- Creating requirements in a document (Index:
requirements > creating)
- Assigning values to requirement attributes (Index: requirement
attributes > values, assigning)
- Creating a view (Index: views > creating views)
| |
|