OOAD

ASSIGNMENT-1

BATCH-21
ONLINE TICKET RESERVATION

Done by

Name: M.SRI SANTH

Reg No: 921721108052
Name: M.SABARIVARSHAN
Reg No.: 921721108039
Name: P.SANJAY
Reg No:921721108303
Use Case Diagram:
A use case diagram is a graphical representation that shows the
interactions between different actors and the system itself. It
helps in understanding the functionalities and constraints of the
system. Below is a textual representation of a use case diagram
for an Online Ticket Reservation System.
Actors:
1. Customer: The primary user who wants to book tickets.
2. Admin: Manages the system, updates show timings, and
handles other administrative tasks.
3. Payment Gateway: External system for handling
payments.
4. Database: Stores all the information about shows, tickets,
and users.
Use Cases:
1. Search Shows: Customer can search for shows by date,
time, or venue.
2. Select Seats: Customer can select the seats they want to
book.
3. Make Payment: Customer makes a payment through the
Payment Gateway.
4. View Ticket: Customer can view the booked ticket.
5. Cancel Ticket: Customer can cancel the booked ticket.
6. Update Show: Admin can update the details of a show.
7. View Reports: Admin can view sales and booking reports.
8. Authenticate: Admin has to log in to access admin
functionalities.

Relationships:
• Customer -> Search Shows
• Customer -> Select Seats
 • Customer -> Make Payment -> Payment Gateway
• Customer -> View Ticket
• Customer -> Cancel Ticket
• Admin -> Authenticate
• Admin -> Update Show
• Admin -> View Reports
• Database -> Stores data for all use cases

V
Class Diagram:
Certainly! A class diagram for an online ticket reservation
system would typically consist of several classes, each
representing different entities in the system, along with their
attributes, methods, and relationships.
Classes

1. User
oAttributes: userID, username, password,
email
o Methods: login(), logout(), register(),

updateProfile()
2. Ticket
o Attributes: ticketID, seatNumber, price,

status
o Methods: book(), cancel(), update()

3. Event
o Attributes: eventID, eventName, location,

time
o Methods: createEvent(), updateEvent(),

deleteEvent()
4. Payment
o Attributes: paymentID, amount,

paymentMethod
o Methods: makePayment(), refund()

5. Seat
o Attributes: seatID, seatType, availability

o Methods: reserve(), release()

6. Venue
o Attributes: venueID, name, location

o Methods: addVenue(), updateVenue()

Relationships
1. User - Ticket: One-to-many
o A user can book multiple tickets, but each ticket is

booked by one user.

2. Ticket - Event: Many-to-one
o Multiple tickets can be associated with a single

event.
3. Event - Venue: Many-to-one
o Multiple events can occur at a single venue.

4. Ticket - Payment: One-to-one

o Each ticket booking has one payment associated

with it.
5. Event - Seat: One-to-many
o An event has multiple seats, but each seat is

associated with one event.

6. Seat - Ticket: One-to-one
o Each seat is associated with one ticket.