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,