Scribd
Upload
22 views

Sowftware Eng - Use Case

Uploaded by

mohamadbatsh64
Copyright
© © All Rights Reserved
Available Formats
Download as PPSX, PDF, TXT or read online on Scribd
22 views

Sowftware Eng - Use Case

Uploaded by

mohamadbatsh64
Copyright
© © All Rights Reserved
Available Formats
Download as PPSX, PDF, TXT or read online on Scribd
You are on page 1/ 29

Software Engineering 1

Use Case Diagram

Eng Sham Dawwa


Table of contents
Introduction Rules
What is use case diagram 01 04 Use Case Diagram Rules

Uses Specification
Why we darw use case 02 05 Use case diagram
diagram specification

Symbols Examples
Use Case Diagram Symbols 03 06 Use Case diagrams
examples.
Introduction
01 What is use case diagram
What is Use case diagram?

A use case diagram is a type of diagram in the Unified Modeling Language (UML) that
illustrates how actors (users, organizations, or external systems) interact with a system.
Uses
02 Why we draw use case diagram
Why we draw use case diagram
: • Use case diagrams help summarize the details of a
01 system’s users and their interactions with the system.

They focus on high-level relationships between use cases,


02 actors, and the system
Symbols
03 Use Case Diagram Symbols
Use Case Diagram Symbols

Represent users who interact with the system. Actors can be people, organizations, or external
systems.
Use Case Diagram Symbols

Represent specific functionalities or scenarios that the system provides to its users

Use case name has to be short and clear..


Use Case Diagram Symbols

A box around the use cases defines the system’s scope.


Use Case Diagram Symbols
Relations
Relationship Types
• Association
01
This relationship is straightforward and present in every use case
diagram.

Key points:

• An actor must be associated with at least one use case.

• An actor can be associated with multiple use cases.

• Multiple actors can be associated with a single use case.


Relationship Types
• Extend
02 Extend Relationship Between Two Use Cases:

• The “extend” relationship adds functionality to the system by


extending a base use case.

• Key points:

• The extending use case depends on the extended (base) use


case.

• The extending use case is usually optional and triggered


conditionally.

• The extended (base) use case must be meaningful on its own.


Relationship Types
• Include
03
Include Relationship Between Two Use Cases:

• The included use case represents a common functionality that can be


reused across multiple use cases
• .
• Key points:

• The including use case depends on the behavior of

the included use case.

• Promotes modular and reusable design.

• Denoted by a dashed arrow pointing from the including use

case to the included use case.


Relationship Types
• Generalization of a Actor
04
• Involves one actor inheriting the role of another actor.

• The descendant actor inherits all the use cases of the ancestor.

• The descendant actor may have additional use cases specific to its

role.

• Generalization of Use case


• Similar to actor generalization but applies to use cases.
05
• One use case can inherit the behavior of another use case.
Rules
04 Use Case Diagram Rules
What is use case diagram
drawing rules?
1. Completeness: Ensure that your use case diagram is complete. Represent all relevant interactions
with the use case.

• If there are too many use cases or actors, focus on including the essential ones.

2. Naming Standards : Use descriptive names for actors and use cases.

• Clear names help stakeholders understand the system’s functionality.

3. Actor Representation: An actor in a use case diagram can be a person, organization, or external

system.
• Represent actors as skeleton-like figures.
What is use case diagram
drawing rules?
• 4. Relationships: Use arrows to indicate relationships between actors and use cases.

• Understand the different types of relationships: association, generalization, include, and extend.

• 5. System Boundary: Use a rectangle to define the scope of the use case.

• The rectangle encloses the actors and use cases relevant to the system.

6. Use Case Representation: A use case represents a specific function or action within the system.
• Draw use cases as ovals and name them accordingly.
Specifications
05 Use case diagram specification
What is use case specification

A use case specification is a detailed document that accompanies a use case in

software development. It provides a textual description of the steps needed to carry

out the normal flow of the use case, as well as exceptional flows
Specification
Content

 Use Case ID.


 Use Case Name
 Actor (Initiator)
 Description
 Precondition
 Post Condition
 Flow of events
 Alternative flow
 Exceptions
 Special requirement
Flow of events
• Describes the main path of execution for the use case.
• Includes a logical sequence of steps.
• Explains what functionality is provided when the use case is executed.

Alternative Flow
• Covers alternative scenarios or error conditions.
• Describes how the system behaves when things go wrong.

Exceptions
• Any errors or problems may happen in the use case
Actor
• Identifies the roles interacting with the system.

Pre condition
• Lists any assumptions or conditions that must be true before the use case starts.

Post condition
• Describes the state of the system after the use case completes.
Examples
06 Use Case diagrams examples.
Thank You for Listening

You might also like