ADP-CS FINAL PROJECT
Railway Management System
Advisor: Sir Ehtsham
PRESENTED BY:
Group ID: ADP-CS G3
Ashan Imtiaz L1F21ASCS0040
M.Umair Haseeb L1F20ASCS0125
Ch.Bilal Ilyas L1F21ASCS0021
University of Central Punjab
Faculty of associate degree program
Software Requirements Specification
Member Name Primary Responsibility
Ashan Imtiaz Back-end
<Project Name>
M.Umair Haseeb Front-End
Ch.Bilal Ilyas Front-End
Frond end at:
Html,Css and Javascript
Back-end:
MongoDB
Table of Contents
Table of Contents ....................................................................................................................... i
1. Introduction and Background ............................................................................................ 1
1.1 Product (Problem Statement) .................................................................................................. 1 1.2
Background ............................................................................................................................ 1 1.3
Scope...................................................................................................................................... 1
1.4 Objective(s)/Aim(s)/Target(s) ................................................................................................. 2 1.5
Completeness Criteria ............................................................................................................. 2
1.6 Business Goals ....................................................................................................................... 3
2. Functional Requirements .................................................................................................... 3
2.1 Functions of System ............................................................................................................... 3 2.2
Requirements Analysis and Modeling ..................................................................................... 4
2.3 Usage Scenarios...................................................................................................................... 6
2.4 Adopted Methodology ............................................................................................................ 6
3. Nonfunctional Requirements .............................................................................................. 7
3.1 Performance Requirements ..................................................................................................... 7
3.2 Safety Requirements ............................................................................................................... 7 3.3
Security Requirements ............................................................................................................ 7
3.4 Additional Software Quality Attributes ................................................................................... 7
4. Other Requirements ............................................................................................................ 8 5.
Revised Project Plan ........................................................................................................... 8 6.
References ............................................................................................................................ 8
Appendix A: Glossary ............................................................................................................... 9
1. Introduction:
In the given project we will be developing a website which will help users to find train details,
book and cancel tickets and the exact rates of their tickets to the desired
<Project Name>
Destination with the help of online booking people can book their tickets online through internet, sitting in
their home by a single click of mouse. Using their credit cards people can easily get their tickets done within
minutes.
1.1 Product (Problem Statement)
The online railway ticket reservation system aims to develop a web application which aims at
providing trains details, trains availability, as well as the facility to book ticket in online
for customers.So, we thought of developing a web based application which would provide the users all these
facilities from his terminal only as well as help them in booking their tickets and further emergency Alter
provide during the booking . The other website not comfortable use our vision provide the comfortable use. .
The railway management 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.
1.2 Background
The railway management 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 govt. website not look like advance feature we choice this website to update the feature. The aim of
case study is to design and develop a database maintaining the records of different trains, train status, and
passengers. The record of train includes its number, name, source, destination, and days on which it is available,
whereas record of train status includes dates for which tickets can be booked, total number of seats available,
and number of seats already booked.
Passengers can book their tickets for the train in which seats are available. For this, passenger has to provide the
desired train number and the date for which ticket is to be booked. Before booking a ticket for a passenger, the
validity of train number and booking date is checked. Once the train number and booking date 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 passenger
1.3 Scope
The railway management system is incorporated with different types of the manual and automatic systems that
include various kinds of tools and services, which help in quick and better management of the rail industry. The
purpose is to help to finalize the requirement set for Infrastructure Management (requirement management tool)
also to Identify and promote diagnostics requirement within RCS signalling products and lift them to the
requirement set. The objectives are threefold:
• Help finalize and set up requirements for Infrastructure Management at system level
• Identify diagnostics requirements within RCS sub-system products and links to system level requirements •
Develop and investigate eventual tools to produce documentation ,and no need to go on queue.
Objective(s)/Aim(s)/Target(s)
The purpose of developing a Railway Management System is to
• Automate the process of Railway Management System.
• To maintain two user levels i.e. Administrator Level
<Project Name>
User Level
To maintain the record of pasanger if he buy the tickets of train Our
vision is to become.
Our mission is to build a world class Railway management system that will become the preferred choice
for a wide range of other sector .
1.4 Completeness Criteria:
Railway management system will be successfully completed if it satisfies the following evaluation criterion.
a) Planned approach towards working: The working in the organization will be well planned and
organized. The data will be stored properly in data stores and on one click browsers, which will help in
retrieval of information as well as its storage.
b) Accuracy: The level of accuracy in the proposed system will be higher. All operation would be done
correctly and it ensures that whatever information is coming from the center is accurate.
c) Reliability: The reliability of the proposed system will be high due to the above stated reasons. The
reason for the increased reliability of the system is that now there would be proper storage of
information and the paper or file system is over and make it low cost.
d) No Redundancy: In the proposed system utmost would be that no information is repeated anywhere,
in storage or otherwise. This would assure economic use of storage space and consistency in the data
stored and no any issue in booking.
e) Immediate retrieval of information: - The main objective of proposed system is to provide for a
quick booking and efficient retrieval of information. Any type of information would be available
whenever the user requires.
f) Easy to Operate: The system should be easy to operate and should be such as The system should be
able to manage waitlists for fully booked trains and automatically upgrade tickets to confirmed status
as and when seats become available..
Business Goals:
Online booking system is a crucial component of a Railway Management System as it enables
passengers to book and reserve train tickets easily and efficiently. A well-designed and
userfriendly online booking system can help to improve customer experience, increase revenue,
and streamline operations for the railway company. It will be designed to manage all operations
and useful to Multi-Specialty ticket, food, Rest House. Various users can easily interconnect with
each other to communicate and share information.
1.5 Functional Requirements
Functions of System
The system will allow access only to authorized users with specific roles (Administrator, Operator). Depending
upon the user’s role, he/she will be able to access only specific modules of the system. A list of the major
functions that the software will perform is given below:
Registration
Check route: The system shall allow check the route to the system.
<Project Name>
Check seat: The system shall allow the seat if the seat available the passenger conserve the seat.
Payment Method: The system shall allow payment as the customer want to pay payment any method avaiable in
Pakistan
Railway matter management
Check Payment: The administrative staff in the Railway shall use system to Check payment to a given
passenger phone number or any method of Passenger payment.
Assign Recept: The administrative staff in the Railway shall use system to assign a recept to a given passenger
phone number about the detail of train,seat,cabin.
Assign other ideas: The administrative staff in the Railway shall use system to give idea other rasturent , Hotel
and weather detail about of booking ticket location to a given passenger phone number.
Emerengcy Report : The system shall generate the report in Emerengcy’s situation to passenger phone number
Report Generation
Passenger information: Every six hours the system shall generate reports on Passenger about the following
information: Passenger’s PHN, Passenger’s name, Passenger Cnic.
Seat Availability: Every six hours the system shall generate reports on seat availability about the following
information: Train name, seat number, occupied/unoccupied
Database
Passenger Mandatory Information: Each Passenger shall have the following mandatory information:
first name, last name, phone number, cnic number, address, postal code, city, country.
Update Passenger Information: The system shall allow the user to update any of the passenger’s
information
Train Information: The system shall allow the user to search for Train information by last name, or ID
number.
Cabin Types: The Cabin is categorized into two types: business Cabin , Ecconmy Cabin.
Cabin Information: Each Cabin in system shall include the following mandatory information: Cabin
name, Cabin number.
Requirements Analysis and Modeling Use
Case Diagram:
<Project Name>
Activity Diagram:
<Project Name>
Usage Scenarios:
Identifier Conserve seat
This function Buy the ticket anywhere and add record to
Purpose the passenger database and generate a passenger
booking recept.
Priority High
Pre-conditions The operator should login with user account.
Post-conditions Booking the ticket by the given route.
Typical Course of Action
S# Actor Action System Response
1 1. User selects “book now” at home Booking the detail of route
page. display.
<Project Name>
User enter data to required fields. Booking successfully, message
2
User selects “Route” displayed.
System generates a booking detail
3
recept and display.
Alternate Course of Action
S# Actor Action System Response
Prompt user to enter all required
1 if required fields left by user
fields
If booking option is not visible at Reload the home page
2 home page Search the option in search bar.
Adopted Methodology:
Railway management system can be developed by using waterfall model/Agile method which is a popular version
of development life cycle model for software engineering. It describes a development method that is linear and
sequential. It has distinct goals for each phase of development. In this model once, a phase of development is
completed, there is no turning back, the development proceeds to the next phase. The advantage of this model is
that it allows for managerial control.
Nonfunctional Requirements
Performance Requirements
• Response time: The system will give responses within 1 second after checking the patient information and
other information.
• Capacity: The system must support 1000 people at a time.
• User interface: User interface screen will response within 5 seconds.
• Conformity: The system must conform to the Microsoft accessibility
Safety Requirements
If there is extensive damage to a wide portion of the database due to catastrophic failure, such as a disk
crash, the recovery method restores a past copy of the database that was backed up to archival storage and
reconstructs a more current state by reapplying or redoing the operations of committed transactions from
the backed-up log, up to the time of failure.
Security Requirements
All the administrative and user have unique logins so system can understand who is login in to system
right now no intruders allowed except system administrative nobody cannot change record and valuable
data.
Additional Software Quality Attributes
The Quality of the system is maintained in such a way so that it can be very user-friendly. The software quality
attributes are assumed as under:
• AVAILABILITY: The system shall be available all the time.
• CORRECTNESS: A bug free software which fulfill the correct need/requirements of the client.
<Project Name>
• MAINTAINABILITY: The ability to maintain, modify information and update fix problems of the
system
• USABILITY: software can be used again and again without distortion.
• ACCESSIBILITY: Administrator and many other users can access the system but the access level is
controlled for each user according to their work scope.
• ACCURACY: The reliability on the information/output. Can depend/be sure of the outcome.
• STABILITY: The system outcome/output won’t change time to time. Same output will be given always
for a given input
• New idea generate: The system shall be availabl after the booking tickets about your destination
recommended the Resturant and hotel and tell the about weather all the time
Other Requirements
A degraded mode of operation should be possible in which each system can operate independently of central
scheduling. The software shall have failure and error recognition codes acting as a safety net, thus keeping the
software from performing any major catastrophic functions.
Revised Project Plan
Task Name Duration Start Date End Date Status
Idea 12 Days 16 November 20 November Finished
2022 2022
Scope 5 Days 30 November 5 December Finished
2022
Functional and Non- 5 Days 7 December 12 December Finished
Functional Requirements 2022 2022
Use Case/ Activity 7 Days 12 December 19 December Finished
Diagrams 2022 2022
Usage Scenarios 16 Days 2 January 2023 18 January 2023 Finished
Work Plan 8 Days 20 March 2023 28 March 2023 In progress
Design Phase 7 Days 3 April 2023 10 April 2023 In progress
Database Design 14 Days 12 April 2023 26 April 2023 In progress
Architectural Design 7 Days 1 May 2023 8 May 2023 In progress
Detailed Design 9 Days 10 May 2023 19 May 2023 In progress
User Interface 10 Days 20 May 2023 30 May 2023 In progress
Testing 3 Days 1 June 2023 3 June 2023 In progress
Final Results 7 Days 5 June 2023 12 June 2023 In progress
<Project Name>
References:
<List all books, conference papers, journal articles, websites, etc. used in preparing the content of this SRS.
Provide enough information so that the reader could access a copy of each reference, including title, author,
volume/edition number, page number(s), and publication year. Mention complete URLs for websites.>
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may
wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms
specific to a single project in each SRS.>
