Scribd
Upload
379 views5 pages

The Image Shows An Entity-Relationship Diagram (ERD) For A Parking Management System

B

Uploaded by

panda73665
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
379 views5 pages

The Image Shows An Entity-Relationship Diagram (ERD) For A Parking Management System

B

Uploaded by

panda73665
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/ 5

The image shows an Entity-

Relationship Diagram (ERD) for a parking


management system.

Let's break down the relationships between the tables:

Entities (Tables):

Customer Details:
Stores information about customers, including
their ID, name, address, and mobile number.
Vehicle Details:
Stores information about vehicles, including their registration number, make, model,
type, and the customer they belong to.

Parking Slot:
Stores information about parking slots, including their ID, area name, total slots,
remaining slots, and the vehicle parked in them.

Receipt:
Stores information about receipts, including their ID, the customer they belong to, the
parking slot they are associated with, the transaction ID, and the in and exit times.

Transaction Details:
Stores information about transactions, including their ID, the customer they belong to,
the transaction status, and the amount paid.

Relationships:
Customer Details - Owns - Vehicle Details:
A one-to-many relationship, where a customer can own multiple vehicles.

Vehicle Details - Parked - Parking Slot:


A one-to-one relationship, where a vehicle can be parked in only one parking slot at a
time.

Customer Details - Receives - Receipt:


A one-to-many relationship, where a customer can receive multiple receipts.

Receipt - Generates - Transaction Details:


A one-to-one relationship, where each receipt generates a single transaction.

Customer Details - Pays - Transaction Details:


A one-to-many relationship, where a customer can make multiple payments.

Key Attributes:

Primary Keys:
Unique identifiers for each entity (e.g., Customer ID, Vehicle Reg. No, Parking Slot ID,
Receipt ID, Transaction ID).

Foreign Keys:
Attributes used to establish relationships between tables (e.g., Customer ID in Vehicle
Details, Parking Slot ID in Receipt, etc.).

In summary:

Customers can own multiple vehicles.

Vehicles can be parked in specific parking slots.

Customers receive receipts for their parking sessions.

Each receipt generates a transaction.

Customers make payments for their transactions.


Based on the Entity-Relationship Diagram (ERD) provided, here's the
structure of the tables:

Customer Details Table:


Column Name Data Type

Customer ID INT (Primary Key)

Customer Name VARCHAR

Address VARCHAR

Mobile No VARCHAR

Vehicle Details Table:


Column Name Data Type
Vehicle Reg. No VARCHAR (Primary Key)

Vehicle Make VARCHAR

Vehicle Model VARCHAR

Vehicle Type VARCHAR

Customer ID INT (Foreign Key referencing Customer Details)

Parking Area Table:


Column Name Data Type
Parking Slot ID INT (Primary Key)

Area Name VARCHAR

Total Slot INT

Remaining Slot INT

Vehicle Reg. No VARCHAR (Foreign Key referencing Vehicle Details)


Receipt Table:
Column Name Data Type
Receipt ID INT (Primary Key)

Customer ID INT (Foreign Key referencing Customer Details)

Parking Slot ID INT (Foreign Key referencing Parking Area)

Transaction ID INT (Foreign Key referencing Transaction Details)

In Time DATETIME

Exit Time DATETIME

Transaction Details Table:


Column Name Data Type
Transaction ID INT (Primary Key)

Customer ID INT (Foreign Key referencing Customer Details)

Amount DECIMAL

Transaction Status VARCHAR

You might also like