the default relationship between and actor and a use case
«communicate»
Give your use case a unique name expressed in a few words
Oblong
are good at helping you to capture, visualize, and describe an ordered set of actions from a beginning to an end.
Activity Diagram
were called decision diamonds in flowcharts.
Decision and merge nodes
are a useful analysis tool and can be used for process reengineering
Activity Diagrams
UML symbol for an actor
Stickman
UML symbol for use case
Oblong
You use this relationship when a chunk of behavior is similar across more than one use case, and you don’t want to keep copying the description of that behavior
«include»
to depict parallel behavior
Fork
are the things that you do or that happen in an activity diagram
Action nodes
represents whoever or whatever (person, machine, or other) interacts with the system
Actor
is a directed arrow. It also referred to as just a flow or an edge.
Control flow
to show relationship in use cases
arrows and lines
are created as a finite set of serial actions or a combination of serial and parallel actions.
Activity Diagram
used to converge parallel behavior back into a single flow
Join
are also very helpful for writing acceptance test cases.
Use Case
help users to describe visually the sequence of actions that leads you through the completion of a task.
Activity Diagram
acts as a sentinel that requires a test be passed before flow continues.
Guard Condition
use the same symbol and convey conditional branching and merging.
Decision and merge nodes
used during requirements analysis as a graphical means of representing the functional requirements of the system.
Use Case