Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Hello World: Rational Software Architect

Design a simple phone book application

Tinny Ng (tng@ca.ibm.com), Advisory Software Developer, IBM Toronto
Tinny Ng
Tinny Ng is a scenario architect at the IBM SWG Scenario Analysis Lab, whose mission is to improve the cross-brand integration capability of IBM SWG products. She has more than 10 years of experience in software development, from design to implementation, including application building, packaging, testing, and support.
(An IBM developerWorks Contributing Author)

Summary:  Welcome to the first tutorial in the "Hello, World! Series", which will provide high-level overviews of various IBM software products. This tutorial introduces you to IBM Rational Software Architect, and highlights some basic features of Rational Software Architect with a hands-on exercise. Learn how to design an application using UML diagrams, publish the model information into a Web page, and transform the design to Java code using Rational Software Architect.

View more content in this series

Date:  05 May 2006
Level:  Introductory PDF:  A4 and Letter (703 KB | 24 pages)Get Adobe® Reader®

Activity:  48713 views
Comments:  

Creating a use case diagram

A use case diagram models the behavior of a system and helps to capture the requirements. It identifies the interactions between the system and its actors, and defines the scope of the system.

Actor
Represents a role of a user that interacts with the system. The user can be a human user, an organization, a machine, or another external system.
Use case
Describes a function that a system performs to achieve the user's goal. A use case must yield an observable result that is of value to the user of the system.

The use cases and actors shown in a use case diagram describe what the system does and how the actors use it, but not how the system operates internally. To relate an actor and a use case, you can create an association relationship to indicate the connection between the two model elements.

For our simple phone book application, assume there is only one actor, Any User, who can carry out the following two use cases against the system:

Add an entry
Enter a unique person name and a phone number using the provided application user interface. The system processes the entered data and stores it.
Search for a phone number
Retrieve a phone number by entering a unique person name using the provided application user interface. The system locates the phone number and returns it to the actor.

Would you like to see these steps demonstrated for you?

Show me Show me

To create a use case diagram that lists the two use cases:

  1. In the Model Explorer view, right-click Phone Book UML Model and select Add Diagram > Use Case Diagram.

    Figure 4. Adding a use case diagram
    Adding a use case diagram
  2. Enter User Case Diagram as the name of the generated diagram to replace the default name Diagram1. Now you can draw the use case diagram by adding various model elements from the Palette to the diagram.

    Figure 5. Adding model elements
    Adding model elements
  3. Select Actor in the Palette, then click anywhere in the diagram to create an Actor. Name it Any User.
  4. Select Use Case in the Palette, then click anywhere in the diagram to create a Use Case. Name it Add an entry.
  5. Similarly, create another use case called Search for a phone number.
  6. Select Association in the Palette. Draw the association relationship line from the actor Any User to the use case Add an entry to initiate a relationship between the two model elements.
  7. Similarly, create another association relationship between the actor Any User and the use case Search for a phone number.
  8. The complete use case diagram should look similar to Figure 6. Select Ctrl-S to save the diagram.

    Figure 6. Complete use case diagram
    Complete use case diagram

6 of 14 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational, Java technology
ArticleID=110599
TutorialTitle=Hello World: Rational Software Architect
publish-date=05052006
author1-email=tng@ca.ibm.com
author1-email-cc=