Railway Enquiry System ER Diagram

This ER (Entity Relationship) Diagram represents the model of Railway Enquiry System Entity. The entity-relationship diagram of Railway Enquiry System shows all the visual instrument of database tables and the relations between Timetable, Stations, Trains, Routes etc. It used structure data and to define the relationships between structured data groups of Railway Enquiry System functionalities. The main entities of the Railway Enquiry System are Trains, Timetable, Fare, Stations, Seats Availability and Routes.

Railway Enquiry System entities and their attributes :

• Trains Entity : Attributes of Trains are train_id, train_name, train_number, train_seat_number, train_ticket, train_type, train_description
• Timetable Entity : Attributes of Timetable are timetable_id, timetable_name, timetable_type, timetable_description timetable_t
• Fare Entity : Attributes of Fare are fare_id, fare_ticket_id, fare_title, fare_type, fare_description
• Stations Entity : Attributes of Stations are station_id, station_name, station_type, station_description
• Seats Availability Entity : Attributes of Seats Availability are seat_id, seat_train_id, seat_customer_id, seat_number, seat_type, seat_description
• Routes Entity : Attributes of Routes are train_route_id, train_route_name, train_route_type, train_route_description

Description of Railway Enquiry System Database :

• The details of Trains is store into the Trains tables respective with all tables
• Each entity ( Routes, Fare, Seats Availability, Timetable, Trains) contains primary key and unique keys.
• The entity Fare, Seats Availability has binded with Trains, Timetable entities with foreign key
• There is one-to-one and one-to-many relationships available between Seats Availability, Stations, Routes, Trains
• All the entities Trains, Seats Availability, Fare, Routes are normalized and reduce duplicacy of records
• We have implemented indexing on each tables of Railway Enquiry System tables for fast query execution.