Manage Your Requirements
with RequisitePro
Kim Werner
Ajilon Consulting
[email protected]
Agenda
• Before You Start - Setting Expectations
– Requirement Definition
• Types, relationships, attributes
– Requirement Capture
• Writing requirements, Document Outlines
– Design Traceability Tree
• RequisitePro Overview
• Demo
Requirement Definition
• A condition or capability to which a system
must conform
• This can be derived or explicitly stated
• In essence, a requirement is something
important in a project that you want to
track
• Requirements can sometimes span
projects
Where in RUP does this fit?
Looking at the Workflow
Types of Requirements
• Not all requirements are the same
• Grouping like-minded requirement types
together can help organization
• For example:
– Stakeholder Request
- Feature
– Supplementary Specification - Use Case
– Business Rules
- Software
– Etc.
Requirement Relationships
• Requirements can have dependencies
– On another requirement of the same type
(Hierarchical)
• STRQ1 – Process Application
The system shall process an online application submitted by the client
– STRQ1.1 – Accept Payment
The system shall accept payment from the client via Debit, Credit Card, or
check
– STRQ1.2 – Fax Application
The system shall fax the content of the application to the telephone number
specified on the client’s application
• STRQ 2 – Assign Client Number
The system shall create a client number for the completed application
Requirement Relationships
• Requirements can have dependencies
– On a requirement of a different type (Traced)
• STRQ1 – Process Application
The system shall process an online application submitted by the client
– STRQ1.1 – Accept Payment
The system shall accept payment from the client via Debit, Credit Card, or
check
» FEAT1 – Validate Debit Payment
The system shall validate the Client’s Debit Card number from the
client’s bank
» FEAT2 – Display Card Error
The system shall display to the client any error identified when validating
the card number
– STRQ1.2 – Fax Application
The system shall fax the content of the application to the telephone number
specified on the client’s application
• STRQ2 – Assign Client Number
The system shall create a client number for the completed application
Requirement Relationships
• When organizing and
managing
requirements, view
the organization as a
pyramid
• 1 inch down, a mile
across
Supporting Use Case
System Boundary
STRQ
Supporting Features
FEAT
UC
SUPL
Supporting Non-Functional
Requirement Attributes
• Some requirements have unique things
about them. I.e. Priority, Status
• These things are captured using
requirement attributes
– Each attribute can have its own domain
values and defaults
• Priority:
High, Medium, Low
• Attributes values can be tracked
Requirement Writing
• Consists of 3 parts
– Short Name - Clear, Concise, Meaningful
– Requirement Text – Testable, Quantifiable
– Optional Context
Short Name
Requirement Text
• STRQ1 – Process Application
The system shall process an online application
submitted by the client. Online applications are
submitted through the company web site, or
sometimes sent as part of a batch.
Optional Context
Document Outlines
• Decide what kind of templates to use or
leverage
– RUP Templates, Custom Templates
• Determine what requirement types reside
in each template
• Where possible, choose shared templates
Design Traceability Tree
• Traceability trees are a pictorial view of
how requirement types relate to each
other
• Traceability trees vary by project
• They are used to help analyze impact to
requirement change
• Typically automated within a set of tools
Design Traceability Tree
Traceability Tree
Significant (Out of the Box)
STRQ
Legend
FEAT
STRQ
SUPL
UC
TERM
FEAT
- Feature
- Stakeholder Request
- Supplementary
- Use Case
UC
SUPL
Design Traceability Tree
Traceability Tree
CHART
Legend
SCOPE
STRQ
TERM
FEAT
CHART - Charter
FEAT - Feature
SCOPE - Scope
STRQ - Stakeholder Request
SUPL - Supplementary
UC
- Use Case
UC
SUPL
Design Traceability Tree
Traceability Tree
REF
CHART
SCOPE
STRQ
MEMO
Legend
ASMP - Assumption
BR
- Business Rule
CHART - Charter
DPR - Data Propagation
DTR - Data Transformation
FEAT - Feature
FSPEC - Functional Spec
REF
- Reference
SCOPE - Scope
STRQ - Stakeholder Request
SUPL - Supplementary
TSPEC - Technical Spec
UC
- Use Case
TERM
FEAT
UC
ASMP
BR
SUPL
Design Traceability Tree
Traceability Tree
REF
CHART
SCOPE
STRQ
MEMO
Legend
ASMP - Assumptions
BR
- Business Rule
CHART - Charter
DPR - Data Propagation
DTR - Data Transformation
FEAT - Feature
FSPEC - Functional Spec
REF
- Reference
SCOPE - Scope
STRQ - Stakeholder Request
SUPL - Supplementary
TSPEC - Technical Spec
UC
- Use Case
TERM
FEAT
UC
DPR
BR
DTR
FSPEC
ASMP
TSPEC
SUPL
Requirement Summary
• There are different types of requirements
• Requirements of the same type can have
parent-child hierarchical relationships
• Requirements of different types can be
traced from each other
• Requirement writing has multiple parts
• View Requirements as a Pyramid
• Traceability Trees help in Impact analysis
RequisitePro Overview
• A Requirements Management tool
• Maintains requirements in a combination
of file artifacts and within a database
repository
• Historically audits requirement revisions
• Import/Export capabilities to MS-Office
• Linkable to other tools
• Tracks project metrics and generates
reports
• Security enabled
RequisitePro Overview
• Deployment Strategies
– Consider Enterprise class RDMS for
concurrency – MS-Access is NOT a solution
– When using a WAN, consolidate file artifacts
on a single server
– Enforce using the tool to update – not direct
database update
– Leverage the RequisiteWeb interface
• Think Enterprise, Coordinate Locally
RequisitePro Overview
• How it all fits
Requirements
Repository
Change
Request
Repository
Testing
Repository
RequisitePro
Use Case
Model
TestManager
ClearQuest
Rose
RequisitePro Overview
• Identify what activities
to capture
• Determine artifacts to
reference to house
your requirements
RequisitePro Overview
• Iterate the requirement capture process
– Write the requirement
– Apply MS-Word style for readability
– Tag the requirement
– Capture known attribute values
– Organize the hierarchy
– THEN Trace (if applicable)
• After each step, review for clarity
• Don’t forget to archive after baseline
review
RequisitePro Overview
RequisitePro Overview
• Demo