advertisement

Rational Requisite Pro - Advanced (http://www.geektester.blogspot.com)

100 %
0 %
advertisement
Information about Rational Requisite Pro - Advanced (http://www.geektester.blogspot.com)

Published on February 17, 2008

Author: raj.kamal13

Source: slideshare.net

Description

Rational Requisite Pro - Advanced Training

http://www.geektester.blogspot.com/
advertisement

Rational Requisite Pro - Requirement Management [email_address] www.itest.co.nr

Courseware Information This session covers Requirement Management Introducing Requisite Pro, Documenting Requirements, Organizing Requirements, Tracking Requirements, Advanced Features and Additional Information

This session covers Requirement Management

Introducing Requisite Pro, Documenting Requirements, Organizing Requirements, Tracking Requirements, Advanced Features and Additional Information

Course Objective & Outline After completing this course, you will be able to user key features of Requisite Pro that will help you to manage project successfully. Course Flow: 4. Organizing Requirements 2. Introducing Requisite Pro 3. Documenting Requirements 5. Tracking Requirements 1. Requirement Mgt 6. Advanced Features 7. Additional Information

After completing this course, you will be able to user key features of Requisite Pro that will help you to manage project successfully.

Course Flow:

Requisite Pro : Overview Requirements Management: provides a definition of requirements management, an explanation of why it is important Introducing RequisitePro: describes the components of the software. Usage of the templates provided with the program to create a project. Documenting Requirements: explains how you can document your requirements in. How to use the templates to create documents and to create requirements within these documents.

Requirements Management: provides a definition of requirements management, an explanation of why it is important

Introducing RequisitePro: describes the components of the software. Usage of the templates provided with the program to create a project.

Documenting Requirements: explains how you can document your requirements in. How to use the templates to create documents and to create requirements within these documents.

Requisite Pro : Contd.. Organizing Requirements: explains how you can use RequisitePro to organize and describe requirements and to view them in table form with various query and sorting options that you choose. Tracking Requirements: shows you how you can use specific features of RequisitePro to establish and track relationships among your requirements. Advanced Features: lists several features that are helpful for advanced users of RequisitePro. Additional Information: provides links to other sources of information.

Organizing Requirements: explains how you can use RequisitePro to organize and describe requirements and to view them in table form with various query and sorting options that you choose.

Tracking Requirements: shows you how you can use specific features of RequisitePro to establish and track relationships among your requirements.

Advanced Features: lists several features that are helpful for advanced users of RequisitePro.

Additional Information: provides links to other sources of information.

1.0 Requirement Management What is requirements management? 1) Agree on a common vocabulary 2) A systematic approach to eliciting, organizing, and documenting the requirements of a system. 3) Maintains agreement between the customer and the project team on the changing requirements of a system. Why is requirements management important? 1) To meet deadlines and on budget 2) Organizing and tracking helps to manage the requirement changes

What is requirements management?

1) Agree on a common vocabulary

2) A systematic approach to eliciting, organizing, and documenting the requirements of a system. 3) Maintains agreement between the customer and the project team on the changing requirements of a system.

Why is requirements management important?

1) To meet deadlines and on budget

2) Organizing and tracking helps to manage the requirement changes

1.0 Requirement Management – Contd.. What are the causes of project failure? 1) Exceeding Budget 2) Run past their deadline 3) Abandoned midway 4) Completed on time but not valuable 5) Lack of stakeholders involvement. RequisitePro offers an easy-to-use tool to manage changing requirements, thereby increasing your chances of delivering a product that your client wants and doing so in a timely manner.

What are the causes of project failure?

1) Exceeding Budget

2) Run past their deadline

3) Abandoned midway

4) Completed on time but not valuable

5) Lack of stakeholders involvement.

RequisitePro offers an easy-to-use tool to manage changing requirements, thereby increasing your chances of delivering a product that your client wants and doing so in a timely manner.

1.0 Requirement Management – Contd.. What should you consider when you manage a project? 1) What is the business problem and who has a stake in its resolution? 2) What features are essential to a solution? 3) How can the proposed solution be described in language that can be understood by technical and non technical people? 4) What are the available resources (time, people, money)? 5) How can you trace dependency relationships between requirement 6) What is the procedure for reviewing and resolving changes to requirements?

What should you consider when you manage a project?

1) What is the business problem and who has a stake in its resolution? 2) What features are essential to a solution? 3) How can the proposed solution be described in language that can be understood by technical and non technical people? 4) What are the available resources (time, people, money)? 5) How can you trace dependency relationships between requirement

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

2.0 Introducing RequisitePro Objective: To create a project using the templates provided with RequisitePro. Topics covered: Working in RequisitePro Working with requirements documents Organizing and tracking requirements· Creating a RequisitePro project RequisitePro is a powerful, easy-to-use requirements management tool that helps teams manage project requirements comprehensively, promotes communication and collaboration among team members, and reduces project risk.

Objective: To create a project using the templates provided with RequisitePro.

Topics covered:

Working in RequisitePro

Working with requirements documents

Organizing and tracking requirements·

Creating a RequisitePro project

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

2.0 Introducing RequisitePro – Contd.. Features: - Power of a database and Microsoft Word - Robust architecture, maintain dynamic linking to the database - Powerful sort capabilities - Powerful query capabilities. - Easy organize and prioritize the requirements - Real time impact analysis - change history for each requirement. - Integration with other Rational Suite products.

Features:

- Power of a database and Microsoft Word

- Robust architecture, maintain dynamic linking to the database

- Powerful sort capabilities

- Powerful query capabilities.

- Easy organize and prioritize the requirements

- Real time impact analysis

- change history for each requirement.

- Integration with other Rational Suite products.

2.0 Introducing RequisitePro – Contd.. Working with requirements documents - A RequisitePro toolbar appears when you open Word in RequisitePro, allowing you to manage requirements documents. You can click the RequisitePro menu to open a document, create or modify requirements, or open a view. Organizing and tracking requirements: - Query function for sorting and filtering requirements using views. - Relationship between requirement and other requirements using views - View displays requirements in Table (Matrix) or an outline tree. - Views can be used to display requirement attributes.

Working with requirements documents

- A RequisitePro toolbar appears when you open Word in RequisitePro, allowing you to manage requirements documents. You can click the RequisitePro menu to open a document, create or modify requirements, or open a view. Organizing and tracking requirements:

- Query function for sorting and filtering requirements using views.

- Relationship between requirement and other requirements using views

- View displays requirements in Table (Matrix) or an outline tree.

- Views can be used to display requirement attributes.

2.0 Introducing RequisitePro – Contd.. Three kind of views: 1. Attribute Matrix view The requirements of a specified types are listed in rows, and their attributes appear in columns 2. Traceability Matrix view displays the relationships between two types of requirements or requirements of the same type. 3. Traceability Tree view displays the chain of traceability to or from requirements of a specified type.

Three kind of views:

1. Attribute Matrix view

The requirements of a specified types are listed in rows, and their attributes appear in columns

2. Traceability Matrix view

displays the relationships between two types of requirements or requirements of the same type.

3. Traceability Tree view

displays the chain of traceability to or from requirements of a specified type.

2.0 Introducing RequisitePro – Contd.. Structural Information Document types: such as glossary document, vision statement, and use cases (which outline how the system behaves). Requirement types: which are categories of requirements such as features, use cases, supplementary specifications, and so on. Requirement attributes: which describe the requirements in terms of priority, status, stability, and other characteristics that you define

Structural Information

Document types: such as glossary document, vision statement, and use cases (which outline how the system behaves). Requirement types: which are categories of requirements such as features, use cases, supplementary specifications, and so on.

Requirement attributes: which describe the requirements in terms of priority, status, stability, and other characteristics that you define

2.0 Introducing RequisitePro – Contd.. Working with 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) Blank Template

Working with 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)

Blank Template

Create a new project Open Rational RequisitePro. Close the splash screen. In the Create Project dialog box, click the New tab. Click the Use-Case Template icon. Click OK. The Rational RequisitePro Project Properties dialog box opens. In the Name box, type My Exercise Project. Filling in the Description box is optional. Click OK. A dialog box opens, and you are asked whether you want to create the project directory. Click Yes. The Create Rational RequisitePro Project dialog box appears and informs you that your project has been created. Click Close.

Open Rational RequisitePro. Close the splash screen. In the Create Project dialog box, click the New tab.

Click the Use-Case Template icon. Click OK. The Rational RequisitePro Project Properties dialog box opens.

In the Name box, type My Exercise Project. Filling in the Description box is optional. Click OK. A dialog box opens, and you are asked whether you want to create the project directory.

Click Yes. The Create Rational RequisitePro Project dialog box appears and informs you that your project has been created. Click Close.

3.0 Documenting Requirements Objective: To demonstrate how to use RequisitePro outlines to create requirements documents and to create requirements in those documents. Topics covered: Working with document types Creating documents Working with requirements

Objective:

To demonstrate how to use RequisitePro outlines to create requirements documents and to create requirements in those documents.

Topics covered:

Working with document types

Creating documents

Working with requirements

Requirement Workflow

3.0 Documenting Requirements – contd.. Working with document types Vision: This document gives the overall view of the system: main characteristics, major features, key stakeholder needs, and key services provided. Glossary: It is important that all stakeholders use consistent terms to express requirements. The Glossary is a tool to capture and define the terms used in the project. Requirements Management Plan: This document sets out guidelines for establishing the requirements documents, types, attributes, and traceability in order to manage the project requirements.

Working with document types

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

Glossary: It is important that all stakeholders use consistent terms to express requirements. The Glossary is a tool to capture and define the terms used in the project.

Requirements Management Plan: This document sets out guidelines for establishing the requirements documents, types, attributes, and traceability in order to manage the project requirements.

3.0 Documenting Requirements – contd.. Use-Case Specification. Use cases serve as a format to express functional requirements in sequence. A use case is a sequence of actions performed by a system that yields an observable result (a work output) of value to a particular actor. 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. Test Plan: This document 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.

Use-Case Specification. Use cases serve as a format to express functional requirements in sequence. A use case is a sequence of actions performed by a system that yields an observable result (a work output) of value to a particular actor. 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.

Test Plan: This document 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.

3.0 Documenting Requirements – contd.. Working with requirements Name. A requirement name is a user-defined title. Requirement text. Requirement text is the full textual content of a requirement. Requirement tag. The requirement tag is the requirement's unique identifier. It consists of a prefix, which indicates the requirement type, and a number, which is generated by RequisitePro and which is unique within the requirement type. Requirement attributes. Each requirement is associated with attributes or descriptors that have been established for that requirement type.

Working with requirements

Name. A requirement name is a user-defined title.

Requirement text. Requirement text is the full textual content of a requirement.

Requirement tag. The requirement tag is the requirement's unique identifier. It consists of a prefix, which indicates the requirement type, and a number, which is generated by RequisitePro and which is unique within the requirement type.

Requirement attributes. Each requirement is associated with attributes or descriptors that have been established for that requirement type.

4.0 Organizing Requirements Objective: To demonstrate how to create requirements directly in a view, set attribute values, and navigate between the view and the document in which a requirement was created. Topics Covered: - Create requirements in a view - Managing requirements in views - Using attributes to organize requirement information

Objective: To demonstrate how to create requirements directly in a view, set attribute values, and navigate between the view and the document in which a requirement was created.

Topics Covered:

- Create requirements in a view

- Managing requirements in views

- Using attributes to organize requirement information

4.0 Organizing Requirements - Contd..   Create requirements in a view In the Explorer, expand the Features and Vision package and double-click All Features. The All Features Attribute Matrix appears. Explore the menus associated with this type of view The last entry in the Requirements column is entitled <Click here to create a requirement>. Click once to activate the row, and click again to allow editing. Type the following new requirement in the Name box: Click any other cell in the view, and your requirement is immediately saved and committed to the database.

  Create requirements in a view

In the Explorer, expand the Features and Vision package and double-click All Features. The All Features Attribute Matrix appears. Explore the menus associated with this type of view

The last entry in the Requirements column is entitled <Click here to create a requirement>. Click once to activate the row, and click again to allow editing.

Type the following new requirement in the Name box:

Click any other cell in the view, and your requirement is immediately saved and committed to the database.

4.0 Organizing Requirements - Contd..   Edit a requirement outside of a document Click Tools > Options. In the Views section of the dialog box, make sure the check box Double-click to go to source is selected. Click OK. Edit a requirement Then click any other cell in the matrix to save the edits. Double-click the requirement you edited. The document in which the requirement was created is opened, and your edit is reflected in it. From the Word menu bar, click RequisitePro > Document > Close. The Document Changed dialog box opens, and you are asked whether you want to save the modified document before closing it and Click Yes.

  Edit a requirement outside of a document

Click Tools > Options. In the Views section of the dialog box, make sure the check box Double-click to go to source is selected. Click OK.

Edit a requirement Then click any other cell in the matrix to save the edits.

Double-click the requirement you edited. The document in which the requirement was created is opened, and your edit is reflected in it.

From the Word menu bar, click RequisitePro > Document > Close. The Document Changed dialog box opens, and you are asked whether you want to save the modified document before closing it and Click Yes.

4.0 Organizing Requirements - Contd.. Using attributes to organize requirement information Attributes are data fields associated with each requirement that contain important project information. Each new RequisitePro requirement type is assigned default attributes by the system. You can delete, modify, or add an unlimited number of other attributes appropriate to your project Attributes can be either list-type or entry-type List (single value): A set of values from which a single value can be selected (up to 20 characters); for example, high, medium, or low. List (multiple value): A set of values from which more than one value can be selected (up to 20 characters); for example, Sue, Bob, John.

Using attributes to organize requirement information

Attributes are data fields associated with each requirement that contain important project information. Each new RequisitePro requirement type is assigned default attributes by the system. You can delete, modify, or add an unlimited number of other attributes appropriate to your project

Attributes can be either list-type or entry-type

List (single value): A set of values from which a single value can be selected (up to 20 characters); for example, high, medium, or low. List (multiple value): A set of values from which more than one value can be selected (up to 20 characters); for example, Sue, Bob, John.

4.0 Organizing Requirements - Contd.. Text: a text string up to 255 characters; for example, John Smith. Integer: whole numbers; for example, 5 or 1500. Real: real numbers; for example, 1.347 or 6.5. Date: a date in the format defined by the user's Windows setting; for example, mm/dd/yy. Time: a time in the format defined by the user's Windows setting; for example, 10:00 A.M.

Text: a text string up to 255 characters; for example, John Smith.

Integer: whole numbers; for example, 5 or 1500. Real: real numbers; for example, 1.347 or 6.5. Date: a date in the format defined by the user's Windows setting; for example, mm/dd/yy. Time: a time in the format defined by the user's Windows setting; for example, 10:00 A.M.

4.0 Organizing Requirements - Contd.. Requirements Priority: assign high priority to certain requirements that are important to the customer. You can then sort through your requirements and address those with high priority early in your project. - Can the requirement be met within your schedule constraints? - Is the requirement feasible given the risks associated with it? - If the requirement is implemented, how will it affect your ability to maintain the product? - Do you have time to complete all of your high priorities?

Requirements Priority:

assign high priority to certain requirements that are important to the customer. You can then sort through your requirements and address those with high priority early in your project.

- Can the requirement be met within your schedule constraints? - Is the requirement feasible given the risks associated with it? - If the requirement is implemented, how will it affect your ability to maintain the product?

- Do you have time to complete all of your high priorities?

4.0 Organizing Requirements - Contd.. Set attribute values in a view In the Features and Vision package, select the All Features view. Then double-click the intersection of the FEAT4 requirement and the attribute column Status. In the list, click Approved, and then set the value by clicking another requirement or attribute cell. [Note: You can also change multiple attribute values simultaneously using Microsoft's Extended Select (Shift > click or Ctrl > click).] Click File > Save View, and then close the view by clicking the lower X in the upper right corner.

Set attribute values in a view

In the Features and Vision package, select the All Features view. Then double-click the intersection of the FEAT4 requirement and the attribute column Status.

In the list, click Approved, and then set the value by clicking another requirement or attribute cell. [Note: You can also change multiple attribute values simultaneously using Microsoft's Extended Select (Shift > click or Ctrl > click).]

Click File > Save View, and then close the view by clicking the lower X in the upper right corner.

5.0 Tracking Requirements Objectives: To demonstrate how you can create traceability relationships among requirements in a Word document, use RequisitePro's suspect link feature to help you manage change, and sort requirements that you establish. Topics Covered: Managing changing requirements Setting traceability Managing change through traceability views Using suspect links Establishing hierarchy Querying (filtering and sorting)

Objectives: To demonstrate how you can create traceability relationships among requirements in a Word document, use RequisitePro's suspect link feature to help you manage change, and sort requirements that you establish.

Topics Covered:

Managing changing requirements

Setting traceability

Managing change through traceability views

Using suspect links

Establishing hierarchy

Querying (filtering and sorting)

5.0 Tracking Requirements – Contd.. Managing requirement change 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

Managing requirement change 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

5.0 Tracking Requirements – Contd.. Setting traceability Traceability is a directional relationship between any two requirements (of the same type or different types). ReqA --> ReqB means that ReqA is traced to ReqB. ReqA <-- ReqB means that ReqA is traced from ReqB There may be times, however, when features do not apply to a specific use case, they are not easily traced from a particular use case, or they are not functional requirements. In these situations, you can trace supplementary specification (SUPP) requirements to the feature requirements

Setting traceability

Traceability is a directional relationship between any two requirements (of the same type or different types). ReqA --> ReqB means that ReqA is traced to ReqB. ReqA <-- ReqB means that ReqA is traced from ReqB

There may be times, however, when features do not apply to a specific use case, they are not easily traced from a particular use case, or they are not functional requirements. In these situations, you can trace supplementary specification (SUPP) requirements to the feature requirements

5.0 Tracking Requirements – Contd.. Managing change through traceability views Traceability Matrix: which illustrates the relationships between requirements of the same or different types. Use this matrix to create, modify, and delete traceability relationships and to view traceability relationships with a suspect state. Also use the Traceability Matrix to filter and sort the row requirements and column requirements separately. Traceability Tree, which displays all internal and external requirements traced to or from a requirement (depending on the direction of the tree). The Traceability Tree displays only the first level of traceability among requirements that reside in different projects (cross-project traceability).

Managing change through traceability views

Traceability Matrix: which illustrates the relationships between requirements of the same or different types. Use this matrix to create, modify, and delete traceability relationships and to view traceability relationships with a suspect state. Also use the Traceability Matrix to filter and sort the row requirements and column requirements separately.

Traceability Tree, which displays all internal and external requirements traced to or from a requirement (depending on the direction of the tree). The Traceability Tree displays only the first level of traceability among requirements that reside in different projects (cross-project traceability).

5.0 Tracking Requirements – Contd..   Create and clear traceability relationships from a matrix view 1. Explorer, click the plus sign next to the Coverage Analysis package to expand it, and double-click the view Functional Requirements Coverage. 2. Select one of the empty intersections between a UC and FEAT requirement. 3. Click Traceability > Trace to. You have just created a traceability relationship! 4. Review the traceability; then select the same requirements as above and click Edit > Set Value. Select Delete Trace and click OK; click Yes in response to the dialog box that asks you to confirm your selection. The traceability relationships created above have been removed

  Create and clear traceability relationships from a matrix view

1. Explorer, click the plus sign next to the Coverage Analysis package to expand it, and double-click the view Functional Requirements Coverage.

2. Select one of the empty intersections between a UC and FEAT requirement. 3. Click Traceability > Trace to. You have just created a traceability relationship! 4. Review the traceability; then select the same requirements as above and click Edit > Set Value. Select Delete Trace and click OK; click Yes in response to the dialog box that asks you to confirm your selection. The traceability relationships created above have been removed

5.0 Tracking Requirements – Contd..   Create traceability relationships from the Word document 1. Double-click the document to open it and scroll to any section containing requirement. 2. Click RequisitePro > Requirement > Properties. The Requirement Properties dialog box opens. 3. Click the Traceability tab. From this tab, you can add, delete, and modify the relationships between the requirement you selected and any other requirement. 4. In the To section of the dialog box, click the Add button. (This will enable you to add a traceability relationship from the use-case requirement to another requirement.)

  Create traceability relationships from the Word document

1. Double-click the document to open it and scroll to any section containing requirement.

2. Click RequisitePro > Requirement > Properties. The Requirement Properties dialog box opens. 3. Click the Traceability tab. From this tab, you can add, delete, and modify the relationships between the requirement you selected and any other requirement. 4. In the To section of the dialog box, click the Add button. (This will enable you to add a traceability relationship from the use-case requirement to another requirement.)

5.0 Tracking Requirements – Contd.. Using suspect links RequisitePro signals suspect condition with a red diagonal line through the traced to or traced from arrow in a Traceability Matrix or Traceability Tree For example, if traceability relationships exist between Requirements A and B and between Requirements B and C, and you modify Requirement A, the relationship between Requirements A and B becomes suspect, but the relationship between Requirements B and C does not. Requirement B may need to be updated to reflect the modifications made to Requirement A. Ability to modify traceability depends upon the security permissions that have been assigned to you as a user

Using suspect links

RequisitePro signals suspect condition with a red diagonal line through the traced to or traced from arrow in a Traceability Matrix or Traceability Tree

For example, if traceability relationships exist between Requirements A and B and between Requirements B and C, and you modify Requirement A, the relationship between Requirements A and B becomes suspect, but the relationship between Requirements B and C does not. Requirement B may need to be updated to reflect the modifications made to Requirement A.

Ability to modify traceability depends upon the security permissions that have been assigned to you as a user

5.0 Tracking Requirements – Contd.. Create a suspect relationship 1. Open a requirement in Word 2. Modify the text for any existing requirement. 3.Click RequisitePro > Document > Save. The Change Description dialog box opens and asks for a reason for the change. 4. Type for the purpose and click OK. Then minimize the document. 5. Open a view and check that “Suspect” symbol is displayed for all the requirements affected by the change. 6. Suspect links can be cleared after you have reviewed the impact of your edit by right-clicking the suspect link and then clicking Clear Suspect

Create a suspect relationship

1. Open a requirement in Word

2. Modify the text for any existing requirement.

3.Click RequisitePro > Document > Save. The Change Description dialog box opens and asks for a reason for the change. 4. Type for the purpose and click OK. Then minimize the document.

5. Open a view and check that “Suspect” symbol is displayed for all the requirements affected by the change.

6. Suspect links can be cleared after you have reviewed the impact of your edit by right-clicking the suspect link and then clicking Clear Suspect

5.0 Tracking Requirements – Contd.. Create suspect relationships in an Attribute Matrix view - In the Explorer, expand the Use Cases package and select the Attribute Matrix view All Use Cases. Double-click it to open it. - Click View > Query Row Requirements. - In the Select Attribute dialog box, select Traced-to as the attribute to be filtered, and click OK. The Query Requirements dialog box opens. - Click the FEAT requirement type, and make sure that the Traced button and the Suspect only check box are activated. Then click OK. - In the Query Row Requirements dialog box, click OK to run the query builder, which shows you the current criteria of your query.

Create suspect relationships in an Attribute Matrix view

- In the Explorer, expand the Use Cases package and select the Attribute Matrix view All Use Cases. Double-click it to open it.

- Click View > Query Row Requirements.

- In the Select Attribute dialog box, select Traced-to as the attribute to be filtered, and click OK. The Query Requirements dialog box opens.

- Click the FEAT requirement type, and make sure that the Traced button and the Suspect only check box are activated. Then click OK.

- In the Query Row Requirements dialog box, click OK to run the query builder, which shows you the current criteria of your query.

5.0 Tracking Requirements – Contd.. Create suspect relationships in an Attribute Matrix view - contd.. In the resulting view, scroll to the right until you reach the Traced-to column; note the &quot;(s)&quot; entries after requirements. This entry indicates that the traceability relationship between the two requirements must be reexamined because a change has been made to one of the requirements

Create suspect relationships in an Attribute Matrix view - contd..

In the resulting view, scroll to the right until you reach the Traced-to column; note the &quot;(s)&quot; entries after requirements. This entry indicates that the traceability relationship between the two requirements must be reexamined because a change has been made to one of the requirements

5.0 Tracking Requirements – Contd.. Establishing hierarchy A hierarchical requirement is a requirement that is included within a parent-child relationship with other requirements of the same type. Hierarchical relationships can be used to subdivide a general requirement into more explicit requirements If a parent requirement appears in a document, the child requirements must appear in the same document. The parent requirement and all of its children must be of the same requirement type. Each child requirement can only have one parent, but a requirement can be both a parent and a child. If a parent requirement is changed, the relationships with its children become suspect.

Establishing hierarchy

A hierarchical requirement is a requirement that is included within a parent-child relationship with other requirements of the same type. Hierarchical relationships can be used to subdivide a general requirement into more explicit requirements

If a parent requirement appears in a document, the child requirements must appear in the same document. The parent requirement and all of its children must be of the same requirement type.

Each child requirement can only have one parent, but a requirement can be both a parent and a child. If a parent requirement is changed, the relationships with its children become suspect.

5.0 Tracking Requirements – Contd..   Create hierarchical requirements in a document Create a Requirement: Open the use-case document and press ENTER to begin a new line, and then type text for new requirement. Select the text you typed and click RequisitePro > Requirement > New. The Requirement Properties dialog box opens. In the Type box, accept the default (UC: Use Case); in the Name box, type any valid requirement name and Click OK. Click RequisitePro > Document > Save to create the requirement.

  Create hierarchical requirements in a document

Create a Requirement:

Open the use-case document and press ENTER to begin a new line, and then type text for new requirement.

Select the text you typed and click RequisitePro > Requirement > New. The Requirement Properties dialog box opens.

In the Type box, accept the default (UC: Use Case); in the Name box, type any valid requirement name and Click OK.

Click RequisitePro > Document > Save to create the requirement.

5.0 Tracking Requirements – Contd.. Next, make the requirement you created a child requirement - Click anywhere in the text of the requirement you just created - Click RequisitePro > Requirement > Properties. The Requirement Properties dialog box opens. - Click the Hierarchy tab. In the Parent box, select Choose Parent. The Parent Requirement Browser dialog box opens. - Select a valid existing requirement as the parent and click OK. Click OK to close the Requirement Properties dialog box. - Click RequisitePro > Document > Save to commit the requirement. -The Change Description dialog box asks you to provide a reason for the requirement change. Type &quot;for the purpose of this exercise&quot; and click OK.

Next, make the requirement you created a child requirement

- Click anywhere in the text of the requirement you just created

- Click RequisitePro > Requirement > Properties. The Requirement Properties dialog box opens.

- Click the Hierarchy tab. In the Parent box, select Choose Parent. The Parent Requirement Browser dialog box opens. - Select a valid existing requirement as the parent and click OK. Click OK to close the Requirement Properties dialog box. - Click RequisitePro > Document > Save to commit the requirement. -The Change Description dialog box asks you to provide a reason for the requirement change. Type &quot;for the purpose of this exercise&quot; and click OK.

5.0 Tracking Requirements Change the parent of a child requirement - In the document select a child requirement and Click RequisitePro > Requirement > Properties. The Requirement Properties dialog box opens. - Click the Hierarchy tab, and from the Parent box, select the choose parent option. - Select a different parent requirement and click OK. - On the Word menu bar, click RequisitePro > Document > Save The Change Description dialog box opens, and you are required to give a reason for the change; in the window, type Assigned to a different parent for more logical clustering of child requirements. Then click OK.

Change the parent of a child requirement

- In the document select a child requirement and Click RequisitePro > Requirement > Properties. The Requirement Properties dialog box opens. - Click the Hierarchy tab, and from the Parent box, select the choose parent option.

- Select a different parent requirement and click OK.

- On the Word menu bar, click RequisitePro > Document > Save The Change Description dialog box opens, and you are required to give a reason for the change; in the window, type Assigned to a different parent for more logical clustering of child requirements. Then click OK.

5.0 Tracking Requirements – Contd.. Querying (Filtering and Sorting) Filtering restricts the information being displayed, and sorting determines the order in which information is displayed. You filter and sort requirements by applying query criteria to the attributes. These criteria limit the values of the attributes or limit the traceability relationships. You can create a simple query involving only one attribute, so that you can see the results of each query. Or you can create a query that filters and sorts all at once for several attributes.

Querying (Filtering and Sorting)

Filtering restricts the information being displayed, and sorting determines the order in which information is displayed.

You filter and sort requirements by applying query criteria to the attributes. These criteria limit the values of the attributes or limit the traceability relationships. You can create a simple query involving only one attribute, so that you can see the results of each query. Or you can create a query that filters and sorts all at once for several attributes.

5.0 Tracking Requirements – Contd..   Create a query in an Attribute Matrix -In the Explorer, select the All Features Attribute Matrix, and double-click it to open it. - Click View > Query Row Requirements. (You may also select the Query row requirements icon  .) This opens the query builder. - In the Select Attribute dialog box, make sure the FEAT requirement is displayed in the Requirement Types box; in the Attribute to Filter/Sort Requirements field, select Difficulty and click OK. The Query Requirements dialog box opens.

  Create a query in an Attribute Matrix

-In the Explorer, select the All Features Attribute Matrix, and double-click it to open it.

- Click View > Query Row Requirements. (You may also select the Query row requirements icon  .) This opens the query builder. - In the Select Attribute dialog box, make sure the FEAT requirement is displayed in the Requirement Types box; in the Attribute to Filter/Sort Requirements field, select Difficulty and click OK. The Query Requirements dialog box opens.

5.0 Tracking Requirements – Contd.. - Click the None button to clear all attribute values, select the value Low, and click OK. This criterion is now added to the Query Row Requirements window. - Click the Add button and follow the same procedure to add the attribute Stability with a value of High. Both attributes appear in the Query Row Requirements window. - Click OK to run this query. - The result of this query scopes and directs the development toward those requirements that are stable and relatively easy to implement. Two requirements meet the criteria.

- Click the None button to clear all attribute values, select the value Low, and click OK. This criterion is now added to the Query Row Requirements window. - Click the Add button and follow the same procedure to add the attribute Stability with a value of High. Both attributes appear in the Query Row Requirements window. - Click OK to run this query.

- The result of this query scopes and directs the development toward those requirements that are stable and relatively easy to implement. Two requirements meet the criteria.

6.0 Advanced Features RequisitePro includes two powerful management tools that help you track the status of your requirements, trace the changes to requirements, and enhance your ability to perform impact analyses when changes occur. Traceability provides a methodical approach for managing changes by linking high-level requirements to their more specific descendants. Traceability relationships make it easy to track changes to a requirement throughout the development cycle. Version control through archiving and creating baselines allows you to trace changes.

RequisitePro includes two powerful management tools that help you track the status of your requirements, trace the changes to requirements, and enhance your ability to perform impact analyses when changes occur.

Traceability provides a methodical approach for managing changes by linking high-level requirements to their more specific descendants. Traceability relationships make it easy to track changes to a requirement throughout the development cycle.

Version control through archiving and creating baselines allows you to trace changes.

6.0 Advanced Features – Contd.. Advanced features of RequisitePro are described below. Archiving : RequisitePro offers two ways that you can archive your projects. Archiving is the process of duplicating a project (the database, documents, and all related files) in a directory of your choice for the purpose of restoring at a later time. - The RequisitePro Archive command. - The Rational ClearCase command

Advanced features of RequisitePro are described below.

Archiving : RequisitePro offers two ways that you can archive your projects. Archiving is the process of duplicating a project (the database, documents, and all related files) in a directory of your choice for the purpose of restoring at a later time.

- The RequisitePro Archive command.

- The Rational ClearCase command

6.0 Advanced Features – Contd.. Archiving projects with the RequisitePro Archive command 1. Click File > Project Administration > Archive > RequisitePro Archive. The Archive Project dialog box appears. 2. Select the directory where you want the backup copy stored. Click Browse to open the Browse for Folder dialog box. Navigate to a directory, select a folder, and click OK. 3. If you want to add a new revision number for the project, type it in the Revision # text box. 4.. To apply the revision number to the requirement documents, select the Propagate to all documents (offline documents excluded) check box.

Archiving projects with the RequisitePro Archive command

1. Click File > Project Administration > Archive > RequisitePro Archive. The Archive Project dialog box appears.

2. Select the directory where you want the backup copy stored. Click Browse to open the Browse for Folder dialog box. Navigate to a directory, select a folder, and click OK.

3. If you want to add a new revision number for the project, type it in the Revision # text box.

4.. To apply the revision number to the requirement documents, select the Propagate to all documents (offline documents excluded) check box.

6.0 Advanced Features – Contd.. The RequisitePro Archive command performs the following: - Creates a directory (beginning with &quot;bak&quot;) to hold the archive files. - Copies the RequisitePro project files (.rqs and .rql) to the directory. - Copies all project documents to the directory. - Updates the version of the original project (if you have security permissions to modify the project structure). For Microsoft Access-based projects the RequisitePro archive also performs the following: - Copies the project database file (.mdb) to the directory. - Updates the .mdb file in the archive directory with the location of the project documents in the archive.

The RequisitePro Archive command performs the following:

- Creates a directory (beginning with &quot;bak&quot;) to hold the archive files.

- Copies the RequisitePro project files (.rqs and .rql) to the directory.

- Copies all project documents to the directory.

- Updates the version of the original project (if you have security permissions to modify the project structure).

For Microsoft Access-based projects the RequisitePro archive also performs the following:

- Copies the project database file (.mdb) to the directory.

- Updates the .mdb file in the archive directory with the location of the project documents in the archive.

6.0 Advanced Features – Contd.. Archiving projects with Rational ClearCase To archive your Rational RequisitePro projects in ClearCase, open the RequisitePro Options dialog box (click Tools > Options) and specify the path of the default ClearCase view for any new project being archived. - Copies the RequisitePro project files (.rqs and .rql) to the directory. - Copies all project documents to the directory. - Updates the RequisitePro Revision # of the original project (if you have security permissions to modify the project structure). - Checks in all files and the directory.

Archiving projects with Rational ClearCase

To archive your Rational RequisitePro projects in ClearCase, open the RequisitePro Options dialog box (click Tools > Options) and specify the path of the default ClearCase view for any new project being archived.

- Copies the RequisitePro project files (.rqs and .rql) to the directory.

- Copies all project documents to the directory.

- Updates the RequisitePro Revision # of the original project (if you have security permissions to modify the project structure).

- Checks in all files and the directory.

6.0 Advanced Features – Contd.. Unified Change Management Rationale's out-of-the-box usage model for managing change in software system development, from requirements to release. UCM is a unified approach to configuration management and change request management, automated in Rational ClearCase and Rational ClearQuest. ClearCase can be set up to implement the UCM model for basic activity-based configuration management or in conjunction with ClearQuest to provide full change-request management. To implement the UCM model for creating a baseline of a Rational RequisitePro project, the project must be associated with a UCM-enabled Rational project in the Rational Administrator.

Unified Change Management

Rationale's out-of-the-box usage model for managing change in software system development, from requirements to release. UCM is a unified approach to configuration management and change request management, automated in Rational ClearCase and Rational ClearQuest. ClearCase can be set up to implement the UCM model for basic activity-based configuration management or in conjunction with ClearQuest to provide full change-request management. To implement the UCM model for creating a baseline of a Rational RequisitePro project, the project must be associated with a UCM-enabled Rational project in the Rational Administrator.

6.0 Advanced Features – Contd.. You can create a baseline of a RequisitePro project when the following conditions are met: - The RequisitePro project must be associated with a UCM-enabled Rational project in Rational Administrator. - The RequisitePro project must be versioned. - All users must have closed the RequisitePro project.

You can create a baseline of a RequisitePro project when the following conditions are met:

- The RequisitePro project must be associated with a UCM-enabled Rational project in Rational Administrator.

- The RequisitePro project must be versioned.

- All users must have closed the RequisitePro project.

6.0 Advanced Features – Contd.. Check in the RequisitePro project 1.Click Tools > Rational Administrator to open Rational Administrator. 2. Select the Rational Administrator project, right-click, and click Configure on the shortcut menu. 3. In the Configure Project dialog box, in the Requirement Assets area, click Check In All. 4. Confirm your selection at the messages that follow, and type an activity to describe the baseline in the Check in all dialog box. 5. After the check in operation is complete, close the Configure Project dialog box.

Check in the RequisitePro project

1.Click Tools > Rational Administrator to open Rational Administrator.

2. Select the Rational Administrator project, right-click, and click Configure on the shortcut menu.

3. In the Configure Project dialog box, in the Requirement Assets area, click Check In All.

4. Confirm your selection at the messages that follow, and type an activity to describe the baseline in the Check in all dialog box.

5. After the check in operation is complete, close the Configure Project dialog box.

6.0 Advanced Features – Contd.. Create the baseline (Refer to ClearCase Help for more information.) 1. Open the Rational ClearCase Project Explorer. (From Rational Administrator, you can click Tools > Rational ClearCase Project Explorer.) 2. Right-click the integration stream for the associated UCM project and click Make Baseline on the shortcut menu. 3. Type or edit the Baseline Title, select a View Context, and click OK.

Create the baseline (Refer to ClearCase Help for more information.)

1. Open the Rational ClearCase Project Explorer. (From Rational Administrator, you can click Tools > Rational ClearCase Project Explorer.)

2. Right-click the integration stream for the associated UCM project and click Make Baseline on the shortcut menu.

3. Type or edit the Baseline Title, select a View Context, and click OK.

6.0 Advanced Features – Contd.. Creating baselines: You can use RequisitePro to create a baseline, or snapshot of the project's current state. A RequisitePro baseline is a Rational Unified Change Management object that typically represents a stable configuration of one or more components. A baseline identifies activities and one version of every element visible in one or more components. It should be created at project milestones. Cross-project traceability: RequisitePro's cross-project traceability feature helps you establish traceability between requirements that reside in different projects. It is helpful in storing requirements common to multiple projects.

Creating baselines: You can use RequisitePro to create a baseline, or snapshot of the project's current state. A RequisitePro baseline is a Rational Unified Change Management object that typically represents a stable configuration of one or more components. A baseline identifies activities and one version of every element visible in one or more components. It should be created at project milestones.

Cross-project traceability: RequisitePro's cross-project traceability feature helps you establish traceability between requirements that reside in different projects. It is helpful in storing requirements common to multiple projects.

6.0 Advanced Features – Contd.. Customizing document and requirement types and attributes We explained how you can use the defaults provided by RequisitePro to create documents and requirements. You can also create, edit, and delete document and requirement types and attributes as needed. To modify the existing types, you select the project in the Explorer, click File > Properties, and then click the appropriate tab. Click the Add, Delete, or Edit buttons on the tab and follow the prompts to add or delete information as necessary.

Customizing document and requirement types and attributes

We explained how you can use the defaults provided by RequisitePro to create documents and requirements. You can also create, edit, and delete document and requirement types and attributes as needed.

To modify the existing types, you select the project in the Explorer, click File > Properties, and then click the appropriate tab. Click the Add, Delete, or Edit buttons on the tab and follow the prompts to add or delete information as necessary.

6.0 Advanced Features – Contd.. Deleting requirements RequisitePro provides several ways for you to delete requirements 1. The Delete-Unmark command enables you to delete a requirement from the database but to retain the requirement text as ordinary text in the document; 2. The Delete-Remove command allows you to delete a requirement from the database and to delete the text of the requirement from the document. These methods cause the requirement history and traceability relationships to be permanently removed from the project database

Deleting requirements

RequisitePro provides several ways for you to delete requirements

1. The Delete-Unmark command enables you to delete a requirement from the database but to retain the requirement text as ordinary text in the document;

2. The Delete-Remove command allows you to delete a requirement from the database and to delete the text of the requirement from the document. These methods cause the requirement history and traceability relationships to be permanently removed from the project database

6.0 Advanced Features – Contd.. Deleting requirements - Contd… 3. These methods cause the requirement history and traceability relationships to be permanently removed from the project database. A third way—and this is the way we recommend—is to keep the requirement but to modify the requirement attributes to indicate that the requirement is invalid. Add an attribute value, such as Invalid or Deleted, to an existing attribute, such as Status. When you sort your requirements, this value clearly indicates that the requirement is not active. Unlike the Delete commands, this method of deleting requirements does not delete the requirement history, which is often helpful to retain for reference purposes.

Deleting requirements - Contd…

3. These methods cause the requirement history and traceability relationships to be permanently removed from the project database. A third way—and this is the way we recommend—is to keep the requirement but to modify the requirement attributes to indicate that the requirement is invalid.

Add an attribute value, such as Invalid or Deleted, to an existing attribute, such as Status. When you sort your requirements, this value clearly indicates that the requirement is not active. Unlike the Delete commands, this method of deleting requirements does not delete the requirement history, which is often helpful to retain for reference purposes.

6.0 Advanced Features – Contd.. Discussion groups - Discussion groups let you comment and raise issues and questions to a group of project users (participants). Discussions can be associated with one or many requirements, or they may refer to the project as a whole. 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

Discussion groups - Discussion groups let you comment and raise issues and questions to a group of project users (participants). Discussions can be associated with one or many requirements, or they may refer to the project as a whole.

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

6.0 Advanced Features – Contd.. Offline authoring Offline authoring lets you edit a requirements document outside of RequisitePro (i.e., offline). A read-only copy of the document is retained in the project for other project users to view while edits are being made offline. You can add and delete requirements in the offline document, and when you bring the document back online, RequisitePro replaces the read-only document with the modified document. Requirement Metrics - Requirement Metrics enables you to report statistics on requirement text, attributes, relationships, and revisions. You can select a subset of requirements (a requirement type or a saved view) for your report, choose filter criteria, and add them to your report. The report results are displayed in Microsoft Excel and can be manipulated using Excel's charting capabilities.

Offline authoring

Offline authoring lets you edit a requirements document outside of RequisitePro (i.e., offline). A read-only copy of the document is retained in the project for other project users to view while edits are being made offline. You can add and delete requirements in the offline document, and when you bring the document back online, RequisitePro replaces the read-only document with the modified document.

Requirement Metrics - Requirement Metrics enables you to report statistics on requirement text, attributes, relationships, and revisions. You can select a subset of requirements (a requirement type or a saved view) for your report, choose filter criteria, and add them to your report. The report results are displayed in Microsoft Excel and can be manipulated using Excel's charting capabilities.

6.0 Advanced Features – Contd.. Simplified Configuration of Rational RequisiteWeb Configuring your Web server for RequisiteWeb is quick and easy, requiring just five steps: Install the application, specify your username, configure SSL (optional), reboot the machine, and add your projects to the project list. You can customize the RequisiteWeb Login Page and footer to accommodate your company's needs.

Simplified Configuration of Rational RequisiteWeb

Configuring your Web server for RequisiteWeb is quick and easy, requiring just five steps: Install the application, specify your username, configure SSL (optional), reboot the machine, and add your projects to the project list.

You can customize the RequisiteWeb Login Page and footer to accommodate your company's needs.

6.0 Advanced Features – Contd.. Requirement Metrics Overview Requirement Metrics provides project managers and product analysts with statistics concerning a RequisitePro project’s requirement attributes, relationships, and revisions. These statistics are displayed in Microsoft Excel. You can use Requirement Metrics to retrieve information that is vital for evaluating - the progress of a project - priorities, workloads, and deadlines - the addition of new requirements - changing or unstable requirements - approved and incorporated features

Requirement Metrics Overview

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

You can use Requirement Metrics to retrieve information that is vital for evaluating

- the progress of a project

- priorities, workloads, and deadlines

- the addition of new requirements

- changing or unstable requirements

- approved and incorporated features

6.0 Advanced Features – Contd.. There are two types of reports that are available in Requirement Metrics: A static report uses static filters and shows results about the project at the present time. A trend analysis report uses time-sensitive filters that analyze changes in requirement text, attributes, traceability, and hierarchical relationships. Trend analysis reports require that you specify an increment for displaying revisions.

There are two types of reports that are available in Requirement Metrics:

A static report uses static filters and shows results about the project at the present time.

A trend analysis report uses time-sensitive filters that analyze changes in requirement text, attributes, traceability, and hierarchical relationships. Trend analysis reports require that you specify an increment for displaying revisions.

6.0 Advanced Features – Contd.. Filter A filter defines retrieval criteria for a particular aspect of a requirement. It is the elemental building block of a Requirement Metrics query. Query A query is a collection of filters. In order for a requirement to be returned from a query, it must pass all the filters that make up the query.

Filter

A filter defines retrieval criteria for a particular aspect of a requirement. It is the elemental building block of a Requirement Metrics query.

Query

A query is a collection of filters. In order for a requirement to be returned from a query, it must pass all the filters that make up the query.

6.0 Advanced Features – Contd.. Question1: How many requirements were created since the last release? Requirements Creation filter Options/Time Period > 10/15/99 Question 2: How many requirements went from Low Priority to High Priority in the last month? Attribute Value Change filter Priority Before = Low Priority After = High Options/Time Period/Last Month

Question1: How many requirements were created since the last release?

Requirements Creation filter Options/Time Period > 10/15/99

Question 2: How many requirements went from Low Priority to High Priority in the last month?

Attribute Value Change filter

Priority Before = Low

Priority After = High

Options/Time Period/Last Month

6.0 Advanced Features – Contd.. Question 3: Are my associations with other requirements stable? Traceability Change filter: Select All Relationship = Trace To and From Action = Added or Removed Question 4: How many requirements contain text that has changed more than three times since the last iteration? Requirement Text Change filter Number of changes > 3 Options/Time Period > 10/15/99

Question 3: Are my associations with other requirements stable?

Traceability Change filter: Select All

Relationship = Trace To and From

Action = Added or Removed

Question 4: How many requirements contain text that has changed

Add a comment

Related pages

Rational Requisite Pro - Requirement Management (Advanced ...

Raj Raj Kamal is working as a Test Architect at Microsoft and specializes in different types of testing techniques, test automation and ...
Read more

Rational Requisite Pro - Requirement Management (Advanced ...

Rational Requisite Pro ... MSDN Blogs > geektester > Rational Requisite Pro ... Rational Requisite Pro - Requirement Management (Advanced Training)
Read more

Rational | LinkedIn

View 272120 Rational posts, presentations, experts, and more. Get the professional knowledge you need on LinkedIn. LinkedIn Home What is LinkedIn?
Read more

Tester Testifies: February 2008

For want of a nail, the shoe was lost; for want of a shoe, the horse was lost; For want of a horse, the rider was lost; for want of a rider, the ...
Read more

Rational Software - Wikipedia, the free encyclopedia

Rational Machines was founded by Paul Levy and Mike Devlin in 1981 to provide tools to expand the use of modern software engineering practices ...
Read more

IBM Rational software and systems delivery

IBM Rational software helps organizations succeed by supporting DevOps, continuous engineering, ... Rational Team Concert Achieve visibility, ...
Read more