Professional Documents
Culture Documents
L07 UseCaseDiagram
L07 UseCaseDiagram
CS20006
Lecture 7
• Example:
– On-line purchase (OLP) system
S earch item s
P lace o rd er
C ustom er
<<S ystem >>
P ro cess o rd er
P aym ent processor
In v en to ry co n tro l
• Formal definition
• A use case is a sequence of transactions performed by the system
that yields a measurable result of values for a particular user (actor)
P lace o rd er
• Note: Actors are not part of the system; they represent any one or any thing
that interact with the system
Notation
P lace o rd er
In v en to ry co n tro l
R e le a s e 2
M anager
Notation T ax calcu latio n
R e le a s e 3
O n -lin e h elp
R e le a s e 4
R egistration
Note: Usually package can be used when a UML diagram is quite large and
can not be accommodated on a single page, or organize a large diagram
into smaller ones
S tudent R egistration
S ystem
C ourse
R egistration B illing
allotm ent
Note: From one scenario, another scenario can arise. For example: at 3 incomplete
information, at 6 authorization fails etc.
….. etc.
– Will any actor create, change, store, remove, or read information in the
system?
….etc.
– information storing/updating
….etc.
– Extend
– Generalization
<<include>>
B illing C ash paym ent
S earch B ook
n c lude>>
<<i
Issue B ook
<<include>>
U pdate B ook
• Optional behavior
B illing <<ex
tend > C heque paym ent
>>
c lu de>
<<in
O ther paym ents <<in
c lude
>>
C redit card paym ent
<<extend>>
S ecurity C heck
P rocess O rder
If a student is
w ith foriegn visa
<<extend>> <<extend>>
If the custom er
T o a special type
is not a regular
of custom er
custom er
P ay F ees
S tudent
S tudent
Internation
student
UG PG R eserach
• When there are too many use cases in the use case diagram, it
is better to package the related use cases so that it can be better
documented
U se case 1 U se case 2
U se case 3
U se case 3.3
U se case 3.3.3