rational requisitepro2007-2008

8/7/2019 Rational RequisitePro2007-2008

1/39

Rational RequisiteProSoftware Tool

By: Shayma YaqoubSecond Semester

2007-2008


2/39

What is Rational Requisitepro ??

Rational Requisitepro is a RationalRequirements Management Tool.

Rational Requisitepro Main Characteristics:1. Provide Templates as packages, queries,

and documents; to document a projectrequirements.

2. It is easy to Attach project requirementdocuments with other rational tools as UML,RUP

/39


3/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 theability to manage all project requirements comprehensively

and facilitating team collaboration and communication.

RequisitePro enables you to organize, prioritize, tracerelationships, and easily track changes to your requirements,

because of the programs unique architecture and dynamiclinks make it possible for you to move easily between therequirements in the database and their presentation in Worddocuments.

/39


4/39

Key Concepts in RequisitePro

The main concept is Requirements

1. Project

2. Documents

3. Relationships4. Views

/39


5/39

The ProjectIn Rational RequisitePro, the concept of a project is

used to provide the GROUNDWORK for organizing andeffectively managing requirements.Each project includes the following: a database,documents, packages, document types, requirements,

requirement types, attributes, attribute values,discussions, traceability relationships, saved personaland project-wide views, revision histories, and securityinformation.

ONLY ONE project can be opened at a time.Numerous Requirement Documents can belong to aproject; that means different users can edit differentdocuments simultaneously.

/39


6/39

Project Templates

Three Project Templates are shipped withRequisitePro:1. Use-Case Template: Use cases are

particularly applicable to object-oriented

software design using the Unified ModelingLanguage and for applications that are user-intensive. ( Use-Case Definition )

2. Traditional Template: This template includesa traditional Software RequirementsSpecification outline rather than use cases.

3. Composite Template .

/39


7/39

Start using Rational RequisitePro

Program >Rational Software >Rational RequisitePro >

Use Case Template Use Case Template

To create newproject

/39


8/39

/39


9/39

/39


10/39

/39


11/39

Working with Document Types

A Document Type is a document structure; based ondocument outlines.

The common Document Types are:

Vision : overall view of the system.Glossary .Test Plan .

/39


12/39

Also

* Requirements Management Plan : This documentsets out guidelines for establishing the requirementsdocuments, types, attributes, and traceability in order tomanage the project requirements.* Use-Case Specification . Use cases serve as a formatto express functional requirements in sequence. Usecases are especially good at documenting functionalsoftware requirements.

* Supplementary Requirement Specification . Thisdocument captures any requirements that cannot be tieddirectly to any specific use case, and especially many of the nonfunctional requirements and design constraints.

/39


13/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 withattributes 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 anddelivering a product that the client still wants.

/39


14/39

Types of Requirements as follows:

1. Functional requirements : feature sets, capabilities, andsecurity.

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 timebetween failure.

4. P erformance requirements : conditions imposed onfunctional requirements.

5. S upportability requirements : testability, extensibility,adaptability, maintainability, compatibility, configurability,serviceability, installability, and localizability.

/39


15/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


16/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 withbookmarks.And the following Information is associated with the new requirement:

1. Requirement tag identifier. A requirement tag consists of a prefixand 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 theattributes established for the requirement type.

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

/39


17/39

Requirement Properties Window

/39


18/39

/39


19/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 itsWeb shop with the corporations order processing andfulfillment system. We envision a smaller scale supply-chainmanagement system that integrates the Web application withall the stores, suppliers, and warehouses. This includes thefollowing:

1. A Home Shopping e-commerce system2. A warehouse system3. An order processing system

(1)

/39


20/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 problemdomain.

Note: You can add some Requirements in this part assystem or product features, organizational standards

and environmental conditions.

(2)

/39


21/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 commonWeb user interface guidelines.

Case Study:Requirements in Vision Document

(2 )

/39


22/39

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

Reliability1. 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


23/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 InternetExplorer and Netscape Navigator as stated in the MicrosoftInternet Explorer and Netscape Navigator compatibilityrequirements documents.

(3 )

/39


24/39

The Use-Case

A Use-Case is a sequence of actions or events which asystem 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


25/39

Use Case Diagram Example

Go Back to Project Template slide /39


26/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 SpecificationDocument. ( 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 andAlternative Flows of Use-Case, andConditions that should be followed.

26/39


27/39

GO BACK /39


28/39

GO BACK /39


29/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 theUse-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


30/39


31/39


32/39

The Views (The Traceability Matrix or Tree )In Rational RequisitePro; the Views are tables or outline trees used

to display requirements and their attributes or the traceabilityrelationships 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 betweenrequirements of two types.3. A Traceability Tree view, which displays the chain of traceability through the

project requirements.

/39


33/39

Traceability in a ViewThe Traceability Matrix and Traceability Tree

views display traceability relationships , and theTraced-to or Traced-from attributes appear inthe Attribute Matrix.A traceability relationship is displayed as

suspect when you make a change to arequirement.Arrows are used to indicate direct traceabilityrelationships in the Traceability Matrix andTraceability Tree views.

Example: If the arrow points from A to B, then thefollowing two statements are true: A is traced toB and B is traced from A .

/39


34/39

/39


35/39

/39


36/39

The Traceability Matrix

/39


37/39

Traceability Property of the Requirements

/39


38/39

/39


39/39

Case Study:Create the Traceability Matrix and Tree

After Modifying traceability properties of allrequirements,Add Traceability Matrix that connect all the

Requirements (Supplementary and placedin Vision document) with Use-Cases, andthat show traced to and from relationships.

Add Traceability Trees , to show theTraceability Relations (to and fromrelations)

(5)

/39