Purpose

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

Related Rational Unified Process Activities:

Find Actors and Use Cases

Detail a Use Case

Overview

Implementers, testing professionals, and project managers need to manage use cases as they are developed and refined throughout inception, elaboration, construction, and transition phases of the 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 in Rose using attributes, such as Priority, Risk, Status, and Iteration, by associating use cases in Rose with RequisitePro documents and requirements. You can easily navigate from use-case models in Rose to RequisitePro use-case documents and requirements. Use-case management in RequisitePro adds depth and relational information to your Rose use cases with support for:

  • textual definitions of use cases in a Microsoft Word documents;
  • detailed descriptions of flows of events, special requirements, pre-conditions and post-conditions;
  • hierarchical (parent/child) relationships between use-case names and actions within the use-case flow of events;
  • traceability to and from other use cases, associated design features, and test plans.

While many developers may prefer to initially develop use cases in Rational Rose, most analysts will prefer to first develop 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 through Rose and RequisitePro with several easy menu selections.

This document contains the following sections:

Associating Rose and RequisitePro Artifacts

Associating a model or package with a RequisitePro project

Associating a use case with a requirement

Associating a use case with a document

Managing Use-Case Attributes and Documents

Creating Rose Use Cases from RequisitePro Requirements

Associating Rose and RequisitePro Artifacts To top of page

In order 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.

Use cases can then be associated with existing or new RequisitePro use-case documents. Each use case can also be associated directly to a RequisitePro requirement. This requirement association provides the specific attributes to manage the use-case development.

Tool Steps

Associating a model or package with a RequisitePro project

To associate a Rose model with a RequisitePro project, do the following:

  1. Open the Rose model.
  2. Do one of the following:
    - To associate the model with a project, select Tools > 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 select RequisitePro > Associate Package to Project. The "Associate Package to Project" dialog box appears.
  3. 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 C:\Program Files\Rational\RequisitePro 4\Projects directory. This may vary when accessing network-based projects or customized local project directories.
  4. 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.
  5. 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.
  6. At the Default Requirement Type field, click the down arrow and select a requirement type from the list.
    This requirement type, such as UC, controls the choice of attributes (such as Priority, Status, and Iteration) that you will use when managing your use cases.
  7. Select a Rose Path Map if you are using a virtual path map for your Rose model.
  8. Click OK to save the association and close the dialog box.

For More Information

Refer to the following help topic in the Integrated Use Case Management online help:

  • Associating a model with a project

Associating a use case with a requirement

In order to add attributes to a use case, you associate the use case with a requirement.

  1. In the Rose model browser tree or use-case diagram, right-click a use case.
  2. To add new attributes to a use case, select Requirement Attributes > New from the context 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.

Note: To add attributes of an existing requirement to the use case, select Requirement Attributes > Associate from the context 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. The text of the existing requirement is updated to the name of the Rose use case.

For More Information

Refer to the following help 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

Associating a use case with a document

  1. In the Rose model browser tree or use-case diagram, right-click a use case.
  2. Do one of the following:
  • To create a new document, select Use Case Document > New from the context 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 RequisitePro's Word Workplace to save the document.
  • To associate the use case with an existing document, select Use Case Document > Associate from the context 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.

For More Information

Refer to the following help topic in the Integrated Use Case Management online help:

  • Associating a use case with an existing document

Managing use-case attributes and documents To top of page

Use-case attributes are managed in an associated RequisitePro requirement. The requirement dialog box defaults to the Attributes tab when the dialog box opens. 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.

Tool Steps

To set the values of the use-case attributes, do the following:

  1. Right-click on a Rose use case that is associated with a requirement or a document.
  2. Select Requirements Attributes > Open from the context menu. The requirement dialog box appears.
  3. At the attribute fields on the Attributes tab select or type a value for each attribute field.
    Note: Do not modify the RoseType, RoseModelPath, or RoseItemID attributes.
  4. Click OK to save your settings and close the dialog box.

To open the RequisitePro requirements document that is associated with a use case:

  1. In the browser tree or use-case diagram, right-click a use case that has an association with a RequisitePro document.
  2. Select Use Case Document > Open from the context menu.

For More Information

Refer to the following help topic in the Integrated Use Case Management online help:

  • Assigning attribute values to a use case
  • Opening the associated document

Creating Rose Use Cases from RequisitePro Requirements To top of page

To use RequisitePro use case requirements to create use cases in a Rose model:

  1. Select a requirement in a RequisitePro view or document. For a document-based requirements, open the document and simply place the cursor in the requirement text.
  2. Select Requirement > Rational Rose >Associate to Use Case. In the Word Workplace, these menu selections are found on the RequisitePro menu. The Document Rose Use Case Association dialog box appears.
  3. Type a full path and Rose model file name in the indicated field, or click Browse and open the Rose model file.
  4. Click Apply. Any use cases in the model that are not associated to a requirement or document appear in the Select Rose Item(s) list.
  5. Select a use case and click Create. The Create a New Use Case dialog box appears. The Use Case Name field displays the selected requirement text, by default. To change the name of the new use case, type a new entry.
  6. Select a package in which the new use case will be located.
  7. Click OK. If the Use Case Name entry is different than the requirement text, the Resolve Use Case name dialog box appears.
  8. 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.
  9. Click OK.

For More Information

Refer to the following topic in the Integrated Use Case Management online help:

  • Creating use cases from requirements
Copyright  ⌐ 1987 - 2000 Rational Software Corporation

Display Rational Unified Process using frames

Rational Unified Process