CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

RAILWAY RESERVATION

PROJECT REPORT
Submitted by

Vishal Mohanty 16BCE0881

Swastik Das 16BCE0586
Amartya Sonbhadra 16BCE2152
Archit Hooda 16BCE2168
Akshat Sood 16BCE0872

Prepared For

DATABASE SYSTEMS (CSE2004) – PROJECT COMPONENT

Submitted To
Dr. B.K. Tripathy

School of Computer Science and Engineering

1.1.1.1.1.1.1

PAGE 1
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

Table of Contents
1. Introduction....................................................................................................... 3
2. Project SCOPE.................................................................................................. 3
3. Project Resource Requirements ...................................................................... 4
4.1Software Resource Requirements....................................................... 4
4.2 Functional & Non-Functional Requirements
4. Diagrams
5. Participation and Cardinality Schema
6. ER Diagram
7. Relational Schema
8. Tables and Constraints................................................................................... 14
9. Results (Snapshots)
10. Future Enhancements

PAGE 2
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

1. INTRODUCTION
In this emerging world of computers, almost all-manual system has switched to automated and
computerized system. Therefore, we are developing the software for “Railway Reservation System” to
model the present system and to remove the drawbacks of the present system. This project explore show
computer technology can be used to solve the problem of user. This being a big step in terms of
improvement in the railway system it is widely accepted across the country. Rather than designing
manually, we have made use of computer. Use of computer has solved many problems, which are faced
during manual calculation. Once data are fed, it can perform accurate functions. Therefore, to reduce the
complexity and efficiency a versatile and an out sourcing railway reservation system has been
developed. This project introduces railway reservation system. It explains how reservation is being done
in Indian Railways. The systematic procedure is explained. We will try to make an application for this
reservation system using PHP, CSS and HTML as the front end and MYSQL, PHPMYADMIN AND
WAMP SERVER to create the database as the back-end. Now in our application we have made some
additional features like providing the SPECIAL OFFERS to the users booking their tickets. The users
can apply for OLA cab services as well. We gave our main focus on the back end portion and tried to
create the database as user friendly as possible. However in our project initially we will only cover the
trains from Katpadi to Chennai, Bengaluru, Madurai, Bhubaneshwar, Trichy, Hyderabad, Kodaikanal.

2. PROJECT SCOPE
•All the manual work would be converted into computerized system and the work of the employees
should decrease a lot.
•The records should be stored in databases in place of files which will reduce the inconsistency and
redundancy of data.
•We also have included an option for special offers which the passengers can apply for booking the
tickets. It will automatically provide special discounts and offers to the registered customers based on
our sponsors.
•Users will be able to see the timings and available seats of all the trains for their respective destinations
•Passengers can reserve and cancel the tickets any time as they want. The available seats will be updated
with appropriate queries.
•The main objective of the project is to make the application of train reservation as much user friendly
as possible and any type of suggestions to improve the application from the users or other people is
always welcome.

PAGE 3
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

3. PROJECT RESOURCE REQUIREMENTS

3.1 Software Resource Requirements

Windows 7/8/10
WAMP Server
PHP 11.0
HTML 5
Mozilla Firefox
PHPMyAdmin
MYSQL

3.2 Functional and Non Functional Requirements

Functional requirements includes a set of use cases that describes all the interactions the users will have with the
software. In addition to use cases, the Software Requirements Specification (SRS) also contains non functional
(or supplementary) requirements. Non Functional Requirements are requirements which impose constraints on the
design or implementation (such as performance engineering requirements, quality standards or design
constraints).

3.2.1 Performance requirements

User Satisfaction :- The system is such that it stands up to the user expectations.

Response Time :- The response of all the operation is good. This has been made possible by careful
programming.

Error Handling :- Response to user errors and undesired situations has been taken care of to ensure that
the system operates without halting.

Safety and Robustness :- The system is able to avoid or tackle disastrous action. In other words, it should
be foul proof. The system safeguards against undesired events, without human intervention.

Portable :- The software should not be architecture specific. It should be easily transferable to other
platforms if needed.

PAGE 4
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

User Friendliness :- The system is easy to learn and understand. A native user can also use the system
effectively, without any difficulties.

3.2.2 Design Constraints

Standard Compliance :- This specifies the requirements for the standard the system must follow. The
standards may include the report format and accounting properties.

Hardware Limitation :- The software may have to operate on some existing or predetermined hardware,
this imposing restrictions on the design. Hardware limitation can include the types of machines to be
used, operating system available on the system, languages supported and limits on primary and secondary
storage.

Reliability and Fault Tolerance :- Fault tolerance requirements can place a major constraints on how the
system is to be designed. Fault tolerance requirements often make the system more complex and
expensive. Requirements about system behavior in the face of certain kinds of faults are specified.
Recovery requirements are often an integral part here, detailing what the system should do I some failure
occurs to ensure certain properties. Reliability requirements are very important and critical applications.

Security :- Security requirements are particularly significant in defence systems and database systems.
They place restrictions on the use of certain commands, control access to data, provide different kinds of
access requirements for different people, require the use of passwords and cryptography techniques and
maintain a log of activities in the system.

3.2.3 Hardware Requirements

Minimum Hardware Requirements

Processor Pentium III

Hard Disk Drive 40GB

RAM 128MB

Cache 512 KB

Preferred Hardware Requirements

Processor Pentium IV

Hard disk drive 80GB

RAM 256 MB

Cache 512 KB

PAGE 5
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

3.3 Non functional Requirements

3.3.1 Security

The system use SSL in all transactions that include any confidential customer information. The system
must automatically log out all customers after a period of inactivity. The system should not leave any
cookies on the customer’s computer containing the user’s password/ The system back end servers shall
only be accessible to authenticated management.
3.3.2
Reliability

The reliability of the overall project depends on the reliability of the separate components. The main pillar
of reliability of the system is the backup of the database which is continuously maintained and updated to
reflect the most recent changes. Also the system will be functioning inside a container. Thus the overall
stability of the system depends on the stability of container and its underlying operating system.
3.3.3
Availability

The system should be available at all times, meaning the user can access it using a sweb browser, only
restricted by the down time of the server on which the system runs. A customer friendly system which is
in access of people around the world should work 24 hours. In case of a hardware failure or database
corruption, a replacement page will be shown. Also in case of a hardware failure or database corruption,
backups of the database should be retrieved from the server and saved the organizers. Then the service
will be restarted. It means 24X7 availability.

3.3.4 Maintainability

A commercial database is used for maintaining the database and the application server takes care of the
site. In case of a failure, a re-initialization of the project will be done. Also the software design is being
done with modularity in mind so that maintainability can be done efficiently.
3.3.5
Supportability

The code and supporting modules of the system will be well documented and easy to understand. Online
User Documentation and Help System Requirements.

PAGE 6
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

4. DIAGRAMS

4.1 Use-case Diagram

PAGE 7
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

4.2 Class Diagram

PAGE 8
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

4.3 Class Diagram

PAGE 9
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

4.4 Context Diagram

PAGE 10
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

5. PARTICIPATION AND CARDINALITY SCHEMA

1. Mandatory-Mandatory

2. Mandatory-Optional

3. Optional-Mandatory

4. Optional-Optional

5. One-One

6. One-Many

7. Many-One

8. Many-Many

PAGE 11
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

6. ER DIAGRAM

PAGE 12
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

7. RELATIONAL SCHEMA

PAGE 13
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

8. TABLES AND CONSTRAINTS

User:

Attributes type constraints

User -id Char(10) Primary key
Password Varchar(20) Check password.length>8,not
null

Employee:

Attributes type Constraints

Name Varchar(30) Not null
Address Varchar(50) Not null
Date of birth Date Not null
Date of joining Date Not null
Position Varchar(20) Not null
Employee-id Char(10) Primary Key

Reservation:

Attributes Type Constraints

Ticket-type Number(9) Not null
Class Varchar(10) Check class in 3-AC 2-AC 1-AC
OR Sleeper
Train-name Varchar(30) Not null
Train_number Number(20) Foreign key references
train(train_no)
From Varchar(20) Not Null
To Varchar(20) Not null
Date-of-journey Date Not null
F-name Varchar(20) Not null
L-name Varchar(20)
Age Number(3) Not null
Sex Varchar(6) Check in Male or female
Senior-citizen Varchar(3) Check in Yes or no
Seat-no Number(3) Foreign key references seat
(seat_no)
PNR no: Number(16) Primary key
Auto-upgradation Varchar(3) Check in Yes or No

Seats
Attributes Type Constraints
Seat_id Number(10) Primary Key
Seat_no Number(3) Not null
Available seats Number(4) Not null

PAGE 14
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

Class Varchar(10) Check class in 3-AC 2-AC 1-AC

OR Sleeper
Train_name Varchar(30) Not-null

Fares
Attributes Type Constraints
Train_name Varchar(30) Not_null
For_employees Number(6,2)
For_children Number(6,2)
For_senior citizen Number(6,2)
Seat_id Number(10) Foreign key references
seat(seat_id)
Train_Number Number(10) Foreign key references
train(train number)

Admin
Attributes Type Constraints
Admin_id Number(10) Primary key
Password Number(10) Check password.length>8, not
null
User_id Char(10) Foreign key references
user(user_id)

Ticket
Attributes Type Constraints
Receipt_no Number Partially unique
Class Varchar(10) Check class in 3-AC 2-AC 1-AC
OR Sleeper
Name Varchar(30) Not null
Date of birth date Not null
Gender Varchar(10) Check in Male or female
Train number Varchar(10) Foreign key references
train(train no)
PNR number Char(16) Foreign key references
reservation(PNR no)

Food
Attributes Type Constraints
Number of meals number
Menu Varchar(10) Check in veg or non veg or both
Seat_id Number(10) Foreign key references
seat(seat_id)
Train number Number(10) Foreign key references
train(train number)

PAGE 15
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

Railway
Reservation
System

Front End Back End

Reservation OLA Cabs Trains

Cancellation Data Data

Special Offers Availability Users Offers

Data Data

Print Ticket Registration/L Available Seats

ogin Handler

Payment
Module

PAGE 16
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

10. RESULTS (SNAPSHOTS)

10.1 Homepage

10.2 Registration

PAGE 17
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

10.3 Login

PAGE 18
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

10.4 Search Trains

10.5 Cancellation

PAGE 19
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

10.6 Reservation

10.7 Special Offers

PAGE 20
 CSE2004–DATABASESYSTEMS–JCOMPONENTPROJECTWORKREPORT

11. FUTURE ENHANCEMENTS

As mentioned above, although our system had been completed but it is not perfect, we had planned to make some
enhancements in the future.
We think that our system still has potential to grow. Besides, we will include more functions and introduce more
widgets to the system.

So there are many things for future enhancement of this project. The future enhancements
that are possible in the project are as follows.

1. Web Based interface for system administrator to add modify database, which
presently done from back end
2. Web based interface for generate information, reports, student campus
details for system administrator
3. Linking and integration of other educational database .
4. Integration with university database through Web Services
5. Connection to third-party applications
6. In the area of data security and system security.
7. Provide more tips and help
8. Tatkaal Booking
9. DNN, rDOS, XSS and SQLi attacks prevention