Professional Documents
Culture Documents
Superior University Lahore: Railway Management System
Superior University Lahore: Railway Management System
Team
Student Name Student ID Program Contact Number Email Address
Ayesha Ahoor BSEM-F16-159 BSSE Bsem-f16-159@superior.edu.pk
Zaeema Rabeet BSEM-F16-160 BSSE Bsem-f16-160@superior.edu.pk
Bakhtawar Liaquat BSEM-F16-242 BSSE Bsem-f16-242@superior.edu.pk
Supervisor
Mr. Muhammad Ahmed Kahloon
Project Report: Railway Reservation System
Project Report
Railway Management System
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0
APPROVAL
PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
Date:_______________________________ Signature:__________________________
1 Dedication
We dedicated our dissertation to our beloved parents, who taught us that even
the largest task can be accomplished if it is done with sincerity and devotion and
given us all of their resources for our study. We want to dedicate this to our
teachers also who enlightened us with knowledge.
2 Acknowledgements
First of all we are very grateful to Almighty ALLAH who gave us strength and guidance to carry
out our research project. We take immense pleasure in thanking Assistant Professor Sir Ahmed
Kahloon , our project supervisor (The Superior University Lahore) for having permitted us to
carry out this project work.
We would like to express our heartfelt thankful to our beloved parents for their blessings.
Our friends for their help and wishes for the successful completion of this project.
3 Executive Summary
The project is about Railway Management. It's all about to solve the current problems of
railway management. Through this you can check the schedule of trains from departure to
arrival time and the stations from which train has to pass by. You can reserves seats online,
check the availability of seats also you can discriminate seats for male and females. Through
this we can improve our system and our file system. File system will be finished and the system
become online. By using database we can arrange data properly according to our requirements.
4 Table of Contents
1 Dedication ............................................................................................................................... iv
2 Acknowledgements ................................................................................................................. v
3 Executive Summary................................................................................................................ vi
5 List of Tables .......................................................................................................................... ix
6 List of Figures ......................................................................................................................... xi
Chapter 1 ....................................................................................................................................... 12
Introduction ................................................................................................................................... 12
1.1. Background .................................................................................................................... 14
1.2. Goals and Objectives ...................................................................................................... 14
1.3. Literature Review/Existing Solutions ............................................................................ 15
1.4. Proposed Solution .......................................................................................................... 15
1.5. Project Plan .................................................................................................................... 16
1.5.1. Work Breakdown Structure ........................................................................................ 16
1.5.2 Gant Chart ........................................................................................................................ 17
Figure 1.5.2 ............................................................................................................................... 17
1.5.3 Roles & Responsibility Matrix ........................................................................................ 18
Table 1.5.3 ................................................................................................................................ 18
1.6. Report Outline ................................................................................................................ 18
Chapter 2 ....................................................................................................................................... 20
Software Requirement .................................................................................................................. 20
Specifications ................................................................................................................................ 20
2.1. Introduction .................................................................................................................... 21
2.1.1. Purpose ....................................................................................................................... 21
2.1.2. Document Conventions .............................................................................................. 21
2.1.3. Intended Audience and Reading Suggestions ............................................................ 21
2.1.4. Product Scope ............................................................................................................. 21
2.1.5. References .................................................................................................................. 22
2.2Overall Description .............................................................................................................. 22
2.1.1 Product Perspective .......................................................................................................... 22
2.1.2Product Functions ............................................................................................................. 23
2.2 Operating Environment ....................................................................................................... 24
2.2.1 Design and Implementation Constraints .......................................................................... 24
2.2.2 User Documentation ........................................................................................................ 24
2.2.3 Assumptions and Dependencies ...................................................................................... 25
2.2.4 User Classes and Characteristics ..................................................................................... 25
2.3 External Interface Requirements......................................................................................... 26
2.3.1 User Interfaces .................................................................................................................... 26
2.3.1 Hardware Interfaces .................................................................................................... 26
2.3.2 Software Interfaces ..................................................................................................... 27
2.3.3 Communications Interfaces ........................................................................................ 27
2.4 System Features.............................................................................................................. 28
2.4.1 System Feature ................................................................................................................ 28
2.4.1.2.1 Functional requirement 1: .............................................................................................. 28
2.4.1.2.3 Functional requirement 3:.................................................................................................. 29
5 List of Tables
6 List of Figures
Chapter 1
Introduction
Chapter 1: Introduction
This document is all about the requirements for the railway management system for the
Pakistan railway. This project is will be very helpful in making the things fast and reliable. It
decreases the work load and man power and also the government assets once it is deployed it
will save a lot of governments assets and made our country progressive and railway system
more efficient. Thing which is going to be done in hours happens in minutes with the help of this.
Through this way we can easily find the schedule of trains arrival time, we can also check the
reservation of seats by online system. In this project we use database system management for
arranging data.
1.1. Background
Railway system is the most important way of transportation. It is very useful for the business
and trade purpose. The background of the railway management system is in 13 May 1861 the
first railway system line was started for people and public transportation.
We find the problems in the current railway management system that we have not appropriate
records of passengers and employs, though we thought that there should be something that can
make records of all these things so we made our system more fast and easy to use.
• Schedule structure : it manage the timetable of arrival and departure of the trains
• Login system : it used to manage the login details
• customer system : it manage the information and details of customers
• user system : it use to manage the user details and information
• fare and booking : they manage the information about fare and booking system
Project
Schedule MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER OCTOBER Summery
2018 2018 2018 2018 2018 2018 2018 2018
TASKS Hours Percent
Requirements 12 12 12 9 45 22.20%
Design 5 7 12 8 32 14.90%
Code and 3 7 4 2 4 5 6 8 2 6 47 13.20&
Unit Test
Test and 3 6 9 12 15 15 12 9 6 3 90 6.60%
integrate
User Manual 16 12 8 4 38 21.10%
Write
Report 2 4 6 8 10 12 14 16 72 1.90%
Writing
Demonstrate 8 8 20.20%
Hours 12 12 10 9 10 12 14 18 10 12 20 10 8 20 21 12 332 100.00%
Figure 1.5.2
Table 1.5.3
1. User Roles:
• Can reserve the seats according to their will.
• Can buy tickets online
• Can buy pre-booked seats
• Can do cargo tracking
• Can complains about the system.
• It produce or create the report of customers, users, schedule of train timetable and
trains.
• It generates the pure and clear report of fare, booking and trains.
• PDF reports of trains, schedule of timetable, customer and fare also generates.
Chapter 2
Software Requirement
Specifications
2.1. Introduction
2.1.1. Purpose
This document is all about the requirements for the RMS for the Pakistan railway. This
project is will be very helpful in making the things fast and reliable. It decreases the work load
and man power and also the government assets once it is deployed it will save a lot of
governments assets and made our country progressive and railway system more efficient. Thing
which is going to be done in hours happens in minutes with the help of this.
2.1.5. References
3. [1] SOFTWARE ENGINEERING Tenth Edition Ian Sommerville
2.2Overall Description
2.1.1 Product Perspective
Existing system has these features
Data is stored in papers ,is not secured due to natural calamities
• As the data is on paper so it is unable to update ,delete ,add or view data
• Existing system is more time consuming
• Existing system consumes more men power
• Existing system has to deal with large volume of data to deal
• Existing system has to deal with a lot of calculations
• Existing system is manual which involves a lot of paper work
• To regain control of the railway tickets sales to avoid scalping and overselling of
tickets.
• To implement a prototype of a scaled down version of the final system to test the
solution and further develop requirements.
• To collect statistics in a more efficient manner for future railway development and
construction.
• To increase efficiency of railway.
2.1.2Product Functions
Functionalities of this project are
• It will provide searching facility
• It manages the customer details ,online fare details ,booking details and trains details
• It gives all the information about timetables
• It shows the description of trains
• It also monitors the transactions of fare
• Editing ,adding and updating of records
• Editing, adding and updating of fare
• Integrity of all records of booking
• Simple status and resolutions
• Decrease the person load involved in existing manual system
• Individual access to any information
• Reports are well designed
• It will provide multi level priorities
• Better storage capacity
• Updation is more easy
• work speed is increased
• retrieval of information is easy and fast
• to maintain the security user accounts are being secured
Hardware:
• Ram
• Hark disk
• Processor
• Monitor
• Keyboard
• Mouse
2 It manages the customer details ,online fare details ,booking details and trains details
Functional requirements are the requirements which is necessary for completion of the
details given by the client. In this some requirements are putted by software engineer
which is necessary for proper functionality
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Enter the seat number and numbers of seats you want to reserve
Output:
A message will appear on the screen “Mr Ali reserved the seat number 1,2,3 of train
LE1473 lahore to Karachi of 21:00 pst. Do you want to buy tickets now”
42.4.1.2.9 Functional requirement 9:
Description:
It should have visuality of full train so that passengers can select desired seat
Input:
Description:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Output:
Description:
Input:
Description:
Input:
User get the notification from the product to their respective devices
Description:
Input:
User get alerts of new offers, new timmings, delays of trains and other discount offers
from the product to their respective devices
Description:
For new users, it should have a guide book “how to use this forum”
Input:
Description:
Input:
It should display a messege “you want to change language” and switch to that desired
language
Description:
Input:
Click to the links where videos are placed for the users
Output:
video of the clicked link will start playing and its voice and print is as clear as it should
b listen to every one easily
Description:
Input:
Description:
Input:
Description:
Input:
Best matched word will be on top number and rest are as down below
Description:
Input:
Cancel the reservation and display a message “your reservation has been cancelled”
Description:
Input:
Description:
Input:
Description:
Input:
Description:
Input:
Description:
Input:
Description:
Input:
Will get the visuality of that class block of train not the complete train
Description:
Input:
Will get the visuality of that class block of train not the complete train
Description:
class types
Input:
Will get the visuality of that class block of train not the complete train
In this document the requirements are written first as of first priority and last of that least
priority
Functional Requirements
Functional requirements are the requirements which is necessary for completion of the
details given by the client. In this some requirements are putted by software engineer which is
necessary for proper functionality.
2.8 Availability
System should be available all the 24 hours so that it could not be have any difficulty in
reserving the seats for the trains
2.9 Reliability
System should be reliable so that client can give their personal information to the product easily
and trust them that their information is not leaked out for any purpose
2.11.1Business Rules
• The software design (maintainability) will not be responsibility of developer or
company.
• In case of any mishap in the software the developer or company will not be
responsible for that lose
• Developer or company gives a first trail of the software and after that they will not
entertain their quires.
• After delivering the project any increment in the software will be charged by per hour.
2.13.1 Login
Diagram 1:
Diagram:2
Diagram 3:
Diagram 4:
Diagram:5
Diagram:6
Diagram:7
Daigram:8
Chapter 3
Use Case Analysis
Reference: 2.4.1.2.1
Use Case Name: Store Information about entry time of train
Priority 5
Trigger When note the time train entrance at the
terminal
Precondition Train should just arrived
Basic Path 1-RRSS send the data to the DB of RRS and
stores the data
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition It will displayed at the time of reservations
with the route
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.1
Reference: 2.4.1.2.2
Use Case Name: Record of stations
Priority 5
Trigger Enter all the stations from where train has to
pass
Precondition Train route is decided
Basic Path 1-RRSS send the data to the DB of RRS and
stores the data
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition It will displayed at the time of reservations
with the route
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.2
Reference: 2.4.1.2.3
Use Case Name: Update record
Priority 5
Trigger When any admin login update the record
Precondition 1-Admin account is logged in.
2-Admin clicks on the update button
Basic Path 1-RRSS send the data to the DB of RRS and
updates the data
2-DB resend the data to the RRSS
Alternate Path N/A
Reference: 2.4.1.2.4
Use Case Name: Delete record
Priority 5
Trigger When any admin login delete the record
Precondition 1-Admin account is logged in.
2-Admin clicks on the delete button
Basic Path 1-RRSS send the data to the DB of RRS and
updates the data
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition It shows that update is made on the admin
interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.4
Reference: 2.4.1.2.5
Use Case Name: Passenger’s login account
Priority 5
Trigger When enter a correct email and password
Precondition Passenger’s device is connected to internet
Basic Path 1-RRSS send the data to the DB of RRS and
matches with the data
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition User should have a home page
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.5
Reference: 2.4.1.2.6
Use Case Name: Admin’s login account
Priority 5
Trigger When enters correct Admin’s or Staff id and
password
Precondition Admin’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS and
matches the data
2-DB resend the data to the RRSS
Alternate Path N/A
Reference: 2.4.1.2.7
Use Case Name: Guest’s login account
Priority 3
Trigger When clicks on the guests account icon
Precondition User’s device should connect to internet
Basic Path 1-RRSS send the data to the DB of RRS
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition It shows that update is made on the user
interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.7
Reference: 2.4.1.2.8
Use Case Name: Reservation System
Priority 5
Trigger When enters the seat number and number of
seats you want to reserve
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Reference: 2.4.1.2.9
Use Case Name: Visuality of train
Priority 4
Trigger When enters the seat number and number of
seats you want to reserve
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
3-user clicks on the desired seat/seats
Basic Path 1-RRSS send the data to the DB of RRS and
reserves the seats
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition generates a message on user’s interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.9
Reference: 2.4.1.2.10
Use Case Name: Mobile Application
Priority 5
Trigger When clicks on the mobile application icon
Precondition 1-User should connect to the internet
2-Mobile application is downloaded on user’s
device
Basic Path 1-RRSS send the data to the DB of RRS
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition Go to the user’s panel home page
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.10
Reference: 2.4.1.211
Use Case Name: Wallet System
Priority 4
Trigger Add money to the wallet of user
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
3-user’s account is connected to the bank
service
Basic Path 1-RRSS send the data to the DB of RRS and add
the money
2-DB resend the data to the RRSS
Alternate Path N/A
Reference: 2.4.1.2.8
Use Case Name: Withdraw money from Wallet
Priority 4
Trigger When withdraw the money from the wallet
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
3-user’s wallet has money
Basic Path 1-RRSS send the data to the DB of RRS and
withdraw money
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition generates a message on user’s interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.12
Reference: 2.4.1.2.13
Use Case Name: View of wallet
Priority 5
Trigger When clicks on the view of wallet
Reference: 2.4.1.2.14
Use Case Name: Cargo tracking system
Priority 4
Trigger When enters the cargo number and
destination of cargo
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS and
reserves the seats
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition Will get the position of cargo on user’s
interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.14
Reference: 2.4.1.2.15
Use Case Name: Online payment System
Priority 5
Trigger When user enters its bank account number
and password
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
3-User has bank account
Basic Path 1-RRSS send the data to the DB of RRS and
connect to the BOPS
2-DB resend the data to the RRSS and add
money to RRS account
Alternate Path N/A
Post Condition Transfer money from user’s account to the
management’s account
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.15
Reference: 2.4.1.2.16
Use Case Name: Notification
Priority 4
Trigger When user reserve any seat on bookmark the
seat
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Reference: 2.4.1.2.17
Use Case Name: Alert System
Priority 4
Trigger When any change happens on the user’s panel
by the admin’s panel
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS
2-DB resend the data to the RRSS and RRSS
send the alert to the device
Alternate Path N/A
Post Condition User gets the alert on user’s devices
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.17
Reference: 2.4.1.2.18
Use Case Name: Guide Book
Priority 3
Trigger When Clicks to that link where guide book is
placed
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS and
refer to that link
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition Open ups the guide book on user’s interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.18
Reference: 2.4.1.2.19
Use Case Name: Language option
Priority 3
Trigger When clicks to the language option change
link
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS
2-DB resend the data to the RRSS
Reference: 2.4.1.2.20
Use Case Name: Video tutorials
Priority 3
Trigger When Click to the link where videos are places
for the users
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition Video is start playing on user’s interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.20
Reference: 2.4.1.2.22
Use Case Name: Search area
Priority 5
Trigger Write there what user want to search
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS and
search from the complete forum
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition Searched results are displayed in a dropdown
list on user’s interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.21
Reference: 2.4.1.2.24
Use Case Name: Cancellation System
Priority 5
Trigger When cancel the reservation
Precondition 1-User’s account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS and
cancel the reservation
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition generates a message on user’s interface
Reference: 2.4.1.2.25
Use Case Name: Concession option
Priority 5
Trigger When click on the concession option
Precondition 1-User account is logged in.
2-User’s device is connected to the internet
Basic Path 1-RRSS send the data to the DB of RRS
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition Open up the concession form on user’s
interface
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.23
Reference: 2.4.1.2.30
Use Case Name: Class Option
Priority 5
Trigger When enters the class type to reserve the seat
Figure 3.2.1
Chapter 4
System Design
Figure 4.1
Figure 4.2
Figure 4.3
4.4 Data Flow diagram
LOGOUT/LOGIN/REGISTER
Figure 4.4.1
Figure 4.4.2
Figure 4.4
4.5Development diagram:
Figure 4.5
Figure 4.6
CHAPTER 5
IMPLEMENTATION
Chapter 5: Implementation
It's all about components, libraries, web services and stubs. In this chapter we will see the
important flow control and pseudo codes. We also see development environment in this chapter
in which we see the flow
REFRENCES
AND
BIBLIOGRAPHY
Appendix