Scribd
Upload
6 views9 pages

Lab 03

The document provides an overview of use case diagrams, detailing their purpose, benefits, and key elements such as actors, use cases, and system boundaries. It explains various relationships within use cases, including association, include, extend, and generalization, and outlines the components of a use case specification document. Additionally, it includes multiple-choice questions to assess understanding and examples of systems for practical application.

Uploaded by

Mariam Nasr
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
6 views9 pages

Lab 03

The document provides an overview of use case diagrams, detailing their purpose, benefits, and key elements such as actors, use cases, and system boundaries. It explains various relationships within use cases, including association, include, extend, and generalization, and outlines the components of a use case specification document. Additionally, it includes multiple-choice questions to assess understanding and examples of systems for practical application.

Uploaded by

Mariam Nasr
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/ 9

System Analysis & Design

Lab 03
Instructor: Dr.Nesreen El saber
TA : Eng.Saja Saadoun , Eng.Pansy Youssef
2

What Is a Use Case?


It represents how a system interacts with its environment by illustrating the
activities that are performed by the users of the system and the system’s
responses .
A type of UML (Unified Modeling Language) diagram that visually represents
the interactions between users (actors) and a system

Benefits of a Use Case Diagram:


1.​ Clear System Understanding
2.​ User-Centric Approach
3.​ Improves Communication
3

Elements of a Use Case Diagram:

●​ Actor
1.​ Someone interacts with a use case .
2.​ Named by a noun.

●​ Use Case
1.​ System function .
2.​ Named by verb + Noun.
3.​ Each Actor must be linked to a use case .

●​ System Boundary
1.​ Defines the scope of the system.
2.​ Everything inside the boundary is part of the system.
3.​ Everything outside the boundary interacts with the
system .

●​ Communication Link
1.​ The connection between an actor and a use case by a solid link.
4

Use Case Relationships :

●​ Association: A link between an


actor and a use case.

●​ Include : Adds additional


functionality
○​ The included use case is a
part of the main use case
and cannot exist
independently.
○​ Used when a use case
always requires another
use case.

●​ Extend: Shows optional


functionality or system
behavior
○​ The extended use case is
optional and adds additional
functionality.
○​ Used when a use case
sometimes triggers another
use case under certain conditions.

●​ Generalization: Represents inheritance between


actors or use cases.
○​ A child use case inherits the behavior and
meaning of the parent use case.
○​ One actor can inherit the role of the other
actor.
5

Use Case Specification Document :


It provides a detailed textual description of a specific use case in a structured
format

Purpose of Table in Use Case Modeling:


1.​ Provides a detailed explanation beyond just the use case diagram.
2.​ Helps developers, testers, and business analysts understand the exact
flow of the use case.
3.​ Identifies possible errors, alternatives, and dependencies.
6

Table Components:
1.​ Use Case Name: A clear name that describes the purpose of the use case.

2.​ Actor(s): The users or external systems interacting with the use case .

3.​ Description: A brief explanation of what the use case does, describing the
goal of the use case.

4.​ Trigger: What causes the use case to start.

5.​ Type: Indicates the nature of the use case, such as:

○​ External (User-initiated)
○​ Internal (Triggered by the system)
○​ Temporal (Triggered by time)

6.​ Preconditions: Conditions that must be met before the use case can be
executed.

7.​ Normal Course: The step-by-step sequence of interactions between the


actor(s) and the system , the most common and expected flow without
errors.

8.​ Information for Steps: Extra details about key steps in the process , It helps
clarify what data is involved, what actions are taken, and how different
components interact during the process.
7

Table Components Cont.. :


9.​ Alternative Courses: Variations in the process (e.g., if something changes or
different paths exist).

10.​Postconditions: The state of the system after the use case is completed.

11.​Summary (Inputs/Outputs): Data that is received, processed, or generated


by the use case

Field Details

Inputs Data entered by the user

Outputs System generated data

Destination Where the output is sent


8

Multiple Choice Questions :

1.​ What is the primary purpose of a Use Case Diagram?


A) To represent the interactions between users and a system
B) To define the internal structure of a system
C) To design the database schema
D) To describe the coding logic of an application

2.​ In a Use Case Diagram, what does an actor represent?


A) A random collection of unrelated components
B) A software program
C) A set of interrelated components working towards a common goal
d) A collection of hardware devices

3.​ Which relationship is used when one use case is always required as part of
another?
A) Extend
B) Association
C) Generalization
D) Include

4.​ What does the "extend" relationship indicate in a Use Case Diagram?
A) A use case that can optionally occur under certain conditions
B) A mandatory sub-use case
C) A replacement of the original use case
D) A direct interaction between an actor and a system

5.​ In a Use Case Diagram, what does the "generalization" relationship indicate?
A) The system interacts with a database
B) One actor inherits the behaviors of another actor
C) One use case extends another use case
D) One use case includes another use case
9

Create a use case diagram with its table using a paper them implement
it:
Lucidchart link : https://app.diagrams.net/

1.​ Student Hostel Management System :


●​ Apply for Hostel Accommodation
●​ Pay Hostel Fees
●​ Request Maintenance Service
●​ Check Room Availability
●​ Report an Issue

2.​ University Event Management System


●​ Register for an Event
●​ Cancel Event Registration
●​ View Event Schedule
●​ Give Event Feedback
●​ Receive Event Notifications

3.​ University Transportation System


●​ Book Bus Seat
●​ Cancel Booking
●​ Track Bus Location
●​ View Bus Schedule
●​ Pay Transport Fees

4.​ Online Shopping System


●​ Browse Products
●​ Add to Cart
●​ Place Order
●​ Make Payment
●​ Manage Inventory

You might also like