Beruflich Dokumente
Kultur Dokumente
UML Modeler
IBM
User Guide
Version 4.2.2
Note !
Before using this information and the products it supports, be sure to read the general information
under Notices and Trademarks on page 163.
IBM welcomes your comments. You can send to the following address:
Include the title and order number of this book, and the page number or topic related to your comment.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the
information in any way it believes appropriate without incurring any obligation to you.
Chapter 1: Getting Started with UML Modeler shows you how to install and launch the UML
Modeler as a stand-alone application; and introduces the main windows, toolbars, and
diagrams of UML Modeler. It also shows you how to organize model elements in packages
and provide general guidelines on how to work with UML Modeler.
Chapter 2: Use Case Diagrams shows you how to create and open Use Case diagrams and
work with their elements: Use Cases, Actors, and Relationships.
Chapter 4: Class Diagrams shows you how to use the Class Diagram Toolbar to create their
main elements: Classes and Relationships and how to use the Class Properties dialog box
define the Class properties.
Chapter 5: State Machine Model introduces the two types of diagrams: Activity Diagrams
and State Diagrams and shows you how to work with their elements.
Chapter 6: Component Diagrams shows you how to create and open Component diagrams
and work with their elements: Subprogram, Package, Task, and Database
Related Guides
User Guide provides a general introduction to IBM Holosofx Workbench, a description of
the contents of the Repository, and information about how to customize the IBM
Holosofx Workbench application.
Modeling Guide provides information about the objects used to create Process Models
and how to handle specific situations in a Process Model.
Analysis Guide provides information about how to perform Case, Weighted Average,
and Simulation Analysis.
Reporting Guide provides information about how to generate and use the many tables,
charts, and reports produced from analysis of IBM Holosofx Workbench Processes.
Tutorial provides a hands-on practice session that will familiarize you with the basic
components of IBM Holosofx Workbench and how to use the software for BPR. The
Tutorial takes approximately four to six hours to complete.
The UML Modeler window consists of the menu bar, toolbars, Browser pane,
Work Space area, and Documentation pane. The table below lists the main
purpose of each of them.
Work Space Visual environment for creating, Create and edit UML objects and
defining, and linking UML objects diagrams.
Documentation pane Visual environment for viewing the View the documentation
documentation associated with associated with a selected UML
UML objects object in the Browser pane.
The Standard toolbar is the only toolbar in the UML Modeler window. The
descriptions of its buttons are given below.
The Shape Style toolbar appears in the Work Space in all UML Modeler
diagram windows. It is the leftmost horizontal toolbar in the Work Space. The
toolbar is activated only when a diagram element is selected. A description of
the toolbar buttons is given below.
Background Selects the background color. To change the colors, click new
Color colors in the Foreground and Background boxes.Select the
background color you want for the pattern
Line Style Selects line style and thickness for the selected element.
Line Color Toggles the color of the outline of the selected Class, Package,
or Object image. Each click of the button changes the color to
the next in a sequence of 16
Shadow Toggles a shadow effect, on and off, for the selected Class,
Package, or Object image
The Formatting toolbar appears in the Work Space in all diagram windows. It is
the third horizontal toolbar in the Work Space. The toolbar is activated only
when a diagram element is selected. A description of the toolbar buttons is
given below.
Font Size Selects the Font Size for the selected text. The
sizes in the Font Size selection box depend on the
selection in the Font Type selection box and the
active printer
Align Left Aligns the selected text with the left margin
Align Center Aligns the selected text directly between the left and
right margins
Align Right Aligns the selected text with the right margin
Bold Toggles bold typeset on and off for the selected text
Italic Toggles italic typeset on and off for the selected text
The File menu is concerned with the organization of the files containing UML
Modeler diagrams. These files have an extension of umm. The File menu
items are described below.
Open Model Opens an existing model. Pressing Ctrl+O also activates this item
Save Model Saves the current model. Pressing Ctrl+S also activates this item
Print Opens the Print dialog box, which allows you to print model diagrams.
Pressing Ctrl+P also activates this item
Print Preview Shows on the screen how a file will look like when you print it
The Edit menu is concerned with basic editing functions, and conforms to the
Windows standard. The Edit menu items are described below.
Redo Redoes the last action. Pressing Ctrl+Y also activates this item
Cut Cuts the elements selected in the diagram (does not delete the
elements from the model, but only from the diagram). Pressing
Ctrl+X also activates this item
Paste Pastes the previously cut or copied elements into the diagram.
Pressing Ctrl+V also activates this item
Delete Deletes the elements selected in the diagram (does not delete
the elements from the model, but only from the diagram)
The View menu is concerned with the visual display of the UML Modeler
window plus a list of the opened diagrams. There are a number of items on the
View menu. These items are described in the following table:
Status Bar Toggles the display of the status bar. If a check mark appears next to the Status
Bar item on the View menu, then the status bar is displayed. If no check mark
appears, then the status bar is not displayed.
Browser Toggles the display of the Browser. If a check mark appears next to the Browser
item on the View menu, then the Browser is displayed. If no check mark appears,
then the Browser is not displayed.
Drawing Shape Style Toggles the display of the Shape Style toolbar of the active diagram. If a check
Toolbars mark appears next to the Shape Style item on the View menu, then the Shape
Style toolbar is displayed. If no check mark appears, then the Shape Style toolbar
is not displayed.
Formatting Toggles the display of the Formatting toolbar of the active diagram. If a check
mark appears next to the Formatting item , then the Formatting toolbar is dis-
played. If no check mark appears, then the Shape Style toolbar is not displayed.
Diagram Toggles the display of the Diagram View toolbar of the active diagram. If a check
View mark appears next to the Diagram View item on the View menu, then the Diagram
View toolbar is displayed. If no check mark appears, then the Diagram View tool-
bar is not displayed.
Construction Toggles the display of the Construction toolbar of the active diagram. If a check
mark appears next to theConstruction item on the View menu, then the Construc-
tion toolbar is displayed. If no check mark appears, then the Construction toolbar
is not displayed.
Layout Arranges the diagram objects in a more organized way, based on the diagram
objects' inter-relationships.
Options Opens the Options dialog box where you can add, modify and save several
templates that hold custom settings for current diagram-type objects.
<Opened Diagram Displays the diagrams' names in the order in which they were opened or added.
Windows List> The diagram name that is marked with a check mark is the current active
diagram. To cause a different diagram to become the active one, simply select it
from the list.
The Help menu offers information about the UML Modeler and its operation.
There are two items on the Help menu. These items are described below.
Sequence Shows the interactions among objects with Developers & Architects
an emphasis on time & IT Analysts
From the menu bar, you can select File > New Diagram to access
the New Diagram dialog box.
3. Select a radio button indicating the type of diagram: Class, Use Case,
Collaboration, or Sequence.
* If you select Sequence or Collaboration, select or clear the
Enhanced check box to indicate whether the diagram is to be
enhanced or regular (That is, the toolbar for this diagram displays full
range of tools buttons or only some of them).
4. Type a name for this diagram in the Name text box.
5. Click OK.
4. Once you have added the elements, you can rearrange them by
dragging and dropping them where you please.
You can drag some element types, like Classes and Use Cases,
from the Browser and drop them in the diagram while other
element are not draggable.
3. Navigate to the diagram into which you want to paste your copied (or
cut) elements, and make that the active diagram.
4. Select Paste from the Edit menu. The copied (or cut) element(s)
appear in the active diagram, in the same location, with respect to the
upper left corner of the Work Space, that the original elements occupied.
You can also paste the cut or copied object (s) by right-
clicking the Work Space in the diagram where you want to
paste the selected element(s) and selecting Paste from the
shortcut menu.
Use the Text Box element to display free-floating text in your diagram. To add
a Text Box element into a diagram:
1. Select the Text Box button . The cursor within the diagram area
will resemble an asterisk.
2. Click inside the diagram area, in the approximate area where you want
the Text Box to be displayed. The word Text appears in the currently
active Font Type and Font Size.
- The program default Font Type is Arial 14, and the default Font Size is
12.
If you select a large italicized Font Type, then you may need to add
a space at the end of your text in order for the entire line of text to
be displayed.
3. Select the Font Type and Font Size you want to use from the
Formatting toolbar.
4. Select the other buttons on the
Formatting toolbar to color, align,
make you text bold, italic, or underlined.
5. Type over the word Text the text that you want to be displayed in this
location.
7. Select the Selection Tool button to drag the text to its final location.
To modify an existing Text Box element:
1. Double-click the Text Box element. The text cursor appears blinking at
the beginning of your existing text.
2. Edit the text.
3. Press the Esc Key when you are finished.
Use the Note element to display text in the form of a note in your diagram.
To add a Note element into a diagram:
1. Click the Note button . The cursor within the diagram area will
resemble an asterisk.
2. Click inside the diagram area, in the approximate area where you want
the Note to be displayed. A Note element appears.
If you select a large italicized type, then you may need to add a
space at the end of your text in order for the last text character to
be displayed.
Use the Group element to provide your diagram with a visible, logical grouping
of elements.
1. Click the Group button . The cursor within the diagram area will
resemble an asterisk.
2. Move the mouse cursor to where you want the center of the Group box
to be displayed.
3. Click in the workspace area.
Modifying
To modify an existing Group element:
1. Select the Group element.
1. Click the Anchor button . The cursor within the diagram area will
resemble an asterisk.
2. Move the mouse cursor from the center of the diagram element to the
center of the Note element to be connected.
Rules Tab
The Rules tab allows you to apply the following settings:
Select the diagram object to which you apply custom settings from the
Active Shapes list.
Select the In Shapes (diagram objects from which relationships can be
established with the selected object) and/or the Out Shapes (diagram
objects to which the selected object can connect and establish
relationships).
Add or remove one or more diagram objects from the In Shapes or the Out
Shapes list by using the Add (represented by a single right arrow), Add All
(represented by double right arrows), Remove (represented by a single left
arrow), or Remove All (represented by double left arrows) buttons.
Select the sides of the diagram object that relationships from other
diagram objects can be connected to (In Sides), and the sides of the
selected object from which the relationships can emerge to other diagram
objects (Out Sides).
Text Tab
The Text tab allows you to apply the following settings:
Select the diagram object to which you will apply custom settings from the
Active Shape list.
Using the Text Edit dialog box, Add, Edit, and Delete the text position(s)
for the selected diagram object.
Preview the settings applied to the diagram object in the preview area.
6. In the Rules tab, select the diagram object to which you want to apply
settings from the Active Shapes list. Then click InShapes or
OutShapes to display the diagram objects that can have a relationship
with the selected shape.
7. In the Text tab, select the diagram object to which you want to apply
settings from the Active Shapes list. Then add, edit, or delete the text
positions in the selected diagram object.
- To add a text position, click Add. The Text Edit dialog box will open.
* Select a text position from the Position list.
* Select a text alignment by clicking one of the Align radio buttons
(Left, Center, Right).
* To change the font, click the Setting button. The Font dialog box
opens. Apply the selected font settings, and then click OK. The
Text Edit dialog will appear.
* To disable editing of the object's text while working in the diagram,
clear the Enable Editing check box.
* Click OK. The Template Setting dialog box appears.
8. Click OK. The Options dialog box will appear.
You can add or remove one or more diagram objects from the In
Shapes or the Out Shapes list by using the Add (represented by a
single right arrow), Add All (represented by double right arrows),
Remove (represented by a single left arrow), or Remove All
(represented by double left arrows) buttons.
6. In the InSides area, clear the check box(es) next to the object's side(s)
to which relationships should not be connected, or in the OutSides
area, clear the check box (es) next to the object's side(s) from which the
selected object's relationships should not emerge.
7. Click OK.
The Package has been removed from the diagram, but still exists
in the Browser and in other diagrams.
2. Browse to locate the UML Modeler file that you want to open.
3. When the UML Modeler file you want to open is displayed in the list box,
either:
- Double-click the file, or
- Select it and then click the Open button.
3. Type the name of the (.mdl) to which you want to export the UML model
in the File name box, and select the location where you want to save
the exported file.
If you type a file name that already exists, then a warning message
will appear to ask you if you want to replace the existing file name
with another one. Click Yes to continue or No to re-type a different
file name.
4. Click Save. A progress indicator window appears notifying you with the
status of the model export, then disappears when export is completed.
The UML model is exported to a (.mdl) file and saved in the selected
location.
2. Select the (.mdl) file that you want to import into the UML Modeler, and
click Open. A progress indicator window appears notifying you with the
status of the model import, then disappears when import is completed.
The UML Modeler will open the imported file.
If you type a file name that already exists, then a warning message
will appear to ask you if you want to replace the existing file with
the new one. Click Yes to continue or No to re-type a different file
name.
3. Click Save. The UML model will be exported to an XML file and saved in
the selected location. A confirmation message will appear to inform you
that the export has been done.
2. Select the XML file that you want to import into the UML Modeler, and
click Open. The file will be imported and opened in UML Modeler.
If you try to import a file that is not a valid UML Modeler XML file,
then an error message will appear notifying you of this.
If you type a file name that already exists, then a warning message
will appear to ask you if you want to replace the existing file with
the new one. Click Yes to continue or No to re-type a different file
name.
4. Select the Stereo Type for the UML model's Activity diagram
swimlanes. You can select one of the following options:
- Role: The swimlanes in the exported Activity diagram will be
represented as roles associated with the IBM Holosofx Workbench
process tasks.
- Organization Unit: The swimlanes in the exported Activity diagram
will be represented as org. units that are associated with the IBM
Holosofx Workbench process tasks.
- Application: The swimlanes in the exported Activity diagram will be
represented as applications that are associated with the IBM Holosofx
Workbench process tasks.
5. Click Transform. The Activity diagram (s) will be exported to an IBM
Holosofx Workbench XML file where each Activity object is transformed
to an IBM Holosofx Workbench task, and the swimlanes are transformed
according to your selection from the Transformation Option dialog box.
To import a UML Activity diagram from an IBM Holosofx Workbench process
diagram:
2. Select the Workbench XML file of the process diagram that you want to
import into the UML Modeler as an Activity diagram, and then click
Open. The Transformation Option dialog box appears.
If you try to import a file that is not a valid Workbench XML file,
then an error message will appear notifying you of this.
3. Select the stereo type to which the swimlanes in activity diagrams will be
transformed from the IBM Holosofx Workbench process tasks. You can
select one of the following options:
If you type a file name that already exists, then a warning message
will appear to ask you if you want to replace the existing file with
the new one. Click Yes to continue or No to re-type a different file
name.
3. Select the stereo type to which the Actors in use case diagrams will be
transformed in the IBM Holosofx Workbench process tasks.You can
select one of the following options:
- Role: The Actors in the exported Use case diagram will be
represented as roles that are associated with the IBM Holosofx
Workbench process tasks.
3. Select the stereo type to which the Actors in use case diagrams will be
transformed from the IBM Holosofx Workbench process tasks. You can
select one of the following options:
- Role: The Actors in the imported Use case diagram will represent the
roles that are associated with the IBM Holosofx Workbench process
tasks.
- Organization Unit: The Actors in the imported Use case diagram will
represent the org. units that are associated with the IBM Holosofx
Workbench process tasks.
- Application: The Actors in the imported Use case diagram will
represent the applications that are associated with the IBM Holosofx
Workbench process tasks.
4. Click Transform. The Workbench XML file will be imported to Use Case
diagram (s) where each IBM Holosofx Workbench task is transformed to
Use Case object, and the Actors will represent your selection from the
Transformation Option dialog box.
3. Type the name of the rule-based file to which you want to export the
sequence diagram in the File name box. Select the location where you
want to save the file and click Save. The sequence diagram will be
exported to a rule-based XML file.
If you type a file name that already exists, then a warning message
will appear to ask you if you want to replace the existing file with
the new one. Click Yes to continue or No to re-type a different file
name.
In UML Modeler, a Use Case diagram depicts the functionalities of your system
by displaying the use cases, actors, and the relationships among these objects.
A Use Case diagram represents detailed system requirements and describes
what the system can do and what the system is intended to accomplish. The
information contained in a Use Case diagram is important for establishing a
solid project foundation. Moreover, the Use Case diagram describes the
sequence of events of an actor that uses the system to complete a process. An
actor could be an external entity, a person, or another system that interacts with
the system.
A Use Case diagram may contain any of the following elements:
Use cases
Actors
Relationships:
* Association relationships between use cases and actors.
* Generalization and Association relationships between use cases.
* Generalization and Association relationships between Actors.
Through the use case diagram, you can determine which actors initiate which
use cases, and when a use case sends information to a actor.
There are several important points to remember while creating Use Case
diagrams in UML Modeler:
Do not model actor-to-actor relationships. By definition, the actors are
outside the scope of the current project, therefore, any relationship
between these actors is also outside the scope of the system. You may
model the actors initiating the system and/or receiving information from the
system.
Use cases must be initiated by an actor. In other words, every use case
should have an Association relationship starting from an actor and ending
at that use case.
Think of a Use Case diagram as being associated with a database. You
can enter information into the database using one use case, and access
the information in the database using another use case. You dont have to
draw arrows from one use case to another to show information flow.
The new use case will be named UseCase 1. If this name is already
used by another use case in the model, the new name will be Use
Case 2, and so on.
For more information about the State Machine model and its diagrams, please
refer to the chapter entitled State Machine Model in this guide.
The new actor will be named Actor 1. If this name is already used
by another actor in the model, the new name will be Actor 2, and
so on.
3. With the new actor selected, open the Actors Properties dialog box.
4. Type the name of the new actor in the Name text box.
5. Click the Update button to replace the default name.
The new actor will be named Actor 1. If this name is already used
by another actor in the model, the new name will be Actor 2, and
so on.
Through this tab, you can name an Actor, add a description to an Actor, delete
an Actor, assign a stereotype to an Actor, and create Abstract, Singlton, Visible,
Persistent, and Transient Actors
Naming Actors
Each actor should be given a unique name.
To name a new actor in the model:
1. Open the Actors Properties dialog box.
2. Click the New Class button. A new actor appears with the default name
in the Classes selection box.
3. Type the new name in the Name text box in the Classes selection box.
4. Click the Update button. The Actor name is update.
To rename an existing actor:
1. Open the Actors Properties dialog box.
2. Type the new name in the Name text box in the Classes selection box.
Deleting Actors
If you want to delete an existing actor from the model, while the Actors
Properties dialog box is opened:
1. Select the actor or class you want to delete in the Classes selection box.
2. Click the Delete Class button. A warning message appears.
3. Click OK to confirm deleting the actor or class, or Cancel to cancel the
deletion.
When modeling the system and the Use Case diagrams, you may want to know
which Sequence and Collaboration diagrams contain a particular actor. UML
Modeler shows you this information in the Instances tab in the Actors
Properties dialog box.
To view a diagram, select it in the list and then click the View
Diagram button.
For more information about a State Machine model and its diagrams, please
refer to chapter entitled State Machine Model in this guide.
Role A defines the source (the actor you draw the relationship
from) and Role B defines the destination (the actor you draw the
relationship to).
Cardinality Meaning
n Many
0..0 Zero
0..n Zero or
more
Role A defines the source (the actor you draw the relationship
from) and Role B defines the destination (the actor you draw the
relationship to).
5. Right-click the condition object and select Properties from the shortcut
menu. The Condition Properties dialog box opens.
6. Select the operation that will evaluate the condition in the Operation
drop-down list, or create a new one.
7. Click the Object Link button on the toolbar.
8. Drag the mouse from the Condition object to the object receiving the
message.
9. Right-click the message and select Properties. The Message
Properties dialog box appears.
10. Type the name of the message.
11. Click OK.
The top section of the Class object in the diagram contains the Class name. The
middle section contains the attributes of the Class. The lower section contains
the operations of the Class.
OR
1. Right-click the desired classs name or icon in the Browser. A shortcut
menu appears.
2. Select Properties from the shortcut menu. The Class Properties dialog
box appears.
OR
1. Select the Class in a Class diagram.
The new stereotype will be now available in the drop-down list box
for association with other classes in the model.
5. Click OK.
You do not have to open the Class Properties dialog box for each
class in order to define this item for it. You can simply open the
Class Properties dialog box of any class, select the desired class
name from the Classes selection box, apply the changes you
want, and then click Update.
You do not have to open the Class Properties dialog box for each
class in order to define this item for it. You can simply open the
Class Properties dialog box of any class, select the desired class
You do not have to open the Class Properties dialog box for each
class in order to define this item for it. You can simply open the
Class Properties dialog box of any class, select the desired class
name from the Classes selection box, apply the changes you
want, and then click Update.
For more information about State Machine model and its diagrams, please refer
to the chapter entitled State Machine Model chapter in this guide.
Remember that Role A defines the source (the Class you draw the
relationship from) and Role B defines the destination (the Class
you draw the relationship to).
Cardinality Meaning
n Many
0..0 Zero
Remember that Role A defines the source and Role B defines the
destination.
State Machine Model is a container that holds two types of diagrams. These
types are State diagrams and Activity diagrams. The State Machine Model and
its diagrams are used as a sub diagram of a Package, Class, or Use Case. This
chapter will illustrate the purpose of these two diagram types, how to create an
Activity or State diagram as a sub diagram of a Package, Class, or Use Case,
and how to work with these diagrams.
You cannot create more than one State Machine Model for each
class, use case or package.
The General tab of the Activity Properties or State Properties dialog box
contains the activity or state properties. These properties are:
Name: When you add a new State or Activity to the diagram, a default
Name Activity 1 or State 1 will be assigned to this State or Activity. If this
name is used by another Activity or State, then the default name will be
Activity 2 or State 2, and so on. You can rename the Activity or State to
give it a name that represents its actual behavior.
Stereotype: The Stereotypes are used to categorize model elements. You
can use this field to create a new category or to select one of the existing
categories for the selected Activity or State.
Owner: This is a read-only field that displays the Class, Use Case or
Package name for the current State Machine model and its diagram. The
name displayed in this field is the same for all elements in the diagram.
Swimlane: This field displays the Swimlane name in which you placed the
selected Activity or State. If you did not add any swimlanes to the diagram,
this field will be empty.
Documentation: This field allows you to add a short description for a State
or Activity.
To edit the Activity or State properties in the General tab:
The Transitions tab displays a table of all transitions that start from the
selected State or Activity. The transitions table consists of three columns:
Source: The Transition Source State or Activity.
Event: The Transition Event that occurs during the transition.
Target: The Transition Target element. The target can be any diagram
element that can be added to the State or Activity diagram.
When you double-click any transition in the Transitions table, the Transition
Specification dialog box will open to display the selected Transition's details.
Each state and activity on a State or Activity diagram may contain a number of
internal actions. An action is best described as a "task" that takes place inside a
state or activity. There are various action triggers within a state or activity. Each
action trigger represents the timing options for specifying when the action is
performed:
Entry: Specifies an action to be performed upon entering a state.
Exit: Specifies an action to be performed upon exiting a state.
Do: Specifies an action to be performed upon entering a state and
continues until exiting the state.
Event: Triggers an action only if a specific event is received.
The Actions tab of the State Properties or Activity Properties dialog box
displays the Actions table that lists all actions associated with the selected State
or Activity. The table consists of two columns:
Type: The Type column lists action trigger of each existing action in the
selected Activity or State.
Name: The Name column lists the Action Name that occurs on the
specified trigger.
To add a new Action click Add to open the Action Details dialog box and edit
the new action settings.
The Action Details dialog box allows you to enter the action settings for the
actions that were added to a state or activity. The Action Details dialog box
displays the following fields:
Action Trigger: The timing option that specifies when to perform an
action.
Event Name: The name of the event that will trigger the action.
Event Argument: Any optional arguments associated with the event.
Event Condition: A conditional Boolean expression.
Response: The type of the action that is performed: either a simple action
(Action) or an action that triggers another event (Send Event).
Action Name: The name of the action that is performed.
Send Argument: The arguments that are sent with the sent event
Send Target: The object that will receive the transition event.
To edit the Activity or State Actions Details:
2. Select the action trigger from the Action Trigger combo box. The
available action triggers are Do, Entry, Exit, and Event.
3. If the selected action trigger is Event, then:
- Type the Event Name in the Event Name text box.
- Type the Event Argument in the Event Argument text box.
- ype the Event Condition in the Event Condition text box.
4. Select the trigger response from the Response combo box. The
available response options are Action and Send Event.
5. Type the Action Name in the Action Name text box.
6. If the Response is Send Event, then type the Send Argument in the
Send Argument text box.
7. Type the Send Target in the Send Target text box
8. Click OK to save the entered data and to close the dialog box, or
Cancel to discard the entered data and to close the dialog box without
saving any changed data.
The General Tab of the Transition Specification dialog box allows you to
enter the following data:
Trigger Event: The name of the event that causes a transition.
Trigger Arguments: The transition's trigger-event arguments.
Stereotype: A category of the entered transition. You can use this field to
create or select a transition category.
Documentation: You can use this field to type a detailed transition
description.
To edit the Transition data in the General tab:
1. Select a Transition
2. Open the Transition Specification dialog box.
3. In the General tab, type the Trigger Event's name in the Trigger Event
text box.
4. Type the Trigger Arguments in the Trigger Arguments text box
5. Type the stereotype name in the Stereotype text box.
6. Type the description in the Documentation text box.
7. Click OK.
The Detail tab of the Transition Specification dialog box allows you to enter
the required values for additional fields that are related to conditional state or
activity transitions. The Detail tab also displays the source and the target
elements of the selected transition.
These fields are:
Guard Condition: The expression that triggers the transition when the
expression returns true.
Trigger Action: The action that occurs to trigger the transition.
Send Event: The name of the event that will trigger the action.
Send Argument: The sent events arguments.
Send Target: The object that will receive the transition event.
Source: The Source element's name (Activity, State, Decisionetc).
Target: The Target element's name (Activity, State, Decisionetc).
To edit the Transition data in the Detail tab:
1. Select a Transition
2. Open the Transition Specification dialog box.
3. Select the Detail tab.
4. Type the Guard Condition's name in the Guard Condition text box.
The General tab of the Decision Properties dialog box displays the decision
properties. These fields are:
Name: A default Name, Decision 1, will be assigned to this decision when
you add a new decision to the diagram. If this name is used by another
decision, then the default name will be Decision 2, and so on. You can
rename the Decision to give it a name that represents its actual behavior.
Stereotype: The Stereotypes are used to categorize model elements. You
can use this field to create a new category or to select previously defined
decision's stereotype.
The Transitions tab displays a grid of all transitions that start from the selected
decision. The transitions grid consists of three columns:
The Swimlane Specification dialog box contains the required Swimlane fields.
These fields are:
Name: A default name, Swimlane 1, will be assigned to this Swimlane
when you add a new Swimlane to the diagram. If this name is used by
another swimlane, then the default name will be Swimlane 2, and so on.
You can rename the Swimlane to give it a name that represents its actual
behavior.
Class: For each Swimlane, you can assign a class that is responsible of
the selected Swimlane. This class can be different from the owner of all
elements in the State Machine model.
Owner: This is a read-only field that displays the Class, Use Case or
Package name for which you created the current State Machine model
and its diagram. The name displayed in this field is the same for all
elements in the diagram.
The Dialog tab of the Synchronization Properties dialog box contains the
Synchronization bar fields. These fields are:
The Transitions tab displays a grid of all transitions that start from the selected
Synchronization bar. The transitions table consists of three columns:
Source: The Transitions Source Synchronization bar.
Event: The Transitions Event that occurs during the transition.
Target: The Transitions Target element. The target can be any diagram
element that can be added to the State or Activity diagram.
The General tab of the Object Instance Specification dialog box contains the
Object Instance data. These data are:
Name: The object instance's name.
Class: The class to which the Object instance belongs.
State: The selected object's state. All existing states in the model will be
listed in the combo box. You can use the combo box to select one of these
states or to create a new state and associate it with the object instance.
Stereotype: The name of the object instances stereotype. The stereotype
can be used to categorize the object instances.
Persistence: The lifetime of the object instances. There are three types of
object instance persistence:
* Persistent: The object continues to exist after its program terminates.
* Static: The object exists until its program terminates.
* Transient: The object exists only when the logic that calls it exists.
Multiple Instances: Shows that this object represents multiple instances
of the same class.
Documentation: This field allows you to add a short description for each
Object Instance.
In the Object Instance Specification dialog box, The Incoming Object Flows
tab displays all object flows that are received by the selected object instance
and sent by an activity. The Outgoing Object Flows tab lists the Object flows
that are sent by the selected object instance and received by an activity.
The Object Flow Properties dialog box allows you to enter the properties of
the Object Flows that connect object instances to activities in Activity diagrams.
The data in the Object Flow Properties dialog box are:
Name: The Object Flow name.
Stereotype: The object instances stereotype. The stereotype can be used
to categorize the object instances.
Class: The Object Flow's class. This field is a read-only field.
Documentation: This field allows you to add a short description for each
Object Flow.
To edit the object flow fields values:
1. Select an Object Flow.
2. Open the Object Flow Properties dialog box.
3. Type the object flow's name in the Name text box.
4. Type a new stereotype name, or select a stereotype from the
Stereotype combo box.
5. Type a description in the Documentation text box.
6. Click OK.
6.1.2 Component
A Component represents a logical part of a system that encapsulates
implementation and software entities, such as source code files, DLLs, and
documents.
A component is assigned to one or more Classes to represent physical
implementation of the class(es). Classes assigned to this component represent
services that are provided by this component.
2. Select New > Component Diagram from the shortcut menu. The New
Component Diagram dialog box appears.
3. Enter the name of the new Component diagram and click OK, or press
Enter. A new component diagram will be created with the entered name
and will open.
Deleting a class from a component object will not delete the class
from the model. It will only be removed from the component
object.
Aggregations
It is a type of classes relationships. Aggregations are
stronger forms of association. An aggregation is a
M Persistent Class
Persistence determines whether object information is
saved in internal storage. There are two persistence
options for a Class:
Persistent
Messages
Object information is saved in internal storage, and so
Through a message, one Object or Class can request
remains in the system after the execution of the
that another carry out some specific function. For
objects application.
example, a form may ask a report object to print itself.
Transient: Object information is not saved in internal
storage, and so is lost as soon as the objects applica-
Multiplicity (Cardinality)
tion has finished.
Multiplicity indicates how many instances of one
class are related to a single instance of another class at
PostConditions
a given point in time.
Postconditions are conditions that must always be true
For example, lets look at the case of accounts in a
after the operation has completed execution. Postcon-
bank. In this case, we will have classes called
ditions are entered in the Postconditions tab of the
Accounts and classes called Customers. The relation-
Operation Properties window.
ship is: customers may have accounts, but also
accounts may have customers. Multiplicity indicates
PreConditions
how many accounts a customer may have at one time,
A precondition is some condition that must be true
and how many customers an account may have at one
before the operation can be executed. You can enter
time.
any preconditions for the operation in the Precondi-
tions tab in the operation properties dialog box. If you
have an Interaction diagram that illustrates the opera-
O tion preconditions, you can enter the Interaction dia-
gram name at the bottom of the Preconditions tab.
Objects
An Interaction diagram can use Object names, Class
names, or both.
R
Operation Role Name
An operation is a behavior associated with a Class.
Role names can be used in associations or aggrega-
An operation has three parts: the operation name, the
tions instead of relationship names to describe the rea-
operation parameters, and the operation return type.
son for which the relationship exists. Generally, you
The operation takes the parameters as input, and pro-
would use a relationship name or a role name, but not
duces the return type as output.
both. Like relationship names, role names are
S
Static Attribute
A static attribute is one that is shared by all instances
of a Class. Returning to the above example, if Salary
were a static attribute, the value in the Static attribute
would be shared by Bill and John.
Unidirectional associations
In UML, Associations can be bi-directional or unidi-
rectional. Unidirectional associations contain one
arrowhead showing the direction of the message.
Use Case
A use case describes the sequence of events of an
actor using the system to complete a process. An actor
is any external entityfor example, a person or
another systemthat interacts with the system. The
entity can be in the form of a person, or another sys-
tem that sends or receives information from the sys-
tem. Use cases include all objects within an
application system.
Uses Relationship
A uses relationship allows one use case to use the
functionality of another use case. This is beneficial
when the functionality of one use case has features
that could also be used by several others. A uses rela-
Notices
IBM may not offer the products, services, or features discussed in this document in all
countries. Consult your local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any IBM intellectual
property right may be used instead. However, it is the users responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in
this document. The furnishing of this document does not give you any license to these
patents. You can send license inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other country
where such provisions are inconsistent with local law:
This information could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or changes in the product(s)
and/or program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only
and do not in any manner serve as an endorsement of those Web sites. The materials at
those Web sites are not part of the materials for this IBM product and use of those Web sites
is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate
without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling:
(i) the exchange of information between independently created programs and other programs
Such information may be available, subject to appropriate terms and conditions, including in
some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are
provided by IBM under terms of the IBM Customer Agreement, IBM International Program
License Agreement, or any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products,
their published announcements or other publicly available sources. IBM has not necessarily
tested those products and cannot confirm the accuracy of performance, compatibility or any
other claims related to non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.
This information may contain examples of data and reports used in daily business operations.
To illustrate them as completely as possible, the examples may include the names of
individuals, companies, brands, and products. All of these names are fictitious and any
similarity to the names and addresses used by an actual business enterprise is entirely
coincidental.
All statements regarding IBMs future direction or intent are subject to change or withdrawal
without notice, and represent goals and objectives only.
COPYRIGHT LICENSE:
This information may contain sample application programs in source language, which
illustrates programming techniques on various operating platforms. You may copy, modify,
and distribute these sample programs in any form without payment to IBM, for the purposes
of developing, using, marketing or distributing application programs conforming to the
application programming interface for the operating platform for which the sample programs
are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
General-use programming interfaces allow you to write application software that obtain the
services of this programs tools.
However, this information may also contain diagnosis, modification, and tuning information.
Diagnosis, modification and tuning information is provided to help you debug your application
software.
Warning: Do not use this diagnosis, modification, and tuning information as a programming
interface because it is subject to change.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other
countries, or both.
Solaris, Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
Other company, product or service names may be trademarks or service marks of others.