requisitepro software requirement management tool a peresentation by: mojdeh jalali-heravi maryam...

RequisitePro

• Software Requirement Management Tool

A peresentation by:Mojdeh Jalali-HeraviMaryam Daneshi

Requirements Management Introducing RequisitePro Documenting Requirements Organizing Requirements Tracking Requirements Advanced Features

What is requirements management? a systematic approach to eliciting,

organizing, and documenting the requirements of a system

a process that establishes and maintains agreement between the customer and the project team on the changing requirements of a system.

Why is requirements management important?

projects must be delivered on time and on budget

they must address the client's needs

Requirements Management Skills

What should you consider when managing a project? What is the business problem you are trying to solve, and who has a stake in

its resolution?

What features are essential to a solution?

How can the proposed solution be described in language that can be understood by technical and non-technical people?

What are the available resources (time, people, money)?

How should requirements be prioritized?

What should you consider when managing a project? (cont.) How can one verify that the system will function as described and

perform with acceptable speed and efficiency?

How can dependency relationships between requirements be traced?

How can changes to the system be limited and negotiated so that the product can be completed and stakeholders remain engaged?

What is the procedure for reviewing and resolving changes to requirements?

What are the causes of project failure? a large percentage of projects do not

succeed.

Standish Group listed lack of user involvement and changing requirements and specifications as among the top 10 factors that most frequently contribute to project failure.

The Problems of Requirements Management

The Problems of Requirements Management (cont.)

Requirements are not always obvious and have many sources.

Requirements are not always easy to express clearly in words.

Many different types of requirements at different levels of detail must be managed.

The number of requirements can become unmanageable if not controlled.

Requirements are related to one another and to other deliverables of the process in a variety of ways.

The Problems of Requirements Management (cont.)

Requirements have unique properties or property values; they are neither equally important nor equally easy to meet.

Many interested and responsible parties are involved in a project, which means that requirements must be managed by cross-functional groups of people.

Requirements change. Requirements can be time-sensitive.

RequisitePro

A powerful, easy-to-use requirements management tool

Helps teams manage project requirements comprehensively, promotes communication and collaboration among team members

Reduces project risk

Why Use RequisitePro?

Team Collaboration and User Satisfaction

Flexibility Through the Web Component

Change Management

Comprehensive Process Support

Project Templates

RequisitePro provides the following project templates: Use-Case Template (using a use-case

methodology)Traditional Template (using standard software

requirements)Composite Template (a combination of the

Use Case and Traditional templates)

Example

Add a new template

A RequisitePro Project a project includes a database it can also include documents Included in the database :

document types glossary document, vision statement, use cases

requirement types categories of requirements such as features, use cases,

supplementary specifications and …

requirement attributes describe the requirements in terms of priority, status,

stability, and other characteristics that you define

Document Type

document types:Vision.

gives the overall view of the system: main characteristics, major features, key stakeholder needs, and key services provided.

Glossary. a tool to capture and define the terms used in the

project.

Document Type (cont.)

Use-case specification. a format to express functional requirements in sequence. A

sequence of actions a system performs that yields an observable result (a work output) of value to a particular actor.

Supplementary specification. captures any requirements that cannot be tied directly to any

specific use case, and especially many of the nonfunctional requirements and design constraints.

Test plan. describes the target-of-test (components, application,

system) and its goals; the stages of testing; and the types of testing that will be addressed by this plan.

Requirements

A requirement describes a condition or capability that a system must provide.

They contain: Name, Text, Tag, Attributes to provide specific details.

Requirements (cont.)

Requirements may be created in a document or in a view.

All requirements information is stored in the database.

Requirement Types

A requirement type defines descriptive and operational information associated with a requirement.

serves as a template for all requirements of the same type.

is useful for ensuring consistency and classifying or grouping similar requirements in a project.

View

a table (matrix ) an outline tree

create a view to display :requirement attributes (status and priority ) to show the relationships between

requirements.

View (cont.)

You can create three different kinds of views:

Attribute Matrix view displays all requirements of a specified type The requirements are listed in rows their attributes appear in columns helps you organize and prioritize requirements

View (cont.)

Traceability Matrix view help you manage the ripple effects caused by

a requirement change displays the relationships between two types

of requirements or requirements of the same type

View (cont.)

Traceability Tree view help you manage the ripple effects caused by

a requirement change displays the chain of traceability to or from

requirements of a specified type

Example

Creating Requirements

Tracking Requirements

Topics to be covered: Managing changing requirements Setting traceability Managing change through traceability views Using suspect links Establishing hierarchy Querying (filtering and sorting)

Managing Changing Requirements

includes (but is not limited to) the following activities:

Keeping track of the history of each requirement

Establishing traceability relationships between related requirements

Maintaining version control

Setting Traceability

a directional relationship between any two requirements ReqA --> ReqB ReqA <-- ReqB

RequisitePro's Traceability

helps assure the quality and completeness of your products

Link abstract requirements trace from use cases to the features

requested by stakeholders can define the dependencies among

requirements of the same type or different types

Managing Change Through Traceability Views Traceability Matrix

Traceability Tree

Example

Create and clear traceability relationships from a matrix view

Example

Create traceability relationships from the Word document

Using Suspect Links

the relationship between the requirements requires attention

RequisitePro signals this suspect condition in a Traceability Matrix or Traceability Tree

Using Suspect Links (cont.)

when either of the requirements has been modified after the initial traceability relationship has been established.

In a Traceability Tree

In an Attribute Matrix with an "(s)" in the Traced to or Traced From columns

Example

Create a suspect relationship

Example

Create suspect relationships in an Attribute Matrix view

Establishing Hierarchy

hierarchical requirement Hierarchical relationships Child requirement dependency

Example

Create hierarchical requirements in a document

Example

Change the parent of a child requirement

Querying (Filtering and Sorting)

After creating a view

Filtering restricts the information being displayed sorting determines the order in which

information is displayed

by applying query criteria to the attributes

Example

Create a query in an Attribute Matrix

Advanced Features

Archiving2 ways

Creating baselinesbaseline identifies activities and one version

of every element visible in one or more components. It should be created at project milestones.

Rational Unified Change Management object

Archiving Example

Create a version from current project

Advanced Features (cont.)

Cross-project traceabilityestablish traceability between requirements

that reside in different projects Customizing document and requirement

types and attributes

Project Properties

Project Properties (cont.)


Deleting requirementsDelete-Unmark Delete-Remove keep the requirement but modify the

requirement attributes (recommended)


Discussion groupscomment and raise issues and questions to a

group of project users


Integrations Rational Rose for object-oriented analysis, modeling,

design, and construction ClearQuest for team-based change request management TestManager for management of software testing

assessments ClearCase LT for configuration management SoDA for project reporting and documentation Rational Unified Process for incorporation of software

development best practices.


Offline authoringedit a requirements document outside of

RequisitePro Requirement Metrics

report statistics on requirement text, attributes, relationships, and revisions

Resources

RequisitPro tutorial

Rational® RequisitePro® User’s Guide VERSION: 2002.05.20

requisitepro software requirement management tool a peresentation by: mojdeh jalali-heravi maryam...

Documents