“Rational RequisitePro”Software Tool

By: Shayma’ YaqoubSecond Semester

2007-2008

What is “Rational Requisitepro” ??

Rational Requisitepro is a Rational Requirements Management Tool.

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”?RequisitePro is used for managing requirements to deliver project on time, on budget, and on target.

RequisitePro helps projects succeed by giving teams the ability to manage all project requirements comprehensively and facilitating team collaboration and communication.

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

The main concept is “Requirements”

1. Project

2. Documents

3. Relationships

4. Views

٤/39

The ProjectIn Rational RequisitePro, the concept of a project is used to provide the GROUNDWORK for organizing and effectively managing requirements. 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.ONLY ONE project can be opened at a time. Numerous Requirement Documents can belong to a project; that means different users can edit different documents simultaneously.

٥/39

Project Templates

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 TemplateUse Case Template

To create new project…

٧/39

٨/39

٩/39

١٠/39

Working with Document TypesA Document Type is a document structure; based on document outlines.

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? A requirement describes a condition or capability that a system must provide.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.All requirements information are stored in the database.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.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??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?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

Case Study: ClassicsCD.com Web Shop SystemTHE 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.

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 system3. An order processing system

(1)

١٩/39

Case Study: Modify the Vision Document

Go to: Features and Vision folder > Vision Document file

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.

(2)

٢٠/39

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.

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.

Other Product features:1. Standard: ClassicsCD applications must comply with common

Web user interface guidelines.

Case Study: Requirements in Vision Document

(2…)

٢١/39

Case Study:Adding Other RequirementsGo to “Requirements in Vision Document” Slide to create these Requirements.Create the Supplementary Package and add these Supplementary Requirements: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.

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.

(3)

٢٢/39

Case Study:Adding Other Requirements

Performance:1. The response time for CD queries shall take less than 5 seconds.

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.

(3…)

٢٣/39

The Use-Case

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.A Use-Case documents Functional Requirements from the perspective of the user.Each Use-Case is described by its Flow (flow of events); the Basic flow and/or Alternative flows.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 PackageGo to any Package > New > Package

or > Document (Go to slide 27)

Modify the properties of the Document that you create to be a Use-Case Specification Document. (Go to slide 28)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

Case Study:Modifying the Use-Cases PackageIn 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.These Use-Cases are:

1. Arrange Shipment2. Check Order Status3. Purchase CD4. Shop for CD

(4)

٢٩/39

Case Study:Modify The Use-Case “Arrange Shipment” Document

Name: Arrange Shipment.Description: In this use case the system interacts with the Warehouse System to ship an item that has been purchased by a Shopper.Flow of Events:

Basic Flow:i. BEGIN ii. SEND ORDER TO WAREHOUSE SYSTEMiii. WAREHOUSE SYSTEM RESPONDS

(4…)

٣٠/39

Case Study:Continue…Modify The Use-Case “Arrange Shipment” Document

Alternative Flows:i. INVENTORY NOT AVAILABLEii. INVALID INFORMATIONiii. NO RESPONSE

PreCondition: ORDER PLACED

PostCondition: SUCCESS

(4…)

٣١/39

The Views (The Traceability Matrix or Tree)In Rational RequisitePro; the Views are tables or outline trees usedto display requirements and their attributes or the traceability relationships between different requirement types.A view is an environment for analyzing all requirements.

Note: You can have multiple views open at one time.

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 ViewThe Traceability Matrix and Traceability Tree views display traceability relationships, and the Traced-to or Traced-from attributes appear in the Attribute Matrix. A traceability relationship is displayed as suspect when you make a change to a requirement.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

Case Study:Create the Traceability Matrix and Tree

After Modifying traceability properties of all requirements, 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.Add Traceability Trees, to show the Traceability Relations (to and from relations)

(5)

٣٩/39