Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

COMPUTER SCIENCE Total Marks:

Obtained Marks:
Date:

DataBase System(LAB)
Project Proposal

RAILWAY MANAGEMENT
SYSTEM

Submitted To: Mam Kashia

NAME REGISTRATION NUMBER

Muhammad Kashif 2212405

Mubeen khan 2212398

Hadya Zaheer 2212388

Gobind Kataria 2212387

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

Introduction:

A Railway Management System (RMS) is a sophisticated software solution designed to streamline and
optimize the operations of railway networks. The system acts as a centralized digital hub where railway
personnel can efficiently manage resources such as trains, schedules, routes, and passengers. It provides a
comprehensive platform for railway staff to schedule trains, allocate routes, monitor passenger records, and
handle ticketing and travel processes. With real-time updates and intelligent analytics, an RMS enhances the
efficiency of operations, improves communication with passengers, and reduces the chances of errors and
delays.

In addition to tracking train movements, the system is crucial for managing booking records, seat reservations,
fare collections, fine management, and operational efficiency. By automating various aspects of railway
operations, it ensures a smoother travel experience for passengers and supports better decision-making for
railway management.

Objectives:

This report aims to provide a comprehensive overview of the key components and relationships within a
Railway Management System (RMS), including:

1. Railway Staff Information: Outlining the personnel responsible for managing railway operations,
including their unique identifiers, names, departments, and contact details.

2. Train Information: Presenting specific details about trains such as unique train IDs, train numbers,
routes, and types, which are vital for scheduling and management.

3. Passenger Information: Capturing passenger data for bookings, including their unique IDs, names,
contact details, and addresses.

4. Booking Records: Maintaining booking details, including booking IDs, passenger IDs, train IDs, seat
assignments, journey dates, and payment statuses.

5. Fare and Fine Management: Tracking ticket fares and fines imposed on passengers for violations like
fare evasion, detailing amounts, status, and payment history.
DB (4B) LAB DB (4B) LAB
 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
Key Components of the Railway Management System:

1. Staff Table

The staff table holds information about railway staff members, including their responsibilities, roles, and contact
information.

 staff_id (PK): Unique identifier for each staff member.

 name: Name of the staff member.

 department: Department to which the staff member belongs (e.g., Operations, Maintenance).

 contact_info: Contact information (e.g., phone number, email).

2. Train Table

This table contains details about each train operating within the network.

 train_id (PK): Unique identifier for each train.

 train_number: Public-facing train number for identification.

 route_id (FK): Links to the Route table.

 train_type: Type of train (e.g., Express, Freight, High-Speed).

 capacity: Total seating capacity of the train.

3. Route Table

The route table defines the various routes within the network, including start and end stations, distances, and
associated train schedules.

 route_id (PK): Unique identifier for each route.

 start_station: Starting station of the route.

 end_station: Ending station of the route.

 distance: Distance of the route in kilometers.

4. Station Table

This table defines the stations within the railway network, serving as the origin and destination points for
various routes.

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
 station_id (PK): Unique identifier for each station.

 name: Name of the station.

 location: Physical location or address of the station.

5. Train_Schedule Table

This table contains the scheduling details for each train, including its route, departure time, and expected arrival
time.

 schedule_id (PK): Unique identifier for each schedule.

 train_id (FK): Links to the Train table.

 route_id (FK): Links to the Route table.

 departure_time: Departure time from the starting station.

 arrival_time: Expected arrival time at the destination station.

 status: Current status of the train (e.g., On Time, Delayed, Cancelled).

6. Passenger Table

The passenger table tracks information about railway passengers who book tickets and use the railway services.

 passenger_id (PK): Unique identifier for each passenger.

 name: Name of the passenger.

 contact_info: Contact information (e.g., phone number, email).

 address: Address of the passenger.

7. Booking Table

This table manages passenger bookings, including train details, journey dates, and payment statuses.

 booking_id (PK): Unique identifier for each booking.

 passenger_id (FK): Links to the Passenger table.

 train_id (FK): Links to the Train table.

 journey_date: Date of travel.

 seat_number: Assigned seat number for the passenger.

DB (4B) LAB DB (4B) LAB
 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
 payment_status: Status of the payment (Paid/Unpaid).

8. Fare Table

The fare table defines the pricing structure for each route, ensuring the appropriate charges are applied for each
journey.

 fare_id (PK): Unique identifier for each fare.

 route_id (FK): Links to the Route table.

 fare_amount: Amount charged for the route.

9. Fine Table

This table records fines imposed on passengers for violations, such as fare evasion or traveling without a ticket.

 fine_id (PK): Unique identifier for each fine.

 passenger_id (FK): Links to the Passenger table.

 amount: Fine amount.

 description: Description of the fine (e.g., No Ticket, Fare Evasion).

 payment_status: Status of fine payment (Paid/Unpaid).

Relationships and Keys:

Foreign Keys (FK):

 train_id in Train_Schedule and Booking tables references Train.train_id.

 route_id in Train and Fare tables references Route.route_id.

 passenger_id in Booking and Fine tables references Passenger.passenger_id.

 route_id in Train_Schedule references Route.route_id.

Primary Keys (PK):

Each table has a unique identifier (*_id) for each entity to ensure data integrity and avoid duplicates. These
primary keys are used to reference entities in other tables through foreign keys.

Additional Entities and Relationships:

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
1. Train_Type Table:

A new table that classifies trains by type, such as "Express," "Freight," "Passenger," and "High-Speed." This
allows better categorization of trains and can be used to link to train schedules and pricing.

 train_type_id (PK): Unique identifier for each train type.

 train_type_name: Name of the train type (e.g., Express, Freight).

 description: Description of the train type.

2. Maintenance Table:

Maintenance records for tracking maintenance activities performed on trains and other railway infrastructure.

 maintenance_id (PK): Unique identifier for each maintenance record.

 train_id (FK): Links to the Train table.

 maintenance_type: Type of maintenance (e.g., Routine, Emergency).

 maintenance_date: Date of maintenance.

 status: Current status of maintenance (e.g., Completed, Pending).

3. Staff_Schedule Table:

Associative entity linking Staff and Train_Schedule, representing the many-to-many relationship where
multiple staff members can manage multiple schedules.

 staff_schedule_id (PK): Unique identifier for each staff schedule.

 staff_id (FK): Links to the Staff table.

 schedule_id (FK): Links to the Train_Schedule table.

4. Route_Station Table:

Associative entity linking Route and Station, representing the many-to-many relationship where multiple
stations are part of multiple routes.

 route_station_id (PK): Unique identifier for each route-station relationship.

 route_id (FK): Links to the Route table.

 station_id (FK): Links to the Station table.

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
ERD SCENARIO

 Staff

 staff_id (PK)
 name
 department
 contact_info

 Train

 train_id (PK)
 train_number
 route_id (FK)
 train_type
 capacity

 Route

 route_id (PK)
 start_station
 end_station
 distance

 Station

 station_id (PK)
 name
 location

 Train_Schedule

 schedule_id (PK)
 train_id (FK)
 route_id (FK)
 departure_time
 arrival_time

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
 status

 Passenger

 passenger_id (PK)
 name
 contact_info
 address

 Booking

 booking_id (PK)
 passenger_id (FK)
 train_id (FK)
 journey_date
 seat_number
 payment_status

 Fare

 fare_id (PK)
 route_id (FK)
 fare_amount

 Fine

 fine_id (PK)
 passenger_id (FK)
 amount
 description
 payment_status

Relationships between Entities:

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology
 Staff to Train_Schedule: Many-to-many relationship. Staff can be responsible for multiple train
schedules, and each schedule may have multiple staff members assigned. This is handled through the
Staff_Schedule table.

 Train to Train_Schedule: One-to-many relationship. A train can have multiple schedules, but each
schedule corresponds to only one train.

 Route to Train: One-to-many relationship. Each route can be served by multiple trains, but each train
follows one specific route.

 Station to Route: Many-to-many relationship. A station can be part of multiple routes, and each route
can pass through multiple stations. This is managed through the Route_Station table.

 Passenger to Booking: One-to-many relationship. A passenger can make multiple bookings, but each
booking is linked to only one passenger.

 Booking to Train: Many-to-one relationship. Multiple bookings can be made for a single train, but each
booking corresponds to one train.

 Route to Fare: One-to-one relationship. Each route has one fare associated with it.

 Passenger to Fine: One-to-many relationship. A passenger can incur multiple fines, but each fine
corresponds to a single passenger.

Conclusion:

The Railway Management System (RMS) is an essential tool for efficiently managing the diverse and complex
operations of modern railways. It integrates a wide range of functionalities, from train scheduling and route
management to ticket booking, fare management, and passenger services. By maintaining detailed relational
databases and ensuring robust relationships between entities, the RMS enhances operational efficiency,
transparency, and service quality. The inclusion of new entities such as Maintenance and Train_Type adds
flexibility and scalability to the system, allowing it to better serve both staff and passengers.

Ultimately, an RMS serves as the backbone of modern railway operations, reducing operational costs,
improving customer satisfaction, and supporting better decision-making, making it an indispensable solution for
railway networks worldwide.

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

 Shaheed Zulfikar Ali Bhutto Institute of Science & Technology

DB (4B) LAB DB (4B) LAB

DB BSCS-4B SZABIST-
ISB
DB BSCS-4B SZABIST-
ISB DB BSCS-4B SZABIST-
ISB