“Rational RequisitePro”

Software Tool

By: Shayma’ Yaqoub

Second Semester
2007-2008
What is “Rational Requisitepro” ??
z Rational Requisitepro is a Rational
Requirements Management Tool.

z Rational Requisitepro Main Characteristics:

1. Provide Templates as packages, queries,
and documents; to document a project
requirements.
2. It is easy to Attach project requirement
documents with other rational tools as UML,
RUP…
٢/39
 Why Using “Rational RequisitPro”?
z RequisitePro is used for managing requirements to deliver
project on time, on budget, and on target.

z RequisitePro helps projects succeed by giving teams the

ability to manage all project requirements comprehensively
and facilitating team collaboration and communication.

z RequisitePro enables you to organize, prioritize, trace

relationships, and easily track changes to your requirements,
because of the program’s unique architecture and dynamic
links make it possible for you to move easily between the
requirements in the database and their presentation in Word
documents.

٣/39
 Key Concepts in RequisitePro

z The main concept is “Requirements”

1. Project

2. Documents

3. Relationships

4. Views

٤/39
 The Project
z In Rational RequisitePro, the concept of a project is
used to provide the GROUNDWORK for organizing and
effectively managing requirements.
z Each project includes the following: a database,
documents, packages, document types, requirements,
requirement types, attributes, attribute values,
discussions, traceability relationships, saved personal
and project-wide views, revision histories, and security
information.
z ONLY ONE project can be opened at a time.
z Numerous Requirement Documents can belong to a
project; that means different users can edit different
documents simultaneously.
٥/39
Project Templates
z Three Project Templates are shipped with
RequisitePro:
1. Use-Case Template: Use cases are
particularly applicable to object-oriented
software design using the Unified Modeling
Language and for applications that are user-
intensive. (Use-Case Definition)
2. Traditional Template: This template includes
a traditional Software Requirements
Specification outline rather than use cases.
3. Composite Template.

٦/39
Start using “Rational RequisitePro”

Program >
Rational Software >
Rational RequisitePro >
Use Case Template

To create new
project…

٧/39
٨/39
٩/39
١٠/39
 Working with Document Types
z A Document Type is a document structure; based on
document outlines.

z The common Document Types are:

¾ Vision: overall view of the system.

¾ Glossary.
¾ Test Plan.

١١/39
Also…
¾ * Requirements Management Plan: This document
sets out guidelines for establishing the requirements
documents, types, attributes, and traceability in order to
manage the project requirements.
¾ * Use-Case Specification. Use cases serve as a format
to express functional requirements in sequence. Use
cases are especially good at documenting functional
software requirements.
¾ * Supplementary Requirement Specification. This
document captures any requirements that cannot be tied
directly to any specific use case, and especially many of
the nonfunctional requirements and design constraints.

١٢/39
 What is the Requirement?
z A requirement describes a condition or capability that a system
must provide.
z Requirements contain a name, text, and they are qualified with
attributes to provide specific details.
Note: Attributes describe a requirement in terms of user-defined
characteristics or properties, such as cost, priority, and status.
z All requirements information are stored in the database.
z After a requirement has been created, it can be modified, moved,
and copied within the project and traced to and from other
requirements in the same project or across projects.
z By organizing and managing the requirement, you improve your
chances of completing your project on time and on budget and
delivering a product that the client still wants.

١٣/39
Types of Requirements as follows:
1. Functional requirements: feature sets, capabilities, and
security.
2. Usability requirements: human factors, aesthetics,
consistency in the user interface, online and context-
sensitive help, wizards and agents, user documentation,
and training materials.
3. Reliability requirements: frequency and severity of
failure, recoverability, predictability, accuracy, mean time
between failure.
4. Performance requirements: conditions imposed on
functional requirements.
5. Supportability requirements: testability, extensibility,
adaptability, maintainability, compatibility, configurability,
serviceability, installability, and localizability.

١٤/39
 How To Add Requirements??
z Many Ways to add Requirements:
1. In a Document.
2. In the Explorer. (The Package)
3. In a View. (Traceability Matrix or Tree)
4. From Tables.
Note: The requirement and its attribute values are not
saved to the project database until you save the
document.
You can use Create Requirement Button in any
Ways of adding requirements.

١٥/39
 Creating Requirement &How it Changed?
z When you create a requirement in a document, RequisitePro performs
the following operations:
¾ The selected requirement text information is bracketed with
bookmarks.
¾ And the following Information is associated with the new requirement:
1. Requirement tag identifier. A requirement tag consists of a prefix
and a number.
2. Color and style format. If the requirement type has color and style,
the new requirement is formatted with these settings.
3. Requirement attributes. The new requirement is associated with the
attributes established for the requirement type.

Note: Attributes can be viewed in the Requirement Properties dialog box.

١٦/39
Requirement Properties Window

١٧/39
١٨/39
 (1)
Case Study:
ClassicsCD.com Web Shop System
z THE SYSTEM: The ClassicsCD.com Web Shop system is an
application available on the World Wide Web.
ClassicsCD.com is intended to provide a new channel of
sales for ClassicsCD, to supplement the existing bricks-and-
mortar retail operation.

z THE PRODUCT: ClassicsCD system wants to integrate its

Web shop with the corporation’s order processing and
fulfillment system. We envision a smaller scale supply-chain
management system that integrates the Web application with
all the stores, suppliers, and warehouses. This includes the
following:
1. A Home Shopping e-commerce system
2. A warehouse system
3. An order processing system
١٩/39
 (2)
Case Study:
Modify the Vision Document

z Go to:
Features and Vision folder > Vision Document file
z Add:

The descriptive part of the system as vision and

objectives, users description, and the problem
domain.
Note: You can add some Requirements in this part as
system or product features, organizational standards
and environmental conditions.

٢٠/39
 (2…)
Case Study:
Requirements in Vision Document
z ClassicsCD.com Web Shop system features:
1. Secure payment method.
2. Easy browsing for available titles.
3. Ability to search for CDs by multiple criteria.
4. Ability to check the status of an order.
z ClassicsCD.com Administration System features:
1. Ability to add/remove CDs available for sale.
2. Ability to check on Shopper orders.
3. Maintain Shopper information.
z Other Product features:
1. Standard: ClassicsCD applications must comply with common
Web user interface guidelines.
٢١/39
 (3)
Case Study:
Adding Other Requirements
z Go to “Requirements in Vision Document” Slide to create these
Requirements.
z Create the Supplementary Package and add these Supplementary
Requirements:
z Usability:
Interface Ease of Use:
1. The system shall follow standard interface guidelines.
2. The system shall be useable by users familiar with basic English.
Training: Training shall be developed for all aspects of the system.
z Reliability
1. The system shall operate in a fault tolerant manner 7 x 24.
2. The system shall support 1,000 concurrent users querying for CDs.
3. The system shall support an inventory of 1,000,000 CDs.
٢٢/39
 (3…)
Case Study:
Adding Other Requirements
z Performance:
1. The response time for CD queries shall take less than 5 seconds.

z Supportability:
1. Application Standards:The system shall be compliant with Internet
Explorer and Netscape Navigator as stated in the Microsoft
Internet Explorer and Netscape Navigator compatibility
requirements documents.

٢٣/39
 The Use-Case
z A Use-Case is a sequence of actions or events which a
system performs that yields an observable result of
value to a particular actor.
z A Use-Case documents Functional Requirements from
the perspective of the user.
z Each Use-Case is described by its Flow (flow of
events); the Basic flow and/or Alternative flows.
z Each Use-Case has its own special requirements,
preconditions and/or postconditions.

٢٤/39
Use Case Diagram Example

Go Back to “Project Template” slide ٢٥/39

Defining Use-Cases in Use-Case Package
z Go to any Package > New > Package
or > Document
(Go to slide 27)
z Modify the properties of the Document that
you create to be a Use-Case Specification
Document. (Go to slide 28)
z Modify the contents of the Use-Case
Document to contain description of the Use-
Case, all details of the Basic Flow and
Alternative Flows of Use-Case, and
Conditions that should be followed.
26/39
GO BACK ٢٧/39
GO BACK ٢٨/39
 (4)
Case Study:
Modifying the Use-Cases Package
z In this case study there are (4) Use-Cases each
of them has its own package which contains the
Use-Case specification document, the events of
basic and alternative flows, special
requirements, and all conditions.
z These Use-Cases are:
1. Arrange Shipment
2. Check Order Status
3. Purchase CD
4. Shop for CD
٢٩/39
 (4…)
Case Study:
Modify The Use-Case “Arrange Shipment” Document
z Name: Arrange Shipment.
z Description: In this use case the system interacts with
the Warehouse System to ship an item that has been
purchased by a Shopper.
z Flow of Events:

Basic Flow:
i. BEGIN

ii. SEND ORDER TO WAREHOUSE SYSTEM

iii. WAREHOUSE SYSTEM RESPONDS

٣٠/39
Case Study: (4…)
Continue…
Modify The Use-Case “Arrange Shipment” Document
Alternative Flows:
i. INVENTORY NOT AVAILABLE
ii. INVALID INFORMATION
iii. NO RESPONSE

z PreCondition: ORDER PLACED

z PostCondition: SUCCESS

٣١/39
 The Views (The Traceability Matrix or Tree)
z In Rational RequisitePro; the Views are tables or outline trees used
to display requirements and their attributes or the traceability
relationships between different requirement types.
z A view is an environment for analyzing all requirements.
Note: You can have multiple views open at one time.

z You can create THREE kinds of views:

1. An Attribute Matrix view, which displays all requirements and their attributes
within a specified type.
2. A Traceability Matrix view, which displays the relationships between
requirements of two types.
3. A Traceability Tree view, which displays the chain of traceability through the
project requirements.

٣٢/39
Traceability in a View
z The Traceability Matrix and Traceability Tree
views display traceability relationships, and the
Traced-to or Traced-from attributes appear in
the Attribute Matrix.
z A traceability relationship is displayed as
suspect when you make a change to a
requirement.
z Arrows are used to indicate direct traceability
relationships in the Traceability Matrix and
Traceability Tree views.
Example: If the arrow points from A to B, then the
following two statements are true: A is traced to
B and B is traced from A.
٣٣/39
٣٤/39
٣٥/39
The Traceability Matrix

٣٦/39
Traceability Property of the Requirements

٣٧/39
٣٨/39
 (5)
Case Study:
Create the Traceability Matrix and Tree
z After Modifying traceability properties of all
requirements,
z Add Traceability Matrix that connect all the
Requirements (Supplementary and placed
in Vision document) with Use-Cases, and
that show traced to and from relationships.
z Add Traceability Trees, to show the
Traceability Relations (to and from
relations)
٣٩/39