Identifying - PowerPoint PPT Presentation

About This Presentation

Title:

Identifying

Description:

Division of AIDS Identifying & Creating Use Cases - Part 3 October 1, 2003 – PowerPoint PPT presentation

Number of Views:75

Avg rating:3.0/5.0

Slides: 80

Provided by: Robert68

Category:

more less

Transcript and Presenter's Notes

Title: Identifying

1
Identifying Creating Use Cases - Part 3
Division of AIDS

October 1, 2003

2
Agenda

Training Plan Overview
Review Parts 1 2
Use-Cases Packages
Activity Diagrams
Activity Diagram Description
Activity Diagram Creation Procedures
Adding Detail
Events
Guard Conditions
States
Analysis
Advanced Diagrams
Swimlanes
Object Flows
Next Steps

3
Training Plan Overview

Identifying Creating Use Cases
Part 1 (Wednesday, September 24)
Part 2 (Friday, September 26)
Part 3 (Today)
Actors and Use Case Diagrams
Detailing Requirements with Requisite Pro
(Parts 1 2)
Sequence Diagrams
State Transition Diagrams
Collaboration Diagrams
Reports
SoDA

4
Part 1 Review

Models
Business
Business Analysis
Use-Case
Analysis
Design
Implementation
Deployment
Packages used to organize the models
Logical breakdown of model elements
Supports model management

5
Part 1 Review

Use Cases
Describes activities
One use case is assigned per package
Each Use Case specified by 5 basic types of
diagrams, text and
Use-Case
Activity
State
Sequence
Collaboration

6
Part 1 Review

For each package identified
Create the Package
Create the packages use-case use the same name
as the package
Create shells of all use-case-related diagrams
Use analysis techniques to fill in the diagrams

7
Part 2 Review

Identifying Use Cases - Analysis Steps
Identification
For each identified use case
Create a context and detail activity diagram
Identify potential sub-use cases
Create a new package, use case, and related
diagrams for the identified sub-use case
Move relevant activities under the sub-use case
Cleanup and Complete

8
Part 2 Review

Organization
Packages
Views
Use-Case View
Logical View
Component View
Deployment View
Hierarchy
Levels of Abstraction

9
Part 2 Review

Activity Diagram
Definition Defines the workflow associated with
the use case
How used
Details the actions to be taken and decisions to
be made for a use case
Helps identify possible use cases at next level
of detail
Types
Regular
With States
With Swimlanes
With Object Flows

10
Part 2 Review

Activity Diagram Model Elements
Start State
End State
Activity
Decision
State Transition
Regular
Transition To Self
Horizontal and Vertical Synchronization
Note
Note Anchor
Text
Swimlanes
State

11
Part 3 - Overview

Activity Diagrams
Labels
Events
Actions
Stereotypes
Conditional Threads
Guard Conditions
History States
Nested Activities
Transitions to Self
Decision Guards
States
Decision Merges

Use-Case Analysis
Swimlanes
Object Flows

12
Activity Diagrams (AD) Components
13
AD Decisions Events

A decision defines a specific location on an
activity diagram or statechart diagram where the
workflow may branch
1 to n branches
1 to 2 branches normal
Event defines a trigger of a state transition (1
to n)
A decision of ???
Type of event

14
AD Decisions Events
15
AD - Events

Add event
Right click transition and select Open
Specification
Select General tab.
Enter Event
Click OK

16
AD - Events

Enter Event
Click OK

17
AD Activity Actions

An action defines a step within an Activity or
State
Add Actions
Right click activity
Select Actions tab
Right click and select Insert

18
AD Activity Actions

Specify action
Right click added action
Select When
Select Type
Enter Name
Click OK
Repeat as Necessary

19
AD Activity Actions
20
AD Activity Stereotype

A stereotype defines a sub-classification of a
model element
Add Stereotype
Right click activity
Select General tab
Select stereotype from drop down or add new type

21
AD Activity Stereotype

Change Stereotype Display
Right click and select Options, Stereotype
Display, Decoration

22
AD Details
23
AD Conditional Threads

A conditional thread defines a branch of workflow
which only occurs when a set of conditions exist

24
AD Guard Conditions

A Guard Condition defines a condition which, when
true, allows the transition to occur. As long as
the condition remains false, the transition will
not occur.
Add guard condition
Right click transition and select Open
Specification
Select Detail tab.
Enter Guard Condition
Click OK

25
AD Conditional Threads and Guard Conditions
26
AD Conditional Threads and Guard Conditions
27
AD History States

History states allow the state machine to
re-enter the last sub-state that was active prior
to leaving the composite state.
Add history state
Right click activity and select Open
Specification
Select State/Activity History check box.
Select OK

28
AD History States
29
AD Nested Activities

Nested Activities are a way to visually present
the equivalent of a sub- diagram of activities
Enclosing activity is referred to as a
superactivity
Nested activities are called subactivities

30
AD Nested Activities
31
AD Transitions to Self

Transitions to Self are a looping mechanism
Drag and Drop Transition to Self tool onto
activity
Add guard condition to new transition
Add guard condition to activity completion
transition

32
AD Transitions to Self
33
AD Decision Guard Conditions

Decision Guards Conditions control the flow of a
decision via the transitions from the decision
Boolean logic of True

34
AD Decision Guards
35
AD Decision Guards
36
Use-Case View

Activities Added
State/Models Added
Clean Up
Rename
Other Sub-model elements added

37
AD - States

A state defines a condition of an object in which
it performs some activity or waits for an event
Add a state
Drag and drop State tool on to the diagram
Name the state
Connect transitions

38
AD - States
39
AD - States
40
AD - States
41
AD - States
42
Use-Case View

States Added

43
Use-Case View

Review
Reorganize
Complete

44
Use-Case Analysis
45
Use-Case Analysis

3 New Use-Cases
Check In Passenger
Verify Reservation
Passenger List
Add New Use-Cases
Follow Process

46
Use-Case Analysis

Rename Verify Reservation to Check In Passenger

47
Use-Case Analysis

Delete Actions

48
Use-Case Analysis
49
Use-Case Analysis
50
Use-Case Analysis
51
Use-Case Analysis
52
Use-Case Analysis
53
Use-Case Analysis
54
Use-Case Analysis
55
AD Decision Merges

Use decisions to show where the threads merge
again

56
AD Clean Up
57
AD Clean Up
58
AD Clean Up
59
AD Clean Up
60
AD Clean Up
61
AD Clean Up
62
Advanced AD - Swimlanes

Swimlanes are similar to an object
Represent organizational units or roles
Allow assignment of activities to the
organizational units or roles

63
Advanced AD - Swimlanes
64
Advanced AD - Swimlanes
65
Advanced AD - Swimlanes
66
Advanced AD - Swimlanes
67
Advanced AD - Swimlanes
68
Advanced AD - Swimlanes
69
Advanced AD - Swimlanes
70
Advanced AD - Swimlanes
71
Advanced AD - Swimlanes
72
Advanced AD Object Flows

Object flows are used to show how business
entities are created and used in a workflow
The object flow state represents the state of an
object of a class as it participates in the
workflow
The same object can be manipulated by a number of
successive activities that change the object's
state.
The same object can then be displayed multiple
times in an activity graph, with each appearance
representing a different state during its life.

73
Advanced AD Object Flows