0% found this document useful (0 votes)
23 views12 pages

Module 3 - Use Case Diagrams

The document explains the importance of creating a use-case model for effective communication between customers and system developers regarding system functions. It defines use-case diagrams, actors, and relationships, including communication, uses, and extends relationships, while providing examples relevant to a Library Management System. The use-case model serves as a visual contract that outlines the system's intended functions and interactions with external entities.

Uploaded by

vallerutejasree
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
23 views12 pages

Module 3 - Use Case Diagrams

The document explains the importance of creating a use-case model for effective communication between customers and system developers regarding system functions. It defines use-case diagrams, actors, and relationships, including communication, uses, and extends relationships, while providing examples relevant to a Library Management System. The use-case model serves as a visual contract that outlines the system's intended functions and interactions with external entities.

Uploaded by

vallerutejasree
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Use-Case Diagram

OOAD
Thilagavathi M, AP(Sr.), SCORE

1
Why Create a Use-Case Model?

 A use-case model allows the customer and


system developer to communicate WHAT
the system should do, in a language
understandable to the customer.
 Consider the use-case model as the visual
contract between customer and developer.

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 2


What Is a Use-Case Model?

 A use-case model is representation of the


system’s intended functions and its
environment.
 It is created in the Use-Case View and
can include the following
Use-case diagrams
Use-case flow of events
Supplemental information

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 3


What Is a Use-Case Diagram?
 A use-case diagram is an illustration that
shows the relationships among use cases
and actors and among related use cases.

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 4


Actors

 An actor is someone or something outside


the system that interacts with the system.
Example: Human user, external hardware or
another system.
 In the UML, an actor is represented by a
“stickman.”

<<actor>> <<actor>>
Customer Customer

Customer

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 5


Use Cases
 A use case is a sequence of actions
performed by the system that yields a
measurable value for an actor.
 In the UML, a use case is represented
by an oval.

Use Case

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 6


Relationships

A relationship illustrates a semantic


connection among model elements.

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 7


Communication Relationship
May exist between an actor and a use case and
between use cases.
Also called association relationship.
Is often referred to as a “communicate” relationship
since it refers to communication between actor and use
case.
Can be navigable in one or both directions. The
navigation direction represents who is initiating the
communication.

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 8


Communication Relationship
An association with an arrowhead denotes
communication in one direction and is called a
unidirectional association. The end with the arrow
indicates who or what is receiving the communication.

An association without an arrowhead denotes


communication in both directions and is called a bi-
directional association.

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 9


Uses Relationship
The uses relationship is used when use cases
have some sub flows in common.
In the UML, a uses relationship between use
cases is shown by a generalization arrow from
the use case.

<<uses>>

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 10


Extends Relationship
The extends relationship is used when you
have one use case that is similar to another use
case but does a bit more. In essence, it is like a
subclass.
In the UML, the extends relationship between
use cases is shown by a generalization arrow
from the use case.

<<extends>>

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 11


Example: Library Management System

ISWE207L: OOAD Thilagavathi M, AP(Sr.), SCORE 12

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy