Introduction to RM Using RequisitePro

Education & Research

Contents
• Why RequisitePro?
• What are the components of Requisite Pro?
• The concept of “requirement” in RequisitePro
• How to use RequisitePro?
• Summary
• Q&A

2
Why RequisitePro?
• RequisitePro is a powerful, easy-to-use RM tool that helps teams manage
project requirements comprehensively, promotes communication and
collaboration among team members, and reduces project risk.

• Requirements are itemized and stored in a database

• Team based repository
• Works with MS Word
• Requirement Attributes
• Impact analysis and change management
• Traceability matrix and traceability tree
• Discussions

3
Concept of “Requirement” in Req Pro

• The term “Requirement” is overloaded.

• The term requirement in Req Pro encompasses various types of

requirements
– business requirements
– software requirements
– supplementary requirements like performance, usability requirements, test
cases, sections of design docs.

• Essentially, anything that you want to trace should be created as a

requirement

4
Concept of “Requirement” in Req Pro (Contd …)
E-Mails End Users
Documents Stakeholder Requests Management
Meetings Marketing Users

Features

Supplementary
Use Cases Requirements

5
Components of RequisitePro

6
RequisitePro Shell

7
The Tool Palette

8
RequisitePro Menu in Word Doc

9
How to use Req Pro

• Create a RequisitePro project

• Create Requirement types and requirement attributes
• Create and customize document types
• Create, import, and revise requirements, attributes, and requirement
documents
• Define hierarchies of requirements
• Establish traceability
• Manage changing requirements through views, queries, and metrics

10
1. Creating a project
• Choose a template
(blank, composite, UC) or
import structure of an
existing project

• Name the project

• Choose Directory

• Choose Database(SQL
Server, ORACLE,
ACCESS)

11
2. Create Requirement Types & Attributes

• Requirement Types
– Feature requirement
type
– Use Case requirement
type
– Supplementary
requirement type
– Glossary requirement
type

• Requirement Attributes
– Status
– Priority
– Stability
– Risk
– Difficulty

12
3. Create and customize document types

• Document types
– Vision Document
– Use case
document
– Glossary document
– Test case
document

13
4. Create, import, and revise requirements,
attributes, and requirement documents
• Creating requirements using RequisitePro

• Importing requirements from a word document

– Manually identify the requirements
– Use of key word like “should”, “must”, etc

• Committing requirements to database

14
 5. Define hierarchies of requirements
• Create parent
• Create child
• Re-parenting
requirements

15
6. Establish Traceability
• Create traceability

– Trace to

– Trace from

– Suspect Relationships: A relationship between requirements becomes

questionable or suspect if Requisite Pro detects that one of the requirements
in the relationship has been modified.

16
6. Establish Traceability (Contd..)

17
Attribute Matrix

18
7. Manage Changing Requirements Through
Views, Queries, and Metrics
• Keeping track of the history of each requirement

• Establishing traceability relationships between related requirements

• Maintaining version control

19
Requirement Metrics
• Requirement Metrics provides project managers / analysts with statistics
concerning a RequisitePro project’s requirement attributes, relationships, and
revisions. These are displayed in Microsoft Excel.

• You can use Requirement Metrics to manage requirements by evaluating:

– the progress of the project
– priorities, workloads, and deadlines
– the addition of new requirements
– changing or unstable requirements
– approved and incorporated features

20
Requirement Metrics (Contd …)

21
How to use Req Pro – Points covered

• Create a Requisite Pro project

• Create Requirement types and requirement attributes
• Create and customize document types
• Create, import, and revise requirements, attributes, and requirement
documents
• Define hierarchies of requirements
• Establish traceability
• Manage changing requirements through views, queries, and metrics

22
Other Features
• Taking the requirements doc offline

• Discussions
– Can create and view the discussion on a particular document, requirement, etc

• The security scheme lets you define:

– Read/update/create/delete rights for document types
– Update/create/delete rights for requirement types
– Update/create/delete rights for requirement name, text, and attributes
– Update rights for requirement attribute values, and
– Read/mark suspect/clear suspect/create/delete rights for traceability
relationships

23
Summary

• Requirements are treated as entities, not as paragraphs in a document

• Requirement hierarchies are clearly established

• Traceability matrix is not a static artifact which is only updated but, not
used. Traceability can be established and suspects marked. Dynamic in
nature.

• Requirement metrics are captured

• Can query on requirements

• Attributes are defined for each requirement

• Helps prioritize the requirements

• Can integrate with Rose

24
Thank You