ASSIGNMENT # 1

MUHAMMAD MUNEEB
17-ARID-1655
BSIT 5A
SOFTWARE ENGINEERING II
Case Studies (Use case Diagrams, Use case Description & Typical Course of Events):
Case Study : 1
Our auditorium is used for different types of events. Some of the events are one-time events, such as
basketball games. Other events consist of a number of shows , such as plays or concerts. The event planner
can change the floor plan for each event. Some events use the floor for seating( like concerts ) and others
do not (like basketball games). All the show seating charts for the same event should be based on same
floor plan. The event planner schedules events and shows. Once an event is negotiated, the event planner
decides on the floor plan and schedules the individual shows for the event. Once the shows are scheduled
the event planner prices the shows. Pricing is done using a pricing plan. A pricing plan consists of a set of
price tiers. Each price tier contains prices for one or more prices: adult, senior, student, and child. The
event planner assigns each price tier to a group of seats in a show, one tier per seat. The event planner
may also add one or more discounts to the show to improve sales. Customers can purchase seats online.
Once they provide us with their mailing address they can look up the shows and select the seats they want
to reserve. Customers may pay only by credit card payments. If they want refunds, we will credit the card
used to purchase the ticket.

Identify Actors:
 Customers
 Event planner

Use Cases:
 Schedule Events
 Change Floor Plan
 Event Pricing
 Assigns Seats
 Purchase Seats
 Provide Mailing Address
 Look Up Shows
 Reserve Seats
 Payment
Use Case Diagram:

One Time Events Other Events

<<include>> <<include>>

SCHEDULE EVENTS

Pricing Plan CHANGE FLOOR PLAN

<<extend>>

EVENT PRICING

<<extend>>

Add Discounts ASSIGN SEATS

EVENT PLANNER

PURCHASE SEATS

PROVIDE MAILING
ADDRESS

LOOK UP SHOWS
CUSTOMER

RESERVE SEATS Credit Cards

<<include>>

PAYMENT
Use Case Description:
Schedule Events

Use Case Schedule Events

Actors Event Planner
Type Primary
Description Auditorium is used for one-time events or other
events. The event planner schedules events and
shows. Once an event is negotiated, the event
planner decides on the floor plan and schedules
the individual shows for the event.

Change Floor Plan

Use Case Change Floor Plan
Actors Event Planner
Type Primary
Description The event planner can change the floor plan for
each event. Some events use the floor for seating(
like concerts) and others do not (like basketball
games). All the show seating charts for the same
event should be based on same floor plan.

Event Pricing

Use Case Event Pricing

Actors Event Planner
Type Primary
Description The event planner prices the shows after
scheduling. Pricing is done using a pricing plan. A
pricing plan consists of a set of price tiers. Each
price tier contains prices for one or more prices:
adult, senior, student, and child. The event
planner may also add one or more discounts to the
show to improve sales.

Assign Seats

Use Case Assign Seats

Actors Event Planner
Type Primary
Description The event planner assigns each price tier to a
group of seats in a show, one tier per seat.
Purchase Seats

Use Case Purchase Seats

Actors Customer
Type Primary
Description Through this use case customers can purchase
seats online.

Provide Mailing Address

Use Case Provide Mailing Address

Actors Customer
Type Primary
Description Customer provide his/her mailing address. After
which he/she can interact with the system easily.

Look Up Shows

Use Case Look Up Shows

Actors Customer
Type Primary
Description Once they provide us with their mailing address
they can look up the shows easily.(See Shows
status)

Reserve Seats

Use Case Reserve Seats

Actors Customer
Type Primary
Description Customer can select the seats they want to
reserve easily after providing his/her mailing
address.

Payment

Use Case Payment

Actors Customer
Type Primary
Description Through this use case customer can make
payment. Customers may pay only by credit card
payments. If they want refunds, we will credit the
card used to purchase the ticket.
Typical Course of Events
Schedule Events
Event Planner
1. This use case begins when the event
planner sets the schedule that match
with the floor plan and events.
Change Floor Plan
Event Planner
1. This use case begins when the event
planner can change the floor plan for
each event. Some events use the floor for
seating( like concerts ) and others do not
(like basketball games). All the show
seating charts for the same event should
be based on same floor plan.
Event Pricing
Event Planner
1. The event planner prices the shows.
Pricing is done using a pricing plan. The
event planner assigns each price tier to a
group of seats in a show, one tier per
seat.
3. The event planner may also add one or
more discounts to the show to improve
sales.
Assign Seats
Event Planner
1. The event planner assigns each price tier
to a group of seats in a show, one tier per
seat.
SYSTEM
2. The system sets the schedule that
fulfill the need of event planner.
SYSTEM
2. The system take instructions from the
event planner and change the floor
plan for the event planner.
SYSTEM
2. System takes input for each price tier
that contains prices for one or more
prices: adult, senior, student, and child.
4. The system adds this discount to the
pricing plan that is set by the event
planner.
SYSTEM
2. The system accepts the order of event
planner and assigns each price tier to a
group of show.
Purchase Seats

Customer SYSTEM
1. Customers can purchase seats online. 2. The system can book the seats for the
customer.

Provide Mailing Address

Customer
1. Once the customers provide their mailing
address.
3. Customers can easily interact with the
system. This mailing address acts like a
login system.
SYSTEM
2. The system take the input and store it.
4. The system verifies the mailing
address to enter the customer in to the
system.

Look Up Shows

Customer SYSTEM
1. After providing the mailing address 2. The system provides a display of
the customer can easily looks up the shows to the customer.
shows.

Reserve Seats

Customer SYSTEM
1. Customer can select the seats they want 2. The system book the seats that the
to reserve. customer wants.

Payment

Customer
1. This use case begins when the
customer inputs the credit card in the
system.
3. If the customer wants refund.
5. The customer take the ticket.
SYSTEM
2. The system verifies the credit card.
a : If the card is being verified then the
payment is deducted.
b : Else the card is being ejected from the
system. And system wants the correct input.
4. The system credit the card used to
purchase the ticket.
Case Study : 2
Creating a Dictionary system:

The use case diagram for the dictionary system is created. It provides an external view of a dictionary
system. In this system, the user first login to the system with user name and password. user name of every
user is unique. The user enters the word to the system for finding meaning of the word. The system
searches the meaning for the given word. If the word is available on the database then the system retrieve
and display the meaning for the word otherwise it show the message box that contains please enter
correct word.

Identify Actor:
1. User
2. Database.
Use cases:
1. Login
2. Enter the word
3. Search
4. Retrieve

Use case diagram:

LOGIN

ENTER WORD

USER SEARCH DATABASE SYSTEM

RETRIEVE
USE CASE DESCRIPTION
LOGIN:

Use Case Login

Actors User, Database System
Type Primary
Description User enters his/her name and password that
must be unique. After which the database system
can verify the user and allows the user to do
other activities otherwise user is not allowed to
do anything.

ENTER WORD:

Use Case Enter the Word

Actors User, Database System
Type Primary
Description User enters the word to find its meaning, If the
meaning of the word is available/found in
database system then this word/meaning
displayed to the user. Else the msg of word not
found is displayed to the user.

SEARCH:

Use Case Search

Actors User, Database System
Type Primary
Description The system searches the meaning for the word
given by the user in database system. If the
meaning of the word is available/found in
database system then this word/meaning
displayed to the user. Else the msg of word not
found is displayed to the user.

RETRIEVE:

Use Case Retrieve

Actors User, Database System
Type Primary
Description If the meaning of the word is available/found in
database system then this word/meaning
displayed to the user.
Typical Course of Events
LOGIN

USER
3. This use case begins when the user
enters his/her name and password.
SYSTEM
4. The system verifies the user.
a: If the user is verified the user
can do anything.
b: Else user is not allowed to do
anything.

ENTER WORD

USER SYSTEM
1. This use case begins when the user 2. The system check for the given word
enters the word to find its meaning. in database system to find its meaning.

SEARCH

USER
2. The user see the meaning on the
system or the instruction to enter
correct word.
SYSTEM
1. The system check in database system
to find the meaning:
a: If the word is found then
meaning is displayed on the system.
b: Else a message is displayed that
the please enter correct word.

RETRIEVE

USER SYSTEM
2. The user see the meaning on the 1. The system found the meaning of
system. given word in database system.