Scribd
Upload
34 views10 pages

Cab Management Syatem

Uploaded by

Shawayar Fatma
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
34 views10 pages

Cab Management Syatem

Uploaded by

Shawayar Fatma
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/ 10

PROJECT TITLE: Cab Management

System

STUDENT NAME: Shawayar Fatma


STUDENT BITS ID: 2022MT93760
COURSE ID: SEZG518

1
Version Number Date Author/Owner Description of Change
1 14/08/2023 Shawayar Fatma Requirement Speci cation

2 30/08/2023 Shawayar Fatma Conceptual Design

3 14/09/2023 Shawayar Fatma Relational DB Schema

4 15/09/2023 Shawayar Fatma Normalisation to 3NF

5 16/09/2023 Shawayar Fatma Data Dictionary

2
fi
I. REQUIREMENT SPECIFICATION:

a. Problem Statement & Requirements De nition


We have decided to create a database system that can help book and manage
cabs. The current system is manual which is time consuming and ine cient. This
is prone to error which further leads to customer dissatisfaction.

Here the goal is to create a database that can be used in the system to automate
cab rental and reservation. They can go online and reserve any kind of cab they
want from the inventory of available cabs. It will also keep track of all cab
reservations and returns. This project aims to develop a database for cab
management agencies that allows customers to book their taxi's online from the
comfort of their own home or o ce. The platform will o er an interface where the
cab company can manage the content, and access all bookings and customer
information. The database maintains the information about the customer details,
vehicle details, insurance details, driver details, booking details and transaction
details of the customer. The database will enable storing and retrieving the
required details.

The customer can login/sign up and after successful authentication he/she can
book a desired cab after entering some basic information like current location,
destination location and type of vehicle required. The customer will have the
option to pay online while booking the cab or pay later in cash.

At high level, this system should be able to capture following information:-


CUSTOMER DETAILS- stores all the details of both new and existing customers.
VEHICLE DETAILS- stores all the details of the vehicles used along with their
known defects, mileage, cost/km.
OWNER DETAILS- stores all the details of the owners of the vehicles, vehicles
can be company owned/leased or driver owned.
DRIVER DETAILS- stores all the details of the drivers along with their availability.
BOOKING DETAILS- stores all the booking details of the cab booked.
TRANSACTION DETAILS- stores all the details of the transactions made by the
customers.
CANCELLATION DETAILS- stored all the details of the cancellation done by
customers or drivers.

b. Project Features Identi ed

3
fi
ffi
fi
ff
ffi
Feature ID Feature Name Description
T01 Login/Sign Up On successful
authentication view
dashboard.
T02 Search and Booking Allow customers to search
for cabs based on the info
provided and book.
T03 Cancellation Allow customers/drivers to
cancel booking.
T04 Cab Management Allow sta to add and
update driver’s and
vehicle’s information

c. Software and Hardware Details


Platform Web Browser
Frontend/console React.js
Backend/server Node.js & Express.js
Database MySQL
Programming Language Frontend HTML, CSS & Javascript
Programming Language Backend Javascript

d. Project Plan

4
ff
Google Drive Link for Cab Management System

II. CONCEPTUAL DESIGN:

Entity Relationship Model


ER-Diagram for Cab Management System

5
III. LOGICAL DESIGN:

a. Relational Database Schema

Functional Dependencies :-
(i) User ID -> {First Name, Last Name, Default Address, DOB, Primary No., Alternate No.}
(ii) Transaction ID -> {Amount, Phone No., Payment Date, Payment Mode, Status, User ID,
Booking ID}

6
(iii) Booking ID -> {Estimated Fare, Distance, Stops, Pickup Location, Drop Location, Start
Time, End Time, User ID, Driver ID}
(iv) Driver ID -> {Name, Email, Ratings, Status, Address, Phone No., License No., License
Expiry Date, Vehicle ID}
(v) License No. -> {License Expiry Date}
(vi) Vehicle ID -> {Reg. No., Seating Capacity, Colour, Status, Model, Owner ID}
(vii)Reg. No. -> {Seating Capacity, Colour, Model}
(viii)Owner ID -> {Name, Ownership Type, Leased, Status, Tenure, Start Date, EndDate}
(ix) Cancellation ID -> {Cancelled By, Reason, Charges Applicable, Amount, To Be Paid By,
Booking ID}

b. Normalisation

(i) Table Name: Customer


State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(ii) Table Name: Transaction_Details


State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(iii)Table Name: Booking


State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(iv)Table Name: Driver


State: 2NF
Reason: - No multivalued attributes
- No partial dependencies
- Here Driver ID->{License No.} & License No->{License Expiry Date},
hence {License Expiry Date} transitively depend on Driver ID.

To normalise the table to 3NF, the Driver table is decomposed as follows:-

7
Now,
State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(v) Table Name: Vehicle


State: 2NF
Reason: - No multivalued attributes
- No partial dependencies
- Here Vehicle ID->{Reg. No} & Reg. No->{Seating Capacity, Colour, Model},
hence {Seating Capacity, Colour, Model} transitively depend on Vehicle ID.

To normalise the table to 3NF, the Vehicle table is decomposed as follows:-

Now,
State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(vi)Table Name: Owner


State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(vii)Table Name: Vehicle_Type


State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

(viii)Table Name: Cancellation


State: 3NF
Reason: - No multivalued attributes
- No partial dependencies
- No transitive dependency

8
c. Data Dictionary

9
10

You might also like