Online Bus Ticket Reservation System INTERIM II
Online Bus Ticket Reservation System INTERIM II
RESERVATION SYSTEM.
INTERIM REPORT II
By: Guide: 1
Viswas B Kurian Liji Thomas
Vaishnav B Lal
SYSTEM STUDY REPORT
Objectives
To provide an efficient and user-friendly
platform for booking bus tickets.
To streamline the process of managing bus
schedules, routes, and bookings.
To ensure secure and reliable payment
processing.
To offer a comprehensive admin panel for
monitoring and managing system operations.
2
SYSTEM STUDY REPORT
System Overview
The system comprises multiple modules, each designed to
handle specific tasks related to bus ticket booking and
management:
User Management: Handles user registration, login, and
profile management.
Bus Management: Allows admin and bus operators to
manage bus details and schedules.
Booking Management: Facilitates the booking of bus
tickets by users.
3
DATA FLOW DIAGRAMS
(DFD)
The DFDs provide a visual representation of the data flow within
the system.
1. Levels OF DFD 1. Context Diagram: Depicts the system's
interaction with external entities such as passengers, admin,
bus owners, and payment gateways.
2. Level 1 DFD: Breaks down the system into major processes
and shows the data flow between these processes.
3. Level 2 DFD: Further decomposition into more detailed
processes Provides a more detailed breakdown of the processes
identified in the Level 1 DFD.
4
DATA FLOW DIAGRAMS
(DFD)LEVEL 0 DFD OR CONTEXT DIAGRAM
5
DATA FLOW DIAGRAMS
(DFD) LEVEL 1 DFD
6
DATA FLOW DIAGRAMS
(DFD)LEVEL 2 DFD LOGIN PROCESS (1.0)
7
DATA FLOW DIAGRAMS
(DFD)
LEVEL 2 DFD BUS MANAGEMENT PROCESS (2.0)
8
DATA FLOW DIAGRAMS
(DFD)
LEVEL 2 DFD BOOKING MANAGEMENT PROCESS (3.0)
9
ENTITY-RELATIONSHIP (ER)
DIAGRAM
An Entity Relationship Diagram (ERD) is a graphical representation that
illustrates the relationships between entities in a database.
ERDs help in designing the database structure by clearly showing the
entities, their attributes, and the relationships between them, ensuring a
well-organized and efficient database
Components of an ERD
• Entities: Objects or concepts that have data stored about them.
Represented as Rectangles.
• Attributes: Properties or characteristics of entities. Represented as Ovals
connected to their respective entities.
• Relationships: Associations between entities. Represented as Diamonds or
lines connecting entities.
10
ENTITY-RELATIONSHIP (ER)
DIAGRAM
11
DATABASE DESIGN:
Table Design:
User table
Stores information about passengers, including their personal
details and login credentials.
12
DATABASE DESIGN:
Admin table
Holds data about system administrators who manage the
platform and its functionalities.
13
DATABASE DESIGN:
Bus owner table
Stores information about bus owners, including their personal
details and login credentials.
14
DATABASE DESIGN:
Bus table
Contains details about each bus, such as its number, capacity,
type, and owner.
15
DATABASE DESIGN:
Route table
Keeps track of the routes, including source and destination
locations and the distance between them.
16
DATABASE DESIGN:
Schedule table
Manages bus schedules, detailing departure and arrival times
and associated routes.
17
DATABASE DESIGN:
Booking table
Records ticket bookings, including the user, schedule, seat
number, and booking status.
18
DATABASE DESIGN:
Payment table
Stores information about payments made for bookings,
including the amount, date, and payment method.
19
DATABASE DESIGN:
Cancellation table
Tracks cancellations of bookings and includes details about the
refund amount and cancellation date
20
DATABASE DESIGN:
Level of Normalization:
1NF: Each column contains atomic values.
2NF: The primary key is a single column so no partial
dependencies.
3NF: All columns are directly dependent on the
primary key.
22
LOGIN AND REGISTRATION
PAGES
23
LOGIN AND REGISTRATION
PAGES
24
THANK YOU
25