IBM Rational University. Essentials of IBM Rational RequisitePro v7.0 REQ370 / RR331 October 2006 Student Workbook Part No.

Transcription

1 IBM Rational University Essentials of IBM Rational RequisitePro v7.0 REQ370 / RR331 October 2006 Student Workbook Part No

2 IBM Corporation Rational University REQ370 / RR331 Essentials of IBM Rational RequisitePro v7.0 Student Workbook October 2006 Copyright International Business Machines Corporation, 1998, All rights reserved. This document may not be reproduced in whole or in part without the prior written permission of IBM. The contents of this manual and the associated software are the property of IBM and/or its licensors, and are protected by United States copyright laws, patent laws, and various international treaties. For additional copies of this manual or software, please contact Rational Software. IBM and the IBM logo are trademarks or registered trademarks of IBM Corporation, in the United States, other countries or both. Rational, the Rational logo, ClearCase, ClearCase LT, ClearCase MultiSite, Unified Change Management, Rational SoDA, and Rational XDE are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both. WebSphere, the WebSphere logo, and Studio Application Developer, are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both. Microsoft Windows 2000, Microsoft Word, and Internet Explorer, among others, are trademarks or registered trademarks of Microsoft Corporation. Java and all Java-based marks, among others, are trademarks or registered trademarks of Sun Microsystems in the United States, other countries or both. UNIX is a registered trademark of The Open Group in the United States, other countries or both. Other company, product and service names may be trademarks or service marks of others. Printed in the United States of America. This manual prepared by: IBM Rational Software Homestead Road Cupertino, CA USA

3 Essentials of IBM Rational RequisitePro Workbook Table of Contents Contents Lab 1 Getting Started Lab 1u Getting Started (unguided) Initial Requests for Online Stock Trading System Lab 2 Customize Project Structure Lab 2u Customize Project Structure (unguided) Lab 3 Gather and Enter Requirements Lab 3u Gather and Enter Requirements (unguided) Lab 4 RequisitePro Documents Lab 4u RequisitePro Documents (unguided) Lab 5 Traceability and Queries Lab 5u Traceability and Queries (unguided) Lab 6 Metrics Lab 6u Metrics (unguided) Lab 7 RequisitePro Baseline Manager Lab 7u RequisitePro Baseline Manager (unguided) Lab 8 Group Discussions Lab 8u Group Discussions (unguided) Optional Lab Security... OL-1 Lab Setup Copyright IBM Corp. 1998, 2006 i

4 Essentials of IBM Rational RequisitePro Workbook Table of Contents Copyright IBM Corp. 1998, 2006 ii

5 Getting Started Lab 1.1 Understand Rational RequisitePro Project Structure and Components NOTE: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page 1-9. Otherwise, continue reading. Objectives Open Rational RequisitePro. Explore the RequisitePro project list. Navigate within a sample project. Examine project components and properties. Scenario You have recently been hired by RU Financial Services to help manage their requirements. RU Financial Services uses Rational RequisitePro to organize, create, manage, and maintain the requirements for the software development of a project. Several meetings occurred before you were hired and an initial version of the RequisitePro project has already been created. Some of the project information is given to you. The existing information is in many different formats (CSV files and Word documents). Your task is to manage the requirements for RU Financial Services in accordance with the Requirements Management Plan. Before you begin using Rational RequisitePro to manage requirements, learn about basic skills and online guides. This lab focuses on navigating RequisitePro, RequisitePro Help, and project properties/configurations. Rational RequisitePro offers a learning tutorial that guides a new user through basic skills. Rational RequisitePro is packaged with sample projects. You ll browse the Learning Project Use Cases in this lab. Estimated Time 10 minutes Copyright IBM Corp. 1998,

6 Essentials of IBM Rational RequisitePro Workbook Start RequisitePro and Open the Learning Project - Use Cases 1. Open RequisitePro using the Start menu. The first thing you may see is a Let s Go RequisitePro dialog box. You will explore this resource later. For now, click Close. Note: Let s Go RequisitePro may be turned off. When you start Rational RequisitePro you are presented with the Open Project dialog box. (If the Open Project dialog box does not appear, click File > Open Project.) 2. Click the Existing tab. Look for the Learning Project-Use Cases in the Project list. Click the Learning Project Use Cases, and then click OK. If the Learning Project Use Cases is not listed in the Project list, click Add. Locate the project at: C:\ Program Files\Rational\RequisitePro\samples\Learning_Project- Use_Cases Select the LEARNING USE CASES.RQS file, and then click Open. 1-2 Copyright IBM Corp. 1998, 2006

7 Getting Started 3. Click OK if you are asked to enter a login name. The left panel of Rational RequisitePro is the Explorer. The project that is currently open is at the top of the tree. The packages in the tree are used to visually organize your requirements artifacts. Expand the Use Cases package. Expand the Purchase CD package. The package contains a document called Purchase CD and a number of requirements. Right-click the document, and then click Open. The document opens in a separate Word window. (If you receive an Enable Macros dialog box, click Enable Macros to continue.) (If you receive a Document Changed dialog box, click Yes to continue.) The Word menu bar contains a RequisitePro menu. If the RequisitePro menu is not displayed, click View > Toolbars > Rational RequisitePro. Slowly move the mouse over each of the buttons in the RequisitePro toolbar to view the ToolTip of each button. This document contains use case requirements. The requirements are delineated with bookmarks in Word that look something like this: [UC3 Purchase CD] 4. Click RequisitePro > Document > Close in the menu bar. View Project Properties 5. In RequisitePro: Click File > Project Administration > Properties. All the project properties for a project can be viewed, modified, created, or deleted from this dialog box. Briefly review the tabbed sections (General, Revision, Requirement Types, Documents, Document Types, and Attributes) and explore the structure of a project. The project s structure, or properties, is defined in your Requirements Management Plan before creating the project in RequisitePro. Copyright IBM Corp. 1998,

8 Essentials of IBM Rational RequisitePro Workbook 6. Click Cancel to exit Project Properties. Click File > Close Project. Click Yes to close the project. (If you receive a Document Changed dialog box, click Yes to continue.) Explore Project Templates in RequisitePro 7. Click File > New > Project. Select Use-Case Template. (If the Details check box is not checked, select it.) Read the description of the template. Notice that there are a few packaged templates to choose from, or you may create your own template. You may click other templates to read template descriptions. Click Cancel. Continue to the next guided lab. 1-4 Copyright IBM Corp. 1998, 2006

9 Getting Started Lab 1.2 Using RequisitePro Help Objectives Access Rational RequisitePro Help. Examine many types of Help available. Scenario In Lab 1.1, you explored templates and Rational RequisitePro project structure and properties. Now, glance through the Help menu and the Let s Go RequisitePro interface. Explore Help 1. From the Explorer, click Help > Let s Go RequisitePro. This feature provides help topics and additional information, such as a Rational RequisitePro tutorial, Requirements Management tour, Administration tips, process guidelines, and so on. This interface may be configured to appear when starting Rational RequisitePro (Tools > Options); otherwise it is accessible through the Help menu. 2. Click the icons in Let s Go RequisitePro to explore the different areas of information provided. Spend a few minutes exploring the additional resources. Close Let s Go RequisitePro. 3. Click Help > Contents and Index. Review the related help tabs. Click Cancel. 4. Close all Help windows. Continue to the next guided lab. Copyright IBM Corp. 1998,

10 Essentials of IBM Rational RequisitePro Workbook Lab 1.3 RequisitePro Configuration Options Objective Scenario Locate and review Rational RequisitePro project configuration options. Rational RequisitePro projects may be customized to suit your management needs. Display options, archive locations, and so on can be defined per selection. You can determine settings suited for your project by clicking Tools > Options. Let s view the configuration options available when creating a project. Explore RequisitePro Configuration Options 1. Click Tools > Options. The Options dialog box appears outlining various configuration options. 2. Clear the check boxes in the General section. Click OK. (Note the appearance of the Explorer.) Click Tools > Options. Select all of the check boxes in the General section except the Let s Go RequisitePro at startup check box. There are four General options. Show Buttons controls whether the toolbar buttons are displayed in RequisitePro. Show Status controls the visibility of the status bar at the bottom of the shell. Show Tool Tips controls the visibility of the flyover help for the buttons. If the Let s Go RequisitePro at startup check box is selected, Let s Go RequisitePro appears each time a project is opened or RequisitePro is started. 3. Select In-view requirement creation in the Views section if it is not already selected. This option lets you create a requirement directly in the database without opening the Requirements dialog box. 1-6 Copyright IBM Corp. 1998, 2006

11 Getting Started Explore RequisitePro Configuration Options 4. Review the other available configuration options. Set your options to be the same as in the following example. 5. Click OK. This completes Lab 1. Copyright IBM Corp. 1998,

12 Essentials of IBM Rational RequisitePro Workbook 1-8 Copyright IBM Corp. 1998, 2006

13 Getting Started Unguided Lab 1.1 Understand Rational RequisitePro Project Structure and Components Note: The Unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objectives Open and browse a Rational RequisitePro project. Scenario Explore the RequisitePro project list. Navigate within a sample project. Examine project components and properties. Estimated Time You have recently been hired by RU Financial Services to help manage their requirements. RU Financial Services uses RequisitePro to organize, create, manage, and maintain the requirements for the software development of a project. Several meetings occurred before you were hired and an initial version of the RequisitePro project has already been created. Some of the project information is given to you. The existing information is in many different formats (CSV files and Word documents). Your task is to manage the requirements for RU Financial Services in accordance with the Requirements Management Plan. Before you begin using Rational RequisitePro to manage requirements, learn about basic skills and online guides. This lab focuses on navigating Rational RequisitePro, RequisitePro Help, and project properties/configurations. Rational RequisitePro offers a learning tutorial that guides a new user through basic skills. The product is packaged with sample projects. You ll browse the Learning Project Use Cases in this lab. 10 minutes Copyright IBM Corp. 1998,

14 Essentials of IBM Rational RequisitePro Workbook Start Rational RequisitePro and Open the Learning Project Use Cases If the Learning Project Use Cases isn t in your project list, you will need to add it from: C:\ Program Files\Rational\RequisitePro\samples\Learning_Project-Use_Cases Username is Unknown if prompted. Tip: You can add your name through Tools > Options. Enable macros in MS Word if prompted. Click Yes to change document dialog if prompted. Open and browse the Purchase CD use case specification in the Use Cases package. Roll your mouse over the RequisitePro buttons in the Rational RequisitePro toolbar. Scroll through the document. Do you see requirements identified in the document? Close the document and maximize the Explorer. Need more guidance? See page 1-2, steps 1-4. View the Project s Properties (Select the project icon and click File > Properties) Review the Learning Project Use Cases. o o o Requirement Types. Attributes for each Requirement Type. Document Types. Is there any recent history for the project? Browse the remaining properties for the Learning Project Use Cases. Close the Learning Project Use Cases project. Need more guidance? See page 1-3, steps 5-6. Explore New Project Templates (Click File > New > Templates) Review the four templates. Which template would suit your project? Need more guidance? See page 1-4, step Copyright IBM Corp. 1998, 2006

15 Getting Started Unguided Lab 1.2 Using RequisitePro Help Objectives Scenario Access Rational RequisitePro Help. Examine many types of Help available. In Lab 1.1, you explored templates and RequisitePro project structure and properties. Now, glance through the Help menu and the Let s Go RequisitePro interface. Explore Help What does Let s Go RequisitePro offer? What are the major topics in the Help contents? Did you review the RequisitePro Extensibility Interface subtopic? Need more guidance? See page 1-5, steps 1-4. Copyright IBM Corp. 1998,

16 Essentials of IBM Rational RequisitePro Workbook Unguided Lab 1.3 RequisitePro Configuration Options Objective Locate and review project configuration options. Scenario Rational RequisitePro lets you customize your project. Display options, archive locations, and so on can be defined per selection. Through Tools > Options, you can determine the settings suited for your project. Let s view the configuration options available when creating a project. Review Configuration Options (Click Tools > Options) Study the Options menu. Do you understand what each option does for you? If not, ask the instructor or click Help. Set Configuration for the class project Enable all options for General, Views and Traceability Options except: o Let s Go RequisitePro at startup. o ENTER key inserts new line. Need more guidance? See page 1-6, steps 1-5. This completes Lab 1 Unguided version Copyright IBM Corp. 1998, 2006

17 Initial Requests for Online Stock Trading System The RU Company is a stock trading firm. Recently RU Company has been experiencing a reduction in revenue. An investigation found that the current customer base is moving to companies that provide online trading. In light of this, the RU Financial Services company is beginning an e-commerce project to develop software for a Web-based online stock and securities trading system. The new system has been tentatively named the RU e-st system. The RU e-st system allows its users to trade securities online, using a Web interface (an existing browser such as Netscape or Internet Explorer). A trading customer can log on to the Internet anywhere hotel room, airport, and so on. Users will be able to perform all the basic operations for securities trading: open accounts, trade stocks and other securities, and transfer assets among RU e-st accounts. Users can also obtain current and historical information about their accounts, such as the number of shares held, the current price, and the account total value. Customers will be able to execute many types of trade orders: market trading (buy and sell at current market prices), transfers from one mutual fund to another (within one retirement account), and limit trading (buy and sell at a specific price). The RU e-st system will use the existing Market Trading System to perform the securities trades. RU e-st will also allow users to transfer cash in an account to or from financial institutions such as banks or credit card vendors, using the existing Financial Network System. The usual restrictions will apply: For market sales, the securities to sell must be in the customer s account. For market purchases, cash for the purchase must be in the account. Transfers and purchases from an account will be allowed only if they leave at least the minimum cash in the account. Trading customers will also be able to obtain information about what is happening in the securities markets. A trading customer can obtain price quotes and news headlines by entering the trading symbol (for example, IBM ) for a particular security. The RU e-st system will obtain current and historical quotes from the existing Quote System service and news items from the existing News System. RU e-st will also have a feature to broadcast news headlines periodically on the trading customer s screen (without being asked). The system must report yearly tax information to the IRS and state tax boards. Tax forms must be communicated to the IRS and copies mailed to the customer. The information is also available online for customer viewing. Copyright IBM Corp. 1998,

18 Copyright IBM Corp. 1998,

19 Customize Project Structure Lab 2.1 Open a Rational RequisitePro Project NOTE: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page Otherwise, continue reading. Objective Open a project. Scenario As part of your new role in RU Financial Services you are required to use Rational RequisitePro to support the management of requirements according to the guidelines laid out in the Requirements Management Plan. The project structure lets you organize and manage your requirements. The structure, or project properties, can organize your requirements by type and assign attributes to the requirement types. Similarly, your requirement documents are defined by type. The Exercise CD included with the student workbook contains the initial cut of the RU e-st RequisitePro project. Estimated Time 25 minutes Copyright IBM Corp. 1998,

20 Essentials of IBM Rational RequisitePro Workbook Copy the Project to Your PC 1. Insert the Exercise CD into your computer. From My Computer, click the CD drive to view the contents. Select RU e-st.exe. Double-click RU e-st.exe to extract the project to your hard drive. Accept the default project location of C:\ and click Unzip. RU e-st.exe is a self-extracting file. Close the Self-extracting dialog box. Minimize Windows Explorer. Open an Existing RequisitePro Project 2. Click File > Open Project in RequisitePro. The Open Project dialog box appears. This box contains a list of all projects currently registered with Rational RequisitePro. 3. Click Add. The Add Project dialog box appears. Navigate to the C:\RU e-st directory and select RU e-st.rqs. Click Open. 4. Select the RU e-st project in the Open Project dialog box. Click OK. The RU e-st project opens in the Explorer. Continue to the next guided lab. 2-2 Copyright IBM Corp. 1998, 2006

21 Customize Project Structure Lab 2.2 Create RequisitePro Requirement Types Objective Define additional Requirement Types for your project. Scenario The RU e-st project structure is still a work in progress. After consulting the Requirements Management Plan you decide that an additional Requirement Type is needed. Add a New Requirement Type for a Project 1. Click File > Project Administration > Properties. Click the Requirement Types tab. 2. Compare the list of Requirement Types listed in the RM Plan (Section 3.1.2) located in the student manual. An additional Requirement Type is needed in the RU e-st RequisitePro project. Supplementary Requirement Type. 3. Click Add. The Requirement Type dialog box appears. Copyright IBM Corp. 1998,

22 Essentials of IBM Rational RequisitePro Workbook 4. Use the example below to complete the Requirement Type dialog box. Click OK. The new Supplementary Requirement Type is displayed. Leave the Project Properties dialog box open. Continue to the next guided lab. 2-4 Copyright IBM Corp. 1998, 2006

23 Customize Project Structure Lab 2.3 Create Additional Requirement Attributes Objective Create additional attributes for the Supplementary Requirement Type. Scenario The new Requirement Type includes default attributes. Attributes are used by Rational RequisitePro to assist in managing requirements. Create and modify a couple of attributes and values for the new Requirement Type. Create Requirement Attributes for a Requirement Type 1. Click the Attributes tab. Click SUPL: Supplementary Requirement Type in the Requirement Type list. Notice that default attributes exist. Using the RM Plan from the student manual, compare the attributes for the SUPL Requirement Type in your project. You will find that the RM Plan has two more attributes than exist in the project: Risk. Affects Architecture. 2. Click Add. The Add Attributes box lets you add a new attribute to the selected Requirement Type. Copyright IBM Corp. 1998,

24 Essentials of IBM Rational RequisitePro Workbook 3. Enter Risk in the Label field. Use the example below to complete the Add Attribute dialog box. Click OK. 4. Click Add to enter the attribute Affects Architecture. Use the example below to complete the Add Attribute dialog box. Click OK. 2-6 Copyright IBM Corp. 1998, 2006

25 Customize Project Structure TIP: If you select List (Single Value), you must enter list values such as High, Medium and Low in the related box. The type selected will yield different entry fields such as List Values or Default Value. For more information, see Help. Favor usage of the List data type in preference to the Text data type. By using lists, you can control the nature of the values in the attribute more closely. For example, using a list of priorities allows you to control the values entered as opposed to the unstructured format of a text data type. Copyright IBM Corp. 1998,

26 Essentials of IBM Rational RequisitePro Workbook Modify Attribute 5. Select Risk attribute for SUPL: Supplementary Requirement Type. Click Move Up multiple times until Risk is at the top of the list. Select Medium in the Values per Attribute list and then click Default. This means that Risk will be the first attribute listed in a Supplementary Requirement Attribute matrix. Click Status attribute. Select Proposed in the Values per Attribute list and then click Default. Attributes and attribute values may also be removed, although great caution should be used when removing attributes or values that reflect current project information. Use the following example to check your results. Leave the Project Properties dialog box open. Tip: Think of five to eight attributes that serve your purposes for each Requirement Type. This does not count the system attributes such as the author of a change. It does include the default attributes, such as Status. Continue to the next guided lab. 2-8 Copyright IBM Corp. 1998, 2006

27 Customize Project Structure Lab 2.4 Create and Customize Document Types Objectives Add a Document Type to the project structure. Modify a Document Type. Scenario Many Document Types are already defined. One of the documents you bring into the project is an existing supplementary specification document. Add a Document Type to the project for your supplementary requirements. Create a Document Type 1. Click the Document Types tab in the Project Properties dialog box. Compare the Document Types listed in your project to those required by the RM Plan. The Supplementary Requirements Document Type is missing from the Project properties. Copyright IBM Corp. 1998,

28 Essentials of IBM Rational RequisitePro Workbook 2. Click Add. The Document Type dialog box appears. Complete the following information to create another Document Type. Click OK. Your new Document Type appears in the list. 3. Click OK in the Project Properties dialog box. Your project remains open and is now defined according to the RM Plan. This completes Lab Copyright IBM Corp. 1998, 2006

29 Customize Project Structure Unguided Lab 2.1 Open a Rational RequisitePro Project NOTE: The unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objective Open a project. Scenario As part of your new role in RU Financial Services you are required to set up the Rational RequisitePro project to support the management of requirements according to the guidelines defined in the Requirements Management Plan. The structure, or project properties, can organize your requirements by type and assign attributes to the requirement types. Similarly, your requirement documents are defined by type. The Exercise CD supplied with the Student Workbook contains the initial cut of the RU e-st RequisitePro project. Estimated Time 25 minutes Copyright IBM Corp. 1998,

30 Essentials of IBM Rational RequisitePro Workbook Extract the class project from the Exercise CD Run RU e-st.exe from the Exercise CD. o This installs the project to C:\RU e-st. Add the RU e-st project to the Project List. (Click File > Open Project and browse to the RU e-st.rqs file.) Note: Another way to add the project to Rational RequisitePro is to open the project file (RU e-st.rqs) from the RU e-st directory. It is automatically added to the project list. Review the properties for the RU e-st project. (Click File > Properties.) Need more guidance? See page 2-2, steps Copyright IBM Corp. 1998, 2006

31 Customize Project Structure Unguided Lab 2.2 Create RequisitePro Requirement Types Objective Define additional an additional Requirement Type for your project. Scenario Your RequisitePro project structure is still a work in progress. After consulting the Requirements Management Plan you decide that an additional Requirement Type is needed. Add a New Requirement Type for a Project (Click File > Properties) What Requirement Type is missing from the project based on the RU e- st RM Plan (Section 3.1.2) in the student manual? Add the missing Requirement Type to the project. o Use the information in the RM Plan to populate the fields. o Start each initial requirement# at 1. These requirements will not be traced to external projects. Need more guidance? See page 2-3, steps 1-4. Copyright IBM Corp. 1998,

32 Essentials of IBM Rational RequisitePro Workbook Unguided Lab 2.3 Create Additional Requirement Attributes Objective Create additional attributes for the Supplementary Specification Requirement Type. Scenario You just created a new Requirement Type, which has default attributes. Attributes are used by Rational RequisitePro to assist in managing requirements. Create and modify a couple of attributes and values for the new Requirement Type. Create Requirement Attributes for a Requirement Type 2-14 Copyright IBM Corp. 1998, 2006

33 Customize Project Structure Identify and Add Missing Attributes Are there missing attributes for SUPL Requirement Type? (Refer to RM Plan.) Add any missing attributes. o o o Tip: Two attributes are missing. Do they need to be hidden? Is there a default value? Modify Risk according to the RM Plan. (Hint: change the default attribute.) Which of these attributes should be listed first? o o o Answer: Risk. Move it to the top of the list. Arrange the other attributes. Click the Status attribute and change the default value to Proposed. Need more guidance? See page 2-5, steps 1-5. Copyright IBM Corp. 1998,

34 Essentials of IBM Rational RequisitePro Workbook Unguided Lab 2.4 Create and Customize Document Types Objectives Add a Document Type to the project structure. Modify a Document Type. Scenario Many Document Types are already defined. One of the documents you bring into the project is an existing supplementary specification document. Add a Supplementary Specification Document Type to the project. Create and Customize a Document Type Identify the missing Document Type (Refer to the RM Plan). Add the missing Document Type. o o Use the information in the RMP to populate the fields. Enforce the use of the RUP templates for the outline. Modify the Outline for Use Case Specification Document Type to None. Need more guidance? See page 2-9, steps 1-3. This completes Lab 2 Unguided version Copyright IBM Corp. 1998, 2006

35 Gather and Enter Requirements Lab 3.1 Import Requirements into the Project Database NOTE: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page Otherwise, continue reading. Objectives Scenario Import requirements from a Comma Separated Value (CSV) file. Your project is defined with Requirement Types, Document Types, and attributes. The structure is typically defined early and documented in a Requirements Management Plan. You are ready to populate the project with requirements and data. An analyst listed the supplementary requirements and their attributes in an Excel document. You don t want to enter these requirements manually, so import the requirements using the RequisitePro Import wizard. Importing data from outside RequisitePro can automatically create requirements in the project database. Estimated Time 30 minutes Copyright IBM Corp. 1998,

36 Essentials of IBM Rational RequisitePro Workbook Import Requirements from a CSV File 1. Create an attribute matrix for the Supplementary requirements. Right-click the RU e-st project in the Explorer and select New > View. Use the following example to complete the View Properties dialog box. The Private check box indicates whether the view is available to the whole team or just yourself. Click OK. Observe the new view created directly under the project. Note that no requirements are defined yet. Note the asterisk (*) next to the view name. This indicates that the view has not yet been saved to the database. (If you cannot see the asterisk you may need to increase the width of the RequisitePro Explorer.) Select File > Save View. Notice that the asterisk is removed from the view name once it has been saved. 2. Select the Project icon in the Explorer. Click File > Import. The Import Wizard dialog box appears. 3-2 Copyright IBM Corp. 1998, 2006

37 Gather and Enter Requirements 3. Click Comma Separated Value. Click Browse and locate the Additional Files folder on the Exercise CD. Select Supplementary Requirements.CSV. Click Open, and then click Next. This step identifies the file to be imported into Rational RequisitePro. 4. In the Requirement Types list, click SUPL: Supplementary Requirement Type. Click Next. 5. Click Match Manually. Rational RequisitePro provides a manual mapping of attributes between the external attributes being imported and the existing attributes. Look at the mappings. Notice that the requirements you are importing do not have all the attributes defined that the project includes. These attributes should be set manually later. Click Cancel. 6. Click Next. This step allows new requirements to be defined by the import, or the option to update only the attributes of the existing requirements from the CSV file. 7. Click Define new RequisitePro requirements. Click Next. 8. Click View. The requirements and attributes data ready for import are listed. You may remove any listed requirements if necessary. Close the Edit Imported Requirements dialog box. Click Next. This window lets you control the requirements that are actually imported into the current project database. Click Current project database. Click Next. Copyright IBM Corp. 1998,

38 Essentials of IBM Rational RequisitePro Workbook 9. The final Import Wizard dialog box displays all text found as requirements. Click Commit. The database is updated. The Import Wizard commits all discovered requirements to the database. The new requirements are located directly under the project icon in the Explorer. In a subsequent exercise, you will create a package and move these requirements for better project organization. You should observe something similar to the example below. Leave the view open. Continue to the next guided lab. 3-4 Copyright IBM Corp. 1998, 2006

39 Gather and Enter Requirements Lab 3.2 Create Requirements in the Project Database Objectives Scenario Create new requirements directly in a view. Identify the location of an existing requirement. Delete a requirement. Now you have imported some supplementary requirements into the database. You would also like to enter requirements into the project database relating to the use cases. Enter new use case requirements and their brief descriptions. This lab focuses on various techniques for manual identification and creation of requirements. Enter Requirements Directly into the Project Through a View 1. Click <Click here to create a new requirement> in the All Supplementary Requirements view. Leave the requirement Name field blank. In the Text box, type: The system shall keep a record of all transactions for seven years. Press the ENTER key. A new software requirement is added to the project. Note: If ENTER does not commit the requirement, go back to Lab 1.3 to set options. Save the view. Close the current view by clicking the Close button in the top-right corner of the view. 2. Right-click the Use Cases package in the Explorer, and then click New > View. Use the following example to complete the View Properties dialog box. Copyright IBM Corp. 1998,

40 Essentials of IBM Rational RequisitePro Workbook Click OK. Observe the new view. No requirements are defined yet. 3. Select and click <Click here to create a requirement>. In the Text box, type: Get Quote. Press ENTER to commit (save) the requirement. The text of the requirement is displayed in the Requirements list. 4. Click <Click here to create a requirement>. In the Name box, type: Quotes about Trading Price. In the Text box, type: The Trading Customer can get current and historical info about stocks. Press ENTER to commit (save) the requirement. Note: The requirement name is displayed in the Requirements column, and it is in bold type (with user default settings). Requirement names are optional and are intended to be short labels that are easy to see in the view. A name was used for this requirement because the text of the requirement is too long to see completely in the view. 5. Click <Click here to create a requirement>. Enter another UC requirement: In the Text box, type: Distribute News. Press ENTER. 3-6 Copyright IBM Corp. 1998, 2006

41 Gather and Enter Requirements 6. Click <Click here to create a requirement>. Enter another UC requirement with the following: Name box: Broadcast news headlines. Text box: RU e-st obtains headlines about current market news and broadcasts them to customers. Press ENTER. 7. Enter another UC requirement with the following information: Text box: Review Account History. Press ENTER. By entering the UC requirements directly in the database you have recorded some use cases before they are documented. You may also enter the values for attributes. Modify Requirement Attributes 8. Select the requirement named Quotes about Trading Price in the view. An arrow on the left indicates the current requirement. Use your arrow keys to find the Priority attribute. Click once in the Priority attribute value cell. Change the value to High and press ENTER key. Use the arrow keys to find the Property attribute. Change the value to Brief Description and press ENTER key. Copyright IBM Corp. 1998,

42 Essentials of IBM Rational RequisitePro Workbook 9. Click the UC: Get Quote requirement in the view. Use the arrow keys to find the Priority attribute. Change the value of this attribute to High and press ENTER. Delete a Requirement from a View 10. Select the UC requirement with the name Broadcast news headlines. 11. Click Edit > Delete from the RequisitePro menu. A message appears, asking you to confirm the deletion. Click Yes. Deleting requirements causes you to lose all the revision history and attribute settings for the requirement. Alternative: Consider having a special attribute called Deleted so you can use the RequisitePro query engine to hide/find deleted entries. 12. Save the view and continue to the next lab. Click File > Save View. 3-8 Copyright IBM Corp. 1998, 2006

43 Gather and Enter Requirements Lab 3.3 Organizing the Project Database Objectives Organize your project using packages. Scenario Move requirements between packages. Some requirements have been entered into the database. You ve manually entered UC requirements and imported software requirements. Some of the requirements can be grouped and organized together. Packages enable you to visually organize your requirements and associated artifacts in a way that promotes ease of use and understanding. Organize Your Requirements 1. Right-click the project icon and then click New > Package. Enter the new package information. Name: Supplementary Requirements. Description: This package contains all requirements and associated artifacts for the Supplementary Requirement type. Click OK. 2. From the Explorer, select the All Supplementary Requirements view, as well as all of the SUPL requirements. Drag and drop the view and all the SUPL requirements in the Supplementary Requirements package. The requirements and view are relocated to the Supplementary Requirements package. Tip: Packages are a very powerful way to visually organize your requirements. They are intended to reduce the need to use hierarchies to organize your requirements. Copyright IBM Corp. 1998,

44 Essentials of IBM Rational RequisitePro Workbook 3. Organize your use case requirements. Create a package called Get Quote under the Use Cases package. Move the four new Get Quote use case requirements to the Get Quote package. It is important that you make the requirements repository as intuitive as possible. You can achieve this by creating a package for each use case. Group the related requirements together. Compare your results to the example below. Continue to the next guided lab Copyright IBM Corp. 1998, 2006

45 Gather and Enter Requirements Lab 3.4 Hierarchical Relationships in the Project Database Objectives Scenario Create hierarchical relationships directly in the project repository. Manipulate hierarchical relationships among requirements. Some requirements have been entered into the database. You ve manually entered UC requirements and imported supplementary requirements. Some of the requirements can be grouped and organized together. Hierarchical relationships are used to subdivide a general requirement into more explicit requirements. Create a Hierarchical Relationship Between Existing Requirements 1. Expand the Use Cases package. If the All Use Case Requirements view is not open, right-click All Use Case Requirements in the Explorer. Click Open. 2. Select the UC requirement Quotes about Trading Price in the view. Copyright IBM Corp. 1998,

46 Essentials of IBM Rational RequisitePro Workbook 3. Right-click the requirement and select Change Parent. The Select New Parent Requirement dialog box allows you to set this requirement as a child of a different requirement. From the New Parent list, click Choose Parent. The Parent Requirement Browser dialog box appears. This lets you scroll through the all candidates and select the parent for the child requirement. Select Get Quote as the new parent requirement. Click OK to confirm the parent selection. Click OK in the Select New Parent dialog box. 4. Select View > Expand All. The Quotes about Trading Price requirement is a child of the requirement Get Quote. Note: RequisitePro converts the use case requirement into a child requirement with the same base tag number as the parent requirement, Get Quote. RequisitePro adjusts the child requirement tag to reflect the same base tag number as the new parent requirement. Also, the leaf number is adjusted to supply a unique number for the new child requirement. Create Hierarchical Relationships by Entering the Child Requirements 5. From the All Use Case Requirements view, right-click the Get Quote requirement. Click New Child. In the Name field, type: Customer Logs On. In the Text field, type The use case starts when the Trading Customer logs on. The system validates the customer ID and password. Press ENTER. The new requirement becomes another child requirement for the Get Quote requirement. RequisitePro creates a child requirement with the same base tag number as the parent requirement. The leaf number is adjusted to supply a unique number for the new child requirement Copyright IBM Corp. 1998, 2006

47 Gather and Enter Requirements 6. Create another new child for the Get Quote requirement. Type in the Text field: The Trading Customer chooses the trading function Get Quote. Press ENTER. The new requirement becomes a third child requirement for the UC Get Quote requirement. 7. Compare your results to the following example: Tip: Reparenting retains the entire sub-tree relationship of the reparented child. Reparenting is the only mechanism for promoting and demoting child relationships. Thus, if you wish to move a child entry up (or down) in a hierarchical tree, you should think in terms of reparenting the child to a higher (or lower) parent in the tree. 8. Save and close all views. Leave the project open for the next lab. This completes Lab 3. Copyright IBM Corp. 1998,

48 Essentials of IBM Rational RequisitePro Workbook 3-14 Copyright IBM Corp. 1998, 2006

49 Gather and Enter Requirements Unguided Lab 3.1 Import Requirements into the Project Database NOTE: The Unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objective Import requirements from a Comma Separated Value (CSV) file. Scenario Your project is defined with Requirement Types, Document Types, and attributes. The structure is typically defined early and documented in a Requirements Management Plan. You are ready to populate the project with more requirements and data. Project data existed before you connected to the RequisitePro project. An analyst listed the supplementary requirements and their attributes in an Excel document. You don t want to re-enter these requirements manually, so import the requirements using the RequisitePro Import Wizard. Importing data from outside RequisitePro can automatically create requirements in the project database. Estimated Time 30 minutes Copyright IBM Corp. 1998,

50 Essentials of Rational IBM RequisitePro Workbook Create a View To Import Requirements from a CSV File Which view allows you to see all of the attributes for a Requirement Type: o Attribute Matrix, Traceability Matrix, Traceability Tree? Create a view that displays all of the Supplementary requirements and their attributes currently in the RU e-st project. o o o o Locate the view under the root directory (not something we d typically do): Name the view All Supplementary Requirements and give it a description. Share the view to all users of the project. How many supplementary requirements did you find? Need more guidance? See page 3-2, steps 1. Import a Supplementary Requirements.CSV file Locate the Supplementary Requirements.csv file (Comma Separated Values) and read its contents. Import the requirements into the project database. o Explore how manual mapping works, then click Cancel. Notice that the view now displays our imported requirements. o o The * indicates that the view has not been saved. A saved view stores the query, not the data. How many requirements are there? You should have created these in a package, not at the top. Need more guidance? See page 3-2, steps Copyright IBM Corp. 1998, 2006

51 Gather and Enter Requirements Unguided Lab 3.2 Create Requirements in the Project Database Objectives Create new requirements directly in a view. Identify the location of an existing requirement. Delete a requirement. Scenario Now you have imported some supplementary requirements into the database. You would also like to enter requirements into the project database relating to the use cases. Enter UC requirements and their brief descriptions. This lab focuses on various techniques for manual identification and creation of requirements. Enter Requirements Directly into the Project Through a View Add a new supplementary requirement. Use the All Supplementary Requirements view. o Requirement is The system shall keep a record of all transactions for seven years. Save the view. Need more guidance? See page 3-5, step 1. Create an Attribute Matrix view in the Use Cases package named All Use Case Requirements. Create the following five use case requirements in the new view: Copyright IBM Corp. 1998,

52 Essentials of Rational IBM RequisitePro Workbook Requirement Name --no name-- Requirement Text Get Quote Quotes about Trading Price --no name-- Broadcast News Headlines --no name-- The Trading Customer can get current and historical information about the trading price of securities. Distribute News RU e-st obtains headlines about current market news and broadcasts them to Trading Customers. Review Account History Using just the keyboard, navigate through the attributes for the requirement Quotes about Trading Price. Its Location value is Database. Set its Priority value to High and its Property value to Brief Description. Set the Priority value for Get Quote requirement to High as well. Delete the Broadcast News Headlines UC requirement. Need more guidance? See page 3-5, steps Copyright IBM Corp. 1998, 2006

53 Gather and Enter Requirements Unguided Lab 3.3 Organizing the Project Database Objectives Organize your project using packages. Move requirements between packages. Scenario Some requirements have been entered into the database. You ve manually entered UC requirements and imported software requirements. Some of the requirements can be grouped and organized together. Packages enable you to visually organize your requirements and associated artifacts in a way that promotes ease of use and understanding. Organize Your Requirements Click Collapse All from the View menu. Create a package named Supplementary Requirements and give it a brief description. Move the Supplementary Requirements view into the new package. Add another package for the Get Quote Use Case. Move all of the current UC requirements into the Get Quote Use Case package (but not the view). Need more guidance? See page 3-9, steps 1-4. Copyright IBM Corp. 1998,

54 Essentials of Rational IBM RequisitePro Workbook Unguided Lab 3.4 Hierarchical Relationships in the Project Database Objectives Scenario Create hierarchical relationships directly in the project repository. Manipulate hierarchical relationships among requirements. Some requirements have been entered into the database. You ve manually entered UC requirements and imported supplementary requirements. Some of the requirements can be grouped and organized together. Hierarchical relationships are used to subdivide a general requirement into more explicit requirements Copyright IBM Corp. 1998, 2006

55 Gather and Enter Requirements Create a Hierarchical Relationship Between Existing Requirements Make Quotes about Trading Price a child requirement of the Get Quotes requirement. Create two new child requirements for Get Quote. o Create the two new requirements directly from Get Quote with the following text: 1. The use case starts when the Trading Customer logs on. The system validates the customer ID and password. 2. The Trading Customer chooses the trading function Get Quote. Compare your results with the following example: Save and Close all views. Need more guidance? See page 3-11, steps 1-8. This completes Lab 3 Unguided version. Copyright IBM Corp. 1998,

56 Essentials of Rational IBM RequisitePro Workbook 3-22 Copyright IBM Corp. 1998, 2006

57 RequisitePro Documents Lab 4.1 Create a Requirements Document from an Outline and Manually Enter Requirement Text NOTE: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page Otherwise, continue reading. Objectives Use a predefined Document Type to create a document in the project. Scenario You have been given external files containing data to import. The requirements in your RequisitePro documents are maintained in the project database. The documents include: Stakeholder Requests document for questionnaire feedback. Execute Trade to capture use case requirements. Vision to define the feature requirements. Supplementary Specification to define supplementary software requirements. Estimated Time 60 minutes Copyright IBM Corp. 1998,

58 Essentials of IBM Rational RequisitePro Workbook Create a New Document in RequisitePro and Manually Add Requirements. 1. Right-click the project icon in the Explorer, and then click New > Package. Create a Stakeholder Requests package. Enter a description for the package: This package contains all requirements and artifacts related to stakeholder requests. 2. Right-click the Stakeholder Requests package, and then click New > Document. The Document Properties dialog box opens. 3. Use the example below to complete the Document Properties dialog box. The Show Tags option sets up the document to automatically display the identification tag of every requirement in the document. Click OK. The new document is created under the Stakeholder Requests package. Word is open and within it, your new document. 4-2 Copyright IBM Corp. 1998, 2006

59 RequisitePro Documents 4. Manually enter requirements in the document. Scroll to Section 3, Assessing the Problem (located beyond the table of contents.) Answer some of the questions and make requirements from the answers. Below the question Why does this problem exist? type: Customers want stock market information 24 hours a day. Select the text you entered. Click RequisitePro > Requirement > New. The Requirement Properties dialog box appears. If New is disabled, click the RequisitePro client window to bring it to the foreground and then click the Word window. Enter the requirement name: Trade online any time. Click the Attributes tab. Set the attribute Priority value to High. Compare your results to the following example. Click OK. A STRQ requirement is created and marked as pending. Copyright IBM Corp. 1998,

60 Essentials of IBM Rational RequisitePro Workbook 5. Using the New Requirement button in the RequisitePro toolbar, create two more requirements in the Stakeholder Requests document. (Enter miscellaneous text.) Set the attribute Priority value to High, and then click OK. The requirements you create are in a pending state. Click RequisitePro > Document > Save from the Word menu bar. The pending status is removed. The requirements are committed to the database. NOTE: Changes to the document may be saved in two ways: Word menu: RequisitePro > Document > Save. Click Save Requirements Document in the RequisitePro toolbar. Compare your results to the following example : 6. Click RequisitePro > Document > Close. Continue to the next guided lab. 4-4 Copyright IBM Corp. 1998, 2006

61 RequisitePro Documents Lab 4.2 Import a Word Document and Manually Create Requirements Objectives Import document information into a RequisitePro project. Manually create new requirements from document text. Import a Word document and its requirements. Scenario Rational RequisitePro lets you use documents created from sources other than RequisitePro. In this lab, insert text from external documents into a newly created RequisitePro document and manually create requirements from the inserted text. Also, import a document (Requirements Management Plan) into the project. Copyright IBM Corp. 1998,

62 Essentials of IBM Rational RequisitePro Workbook Import a Word Document into the Project 1. Create a package to contain the requirements and artifacts for the Execute Trade use case. Right-click the Use Cases package in the RequisitePro Explorer and then click New > Package. Name the package Execute Trade. Description: This package contains the requirements and artifacts related to the Execute Trade use case. Click OK. 2. Click File > Import in the Explorer. The Import Wizard opens. Click Microsoft Word Document as the source. Browse to the Exercise CD. Select Execute_Trade.doc. Click Open, and then click Next. Click Document Only, and then click Next. 3. Use the example below to complete the Document Properties dialog box. Click OK. 4-6 Copyright IBM Corp. 1998, 2006

63 RequisitePro Documents The Import Wizard asks if you want to include formatting of the imported document. This dialog box appears if the imported document does not use the Word normal.dot template or it doesn't match the outline template for the document type. Click No to overwrite the formatting of the imported document. Click Commit. Word opens the Execute Trade document. 4. Scroll the contents of the Execute Trade.UCS document. Create Requirements Manually in the Execute Trade.UCS Document 5. Scroll to section 1. Use Case Name: Execute Trade. Select the text Execute Trade. Click New Requirement button from the RequisitePro toolbar. Click OK in the Requirements Properties dialog box. 6. Create another requirement from the basic flow steps. Scroll to the section named 2. Flow of Events. The basic flow is described in this section. Select the following sentences in the document: The use case starts when the Trading Customer logs on. The system validates the customer ID and password. Click RequisitePro > Requirement > New on the Word menu bar. Change the attribute values for Priority and Status from the Requirement Properties dialog box. (Hint: Scroll the attributes to find Priority and Status.) Click OK in the Requirement Properties dialog box. The document now has two new pending requirements. 7. Select another basic flow step sentence. Click New Requirement in the RequisitePro toolbar. Click the Attributes tab. Change the attribute values for Priority to High and Status to Approved. Click OK. There should be some pending requirements. Copyright IBM Corp. 1998,

64 Essentials of IBM Rational RequisitePro Workbook 8. Create two more requirements from the basic flow section. There is a faster way to create requirements in the document. It is called Fast-Create. You can quickly create a requirement in a document by selecting the text in the document that you want to be the requirement text. Press the SHIFT key and, in Word, click New Requirement on the RequisitePro toolbar. The requirement is automatically created; the Requirement Properties dialog box does not appear. The requirement is based on the default requirement type associated with the Document Type. Note: If you release the SHIFT key too early, the Fast Create reverts to an ordinary Requirement > Create option and opens the Requirements Properties dialog box. 9. Create two more requirements from the Flow of Events section by using Fast Create. All requirements created are pending until you save the document. 10. Click RequisitePro > Document > Save in the Word menu bar. All pending requirements are committed as official requirements. 11. Click RequisitePro > Document > Close in the Word menu bar. It is not necessary to close the document, but it maximizes system resources. Continue to the next guided lab. 4-8 Copyright IBM Corp. 1998, 2006

65 RequisitePro Documents Lab 4.3 Import a Document with Text (Create Requirements Using Keywords) Objectives Create a RequisitePro document by importing the Vision document. Create requirements using keywords while importing. Scenario The Import wizard creates requirements based on keywords, text delimiters, or Word styles. Let s import the existing Vision document into the project. You want RequisitePro to create requirements from the document text while importing the document. Instruct RequisitePro to create a feature requirement (FEAT) from every sentence that contains the keyword must. Import a Vision Document and Requirements Using Keywords 1. Select the Features and Vision package in the Explorer. Click File > Import. The Import Wizard dialog box opens. 2. Click Microsoft Word Document. Browse to the Exercise CD and open the Additional Files folder. Select Vision.doc, and then click Open. Click Next. These steps identify the document to be imported into the project. 3. Click Requirements and document. Click Next. Copyright IBM Corp. 1998,

66 Essentials of IBM Rational RequisitePro Workbook 4. The Document Properties dialog box appears. Move the dialog box from the center of the screen. Enter the following information in the associated boxes. Click OK to close the Document Properties dialog box. (Click Enable Macros IF a Microsoft Word dialog box appears.) The templates are not the same, so the Import Wizard asks if you want to include formatting of the imported document. Click No Copyright IBM Corp. 1998, 2006

67 RequisitePro Documents 5. Use the example below to complete the Import Wizard dialog box. The Import Wizard dialog box appears and allows delimiters to be selected that serve as a basis for requirement creation. Note: In some circumstances the Import Wizard dialog box may be hidden behind the Word window. Click the RequisitePro icon on the taskbar to display this dialog box. Once you change the keyword to must, click Add. You have instructed the Import parser how to recognize a requirement in the document to be imported. Notice that other techniques exist and might be useful depending on your own project development standards. Click Next. RequisitePro searches the document and creates requirements that are based on the established criteria. Each requirement found is displayed in the Requirement Found box. Click Yes. Click Yes to All and bypass confirmation of each requirement. Copyright IBM Corp. 1998,

68 Essentials of IBM Rational RequisitePro Workbook The final Import Wizard page displays all statements found as requirements. 6. Click Commit to update the database. Unlike the manual creation of requirements in an earlier lab, the Import Wizard saves all discovered requirements as final requirements and does not leave them in a pending state. The requirement document is created in the project folder with requirements defined based on the keyword must. 7. Review the Vision document and its requirements (enclosed with bookmarks). The requirements have been created under the correct package in the Explorer. 8. Click RequisitePro > Document > Save. Minimize Word. The Vision document remains open, but minimized. Maximize the Explorer. Continue to the next guided lab Copyright IBM Corp. 1998, 2006

69 RequisitePro Documents Lab 4.4 Import a RequisitePro Document with Requirements Objectives Import a requirements document with existing requirements in bookmarks. Save a requirements document from the project as a Word document. Scenario Import a RequisitePro document already containing requirements from a different project into your project. Import a RequisitePro Document and Requirements 1. Select the Supplementary Requirements package. Click File > Import. 2. Click Microsoft Word Document for source. 3. Browse to the Exercise CD and open the Additional Files folder. Choose All Files (*.*) from the Files of type menu. Hint: The file name extension of the supplementary file is NOT the usual.doc extension. Be careful when searching for the file in the Word Open dialog box. Click Supplementary_Specifcation.SUP. Click Open, and then click Next. Click Document Only, and then click Next. Copyright IBM Corp. 1998,

70 Essentials of IBM Rational RequisitePro Workbook 4. Use the following example to complete the Document Properties dialog box. Click OK. The Import Wizard asks if you want to include formatting of the imported document. Click No for formatting the imported document. Note: In some circumstances the Import Wizard dialog box may be hidden behind the Word window. 5. The Import Wizard prompts you to answer the question: Click No. Since RequisitePro generated this document, it already contains bookmarks that indicate existing requirements. As a result, it is not necessary to indicate any delimiters. RequisitePro automatically detects the bookmarks. Click Commit. Review the contents of the document Copyright IBM Corp. 1998, 2006

71 RequisitePro Documents 6. New requirements have been defined. Scroll to a requirement in the document. Click in the requirement text, and then click RequisitePro > Requirement > Delete (Unmark). Click Yes to confirm the deletion. 7. Click RequisitePro > Document > Save. Copyright IBM Corp. 1998,

72 Essentials of IBM Rational RequisitePro Workbook Export a Document for External Use A RequisitePro document can be exported as a Word document for customers and non-requisitepro users to view. 8. Make sure Supplementary Specification.SUP is open in Word. Click RequisitePro > Document > Save As in the Word menu bar. The RequisitePro standard assumption with Save As is that you wish to create a Word document outside the project boundary. Click Save to create a copy of the RequisitePro document. A dialog box appears notifying you that the document has been saved. Click OK. This saves a copy of the RequisitePro document in Word format with a.doc extension. The RequisitePro document remains intact and in the project. Click Yes if prompted. Notice that the document in Word is now the document you just saved. The document from the project has been closed. Changes to this document will not update the RequisitePro project. 9. Click RequisitePro > Document > Close in Word. Click Yes to save changes if a dialog box appears. Note: The Vision.VIS may still be open from Lab 4.3. Continue to the next guided lab Copyright IBM Corp. 1998, 2006

73 RequisitePro Documents Lab 4.5 Create Hierarchical Requirements in a Document Objectives Create hierarchical requirements in a document. Manipulate hierarchical relationships among requirements. Delete a hierarchical requirement. Scenario As you investigate some of the high-level requirements in your vision, you will create more refined requirements. These need to be expressed in the Vision document. Specifically, you will create requirements in the Vision document and then define some hierarchical relationships for feature requirements (FEAT) in the Vision document. Copyright IBM Corp. 1998,

74 Essentials of IBM Rational RequisitePro Workbook Create Hierarchical Requirements and Remove Requirements in a Document 1. The Vision.VIS document should be open from the previous lab. If not, open Vision.VIS using the skills you learned in earlier labs. 2. Scroll to the FEAT1 requirement in Section 5. Use this requirement as the parent (root) requirement Copyright IBM Corp. 1998, 2006

75 RequisitePro Documents 3. Highlight the sentence For market sales, the securities are in the customer s account. Click New requirement on the RequisitePro toolbar. The Requirement Properties dialog box appears. Set this requirement as a child of the previous requirement. Click the Hierarchy tab. Click choose parent on the Parent drop-down list. Select FEAT1 as parent requirement. Click OK. Click OK to confirm the parent selection. Rational RequisitePro creates a pending child requirement with the same base tag number as the parent requirement. Notice that the leaf number is adjusted to supply a unique number for the new child requirement. Copyright IBM Corp. 1998,

76 Essentials of IBM Rational RequisitePro Workbook Tip: Reparenting retains the entire sub-tree relationship of the reparented child. Reparenting is the only mechanism by which promotion/demotion of child relationships can be accomplished. Thus, if you wish to move a child entry up (or down) in a hierarchical tree, you should think in terms of reparenting the child to a higher (or lower) parent in the tree. 4. Click the Save Requirements Document button on the toolbar. The child requirement is committed to the database. A dialog box may appear, asking you to confirm the action. Rational RequisitePro provides a quick and easy way to assign a new parent to an existing child requirement or to demote a parent or promote a child requirement to a parent. Compare your results to the following example: 5. Click in the newly created child requirement. Click the Requirement Properties button. Note: You can also right-click in the requirement text and select Requirement Properties from the context menu. Click the Hierarchy tab. Make FEAT2 the new parent for the child requirement. Note: A new parent may be selected, or the child requirement may be promoted to a parent requirement. You may also click on a parent requirement and demote it to a child requirement by assigning it a parent in this window. 6. Click the Attributes tab. Set the Priority attribute value to High. Click OK Copyright IBM Corp. 1998, 2006

77 RequisitePro Documents 7. Save the document. Enter a change description. Click OK. Note: In some circumstances, the Change Description dialog box may be hidden behind the Word window. The requirement is committed to the database and the tag is no longer pending. 8. Look at the impact deleting a hierarchical requirement may have. Select the FEAT2 parent requirement. Click RequisitePro > Requirement > Delete (Unmark). RequisitePro asks you to confirm the requirement deletion. Click Yes. Note: The attempted deletion of hierarchical requirements causes a special dialog box to appear. This box allows you to determine the handling of the child requirements when the parent is deleted. Click Cancel. Do not delete the requirement. 9. Click RequisitePro > Document > Close. Save any changes if prompted. Copyright IBM Corp. 1998,

78 Essentials of IBM Rational RequisitePro Workbook Lab 4.6 Take a Document Offline Objectives Take a RequisitePro document offline. Specify a location and reason for taking the document offline. Identify the read-only copy of the document in RequisitePro. Scenario Offline authoring allows a RequisitePro document to be taken out of a project and worked on in Word outside of the RequisitePro software, leaving a read-only copy behind for other project members to view. When taken offline, the documents are embedded with macros that allow the user to create and delete (unmark) requirements from the Word document. When the document is brought back online (into the associated RequisitePro project), the database is updated to reflect the changes made to the document. Project documents can be sent to customers for editing and approval. Their changes can be easily merged into the project. Offline authoring can be a good solution for development teams that work in a dispersed environment. By taking the document offline, you can detail specifications and create requirements outside of RequisitePro Copyright IBM Corp. 1998, 2006

79 RequisitePro Documents Take a Document Offline 1. Click Tools > Offline Documents. The Offline Documents dialog box appears. All documents in the project that are available to be taken offline are listed in the Online Documents list. 2. Click Execute Trade.UCS. Click Take Offline. 3. Enter a reason for taking the document offline, such as Adding an alternative flow for the Execute Trade use case. Click Browse to save the offline document to the desktop. 4. Click OK in the Browse for Folder dialog box. Click OK in the Take Offline Information dialog box. Your document is moved to the Offline Documents section of the Offline Documents dialog box and stored on the desktop. Click Close in the Offline Documents dialog box. Copyright IBM Corp. 1998,

80 Essentials of IBM Rational RequisitePro Workbook 5. Select the Execute Trade document in the Explorer. A modified icon provides a visual indication that the document has been taken offline. The document is available to other team members as a read-only document until the offline document is returned to the project. Right-click Execute Trade. Click Offline > Information. The resulting display shows the location, the current owner, and the date and reason for taking the document offline. Click Close. 6. Click File > Close Project. Click Yes in the Project Close dialog box. Save any views. Exit RequisitePro. Continue to the next guided lab Copyright IBM Corp. 1998, 2006

81 RequisitePro Documents Lab 4.7 Edit an Offline Document Objectives Create requirements in an offline document. Delete (unmark) requirements in an offline document. Edit the text of an offline document. Scenario Now the document is offline and ready for you to update. Let s open it and enter the new information (add an alternative flow). First, make sure the macros are set properly for Word. Word defaults to the highest level for macro security. This setting prevents the enabling of RequisitePro offline authoring macros. Check your security settings before editing the document. Edit an Offline Document Using Word 1. Open Word. (Make sure Rational RequisitePro is closed.) Click Tools > Macro > Security > Medium > OK. 2. Click File > Open. Locate the offline document on your desktop. Select All Files (*.*) on the Files of type menu. Select Execute Trade document. Click Enable Macros if the Microsoft Word dialog box appears. The Word menu bar includes a RequisitePro menu. This is a result of the embedded macros from the RequisitePro offline-authoring feature. Copyright IBM Corp. 1998,

82 Essentials of IBM Rational RequisitePro Workbook 3. Place the cursor anywhere in Section 2.2, Alternative Flows. Type: Newly discovered alternative flow. (This is for demonstration purposes.) Select the text Newly discovered alternative flow. Click RequisitePro > Requirement > Create. Click OK. The requirement is created and becomes styled in a format that will be recognized by RequisitePro when the document is brought online. 4. Create two requirements in the offline document by selecting text in the document. Click RequisitePro > Requirement > Create. Requirements can also be removed from a document while offline from a RequisitePro project. 5. Place the cursor in a requirement you just created. Click RequisitePro > Requirement > Delete (Unmark) in the Word menu. Click Yes when asked to confirm your action. The requirement is unmarked as a requirement. The requirement is deleted from the project and returned to plain text when the document is brought online. Note: Delete (Remove) removes the requirement styling and the associated text. This function is available only within RequisitePro. 6. Save changes that were made during the offline authoring: Click File > Save. Close Word Copyright IBM Corp. 1998, 2006

83 RequisitePro Documents Bring an Offline Document Back Online 1. Start Rational RequisitePro. Open the RU e-st project. 2. Click Tools > Offline Documents. The Offline Documents dialog box appears. 3. Select Execute Trade.UCS document from the Offline documents section. Click Bring Online. A Change Description dialog box appears. Use the example below to complete the Bring Online Information dialog box. Click OK. 4. Click Enable Macros if the Microsoft Word dialog box appears. Rational RequisitePro prompts you to confirm the deletion of any requirements from the project. Copyright IBM Corp. 1998,

84 Essentials of IBM Rational RequisitePro Workbook 5. Browse the document and view the tagged requirements. Your document is brought back online, and all changes are saved. The document is opened in Word with the newly created requirements. Minimize Word. Close the Offline Documents dialog box. This completes Lab Copyright IBM Corp. 1998, 2006

85 RequisitePro Documents Unguided Lab 4.1 Create a Requirements Document from an Outline and Manually Enter Requirement Text NOTE: The Unguided labs are for students who feel they would benefit from fewer stepby-step instructions. Objective Create a RequisitePro document and enter requirements manually. Scenario You have been given external files containing data to import. Now, create RequisitePro documents that enable you to organize requirements by type. The requirements located in your RequisitePro documents are maintained in the project database. The documents include: Stakeholder Requests for questionnaire feedback. Execute Trade to capture use case requirements. Vision to define the feature requirements. Supplementary Specification to define supplementary software requirements. Estimated Time 60 minutes Copyright IBM Corp. 1998,

86 Essentials of IBM Rational RequisitePro Workbook Create a New Document in RequisitePro and Manually Add Requirements. Create a new package at the top level of the project called Stakeholder Requests. Add a new blank document to the package. o o Name: Stakeholder Requests based on the Stakeholder Request Document Type. Show tags in the document. Go to section 3 of the new document and type in the answer for three questions. o For example, an answer to Why does this problem exist? could be, Customers want stock market information 24 hours a day. Customers need access to their accounts beyond normal business hours. Create three requirements from the answers to the questions. Set each requirement priority to High. Need more guidance? See page 4-2, steps Copyright IBM Corp. 1998, 2006

87 RequisitePro Documents Unguided Lab 4.2 Import a Word Document and Manually Create Requirements Objectives Import a document into a RequisitePro project. Manually create new requirements from document text. Import a Word document. Scenario RequisitePro lets you use documents created from sources other than RequisitePro. In this lab, insert text from external documents into a newly created RequisitePro document and manually create requirements from the inserted text. Also, import a document (Requirements Management Plan) into the project. Copyright IBM Corp. 1998,

88 Essentials of IBM Rational RequisitePro Workbook Import Text from Another Source Create a package to hold the Execute Trade use case. Add a new document for the Execute Trade use case. o It is blank because there is no associated template for this document type. Click Insert > File to insert text from Execute_Trade.doc in the Additional Files folder on the Exercise CD. Review the use case. Need more guidance? See page 4-6, steps 1-4. Create Requirements Manually In Section 1, highlight the name of the use case Execute Trade and make it a requirement. Adjust the attributes. In Section 2, highlight four different steps and make each another requirement. Change the attributes values for Priority to High, and Status to Approved. Use Fast-Create to create four more requirements (hold the shift key and click the Create Requirement button). Click RequisitePro >Document >Save. Close the document and minimize Word. Need more guidance? See page 4-7, steps Copyright IBM Corp. 1998, 2006

89 RequisitePro Documents Unguided Lab 4.3 Import a Document with Text (Create Requirements Using Keywords) Objectives Create a RequisitePro document by importing the Vision document. Create requirements using keywords. Scenario The Import Wizard creates requirements based on keywords, text delimiters, or Word styles. Let s import the existing Vision Word document into the project. You want RequisitePro to create requirements from the document text while importing the document. Instruct RequisitePro to create a Feature requirement from every sentence that contains the keyword must. Copyright IBM Corp. 1998,

90 Essentials of IBM Rational RequisitePro Workbook Import a Word Document and Create Requirements Using Keywords (Import Wizard) Select the Features and Vision package in the RequisitePro Explorer. Use the Import Wizard to import the Vision document located in the Additional Files folder on the Exercise CD. (Click File > Import.) o Click Requirements and document. o Import the document into the Features and Vision package. o Each requirement has the keyword must in it and can be an entire paragraph of text. o Accept all the requirements that were identified. After the import, review the Vision document and note the requirements in it. View the Features and Vision package. Save and close the document. Minimize Word. Need more guidance? See page 4-9, steps Copyright IBM Corp. 1998, 2006

91 RequisitePro Documents Unguided Lab 4.4 Import a RequisitePro Document with Requirements Objectives Import a requirements document with requirements in bookmarks. Save a requirements document as a Word document. Scenario Import a RequisitePro document already containing requirements from a different project into your project. Import a RequisitePro Document and Requirements Use the Import Wizard to import the RequisitePro document Supplemental_Specification.SUP located in the Additional Files folder on the Exercise CD. o o o Import only the document. Do not delete the bookmarks. (They delimit the requirements.) Commit. Review the Supplementary Specification. One requirement was a mistake. Remove the requirement from Section 10 using delete (unmark). The text is important, but it shouldn t be a requirement. Save the document. Confirm the requirement deletion. Need more guidance? See page 4-13, steps 1-7. Copyright IBM Corp. 1998,

92 Essentials of IBM Rational RequisitePro Workbook Export a document to Word Export the Supplemental Spec to Word using RequisitePro >Document > Save As. Save and close the document. Minimize Word. Need more guidance? See page 4-16, steps Copyright IBM Corp. 1998, 2006

93 RequisitePro Documents Unguided Lab 4.5 Create Hierarchical Requirements in a Document Objectives Create hierarchical requirements in a document. Manipulate hierarchical relationships among requirements. Delete a hierarchical requirement. Scenario As you investigate some of the high-level requirements in your vision, you will create more refined requirements. These need to be expressed in the Vision document. Specifically, you will create requirements in the Vision document and then define some hierarchical relationships for feature requirements (FEAT) in the Vision document. Copyright IBM Corp. 1998,

94 Essentials of IBM Rational RequisitePro Workbook Create Hierarchical Requirements and Remove Requirements in a Document Find FEAT1 in the Vision document (try finding it in the database, then double-click). Select some text under FEAT1 and create a requirement. o o Make the new requirement a child requirement of FEAT1. Click RequisitePro >Document > Save. Change the parent to FEAT2 and make it High Priority. o Click RequisitePro > Document > Save. Try to delete (unmark) a parent requirement. Cancel after viewing RequisitePro s behavior with regard to children, without deleting the requirement. View the Revision and History for a hierarchical requirement. Save and close the document. Minimize Word. Need more guidance? See page 4-18, steps Copyright IBM Corp. 1998, 2006

95 RequisitePro Documents Unguided Lab Offline Authoring Objectives Take a RequisitePro document offline. Specify a location and reason for taking the document offline. Identify the read-only copy of the document in RequisitePro. Scenario Offline authoring allows a RequisitePro document to be taken out of a project and worked on in Word outside of the RequisitePro software, leaving a read-only copy behind for other project members to view. When taken offline, the documents are embedded with macros that allow the user to create and delete (unmark) requirements from the Word document. Textual changes can also be made in the offline document. When the document is brought back online (into the associated RequisitePro project), the database is updated to reflect the changes made to the document. Project documents can be sent to customers for editing and approval. Their changes can be easily merged into the project. Offline authoring can be a good solution for development teams that work in a dispersed environment. By taking the document offline, you can detail specifications and create requirements outside of RequisitePro. Copyright IBM Corp. 1998,

96 Essentials of IBM Rational RequisitePro Workbook Take a Document Offline Use the Tools menu to take the Execute Trade Use Case offline. o o You are doing this to add an alternate flow. Save the offline document on your desktop. View the offline information for the document. Notice the document icon in the RequisitePro browser changed. Try to open it in RequisitePro. What happens? o Do not bring it back online. Close the project and close RequisitePro. Need more guidance? See page 4-24, steps Copyright IBM Corp. 1998, 2006

97 RequisitePro Documents Unguided Lab 4.7 Edit an Offline Document Objectives Create requirements in an offline document. Delete (unmark) requirements in an offline document. Edit the text of an offline document. Scenario Now the document is offline and ready for you to update. Let s open it and enter the new information (add an alternative flow). First, make sure the macros are set properly for Word. Word 2000 defaults to the highest level for macro security. This setting prevents the enabling of RequisitePro offline authoring macros. Check your security settings before editing the document. Edit an Offline Document Using Word Use MS Word to edit the offline Execute Trade document. o MS Word security must be set to Medium or Low. Click Tools > Macros > Security. Add an alternate flow to Section 2.2: New exciting flow. Make the new flow a requirement. Highlight random text to simulate creating two more requirements. Delete (unmark) one of the other requirements. Save and close the document. Need more guidance? See page 4-26, steps 1-6. Copyright IBM Corp. 1998,

98 Essentials of IBM Rational RequisitePro Workbook Bring the Document Back Online Open the RU e-st project. Bring the document back online. o o Click Tools > Offline Documents. Remove the copy from the desktop. Look in the RequisitePro browser and see the new requirements. Need more guidance? See page 4-28, steps Copyright IBM Corp. 1998, 2006

99 Traceability and Queries Lab 5.1 Set Traceability Relationships NOTE: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page Otherwise, continue reading. Objective Set traceability links between requirements in your project. Scenario Traceability is defined by Rational RequisitePro as a relationship between two requirements that implies the source, derivation, or dependencies between the requirements using the trace to or trace from features shown as arrows in a view. A Traceability view is queried by Requirement Type. For example, a Traceability view can be used to display requirements that are not linked to any other requirement or display only requirements whose links are suspect (due to a change in the requirement or attribute value). The importance of traceability to develop quality software is discussed in Managing Software Requirements, A Unified Approach by Dean Leffingwell and Don Widrig. Open a new view and create a few relationships between requirements. The traceability structure is defined in the RM Plan. It is important to decide on the traceability flow and be consistent with it. The traced relationships either flow from the bottom of the requirements relationship structure to the top (detailed requirements "trace to" top-level requirements) or vice versa. Estimated Time 45 minutes Copyright IBM Corp. 1998,

100 Essentials of IBM Rational RequisitePro Workbook Set Traceability Links Between Two Requirement Types 1. Right-click the Use Cases package, and then click New > View. The View Properties dialog box appears. Use the example below to complete the View Properties dialog box. Click OK. The new view is created under the Use Cases package and the new matrix appears. 2. Right-click in an empty cell, and then click Trace To. You have set a traceability relationship between a UC requirement and a FEAT requirement. In effect, you are saying that a selected UC requirement links to (trace-to) a FEAT requirement. 5-2 Copyright IBM Corp. 1998, 2006

101 Traceability and Queries 3. Repeat the above step until eight more requirements have established Trace to traceability links. Note: This is for training purposes. In your environment, you ll be familiar with the requirements you are tracing. Tip: A left-click in a traced cell displays both the UC and FEAT entries in the bottom panels of the window. You should have something that appears similar to the example below. Save and close the view. Copyright IBM Corp. 1998,

102 Essentials of IBM Rational RequisitePro Workbook 4. Using the techniques you learned, create a new private Traceability Matrix in the Supplementary Requirements package. The view details are: 5-4 Copyright IBM Corp. 1998, 2006

103 Traceability and Queries 5. Create six Trace To traceability links. You have established traceability links between Supplementary Requirements and Feature requirements. (Again, this is for training purposes. In your environment, you know what relationships are necessary.) You should have something that appears similar to the example below. Save and close the view. Continue to the next guided lab. Copyright IBM Corp. 1998,

104 Essentials of IBM Rational RequisitePro Workbook Lab 5.2 Explore Suspect Links Objectives Explore the Suspect Traceability features offered by Rational RequisitePro. Clear suspect links manually. Scenario Rational RequisitePro offers a unique management capability to detect changes made to the project, called suspect linking. When data is changed in a linked requirement, the link becomes suspect and is displayed in the Traceability views. Changes are easy to track and resolutions are determined quickly. Rational RequisitePro tracks any change between the requirements you marked. Suspect links are automatically set when a related requirement is modified, but you can manually set a suspect link as well. Edit a few requirements and see what happens. Set Traceability Links to Manage Change in Your Project 1. Open the Use Cases Traced to Features view in the Use Cases package. The view is displayed, showing the traceability you set up in the previous exercise. 2. Double-click a traced FEAT requirement (not the cell in the matrix) in your UC-FEAT Traceability Matrix view. This step opens the requirement in the Vision.VIS document. Note: You may also right-click a requirement and select Go To. 5-6 Copyright IBM Corp. 1998, 2006

105 Traceability and Queries 3. Change the requirement in the Vision document. (For this step, add meaningless text or delete parts of the requirement). The following is an example of adding some text to FEAT3. Click RequisitePro > Document > Save in the Word menu. A Change description dialog box appears for each requirement that has been modified. Type: Added Text in the description field. Click OK. Close the Vision document. 4. Return to the Use Cases Traced to Features view. The trace relationship for the edited requirement is now suspect (red diagonal lines appear in the traced requirement cell). 5. Select the suspect link (a traced cell with a red diagonal line). Click Traceability > Clear Suspect. This action should be performed only after each of the suspect requirements has been reviewed and resolved. (You can also rightclick in the suspect link to clear suspect link.) Note: Each suspect link must be individually reviewed and cleared. Save and close the view. Copyright IBM Corp. 1998,

106 Essentials of IBM Rational RequisitePro Workbook 6. Using the techniques you learned, create a new private Traceability Matrix inside the Features and Vision package. Use the example below to complete the View Properties dialog box. Set two Trace To links. You should have something that appears similar to the example below. Save and close the view. Continue to the next guided lab. 5-8 Copyright IBM Corp. 1998, 2006

107 Traceability and Queries Lab 5.3 Manipulating Traceability Links Objectives Set multiple traceability links in one step. Clear suspect traceability links. Manually mark traceability links. Scenario Now manually set multiple suspect links that need to be reviewed. Once reviewed, the requirement should be cleared. Create some suspect links and clear them for practice. Manually mark a relationship as suspect. Set Multiple Traceability Links Between Requirements 1. Open the Supplementary Requirements Traced to Features view in the Supplementary Requirements package. The view is displayed showing the Traceability you set up earlier. 2. Select eight empty cells by holding the mouse button and dragging over eight cells or by holding down the CTRL or SHIFT key and clicking over eight cells. Tip: The CTRL key allows you to select multiple individual cells, while the SHIFT key selects all contiguous cells. Experiment with both keys. 3. With the eight cells selected, right-click. Click Trace To. Observe that you have set multiple traceability relationships in a single action between the SUPL requirements and FEAT requirements. Additionally, this method can be used to manually mark suspect traceability relationships and clear suspect relationships. Copyright IBM Corp. 1998,

108 Essentials of IBM Rational RequisitePro Workbook 4. Select four traced cells using the CTRL key. 5. Right-click, and then click Mark Suspect. The traced cells are now marked suspect. 6. Again using the CTRL key OR Shift key, click three suspect links. Right-click and select Clear Suspect. The suspect relationships have been cleared and traceability once again reflects the correct relationship. 7. Save and close the view. Continue to the next guided lab Copyright IBM Corp. 1998, 2006

109 Traceability and Queries Lab 5.4 Experiment with Traceability Views Objective Use the Filter and Sort options in various Traceability views. Scenario Traceability views provide important management data because you can track and manage changing requirements in the project. Specific requirement types and attributes can be sorted and filtered for better management. Create queries by filtering some requirement attributes. Copyright IBM Corp. 1998,

110 Essentials of IBM Rational RequisitePro Workbook Use Queries to View Traceability Links 1. Create a new Traceability Matrix in the Use Cases package. Use the example below to complete the View Properties dialog box. Click OK Copyright IBM Corp. 1998, 2006

111 Traceability and Queries 2. Click the Query row requirements button. Verify that the UC: Use Case Requirement Type is selected. Select Attribute value Traced-to. Click OK. The Traced-to attribute is maintained automatically by the Rational RequisitePro system on the basis of the links you established earlier. Copyright IBM Corp. 1998,

112 Essentials of IBM Rational RequisitePro Workbook 3. Click FEAT Requirement Type in the Query Requirements dialog box. Tip: If all requirement types are already selected, it is quicker to select the None button and then make a selection. Click Not Traced. Select the Direct links only box. (This option lets you query on links that go through other requirements.) Click OK in the Query Requirements dialog box Copyright IBM Corp. 1998, 2006

113 Traceability and Queries 4. Select the Retain Hierarchical Display box. (This shows if a parent traces to a Feature, but the children do not.) Click OK in the Query Row Requirements dialog box. Examine the resulting display. The RM Plan states that all use case requirements must trace to feature requirements. With this query, you have isolated only those requirements that do not show a traceability relationship between the two Requirement Types. This presents an easy method of ensuring your traceability links are complete. Any missing traceability links can easily be set in this queried view. Missing traceability is a good indication of scope creep. 5. Save and close the view. Copyright IBM Corp. 1998,

114 Essentials of IBM Rational RequisitePro Workbook 6. Examine some other ways of viewing the traceability information. Create a Traceability Tree View (Traced into) view in the Features and Vision package. Use the example below to complete the View Properties dialog box. Click OK Copyright IBM Corp. 1998, 2006

115 Traceability and Queries 7. Click View > Expand All. Observe the change in the level of detail shown. This view shows traceability of the entire project into the root requirements (FEAT). Note: If the Explorer has the focus then Expand All expands the hierarchy in the Explorer tree. Save and close the view. Copyright IBM Corp. 1998,

116 Essentials of IBM Rational RequisitePro Workbook 8. Create a Traceability Tree View (Traced out of) view in the Supplementary Requirements package. Follow the example below. Click OK. 9. Click View > Expand All. Observe the change in the level of detail shown. This view shows traceability of the entire project (up) from the supplementary specs requirements. 10. Save and close the view Copyright IBM Corp. 1998, 2006

117 Traceability and Queries Lab 5.5 Requirements Management Queries Objectives Explore the query options available for data management. Remove queries that have been applied to a view. Scenario You ve created many views for analyzing requirement information. Now, use these views to perform routine requirements management tasks. These tasks benefit the development activity in areas such as: Managing scope. Improved planning and decision-making. Ensuring that product goals are met. Eliminating feature creep. Improving team communication. Copyright IBM Corp. 1998,

118 Essentials of IBM Rational RequisitePro Workbook Perform Requirements Management Queries 1. Open the All Use Case Requirements view in the Use Cases package. 2. Experiment with the Funnel buttons in the Views toolbar. Click the Displayed attributes button. The Displayed Attributes dialog box appears. The side-to-side Funnel allows you to select and arrange columns of attribute information when using an attribute matrix. 3. Click None. Select the Priority, Status, Difficulty, and Stability attributes. Click OK. With this example, your view has changed to display only the four attributes identified. You can arrange and select as many or as few attributes as necessary. 4. Query the values of the attribute. Click Query row requirements. Select the Priority attribute, and then click OK. This action displays the Query Requirements dialog box. Here you indicate the attribute(s) to be selected and sorted in the view Copyright IBM Corp. 1998, 2006

119 Traceability and Queries 5. Click All to display all attribute values. Click the Descending in Sort Order section. Click OK, and then click OK again. Observe that the UC row entries are now arranged in Priority order. The definition of descending (or ascending ) is solely determined by the order of appearance of the values defined for the attribute. The Priority column header has changed to indicate that your filtering and sorting has been applied. You should have something that appears similar to the example below. 6. Click the Displayed attributes funnel. Select All, and then click OK. Copyright IBM Corp. 1998,

120 Essentials of IBM Rational RequisitePro Workbook 7. Remove the filter and the sort of the values. Click Query row requirements. Click Remove, and then click OK. These actions remove the queries and return the view to the initial state. You could also create a new view to start your next actions. 8. Query only requirements with the Status attribute value Approved. View the query. Note: Multiple queries can be added as shown in the next step. 9. Add a query for requirements with the Priority attribute value High Copyright IBM Corp. 1998, 2006

121 Traceability and Queries 10. Display all UC requirement attributes. Query the Status attribute with values displayed in a descending order. Click Displayed attributes on the menu. Select the Status attribute in the Display order window. Click Move Up, so that Status is the first attribute to display in the Attribute Matrix. Click OK. Another way to create a query follows: Right-click Priority attribute column. Click Query on Attribute. Click All to display all Priority attributes. Click Descending, and then click OK. Click Displayed attributes. Move the Priority attribute to the top of the attribute list. Click OK. Priority is now the first attribute to appear in the view. You should have something that appears similar to the example below. Save and close the view Continue to next guided lab. Copyright IBM Corp. 1998,

122 Essentials of IBM Rational RequisitePro Workbook Lab 5.6 Change Management Query Objectives Isolate only the requirements that have changed using a query. Query your project database to determine status information. Scenario Use queries to manage your views of the suspect traceability links, as well as query information to determine project status. For project status, create a view with FEAT requirements that have a traceability relationship (through the UC) to a SUPL where the Status is Approved Copyright IBM Corp. 1998, 2006

123 Traceability and Queries Extract feature Requirements with Suspect Links 1. Create a new Traceability Matrix in the Use Cases package. Use the example below to complete the View Properties dialog box. Click OK. Manually set two suspect links. 2. Click the Query row requirements button. Click the attribute value Traced-to, and then click OK. The Traced-to attribute is maintained automatically by the RequisitePro system on the basis of the links you established earlier. Copyright IBM Corp. 1998,

124 Essentials of IBM Rational RequisitePro Workbook 3. Use the following example to complete the Query Requirements dialog box. You have isolated only the suspect links between these two requirement types. This presents an identifiable method of managing change to your project. This display can be printed and distributed to team members for further investigation and resolution. Click OK. Click OK in the Query Row Requirements dialog box. Save and close the view Copyright IBM Corp. 1998, 2006

125 Traceability and Queries Extract Information about Overall Project Status 4. Create a Traceability Tree (Traced into) view in the Use Cases package. Use the example below to complete the View Properties dialog box. Click OK. 5. Click the Query row requirements button. Requirement Type: STRQ: Stakeholder Requests Requirement Type. Select the Traced-from attribute. Click OK. The Query Requirements dialog box opens. Copyright IBM Corp. 1998,

126 Essentials of IBM Rational RequisitePro Workbook 6. Select the Use Case Requirement Type. Clear the Direct links only check box. Click OK, and then click OK again. You have asked the database to show you all stakeholder requests from use cases through any other requirement. In this case, it is through features. Note: When the Direct links only check box is cleared, Rational RequisitePro includes all stakeholder requests that are traced from use cases by way of another requirement. If your query result is empty then you may need to set up some additional traceability links. For example: UC9 > FEAT16 > STRQ2. Click View > Expand All. 7. Save and close the view. Continue to the next guided lab Copyright IBM Corp. 1998, 2006

127 Traceability and Queries Lab 5.7 Export Views Objectives Export various requirements management views for using other applications and reporting functions. Experiment with various utility functions to save and restore a view. Scenario A product team meeting is scheduled for this afternoon and you would like to show the project status. Export the project information for team members who do not have Rational RequisitePro. Save the query definitions so the query may be opened again without redefining the query for each meeting. Copyright IBM Corp. 1998,

128 Essentials of IBM Rational RequisitePro Workbook Extract Information and Export as a Word.doc 1. Open an Attribute matrix view. Click File > Export > Export to Word. Rational RequisitePro opens Word to create the view in document format. The document is saved to the current project directory. As in printing, the attributes and arrangement of the columns are included in the exported output. Where appropriate, Rational RequisitePro creates a header line in the exported file to identify the output fields. 2. Review the exported document (if time permits). Close the view. This completes Lab Copyright IBM Corp. 1998, 2006

129 Traceability and Queries Unguided Lab 5.1 Set Traceability Relationships NOTE: The Unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objective Set traceability links between requirements in your project. Scenario Traceability is defined by Rational RequisitePro as a relationship between two requirements that implies the source, derivation, or dependencies between the requirements using the trace to or trace from features shown as arrows in a view. Traceability views are queried by Requirement Type. For example, a Traceability View can be used to display requirements that are not linked to any other requirement or display only requirements whose links are suspect due to a change in the requirement or attribute value. The importance of traceability to developing quality software is discussed in Managing Software Requirements, A Unified Approach by Dean Leffingwell and Don Widrig. Open a new view and create a few relationships between requirements. The traceability structure is defined in the RM plan. It is important to decide on the traceability flow and be consistent with it. The traced relationships either flow from the bottom of the requirements relationship structure to the top (detailed requirements "trace to" top-level requirements) or vice versa. Estimated Time 45 minutes Copyright IBM Corp. 1998,

130 Essentials of IBM Rational RequisitePro Workbook Set Traceability Links Between Two Requirement Types Create a new Traceability Matrix View in the Use Cases package. o This view allows you to see which use cases trace to features. Create traceability links that show that the Execute Trade use case requirement traces to Features 7, 8, and 10. Add five more traceability links. Create a private Traceability Matrix from SUPL to FEAT. Set six more traceability links from SUPL requirements to the FEAT requirements they support. Need more guidance? See page 5-2, steps Copyright IBM Corp. 1998, 2006

131 Traceability and Queries Unguided Lab 5.2 Explore Suspect Links Objectives Explore the Suspect Traceability features offered by Rational RequisitePro. Clear suspect links manually. Scenario Rational RequisitePro offers a unique management capability to detect changes made to the project, called suspect links. When information is changed in a linked requirement, the link becomes suspect and is displayed in the Traceability view. Changes are easy to track and resolutions are determined quickly. Rational RequisitePro tracks any change between the requirements you marked. Suspect links are automatically set when a related requirement is modified, but you can manually set a suspect link as well. Edit a few requirements and see what happens. Copyright IBM Corp. 1998,

132 Essentials of IBM Rational RequisitePro Workbook Set Traceability Links to Manage Change in Your Project In the Use Cases to Features view, find a Feature requirement that is traced from one or more use cases. Edit the Feature requirement in the document that contains it. o o RequisitePro can find this requirement for you in the document very easily. Change the feature any way you wish, pretending the requirement changed. Click RequisitePro > Document > Save. Visit the view and notice that Rational RequisitePro has indicated a suspect link due to the changed Feature. Clear the suspect links in the Use Cases to Features view only. o This happens after the analyst has studied the impact. Close and save the view. Need more guidance? See page 5-6, steps Copyright IBM Corp. 1998, 2006

133 Traceability and Queries Unguided Lab 5.3 Manipulating Traceability Links Objectives Set multiple traceability links in one step. Clear suspect traceability links. Manually mark traceability links. Scenario Now manually set multiple suspect links that need to be reviewed. Once reviewed, the requirement should be cleared. Create some suspect links and clear them for practice. Manually mark a relationship as suspect. Set Multiple Traceability Links Between Requirements Multi-select eight links in the SUPL to FEAT View to establish some traceability. Mark four of the links suspect in the view, also using multi-select. Clear the suspect indicator on three of them using multi-select. Close the view. Need more guidance? See page 5-9, steps 1-7. Copyright IBM Corp. 1998,

134 Essentials of IBM Rational RequisitePro Workbook Unguided Lab 5.4 Experiment with Traceability Views Objective Experiment with various Traceability views using the Filter and Sort option. Scenario Traceability views provide important management data because you can track and manage changing requirements in the project. Specific requirements and attributes can be sorted and filtered for better management. Create queries by filtering some requirement attributes. Use Queries to View Traceability Links Create a view to show all use cases that do no trace to features. o o o Use the Query Row button on a standard Traceability view. If you Retain Hierarchical Display, you are able to see if a child or a parent is part of a trace (try it both ways). Examine the view. Remove the query using the same Query Row button. Need more guidance? See page 5-12, steps Copyright IBM Corp. 1998, 2006

135 Traceability and Queries Unguided Lab 5.5 Requirements Management Queries Objectives Explore the query options available for data management. Remove any queries that have been applied to a view. Scenario Perform routine requirements management tasks. These tasks benefit the development activity in such areas as: managing scope. improved planning and decision-making. ensuring the product goals are met. eliminating feature creep. improving team communication. Copyright IBM Corp. 1998,

136 Essentials of IBM Rational RequisitePro Workbook Perform Requirements Management Queries Open the All Use Case Requirements view. Experiment with the Funnel buttons. Query values of the attributes such as Priority, Status, and Difficulty. Click Query Row requirements. Select the attribute Priority. Click All to display values. Query so that the attributes are in descending order. Observe the results. Remove the queries. Try any query with requirements with the Status value: Approved. o o Add another query to the view: Priority value High. Remove the query. Create a new view to select and sort a set of FEAT entries. Need more guidance? See page 5-20, steps Copyright IBM Corp. 1998, 2006

137 Traceability and Queries Unguided Lab 5.6 Change Management Query Objectives Isolate only the requirements that have changed and need review using a RequisitePro query. Query your project database to determine status information from a view. Scenario Use the query engine to manage your views of the suspect traceability links and query information to determine project status. For project status, create a view with FEAT requirements that have a traceability relationship (through the UC) to a SUPL where the Status has been Approved. Extract Feature Requirements with Suspect Links Create a new Traceability Matrix within the Use Cases package. o o Name it: Change Management Query. Rows/Columns: UC (Row) and FEAT (Column) Requirement Type. Manually set two suspect links. Click Query Row requirements. Select the attribute value Traced-to. Find all the requirements traced to FEAT that are suspect only. Save the view. Need more guidance? See page 5-25, steps 1-7. Copyright IBM Corp. 1998,

138 Essentials of IBM Rational RequisitePro Workbook Extract Information about Overall Project Status Create a new Traceability Tree (Traced into) within the Use Cases package. o o Name it: Use Case to Stakeholder Request Query. Row Requirement Type: STRQ Requirement Type. Click Query Row requirements. For STRQ, select the attribute value Traced-from. Select UC Requirement Type and select Direct Links Only. Modify the query and clear the Direct Links only option. Click Expand All from the View menu. Need more guidance? See page 5-24, steps Copyright IBM Corp. 1998, 2006

139 Traceability and Queries Unguided Lab 5.7 Export RequisitePro Views Objectives Export various requirements management views for use by other applications and reporting functions. Experiment with various utility functions to save and restore a view. Scenario Now that you have created many views, export the information for others not using Rational RequisitePro. A product team meeting is scheduled for this afternoon and you would like to show the group the project status. Export the project information. Save the query definitions so you can run the query again without redefining the query for each meeting. Extract Information and Export as a Word.doc Prepare a FEAT Attribute Matrix view. Export it to Word. Need more guidance? See page 5-30, steps 1-2. This completes Lab 5 Unguided version. Copyright IBM Corp. 1998,

140 Essentials of IBM Rational RequisitePro Workbook 5-42 Copyright IBM Corp. 1998, 2006

141 Metrics Lab 6.1 Creating a Metrics Report NOTE: Each lab has an unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page 6-9. Otherwise, continue reading. Objectives Create a basic metric report. Insert data labels. Review the report output in Microsoft Excel. Scenario Rational RequisitePro Metrics let project managers and product analysts report statistics on RequisitePro requirements text, attributes, relationships, and revisions. These report results are displayed in Microsoft Excel and can be manipulated using Excel s charting capabilities. Charts and reporting statistics can be saved and re-run throughout the life cycle of the project. Begin by creating a basic report that shows the number of requirements per requirement type in the project. Estimated Time 15 minutes Copyright IBM Corp. 1998,

142 Essentials of IBM Rational RequisitePro Workbook Create a Metric Report 1. Click Tools > Metrics. The Requirement Metrics dialog box opens. This dialog box is the primary user interface for the application. 2. In the Query section, select the <all FEAT> value from the drop-down menu. 3. Click the Add to Report button. Your Requirement Type is added to the Report section of the dialog box. All data included for the report is displayed. 4. In the Report section, click Label. Notice that the cursor changes into edit mode over the label. 5. Type: FEAT as the new label. This label is used to identify Feature requirements in your Excel chart. 6. Repeat steps 3 5 to add additional base filters for: <all UC> <all STRQ> <all SUPL> Update the label of each query to reflect the Requirement Type name. 7. Click Create. An Excel spreadsheet opens a chart of your queries. 6-2 Copyright IBM Corp. 1998, 2006

143 Metrics Review your output. RequisitePro calculates each query criterion, connects to Excel, and populates data with the result of the query. Microsoft Excel opens on your desktop and displays the query output in a default chart format. Notice the location of the label fields that were entered in RequisitePro. Define the Excel Chart 8. Right-click anywhere in the chart. Click Chart Options. 9. Name the new report All Requirements by Type. Click Legend tab. Select the Show legend box. This option creates an associated legend for your chart. 10. Click the Data Labels tab. Select Value. A numerical value for each query is displayed in the chart. Copyright IBM Corp. 1998,

144 Essentials of IBM Rational RequisitePro Workbook 11. Click OK. Your report, complete with label values, legend, and title, is displayed. Click the Summary Sheet tab in the lower-left corner of the Excel chart. (If you don t see the worksheet tabs, maximize the Excel view.) This page is included with each report and lists summary details of each query contained in the report. Compare your results to the chart below. 12. Save and close the Excel report. Click File > Save. Name the report Click File > Exit. Continue to the next lab. 6-4 Copyright IBM Corp. 1998, 2006

145 Metrics Lab 6.2 Creating a Report Using Attribute Value Filters Objectives Scenario Create a report showing all requirement types that have had a specified attribute value change. Continue experimenting with general manipulation of Excel chart formats. A static report retrieves project information that provides a snapshot view of a project. It is useful in determining the current status of the project. For your static report, query the project to determine the number of Use Case Requirements and the status of each value of the Status attribute. For example, How many UC requirements are Approved, Proposed, Validated, and so on? Copyright IBM Corp. 1998,

146 Essentials of IBM Rational RequisitePro Workbook Create a Report Using Filters 1. The Requirement Metrics Dialog box should still be open. 2. In the Choose a Requirement View list, click all UC. The Use Case Requirement Type is the base filter. 3. Click Add Filter, and then click Attribute Value. Click OK. Notice the different types of filters available for use. Choose the Status from the Select an Attribute list. Choose no entry and then click OK. 4. Click Add to Report. Enter a label: No entry. Use the same steps you learned in the previous exercise to complete this task. 6-6 Copyright IBM Corp. 1998, 2006

147 Metrics 5. Enter filters for the four Status attribute values. (Repeat steps 3 and 4.) Proposed. Approved. Incorporated. Validated. Remember to update your labels to reflect the query content for use in your chart. Compare your results to the example below. Click Create after adding your queries. 6. Name your report, show the legend, and show the data values using the skills previously learned. Hint: Right-click in the Excel chart, and then click Chart Options. 7. Review your output. You have bars on your chart, each representing the selected value of the attribute Status for use case requirements. 8. In Excel, select File > Close. (Do not save report.) You are returned to the Requirement Metrics window with your previous queries still listed. 9. Select the base query All UC. Click Add to Report. Label the query All UC. Notice that the UC query was added to the bottom of your list of queries. Copyright IBM Corp. 1998,

148 Essentials of IBM Rational RequisitePro Workbook 10. Select the All UC query. Click Move Up until the query is the first query in the list. Click Create. You can reorder any of your query items using the Move Up and Move Down buttons. 11. Format your report as you wish. You added a new query to the report that can serve as a baseline for comparison. 12. Right-click in the chart, and then click Source Data. 13. Click Columns and then click OK. Review your results. This action changes the chart to reflect a different color for each query result and updates the legend to reflect the correlation between the query color and the query label. 14. Close the report without saving. You are returned to the Requirement Metrics dialog box. 15. Select a query in the Report section. Click Delete Query. Continue until all queries are removed. Close the Requirement Metrics dialog box. It is not necessary to save information. This completes Lab Copyright IBM Corp. 1998, 2006

149 Metrics Unguided Lab 6.1 Creating a Metrics Report NOTE: The Unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objectives Create a basic metric report. Insert data labels. Review the report output in Microsoft Excel. Scenario RequisitePro Metrics let project managers and product analysts report statistics on RequisitePro requirements text, attributes, relationships, and revisions. These report results are displayed in Microsoft Excel and can be manipulated using Excel s charting capabilities. Charts and reporting statistics can be saved and re-run throughout the life cycle of the project. Begin by creating a basic report that shows the number of requirements per Requirement Type in the project. Estimated Time 10 minutes Copyright IBM Corp. 1998,

150 Essentials of IBM Rational RequisitePro Workbook Create a Metric Report Use Tools > Metrics to open the Requirement Metrics dialog box. Create a query for <all FEAT>. o Add <all FEAT> to the report. Create a label FEAT in the report section. Add three additional base filters for: o <all UC> o <all STRQ> o <all SUPL> Generate the report. Review the Excel spreadsheet. Need more guidance? See page 6-2, steps 1-7. Define the Excel Chart Right-click in the chart. Name the new report: All Requirements by Type. Show the Legend. Click the Data Labels tab in the Chart Options dialog box and show the values. Close the report. Remove all queries. Need more guidance? See page 6-2, steps Copyright IBM Corp. 1998, 2006

151 Metrics Unguided Lab 6.2 Creating a Report Using Attribute Value Filters Objectives Create a static report showing all requirement types that have had a specified attribute value change. Continue experimenting with general manipulation of Excel chart formats. Scenario A static report retrieves project information that provides a snapshot view of a project. It is useful in determining the current status of the project. For our static report you will query the project to determine the number of use case requirements and the status of each value of the Status attribute. For example, How many UC requirements are Approved, Proposed, Validated, and so on? Copyright IBM Corp. 1998,

152 Essentials of IBM Rational RequisitePro Workbook Create a Report Using Filters The Requirement Metrics dialog box should still be open. Choose the Use Case Requirement Type as the base. Add an Attribute Value to the filter. o Select the Status attribute with No Entry. Enter a label: No entry. Add four more attribute values to the Status attribute: o Proposed. o Approved. o Incorporated. o Validated. Create labels for each to reflect the query content in the report. Create the report. Name the report, show the legend, show the data values. Close the Excel report. (You do not have to save it.) From the Requirement Metrics dialog box, select the base query all UC. Move the all UC query to the top of the report. Create the report. From the Chart options, click Source Data. Click Columns on the Data Range tab. Close the Excel report and delete the query. Need more guidance? See page 6-6, steps This completes Lab 6 Unguided version Copyright IBM Corp. 1998, 2006

153 RequisitePro Baseline Manager Lab 7.1 Make Baselines Note: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page Otherwise, continue reading. Objectives Launch the IBM Rational RequisitePro Baseline Manager. Browse the RequisitePro Baseline Manager interface and Help Create the baseline directory structure. Make an initial project baseline, package baseline, document baseline, and an Attribute Matrix view baseline. Modify RU e-st project structure and requirements. Make a second project baseline, package baseline, document baseline, and Attribute Matrix view baseline. You will compare the two baselines in Lab 7.2. Estimated Time 25 minutes Copyright IBM Corp. 1998,

154 Essentials of IBM Rational RequisitePro Workbook Create a Directory Structure 1. Open Windows Explorer. 2. Navigate to the C:\RU e-st directory. 3. Create a folder called Baselines under the C:\RU e-st directory. 4. Create the following subfolders under the Baselines folder: ProjectBaselines PackageBaselines DocumentBaselines AttributeMatrixViewBaselines 5. Close Windows Explorer. Launch the RequisitePro Baseline Manager 1. Close the RU e-st project in Rational RequisitePro. 2. In RequisitePro, click Tools > RequisitePro Baseline Manager. 3. Browse the interface. 4. Take a look at the Help where you will find information about making baselines with the RequisitePro Baseline Manager under Working with Projects, Working with Baselines. Make an Initial Project Baseline 1. In the RequisitePro Baseline Manager, click File > Make Baseline to launch the RequisitePro Make Baseline wizard. 2. Select the Project baseline type, if it is not already selected. Click Next. 3. Enter the baseline information: For the RequisitePro Project, click Browse and then navigate to C:\RU e-st. Select the RU e-st.rqs RequisitePro project. Click Open. For the Location, click Browse and then navigate to C:\RU e-st\baselines. Select the ProjectBaselines folder and then click OK. Type a baseline label of Rue-stIteration1. And then click Next. 7-2 Copyright IBM Corp. 1998, 2006

155 RequisitePro Baseline Manager 4. Select the History and Discussions baseline options. Click Next. 5. On the Final Review page, review your baseline choices. Click Next. 6. The RequisitePro Baseline Manager generates the project baseline. The Confirmation page confirms whether or not the baseline generated successfully. Click Finish. Make an Initial Package Baseline 1. Launch the RequisitePro Make Baseline Wizard. 2. Select the Package baseline type. 3. Enter the baseline information: Browse to C:\RU e-st and select the RU e-st.rqs project. Browse to C:\RU e-st Baselines and select the PackageBaselines location. Type a baseline label of UseCases_BL1. Click Next. 4. Choose all of the baseline options except Cross-Project Traceability. Click Next. 5. Choose the artifacts to include in the baseline. Expand RU e-st and then expand the Use Cases package. Select the following packages: Use Cases Execute Trade Get Quote Click Next. 6. On the Final Review page of the wizard, review your baseline choices. Click Next. 7. The RequisitePro Baseline Manager generates the package baseline and informs you of the status on the Confirmation page. Close the wizard. Make an Initial Document Baseline 1. Launch the RequisitePro Make Baseline Wizard. 2. Select the Document baseline type. Copyright IBM Corp. 1998,

156 Essentials of IBM Rational RequisitePro Workbook 3. Enter the baseline information: Browse to C:\RU e-st and select the RU e-st.rqs project. Browse to C:\RU e-st Baselines and then select the DocumentBaselines folder for the location. Type a baseline label of Execute_Trade_BL1. 4. Choose all of the baseline options except Cross-Project Traceability. Click Next. 5. Choose the artifacts to include in the baseline. Expand Documents and then select the Execute Trade artifact. Click Next. 6. On the Final Review page of the wizard, review your baseline choices. Click Next. 7. The RequisitePro Baseline Manager generates the document baseline and informs you of the status in the Confirmation page. Close the wizard. Make an Initial Attribute Matrix View Baseline 1. Launch the RequisitePro Make Baseline Wizard. 2. Select the Attribute Matrix View baseline type. 3. Enter the baseline information: Browse to C:\RU e-st and select the RU e-st.rqs project. Browse to C:\RU e-st\baselines and then select the AttributeMatrixViewBaselines folder for the location. Type a baseline label of All_Use_Cases_BL1. 4. Choose all of the baseline options except Cross-Project Traceability. Click Next. 5. Choose the artifacts to include in the baseline. Expand Views and then select All Use Cases Requirements. Click Next. 6. On the Final Review page of the wizard, review your baseline choices. Click Next. 7. The RequisitePro Baseline Manager generates the Attribute Matrix view baseline and informs you of the status in the Confirmation Page. Close the wizard. 8. Close the RequisitePro Baseline Manager. 9. Open Windows Explorer. Navigate to the C:\RU e-st\baselines directory to view the list of baseline files that you created in the subdirectories. 7-4 Copyright IBM Corp. 1998, 2006

157 RequisitePro Baseline Manager Make Modifications In this step, you make the following modifications: Modify a requirement attribute label Add a new requirement attribute Modify use case requirement attribute values Delete a use case requirement Create a new use case requirement and add trace to a feature Implementing these different types of changes will enable you to see how they will be identified when comparing baselines in Lab Open RequisitePro, if it is not already open. 2. Open the C:\RU e-st\ru e-st project. If a Project Logon dialog box appears, click the Username list, choose admin, and then click OK. 3. Click File > Properties to open the project properties for RU e-st. 4. Click the Attributes tab. 5. Choose UC: Use Case Requirement Type from the Requirement Type list. 6. In the Labels for Attributes list, choose Test. 7. Click Edit. Change the label to Tested, and then click OK. 8. Click Add. Add a new requirement attribute of Owner in the Label box. Choose Text from the Type list. Click OK. 9. Close the Project Properties dialog box. 10. Open the All Use Case Requirements Attribute Matrix view in the Use Cases package. 11. Click the Query row requirements button on the toolbar. 12. Remove all of the query criteria and then click OK. Copyright IBM Corp. 1998,

158 Essentials of IBM Rational RequisitePro Workbook 13. Modify the attribute values of the Execute Trade use case requirement. Right-click the Status cell for the Execute Trade use case requirement and then click Set Value. Change Status from Proposed to Approved and then click OK. Change Stability from Medium to High. Save the view. 14. Open the Execute Trade document in the Execute Trade package. 15. In section 2.1, delete the Newly Discovered Alternative Flow use case requirement. Click in Newly Discovered Alternative Flow. Click RequisitePro > Requirement > Delete Unmark. Click Yes. Save the document. 16. Add a new requirement in the Limit Buy Order (Non-Retirement Accounts only) section. Select the text Limit Buy Order (Non-Retirement Accounts only). Click RequisitePro > Requirement > New. Specify Limit Buy Order for the requirement name. Set the Property attribute value to Alternate Flow on the Attributes tab. In the Traceability tab, in the From section, click Add. Choose FEAT3 from the list in the Trace From Requirement(s) dialog box. Click OK twice. Save and close the Execute Trade document. 17. Close the project. Note: The project must be closed before you create a baseline for it. 7-6 Copyright IBM Corp. 1998, 2006

159 RequisitePro Baseline Manager Make a Second Set of Baselines 1. Launch the RequisitePro Baseline Manager from the RequisitePro Tools menu. 2. Launch the RequisitePro Make Baseline Wizard. 3. Make a project baseline with the following characteristics: RU e-st.rqs project A location of C:\RU e-st Baselines\ProjectBaselines A baseline label of Rue-stIteration2 Baseline options of History and Discussions 4. Make a package baseline with the following characteristics: RU e-st.rqs project A location of C:\REQ315\Baselines\PackageBaselines A baseline label of UseCases_BL2 Baseline options of Traceability, History, and Discussions Use Cases, Execute Trade and Get Quote packages chosen 5. Make a document baseline with the following characteristics: RU e-st.rqs project A location of C:\RU e-st\baselines\documentbaselines A baseline label of Execute_Trade_BL2 Baseline options of Traceability, History, and Discussions Execute Trade document 6. Make an Attribute Matrix view baseline with the following characteristics: RU e-st.rqs project A location of C:\RU e-st\baselines\attributematrixviewbaselines A baseline label of All_Use_Cases_BL2 Baseline options Traceability, History, and Discussions Select All Use Case Requirements Attribute Matrix view Copyright IBM Corp. 1998,

160 Essentials of IBM Rational RequisitePro Workbook Lab 7.2 Compare Baselines Objectives Compare project baselines and navigate the changes Optionally Compare package baselines and navigate the changes Compare document baselines and navigate the changes Compare Attribute Matrix view baselines and navigate the changes Estimated Time 25 minutes 7-8 Copyright IBM Corp. 1998, 2006

161 RequisitePro Baseline Manager Comparing Project Baselines 1. In the RequisitePro Baseline Manager, click File > Compare Baselines. 2. Click Browse for Baseline 1. Navigate to C:\RU e-st\baselines\ ProjectBaselines and select the Rue-stIteration1 folder. 3. Click Browse for Baseline 2. Navigate to C:\RU e-st\baselines\ ProjectBaselines and select the Rue-stIteration2 folder. 4. Select the Show differences only check box. 5. Click Compare. Navigate the Changes in the Project Compare Baselines 1. Maximize the RequisitePro Baseline Manager window. 2. Using the Navigation buttons, click the First Diff button to navigate to the first difference. Look for the Use Case Requirement Type attribute label that you changed from Test to Tested. 3. Using the Navigation buttons, click the Next Diff button to navigate to the next difference. Look for the new requirement attribute Owner that you added. 4. Using the Navigation buttons, navigate to the next difference. In the History folder you will see a new Revision entry. Expand the revision in the second baseline to view the change description. 5. Collapse both History and Project Structure. 6. The contents of the Project Root Package have not been compared yet. Initiate the compare for the Project Root Package: Right-click Project Root Package and then click Expand All. 7. Using the Navigation buttons, look for the changes you made: Modified attribute value for the Execute Trade use case requirements: Status changed from Proposed to Approved; Stability changed from Medium to High. Deleted Newly Discovered Alternative Flow use case requirement Added a new requirement of Limit Buy Order (Non- Retirement Accounts only) Added Traceability between Limit Buy Order (Non- Retirement Accounts only) and FEAT3 Copyright IBM Corp. 1998,

162 Essentials of IBM Rational RequisitePro Workbook Optional Section To view only changes specific to packages, documents, or Attribute Matrix views, try running the following comparisons. Compare Package Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\ PackageBaselines\UseCases_BL1 C:\RU e-st\baselines\ PackageBaselines\UseCases_BL2 Compare Document Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\documentbaselines\execute_trade_bl1 C:\RU e-st\baselines\documentbaselines\execute_trade_bl2 Compare Attribute Matrix View Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\attributematrixviewbaselines\ All_Use_Cases_BL1 C:\RU e-st\baselines\attributematrixviewbaselines\ All_Use_Cases_BL Copyright IBM Corp. 1998, 2006

163 RequisitePro Baseline Manager Unguided Lab 7.1 Make Baselines NOTE: The Unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objectives Launch the RequisitePro Baseline Manager. Browse the RequisitePro Baseline Manager interface and Help Create the baseline directory structure. Make an initial project baseline, package baseline, document baseline, and an Attribute Matrix view baseline. Modify RU e-st project structure and requirements. Make a second project baseline, package baseline, document baseline, and Attribute Matrix view baseline. You will compare the baselines in Lab 7.2. Estimated Time 25 minutes Copyright IBM Corp. 1998,

164 Essentials of IBM Rational RequisitePro Workbook Create a Directory Structure In the C:\RU e-st directory, Create a folder called Baselines. Then create the following subfolders under the Baselines folder: ProjectBaselines PackageBaselines DocumentBaselines AttributeMatrixViewBaselines Launch the RequisitePro Baseline Manager Close the RU e-st project in Rational RequisitePro. In RequisitePro, launch the RequisitePro Baseline Manager. Browse the interface. Take a look at the Help. You will find information about making baselines with the RequisitePro Baseline Manager under Working with Projects, Working with Baselines. Make an Initial Project Baseline Using the RequisitePro Make Baseline Wizard, create a Project baseline with the following the baseline information: For the RequisitePro Project, choose the RU e-st.rqs RequisitePro project in the C:\RU e-st directory. For the Location, choose C:\RU e-st\baselines\projectbaselines. Type a baseline label of Rue-stIteration1. Select the History and Discussions baseline options. Need more guidance? See page 7-2, steps Copyright IBM Corp. 1998, 2006

165 RequisitePro Baseline Manager Make an Initial Package Baseline Using the RequisitePro Make Baseline Wizard, create a Package baseline with the following the baseline information: For the RequisitePro Project, choose the RU e-st.rqs RequisitePro project in the C:\RU e-st directory. For the Location, choose C:\RU e-st\baselines\packagebaselines. Type a baseline label of UseCases_BL1. Choose all of the baseline options except Cross-Project Traceability. Choose the artifacts to include in the baseline. Expand RU e-st and then expand the Use Cases package. Select the following packages: Use Cases Execute Trade Get Quote Need more guidance? See page 7-3, steps 1-7. Make an Initial Document Baseline Using the RequisitePro Make Baseline Wizard, create a Document baseline with the following the baseline information: For the RequisitePro Project, choose the RU e-st.rqs RequisitePro project in the C:\RU e-st directory. For the Location, choose C:\RU e-st\baselines \DocumentBaselines. Type a baseline label of Execute_Trade_BL1. Choose all of the baseline options except Cross-Project Traceability. Choose the artifacts to include in the baseline.: Execute Trade. Need more guidance? See page 7-4, steps 1-7. Copyright IBM Corp. 1998,

166 Essentials of IBM Rational RequisitePro Workbook Make an Initial Attribute Matrix View Baseline Using the RequisitePro Make Baseline Wizard, create a Attribute Matrix View baseline with the following the baseline information: For the RequisitePro Project, choose the RU e-st.rqs RequisitePro project in the C:\RU e-st directory. For the Location, choose C:\RU e-st\baselines \AttributeMatrixViewBaselines. Type a baseline label of All_Use_Cases_BL1. Choose all of the baseline options except Cross-Project Traceability. Choose the artifacts to include in the baseline.: All Use Cases Requirements. Open Windows Explorer. Navigate to the C:\RU e-st\baselines directory and view the list of baseline files created in the sub-directories. Need more guidance? See page 7-4, steps 1-9. Make Modifications In this step, you make the following modifications: Modify a requirement attribute label Add a new requirement attribute Modify use case requirement attribute values Delete a use case requirement Create a new use case requirement and add trace to a feature Implementing these different types of changes will allow you to see how they will be identified when comparing baselines in Lab Open RequisitePro, if it is not already open. 2. In RequisitePro, open the C:\RU e-st\ru e-st project. If you are prompted by a Project Logon dialog box, click the Username list, choose admin, and then click OK. 3. Open the project properties for RU e-st. 4. Click the Attributes tab choose UC: Use Case Requirement Type. 5. Open the All Use Case Requirements Attribute Matrix view in the Use Cases package Copyright IBM Corp. 1998, 2006

167 RequisitePro Baseline Manager 6. Click the Query row requirements button and remove all the query criteria. 7. Modify the attribute values of the Execute Trade use case requirement. Change Status from Proposed to Approved. Change Stability from Medium to High. Save the view. 8. Open the Execute Trade document in the Execute Trade package. 9. In section 2.1, delete the Newly Discovered Alternative Flow use case requirement. Save the document. 10. Add a new requirement in the Limit Buy Order (Non-Retirement Accounts only) section. Select the text Limit Buy Order (Non-Retirement Accounts only) and make it the new requirement. Specify Limit Buy Order for the requirement name. Set the Property attribute value to Alternate Flow on the Attributes tab. On a Traceability tab, in the From section, add FEAT3. Save and close the Execute Trade document. 11. Close the project. The project must be closed before you create a baseline for it. Need more guidance? See page 7-5, steps Make a Second Set of Baselines 1. Launch the RequisitePro Make Baseline Wizard. 2. Make a project baseline with the following characteristics: RU e-st.rqs project A location of C:\RU e-st \Baselines\ProjectBaselines A baseline label of Rue-stIteration2 Baseline options of History and Discussions Copyright IBM Corp. 1998,

168 Essentials of IBM Rational RequisitePro Workbook 3. Make a package baseline with the following characteristics: RU e-st.rqs project A location of C:\REQ315\Baselines\PackageBaselines A baseline label of UseCases_BL2 Baseline options of Traceability, History, and Discussions Use Cases, Execute Trade and Get Quote packages chosen 4. Make a document baseline with the following characteristics: RU e-st.rqs project A location of C:\RU e-st\baselines\documentbaselines A baseline label of Execute_Trade_BL2 Baseline options of Traceability, History, and Discussions Execute Trade document 5. Make an Attribute Matrix view baseline with the following characteristics: RU e-st.rqs project A location of C:\RU e-st\baselines\attributematrixviewbaselines A baseline label of All_Use_Cases_BL2 Baseline options Traceability, History, and Discussions Select All Use Case Requirements Attribute Matrix view 7-16 Copyright IBM Corp. 1998, 2006

169 RequisitePro Baseline Manager Unguided Lab 7.2 Compare Baselines Objectives Compare project baselines and navigate the changes Optionally Compare package baselines and navigate the changes Compare document baselines and navigate the changes Compare Attribute Matrix view baselines and navigate the changes Estimated Time 25 minutes Copyright IBM Corp. 1998,

170 Essentials of IBM Rational RequisitePro Workbook Comparing Project Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\ ProjectBaselines\Rue-stIteration1 C:\RU e-st\baselines\ ProjectBaselines\Rue-stIteration2 Navigate the Changes in the Project Compare Baselines 1. Maximize the RequisitePro Baseline Manager window. 2. Using the Navigation buttons, navigate to the first difference. Look for the Use Case Requirement Type attribute label that you changed from Test to Tested. 3. Using the Navigation buttons, navigate to the next difference. Look for the new requirement attribute Owner that you added. 4. Using the Navigation buttons, navigate to the next difference. In the History folder you will see a new Revision entry. Expand the revision in the second baseline to view the change description. 5. Collapse both History and Project Structure. 6. The contents of the Project Root Package have not been compared yet. Initiate the compare for the Project Root Package by expanding all. 7. Using the Navigation buttons, look for the changes you made: Modified attribute value for the Execute Trade use case requirements: Status changed from Proposed to Approved; Stability changed from Medium to High. Deleted Newly Discovered Alternative Flow use case requirement Added a new requirement of Limit Buy Order (Non- Retirement Accounts only) Added Traceability between Limit Buy Order (Non- Retirement Accounts only) and FEAT Copyright IBM Corp. 1998, 2006

171 RequisitePro Baseline Manager Optional Section To view only changes specific to packages, documents, or Attribute Matrix views, try running the following comparisons. Compare Package Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\ PackageBaselines\UseCases_BL1 C:\RU e-st\baselines\ PackageBaselines\UseCases_BL2 Compare Document Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\documentbaselines\execute_trade_bl1 C:\RU e-st\baselines\documentbaselines\execute_trade_bl2 Compare Attribute Matrix View Baselines 1. Run Compare Baselines. Compare the differences only for the following two baselines: C:\RU e-st\baselines\attributematrixviewbaselines\ All_Use_Cases_BL1 C:\RU e-st\baselines\attributematrixviewbaselines\ All_Use_Cases_BL2 Copyright IBM Corp. 1998,

172 Essentials of IBM Rational RequisitePro Workbook 7-20 Copyright IBM Corp. 1998, 2006

173 Group Discussions Lab 8.1 Create Group Discussion Entries NOTE: Each lab has an Unguided version for students who prefer fewer steps and less guidance for each task. To begin the Unguided lab, go directly to page 8 7. Otherwise, continue reading. Objectives Create a group discussion and reply to a group discussion. Identify attached discussion items. Scenario During the development cycle, issues, comments, and questions arise regarding specific requirements or the project as a whole. Group discussions provide a communication vehicle for team members to record those discussion threads and display the discussions on a requirement or project basis. Any team member with access to the project can view and create group discussions, as well as reply to any discussion. Discussions may also contain attributes such as Priority and Status that are modifiable. Attributes are filtered to display discussions that are high priority or those with open status. Additional filters are performed to display discussions based on subject text, requirements, or participants. Many filters are created to help you manage the project. Discussion groups capture the thread of thought that leads to decisions. Team members participate in discussions, which simplifies gathering information and optimizes the input process. Estimated Time 10 minutes Copyright IBM Corp. 1998,

174 Essentials of IBM Rational RequisitePro Workbook Create a Group Discussion 1. Open the RU e-st project. 2. Click Tools > Discussions. The Discussions dialog box appears. Click Create. TIP: When you open a project that contains new unread discussions, the Show all Discussions icon is raised with lines of text through it indicating there are new unread discussions. Click the Group Discussions icon to review all new unread discussions. 3. In the General tab, type Generate Report in the Subject box. 4. In the Text box, type: How many reports should we plan on generating in our first iteration? 5. Click the Attributes tab. Set the Priority attribute to High. The Priority attribute is the only attribute that can be modified at this point. Once the initial discussion is created, the Status attribute becomes active. 6. Click the Participants tab. You can add a User participant to the discussion. Click Add. Select a user and then click OK. In addition to individual participants, you can add groups for participant and discussion management. 7. Click the Requirements tab, and then click Add. Select a UC requirement, and then click OK. You have associated this discussion with a specific requirement. If your discussion applies to other requirements, repeat this step and add all related requirements. It is not necessary to attach a discussion to a requirement. A discussion can apply to the entire project. Click OK. Your discussion is displayed in the Discussions dialog box. The newly created discussion appears. 8. Select the new discussion. Your discussion text, the associated requirement, and all participants are displayed. 8-2 Copyright IBM Corp. 1998, 2006

175 Group Discussions 9. Click Reply. The Discussion Response dialog box is displayed. Type a response to this discussion: Which reports have been requested by the customer? Click OK. Your reply is added to the Discussions dialog box in a hierarchical display visually indicating a response to the discussion topic. 10. Create another discussion. These discussion threads are used in the next lab. Continue to the next guided lab. Copyright IBM Corp. 1998,

176 Essentials of IBM Rational RequisitePro Workbook Lab 8.2 General Manipulation of Group Discussions Objectives Limit a discussion so that only selected participants can respond to a discussion. Explore the variety of group discussion indicators. Filter a discussion display based upon a group discussion attribute value. Alter the sort order in which the discussions appear in the Discussions dialog box. Scenario Once you begin to build a series of discussions and replies, it becomes necessary to manage the discussions and their display for ease of use. Any team member with access to the project can view and create group discussions. An author can limit the participants in a discussion. Only team members who have been identified as discussion participants can respond to the discussion topic or related responses defined in the discussion. 8-4 Copyright IBM Corp. 1998, 2006

177 Group Discussions Create a Filtered Discussion 1. Open the Discussions dialog box if it is not open from the previous lab. Begin by managing those team members who can add replies to a current discussion. 2. Select one of the discussion topics displayed in the Discussions dialog box. 3. Click Properties. 4. Click the Participants tab. Check the Restrict To Participants box and then click OK. Remember that all team members can view the discussion thread, but once this option is activated, only named participants can reply to the discussion. 5. Close the Discussions dialog box. 6. Open the All Use Case Requirements attribute matrix from the Use Cases package. The Attribute Matrix is displayed on your desktop. 7. Locate a discussion in the view. The discussion indicator is found at the far right of the requirement. 8. Click the discussion indicator. The resulting action opens the Discussions dialog box and displays only the discussions and replies that are associated with this requirement. 9. Close the Discussions dialog box. 10. Experiment further by opening a Traceability Matrix and a Traceability Tree. Locate the discussion indicators and view the discussions. Discussions can be filtered to display specific criteria. Discussions are filtered on the basis of subject text, requirement, users, priority, and status. 11. Click Show all Discussions. All discussions are displayed within this project. Notice that the discussion threads can be expanded or collapsed by selecting the + or symbols. 12. Click Filter. The Discussion Filter dialog box appears, and all possible filter criteria are displayed. Copyright IBM Corp. 1998,

178 Essentials of IBM Rational RequisitePro Workbook 13. Check the Priority box. Click High, and then click OK. Review your display. The Discussions dialog box displays only discussions that have a Priority value of High. 14. Remove the filter. Click Filter. Clear the Priority box, and then click OK. 15. Discussions are sorted according to subject, author, or date. Click the Subject title bar. The display is alphabetically reversed. Click again. The original display is restored. 16. Experiment with sorting the Sent and! (Priority) fields. Close the Discussions dialog box. Remove the Project from the Project List Note: If you will be performing the optional Security lab, then skip this step. 17. Click File > Close Project. Click File > Open Project. Select RU e-st. Click Remove, and then click OK. The project is removed from the Project list. The RU e-st folder is not removed from your local drive. Close RequisitePro. Delete the RU e-st directory from the hard drive. Move the Execute Trade offline document from the desktop to the recycle bin. Remove the Exercise CD from the CD-ROM drive. This completes Lab 8. You have successfully completed the Student Workbook. 8-6 Copyright IBM Corp. 1998, 2006

179 Group Discussions Unguided Lab 8.1 Create Group Discussion Entries NOTE: The Unguided labs are for students who feel they would benefit from fewer step-by-step instructions. Objectives Scenario Create a group discussion and reply to a group discussion. Identify attached discussion items. During the development cycle, issues, comments, and questions arise regarding specific requirements or the project as a whole. Group discussions provide a communication vehicle for team members to record those discussion threads and display the discussions on a requirement or project basis. Any team member with access to the project can view and create group discussions, as well as reply to any discussion. Discussions may also contain attributes such as Priority and Status that are modified. Attributes are filtered to display discussions that are high priority or those with open status. Additional filters are performed to display discussions based on subject text, requirements, or participants. Many filters are created to help you manage the project. Discussion groups capture the thread of thought that leads to decisions. Team members participate in discussions, which simplifies gathering information and optimizes the input process. Copyright IBM Corp. 1998,

180 Essentials of IBM Rational RequisitePro Workbook Create a Group Discussion Open the Group Discussions dialog box. Click Create. Name and discussion: General Report. Type as the discussion thread: How many reports should we plan on generating in our first iteration? Set the discussion as Priority: High. Add a participant to the discussion. Associate a UC requirement to the discussion, and then click OK. Respond to the discussion (for training purposes only). Type the response: Which reports have been requested by the customer? Create another discussion. Need more guidance? See page 8-2, steps Copyright IBM Corp. 1998, 2006

181 Group Discussions Unguided Lab 8.2 General Manipulation of Group Discussions Objectives Limit a discussion so that only indicated participants can respond to a discussion topic. Explore the variety of group discussion indicators. Filter a discussion display based upon a group discussion attribute value. Alter the sort order in which the discussions appear in the Discussions dialog box. Scenario Once you begin to build a series of discussions and replies, it becomes necessary to manage the discussions and their display for ease of use. Any team member with access to the project can view and create group discussions. An author can limit the participant in a discussion. Only team members who have been identified as discussion participants can respond to the discussion topic or related responses defined in the discussion. Copyright IBM Corp. 1998,

182 Essentials of IBM Rational RequisitePro Workbook Create a Filtered Discussion Select a discussion. Restrict to Participants so that only named participants can reply. Close the Discussion dialog box. Open the All Use Case Requirements attribute matrix in the Use Cases package. Find and open a discussion in the matrix. Experiment further by opening a Traceability matrix. Show all discussions. Filter the discussions to show only the discussions that have Priority as High. Remove the filter. Need more guidance? See page 8-5, steps Remove the Project from the Project List Close the project. Remove the project from the Project List. Close RequisitePro. (The project is removed, but the folder is not removed from the local drive.) Delete the RU e-st directory from the hard drive. Move the Execute Trade offline document from the desktop to the recycle bin. Need more guidance? See page 8-6, step 17. This completes Lab 8 Unguided version. You have successfully completed the Student Workbook Copyright IBM Corp. 1998, 2006

183 Optional Lab Optional Lab Establish Security Many companies prefer to use Rational RequisitePro in a multi-user environment and it may become necessary to establish certain types of access control on the project. This lab lets you establish a wide variety of access controls for each project known to RequisitePro. Tip: RequisitePro access controls can be initiated or altered at any point after a project is created. Most administrators find it convenient to delay initiation of security controls until the project has had a little time to define some Document Types, Requirement Types, and Requirement Attributes. After the direction of the project becomes clearer, it may then become appropriate to initiate access controls. You can set security on traceability relationships, giving you better control over who on the project can modify traceability. Permissions on traceability are set by requirement type. There are four traceability permissions: Create, Delete, Mark Suspect, and Clear Suspect. Users must have the appropriate permission on requirements on both ends of the relationship to perform the selected action. Group Permissions Default: When you add a new security group in an existing RequisitePro project, the group has all security permissions by default. You can remove permissions using the Edit Permissions buttons in the Group Permissions dialog box. There is no security on packages. Some projects may not need access controls. Estimated Time 15 minutes. Copyright IBM Corp. 1998, 2006 OL-1

184 Essentials of Rational IBM RequisitePro Student Workbook Apply RequisitePro Security Controls Objectives Define new security groups and add new users to the groups. Demonstrate the ability to set security at the project, document, and requirement levels. Create authorized users and user groups, and assign users to groups. Scenario Create authorized project users, define user groups with associated permissions, and assign users to groups. This process is required only for projects for which you want to limit user access. At any time after adding security to your project, you can add/change/remove users and groups or disable security entirely. By default, RequisitePro assigns a username as Unknown. Before enabling security, users can add their names to any project. Complete the following steps before starting the lab. OL-2 Copyright IBM Corp. 1998, 2006

185 Optional Lab Open the RU e-st Project. Click OK when asked to select a user name. Click Tools > Options. Enter your user name. Click OK. Copyright IBM Corp. 1998, 2006 OL-3

186 Essentials of Rational IBM RequisitePro Student Workbook RequisitePro needs to close the project in order to update its configuration. Close and reopen the project. The next time you open the project, RequisitePro will detect that the name is not in the project. You are given the option of adding it to the project or selecting another user name from the project. Select your user name. Click OK. Your name is added to the project. Steps Comments If necessary, open the newly created project. If it is already open, close any opened documents. 1. Click File > Project Administration > Security. The Project Security dialog box appears. OL-4 Copyright IBM Corp. 1998, 2006

187 Optional Lab Steps Comments 2. Select the Enable security for this project Notice how the Project check box. Security dialog box changes. Note there are three pre-defined access control groups. You may add to or change these groups later. 3. Click the Administrators group. Your name (as it appears in the RequisitePro Tools > Options setting) appears as the default administrator of this project. 4. Select your name in the Users of Group: Administrators list box. Click Edit by the Users of Group list box. (Be careful not to confuse this with the Edit button for the Groups window.) 5. Type the word Password as your password, and verify your password. Click OK. This allows you to set a case-sensitive password for the selected user (in this case, for yourself). Caution: Remember the password that you enter. If you forget it (and there are no other administrators), you will not be able to access your project with administrative privileges (and therefore will not be able to perform many administrative functions such as adding new users and changing permissions). Copyright IBM Corp. 1998, 2006 OL-5

188 Essentials of Rational IBM RequisitePro Student Workbook Steps Comments Tip: To minimize the chances of becoming locked out of a project due to change of administrators, forgotten passwords, and so on, Rational recommends that all projects appoint two administrators. With two administrators, the chances are high that someone will always be able to administer the project. 6. Click the Users entry in the Groups list. Click Edit below the Groups list box. Review available options. The Group Permissions dialog box lets you define the permissions for all users in that group (each user must belong to exactly one group). OL-6 Copyright IBM Corp. 1998, 2006

189 Optional Lab Administer RequisitePro Security Controls Objectives Add new users to the project. Experiment with various access permissions. Steps 1. Under Groups, click the Add button. Add a new group named Marketing. Allow Marketing full access to Vision documents (select Vision document type in the Document Types list box.) Click Edit Permissions. Comments You will see that group now has r/u/c/d permissions for documents of that type. Verify that the Create and the Delete boxes are selected. If not, select both boxes and click OK. 2. Do the same for the related Feature Requirement Type. (Select Feature Requirement Type in the Requirement Types list box.) Click Edit Permissions. Verify that the Create and the Delete boxes are checked. If not, check the boxes and click OK. You will see that group now has r/u/c/d permissions for requirements of that type. It is important to notice the distinction between setting access permissions for requirements versus documents. Copyright IBM Corp. 1998, 2006 OL-7

190 Essentials of Rational IBM RequisitePro Student Workbook Steps 3. Click OK to accept those permissions. Exit the Group Permissions dialog box. 4. Add three new users to your Marketing group. Under Users of Group: Users click the Add button. Type in a username (for example, User1) and password (for example, User1). Comments You will see your new user group in the Groups list. You may also remove permissions. Adding users to your groups is easy! 5. Add other User Groups like Marketing as you wish. After you are done adding users and groups, click OK in the Project Security dialog box. You have now enabled security. You have at least two users, yourself (as an administrator with full privileges) and one other (User1) in the Marketing group. 6. Close the project. Re-open the project. Now, you ll test the security permissions you have established. 7. When you reopen the project, you are asked for a username and password (security is enabled). Enter User1 (password = User1). Open the project properties and explore what that user is able to do within the project. OL-8 Copyright IBM Corp. 1998, 2006

191 Optional Lab Steps Comments 8. Close and re-open the project, this time logging on as yourself. Experiment further with project security as you have time. After you re done, either: a) disable project security, and close the project, re-enter, OR b) exit the project and re-enter as an administrator so that you have full permission. 9. Click File > Close Project in RequisitePro. Click File > Open Project in RequisitePro. Select RU e-st. Click Remove and then click OK. The project is removed from the Project list. The RU e-st folder is not removed from your local drive. Close RequisitePro. Delete the RU e-st directory from the hard drive. Move the Execute Trade offline document from the desktop to the recycle bin. Remove the exercise CD from the CD-ROM drive. This completes the optional lab. Copyright IBM Corp. 1998, 2006 OL-9

192 Essentials of Rational IBM RequisitePro Student Workbook OL-10 Copyright IBM Corp. 1998, 2006

193 Rational RequisitePro version 7.0 Lab Setup and Cleanup Lab Setup For the Essentials of IBM Rational RequisitePro version 7.0 course, the following software and system configuration must be installed. IBM Rational RequisitePro: IBM Rational RequisitePro version 7.0 Operating System: Microsoft (R) Windows (R) 2003 Server, Enterprise Server, Initial, SP1 Microsoft Windows 2003 Server x64 running in 32-bit mode on 64-bit processors (AMD64, EM64T) Microsoft Windows XP Professional SP1, SP2 on 32-bit processors Microsoft Windows XP Professional x64 running in 32-bit mode on 64-bit processors (AMD64, EM64T) Microsoft Windows 2000 Professional SP4 on 32-bit processors Microsoft Word: 2003 SP SP1 and SP Microsoft Excel: 2003 SP SP1 and SP SP1 and SP2 Memory: MB or greater Disk Space: 288 MB Additional Hardware Requirements: CD-ROM drive Lab Setup Extras Ensure that file name extensions are visible. In Windows 2000 or Windows XP, this is set from Windows Explorer. Click Tools > Folder Options > View. Uncheck Hide file extensions for known file types. Copyright IBM Corp. 1998, Course materials may not be reproduced in whole or in part without the prior written permission of IBM

194 If you do not do this then the lab instructions may be confusing for some students because the instructions include the file name extension. The following are not necessary to run the labs, but are listed to save time. Check the Project List for the Learning Project Use Cases. You could save the students a step in Lab 1.1 by adding the Learning Project - Use Cases to the Project List if it is not already there. (There is a step in Lab 1.1 to add the Learning Project - Use Cases to the list if it doesn t appear.) To avoid requiring the students to copy the labs onto their machines you can copy the files for them. Microsoft Word Macro for Security should be set to Medium. This is necessary for editing an offline document. (The student sets the security macros as a step in Lab 4.7.) Click Tools > Macro > Security > Medium. 2 Copyright IBM Corp. 1998, 2006

195 Lab Cleanup The students remove the project from the Project List, remove the RU e-st Project folder from the local drive, and delete the Execute Trade.UCS offline document from the desktop as the last part of Lab 8. To return the software to a clean state after Rational RequisitePro training, complete the following steps (if not completed by the student): Remove RU e-st from the Project List in RequisitePro. Delete the RU e-st folder from the local drive. Delete the Execute_Trade document from the desktop. Remove CDs from the CD-ROM drive. Copyright IBM Corp. 1998, Course materials may not be reproduced in whole or in part without the prior written permission of IBM

196 4 Copyright IBM Corp. 1998, 2006