DATABASE

MANAGEMENT
SYSTEM
MICRO-PROJECT
 YADAVRAO TASGAONKAR POLYTECHNIC
MICRO PROJECT REPORT
Academic year: 2023-24

TITLE OF PROJECT
Health Care Management System

DEPARTMENT: Computer Engineering (III semester)

SUBJECT: Object Oriented Programming
SUBJECT CODE: 22316

SUBMITTED BY:
1. PATIL RONIT JITENDRA
2. KULKARNI RUSHIKESH PRASHANT
3. CHOPADE KEVAL
4. SALUNKHE KRISH RAJENDRA

SUBMITTED TO:
Yadavrao tasgaonkar polytechnic bhivpuri
For academic year 2023-2024

UNDER THE GUIDANCE OF:

Dhanashree mam,
(Lecturer in Database Management System)
 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Certificate

This is to certify that Mr./Ms. __________________

Roll No _________ of Third Semester of Diploma in
Computer Engineering of Institute Yadavrao
Tasgaonkar Polytechnic college, Bhivpuri Road
(code 0960) has Completed the microproject
satisfactorily in subject Database Management
System(22319) for the Academic year 2023-2024 as
prescribed in the curriculum.

Place: _____________.

Date:__________.

Subject Teacher H. O. D. Principal

_____________ ________ ___________
 INDEX

Sr. No. Content Page No.

1 Abstract 5
2 Introduction 6
3 Project 7
Description

4 Information 7
5 Functionalities 8
6 Querrey 9
7 Diagrams 14
Abstract:
The Railway Reservation System facilitates the passengers to
enquire about the trains available on the basis of source and
destination, Booking and Cancellation of tickets, enquire about
the status of the booked ticket, etc. The aim of case study is to
design and develop a Database maintaining the records of
different trains, train status, and passengers. This project contains
Introduction to the Railways reservation system It is the
computerized System of reserving the seats of train seats in
advanced. It is mainly used for long route, On-Line reservation
has made the process for the reservation of seats very much easier
than ever Before. In our country India, there are number of
counters for the reservation el the seats and one can Easily make
reservations and get tickets. Then this project contains entity
relationship model Diagram based on railway reservation system
and introduction to relation model.
Introduction:

Database is an organized collection of data. The data is typically

organized to model aspects of reality in a way that supports processes
requiring information. A DBMS makes it possible for end-users to create,
read, update and delete data in a database. The DBMS essentially serves
as an interface between the database and end users or application
programs, ensuring that data is consistently organized and remains easily
accessible. The DBMS manages three important things the data, the
database engine that allows data to be accessed. locked and modified and
the database schema, which defines the database's logical structure. These
three foundational elements help provide concurrency security, data
integrity, and uniform) administration procedures. The DBMS can offer
both logical and physical data independence Which means It can protect
users and applications from needing to know where data is stored or
having to be concerned about changes to the physical structure of data.

The main purpose of maintaining database for Railway Reservation

System is to reduce the manual errors involved in the booking and
canceling of tickets and make it convenient for the customers and
providers to maintain the data about their customers and also about the
seats available at them. Due to automation many loopholes that exist in
the manual maintenance of the records can be removed. The speed of
obtaining and processing the data will be fast. For future expansion the
proposed system can be web enabled so that clients can make various
enquiries about trains between stations. Due to this, sometimes a lot of
problems occur and they are facing many disputes with customers. To
solve the above problem, we design a data base which includes customer
details availability of seats in trains, no of trains and their details.
Project Description:

This Project is about creating the database about Railway Reservation

System. The railway reservation system facilitates the passengers to
enquire about the trains available on the basis of destination, booking and
cancellation of tickets. Enquire about the status of the booked ticket, etc.
The aim of case study is to design and develop a database maintaining the
records of different trains, train status, and users. The record of train
includes its number, name, description ,capacity, time, destination. Users
can book their tickets for the train in which seats are available. For this,
user has to provide the desired train number and the date for which ticket
is to be booked. Before booking a ticket for a user, the validity of train
number is checked. Once the train number and time are validated, it is
checked whether the seat is available. If yes, the ticket is booked with
confirm status and corresponding ticket ID is generated which is stored
along with other details of the user. The ticket once booked can be
cancelled at any time. For this, the passenger has to provide the ticket ID
(the unique Key).User can do the payment by different
modes(UPI.Cash.Card).

Information:
A railway system database is a complicated one if we compare
it with the vast network of indian railways but in this article, we
will cover the basic functioning of the system as part of the easy
sql projects that one can get started with. We can create a railway
network database solution to handle train schedules, passenger
travel, station information, and more the system facilitates ticket
reservations, train operations, ticket cancellations, pre-departure
chart preparation, rescheduling in case of delays, and more.
Functionalities:

The system will consist of information about the trains like the train name
number of coaches, train type, and if the train is currently between a
journey. This will create a pool of trains from which we can pick available
trains to schedule a new journey.

The system will have a schedule table which will keep a record of the
schedules of the trains including start time, end time, source, destination,
and the route that the train will be taking the system will have provision
to store the data about passengers who have travelled, are travelling, and
are about to travel in future. The basic information of the passengers,
along with the train name they are travelling in, coach number berth
number, ticket status, and their respective schedule will be captured. The
system also requires a list of station names that will provide information
about each station like the name of the station and the city or state it
belongs to.

Finally there will also be a route information table which provides

information about the route that a particular train will be taking between
source and destination stations.
Query:

DROP SCHEMA IF EXISTS railway_system CASCADE;

CREATE SCHEMA IF NOT EXISTS railway_system;

DROP TABLE IF EXISTS railway_system.user_login;

CREATE TABLE IF NOT EXISTS railway_system.user_login (

User_id TEXT PRIMARY KEY,

User_password TEXT,

First_name TEXT,

Last_name TEXT,

Sign_up_on DATE,

Email_id TEXT

);

DROP TABLE IF EXISTS railway_system.passenger;

CREATE TABLE IF NOT EXISTS railway_system.passenger (

Passenger_id TEXT PRIMARY KEY,

 User_password TEXT,

First_name TEXT,

Last_name TEXT,

Sign_up_on DATE,

Email_id TEXT,

Contact TEXT

);

DROP TABLE IF EXISTS railway_system.train_type;

CREATE TABLE IF NOT EXISTS railway_system.train_type (

Train_type_id TEXT PRIMARY KEY,

Train_type TEXT,

Coaches_count TEXT,

Passenger_strength TEXT,

Train_count DATE

);

DROP TABLE IF EXISTS railway_system.stations;

CREATE TABLE IF NOT EXISTS railway_system.stations (

Station_id TEXT PRIMARY KEY,

Station_name TEXT,

City TEXT,

State TEXT

);

DROP TABLE IF EXISTS railway_system.train_details;

CREATE TABLE IF NOT EXISTS railway_system.train_details (

Train_id TEXT PRIMARY KEY,

Train_type_id TEXT REFERENCES railway_system.train_type

(train_type_id),

Source_station_id TEXT REFERENCES railway_system.stations

(station_id),

Destination_station_id TEXT REFERENCES

railway_system.stations (station_id),

Duration_minutes INT,

Journey_start TIMESTAMP,
 Journey_end TIMESTAMP,

Passenger_strength INT,

Is_available BOOLEAN

);

DROP TABLE IF EXISTS railway_system.journey;

CREATE TABLE IF NOT EXISTS railway_system.journey (

Journey_id TEXT PRIMARY KEY,

Passenger_id TEXT REFERENCES railway_system.passenger

(passenger_id),

Train_id TEXT REFERENCES railway_system.train_details

(train_id),

Booking_id TEXT,

Payment_id TEXT,

Payment_status TEXT,

Paid_on TIMESTAMP,

Booking_status TEXT,

Booked_on TIMESTAMP,
 Seat_alloted TEXT,

Meal_booked BOOLEAN

);

DROP TABLE IF EXISTS railway_system.train_routes;

CREATE TABLE IF NOT EXISTS railway_system.train_routes (

Row_id SERIAL PRIMARY KEY,

Route_id TEXT,

Train_id TEXT REFERENCES railway_system.train_details

(train_id),

Station_id TEXT REFERENCES railway_system.stations

(station_id),

Order_number INT,

Halt_duration_minutes INT,

Estimated_arrival TIME,

Estimated_departure TIME

);
Diagrams: