Tool Mentor: Managing Use Cases Using Rational Rose and Rational RequisitePro










var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_qS-iwAIOEdqTna4sZVFRow", "{F6A36701-8189-4691-86CB-1DE7140E9C0B}", "{F07848AD-3E5B-4061-9E6D-E02FB823763C}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_AUv4MAIMEdq-_NKqZM1EhA", "_5ZuQsAIUEdqEutyfYo0quQ", "{F6A36701-8189-4691-86CB-1DE7140E9C0B}", "{F07848AD-3E5B-4061-9E6D-E02FB823763C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_F1OgYAIbEdqEutyfYo0quQ", "{F6A36701-8189-4691-86CB-1DE7140E9C0B}", "{F07848AD-3E5B-4061-9E6D-E02FB823763C}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Tool Mentor: Managing Use Cases Using Rational Rose and Rational RequisitePro















This tool mentor describes how to manage use cases in Rational Rose® using integrated use-case attributes and documents in Rational RequisitePro®.


Tool: Rational Suite AnalystStudio






Main Description



Overview Implementers, testing professionals, and project managers manage use cases as they are developed and refined throughout the inception, elaboration, construction, and transition phases of a project. Effective use-case management requires integrated documentation to record the current status of the use case and to provide detailed descriptions of the use case. Rational's Integrated Use-Case Management allows you to manage use cases using attributes-such as Priority, Risk, Status, and Iteration-by associating use cases in Rose with RequisitePro documents, packages, and requirements. You can easily navigate from use-case models in Rose to RequisitePro use-case documents, packages, and requirements. Use-case management in RequisitePro adds depth and relational information to your Rose use cases by providing support for the following: textual definitions of use cases in a Microsoft® Word documents detailed descriptions of flows of events, special requirements, preconditions, and postconditions hierarchical (parent-child) relationships between use-case names and actions within the use-case flow of events traceability to and from other use cases and associated design features, and test plans Although many developers may prefer to initially develop use cases in Rose, most analysts prefer to begin developing use-case requirements in RequisitePro. Integrated Use-Case Management allows you to begin in either tool and then create associated use cases or use-case requirements in the other tool. Both approaches offer integrated use-case management with several easy menu selections. Tool Steps This document contains the following steps: Associate Rose and RequisitePro work products Associate a model or package with a RequisitePro project Associate use cases with RequisitePro requirements Associate use cases with RequisitePro documents Manage use-case attributes and documents Associate requirements with Rose use cases from RequisitePro 1. Associate Rose and RequisitePro Work products To benefit from Integrated Use-Case Management, you must first associate your Rose model or package with a RequisitePro project. This model or package association establishes available document types and requirements types for your use-case description and management. You can then associate use cases with existing or new RequisitePro use-case documents and requirements. This requirement association provides the specific attributes to manage the use-case development. Associate a model or package with a RequisitePro project Open the Rational Rose model. Do one of the following: To associate a model with a project, click Tools > Rational RequisitePro > Associate Model to Project. The Associate Model to Project dialog box appears. To associate a package with a project, right-click the package and click Rational RequisitePro > Associate Package to Project. The Associate Package to Project dialog box appears. At the Project File field, click the Browse button. Navigate to and select the RequisitePro project file (with an .RQS extension). Typically, this is located in a project subdirectory in the Program FilesRationalRequisiteProProjects directory. This may vary when accessing network-based projects or customized local project directories. Click Open. The full path and name of the RequisitePro.RQS file appears in the Project File field. The available document types and requirement types are listed in their respective fields. At the Default Document Type field, click the down arrow and select a document type from the list. This document type, such as "Use-Case Specification", determines the template for your Word document and a default requirement type for all requirements in that document. At the Default Requirement Type field, click the down arrow and select a requirement type from the list. This requirement type controls the choice of attributes, such as Priority, Status, and Iteration, that you will use when managing your use cases. If you are using a virtual path map for your Rose model, select a Rose Path Map. Click OK to save the association and close the dialog box. Refer to the topic Associating a model with a project in the Integrated Use-Case Management online Help. Associate use cases with RequisitePro requirements Associate a Rose use case with a RequisitePro requirement to take full advantage of use-case management using requirement attributes. Note that the requirement text, not the requirement name, may be used to create this association. Associate a use case with an existing requirement In the Rose model browser tree or use-case diagram, right-click a use case. Select Requirement Properties > Associate from the pop-up menu. The Associate a Requirement to Use Case dialog box appears. At the Requirements of type field, select a requirement type, such as UC, for managing the use-case attributes. Select a requirement from the displayed list and click OK. If the requirement has a name but no text, the Resolve Use Case Name dialog box appears, allowing you to assign the requirement text, the use-case name, or your own entry to both the requirement text and use-case name. If the existing requirement contains text, the text is updated to the name of the Rose use case. A requirement dialog box appears, with the Attributes tab displayed. Make changes to the requirement properties. Associate a use case with a new requirement In the Rose model browser tree or use-case diagram, right-click a use case. Select Requirement Properties > New from the pop-up menu. A new requirement is created in the RequisitePro project. The text of the requirement contains the name of the Rose use case. A requirement dialog box appears, with the Attributes tab displayed. Make changes to the requirement properties. Select the General tab and make changes to the requirements general properties. Make sure to select the appropriate package for the new requirement. Refer to the following topics in the Integrated Use-Case Management online Help: Associating a use case with a new requirement Associating a use case with an existing requirement Associate use cases with RequisitePro documents Associate a use case with an existing document In the Rose model browser tree or use-case diagram, right-click a use case. Select Use Case Document > Associate from the pop-up menu. The Associate Document to Use Case dialog box appears. At the Documents of type field, select a document type for the list below. Select a document from the displayed list and click OK. Associate a use case with a new document In the Rose model browser tree or use-case diagram, right-click a use case. To create a new document, select Use Case Document > New from the pop-up menu. RequisitePro opens a new document of the document type specified in the Rose model or package association with the RequisitePro project. The new document name and file name matches the name of the Rose use case. Use the RequisitePro > Document > Save command in Word to save the document. Refer to Associating a use case with an existing document in the Integrated Use-Case Management online Help. 2. Manage use-case attributes and documents Use-case attributes are managed in an associated RequisitePro requirement. By default, the Attributes tab is displayed when the Requirement dialog box is opened. You can use the General and Revision tabs to review requirement information. In addition, you can use the Traceability tab to add traceability to and from other requirements in RequisitePro. For more information on traceability, refer to the RequisitePro online Help. To set the values of the use-case attributes, do the following: Right-click on a Rose use case that is associated with a requirement or a document. Select Requirements Properties > Open from the pop-up menu. The requirement dialog box appears. On the Attributes tab, select or type a value for each attribute field. Click OK to save your settings and close the dialog box. To open the RequisitePro requirements document that is associated with a use case: In the browser tree or use-case diagram, right-click a use case that has an association with a RequisitePro document. Select Use Case Document > Open from the pop-up menu. Refer to the following topics in the Integrated Use-Case Management online Help: Assigning attribute values to a use case Opening the associated document 3. Associate requirements with Rose use cases from RequisitePro To use RequisitePro use-case requirements to create use cases in a Rose model, do one of the following: From within a RequisitePro document, place the cursor in the requirement text. Click RequisitePro> Requirement > Associate to Rose Use Case. From within a RequisitePro view or the Explorer, select the desired requirement. Click Requirement > Associate to Rose Use Case. The Rose Use-Case Association dialog box appears. Link to the Rose model If the Rose Model File field is already populated with the correct path to the model file you want to use, skip to step 3. Otherwise, type a full path and Rose model file name in the indicated field, or click Browse to find the model file. Click Apply to open the Rose model file. Use cases in the model that are not associated to a requirement or a document appear in the Select Rose Item(s) list. Proceed to associate your requirement with a new or existing use case following the appropriate procedure below. Associate a requirement with an existing use case To use an existing use case in the Rose Use-Case Association dialog box, navigate to the use case in the displayed Rose packages, and click Associate. If the requirement text and the use case name match, a message confirming the association appears. Click OK to return to the Requirement Use Case Association dialog box. The procedure is complete. If the Use-Case Name entry is different than the requirement text, the Resolve Use Case Name dialog box appears. Do one of the following: Select Requirement Text to apply the RequisitePro requirement text to the Rose use-case name. Select Use Case Name to apply the Rose use-case name to the RequisitePro requirement text. Select Other and type a new entry that will be applied to both the RequisitePro requirement text and the Rose use-case name. A message confirming the association appears. Click OK to return to the Requirement Use Case Association dialog box. The procedure is complete. Create a new use case from an existing requirement To create a new use case in the Rose Use-Case Association dialog box, select the appropriate Rose package, and click Create. The Create a New Use Case dialog box appears. The Use-Case Name box displays the selected requirement text, by default. To change the name of the new use case, type a new entry. Select a package in which the new use case will be located. If you have already selected a package in the explorer pane, that package appears as the default selection. Click OK. A message confirming the association appears. Click OK to return to the Requirement Use Case Association dialog box. The procedure is complete. Refer to the topic Creating use cases from requirements in the Integrated Use-Case Management online Help.





©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();