Tool Mentor: Detailing a Business Use CasePurposeThis tool mentor describes the steps for creating activity diagrams under a business use case in Rational Rose®. Related Rational Unified Process activity: Detail a Business Use-Case OverviewThis is a summary of the steps you follow to create an activity diagram in a business use-case model:
For detailed information on Activity Diagrams, see:
1. Create
an Activity Diagram in a Business Use Case
Activity diagrams can be very effective in illustrating the workflow of various events in a use-case diagram. The flow of events of a use case describes what needs to be done by the system in order to provide value to an actor. Also, use case diagrams present a high level view of how the system is used as viewed from an outsider’s (actor’s) perspective. You can use activity diagrams to specify and define each event in a use case diagram.
2. Create Swimlanes
(Optional)
Swimlanes are helpful when modeling a business workflow because they can represent organizational units or roles within a business model. Swimlanes are very similar to an object because they provide a way to tell who is performing a certain role. You should place activities within swimlanes to determine which unit is responsible for carrying out a specific activity. When a swimlane is dragged onto an activity diagram, it becomes a swimlane view. Swimlanes appear as small icons in the browser while a swimlane views appear between the thin, vertical lines with a header that can be renamed and relocated.
3. Create
and Describe an Activity State in the Diagram
An activity represents the performance of a task or duty in a workflow. It may also represent the execution of a statement in a procedure. An activity is similar to a state, but expresses the intent that there is no significant waiting (for events) in an activity.
4. Connect
Activity States with Transitions
Transitions connect activities with other model elements. You can create a transition between two activities or between an activity and a state.
5. Create Synchronization
Bars
Synchronizations enable you to see a simultaneous workflow in an activity diagram. Synchronizations visually define forks and joins representing parallel workflow. A fork construct is used to model a single flow of control that divides into two or more separate, but simultaneous flows. Every fork that appears on an activity diagram should ideally be accompanied by a corresponding join. A join consists of two of more flows of control that unite into a single flow of control. All model elements (such as activities) that appear between a fork and join must complete before the flow of controls can unite into one.
6. Create
Decisions with Guard Conditions
A decision represents a specific location on an activity diagram where the workflow may branch based upon guard conditions. There may be more than two outgoing transitions with different guard conditions, but for the most part, a decision will have only two outgoing transitions determined by a Boolean expression. You can place guard conditions on transitions to or from almost any element on an activity diagram.
|
Rational Unified
Process |