Tool Mentor: Identify Business Goals Using Rational Rose
This tool mentor describes how to use Rational Rose to record the results of finding business goals.
Tool: Rational Rose
Relationships
Main Description

Purpose

This tool mentor describes how to use Rational Rose to record the results of finding business goals.

Overview

To record the results of finding business actors and business use cases using Rational Rose:

1. Create the business goals package

The business goals package is created in the Business Use Case Model package (from Task: Find Business Actors and Use Cases). The Business Use Case Model can be found in the Use Case View in Rational Rose®. To create a package called "Business Goals" in the Business Use Case Model package:

  • Right-click to select the Business Use Case Model package in the browser.
  • Select Package from the New option on the pop-up menu. A NewPackage browser icon is added to the browser.
  • With the new package icon selected, type the name "Business Goals".

2. Create a class diagram

Business goals can be created in a class diagram. To create a class diagram for the business goals:

  • Right-click to select the package named Business Goals in the browser and make the pop-up menu visible.
  • Select Class Diagram from the New option on the pop-up menu. A NewDiagram class diagram icon is added to the browser.
  • With the new class diagram selected, type a name of the diagram.
  • Double-click the new class diagram to display it in the diagram window.

The first class diagram created in the Business Goals package is named Strategic Business Goals. The highest level business goals are created in this class diagram. Each high-level business goal may then have a separate class diagram showing its sub-goals. Each of these diagrams is named the same as the high-level business goal they represent.

3. Create business goals

To create a business goal in the class diagram, do the following:

  • Double-click a class diagram in the Business Goals package in the browser to display the diagram in the diagram window.
  • Click Business goal in the toolbox. The shape of the pointer changes to a plus sign. If you do not see a Business goal button in the toolbox, click a Class.
  • In the class diagram, left-click where you want to place the business goal symbol. Type the name of the new business goal.
  • Open the Class Specification dialog box by double-clicking the business goal's symbol in a class diagram or the browser. The Class Specification appears with «business goal» defined as the stereotype setting.
  • Open the General tab and confirm that the stereotype is «business goal». If not, change it to «business goal».
  • Write a brief description of the business goal in the Documentation field.
  • Click OK to accept and close the Class Specification dialog box.
  • Right-click the business goal and make sure that the Options: Stereotype Display icon is selected.

4. Document the relationship between business goals

To insert a dependency from a superior business goal to a sub business goal in a class diagram, do the following:

  • Click the Dependency arrow in the toolbox in the Class Diagram editor.
  • Position the pointer on the superior business goal in the class diagram. Left-click and move the pointer to the sub-business goal symbol and release.

5. Document the relationship between business goals and business use cases

To insert a supports dependency from a business use case to a business goal in a use case diagram, do the following:

  • Click the Dependency arrow from the toolbox in the class diagram editor.
  • Position the pointer on the business use case in the use case diagram. Left-click and move the pointer to the business goal symbol and release.
  • Double-click the created dependency and select the «supports» stereotype in the Dependency Specification dialog box.
  • Click OK.
  • Right-click the created dependency, and make sure that the Show Stereotype selection is selected in the pop-up menu.
  • If desired, reposition the stereotype label by dragging and dropping it in the diagram.