We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 4
Use Case Diagram(core components)
Actors:
Arole that a user plays with respect to the system,including human
users and other systems. e.g.,inanimate physical objects (e.g. robot); an
external system that needs some information from the current system.
<
Bd
Use case:
A set of scenarios that describing an interaction between a user and
a system,
C >Use Case Diagram (core components)
+ Ause case is a single unit of meaningful work. E.g. login, register, place
an order, etc.
* Each Use Case has a description which describes the functionality that
will be built in the proposed system.
E.g. for use case (‘order title” , a brief description: This use case
receives orders from employee or supervisor, then return the ordered title.
System boundary:
A rectangle diagram representing the boundary between the actors and
the system.Use Case Diagram(core relationship)
As! rt ion:
mmunication between an actor and a use case; represented b
a solid line.
Generalization:
Relationship between one general use case and one specific us
case.
Represented by a line with a triangular arrow head toward th
parent use case, the more general modeling element.Use Case Diagrams
Boundary, Use Case
Os Larry ten 9
cG> ee
= CL
eer
‘Supervisor
+ A generalized description of how a system will be used
* Provides an overview of the intended functionality of the system