Railway Reservation System
Railway Reservation System
Railway Reservation System
Software Engineering
Submitted By:-
Railway Reservation
System
Overview
In this modern world of computer and AI(Artificial Intelligence)
almost all the manual system has been replaced. For example
consider amazon for delivery process Swiggy, Zomato for food
delivery and much more. The main advantage of this computerized
world is it reduces human effort and time to a great extent. We are
developing the “Online Railway Reservation System” with the help of
model presentation even with reducing the drawbacks.
Introduction:
Current System
Selection of Model:
A software-process-model is a brief representation of how a
software process works. It helps to develop a software as per under
the functionality of the user keeps a sequence of steps followed for a
good software. A process model is chosen based on the nature of the
project and application, the methods and tools to be used for
functionalities that are required as per user. For the Railway
Reservation system we choose spiral model.
Spiral Model
Spiral Model:-
FUNCTIONAL REQUIREMENTS:
The center of the prerequisite is the depiction of the necessary conduct, which
must be a reasonable and intelligible portrayal of the necessary conduct. This
conduct may come from authoritative or business rule, or it very well might be found
through elicitation meetings with clients, partners and different specialists inside the
association. Programming necessities must be clear, right and unambiguous, explicit
and obvious.
iii). Better and accurate segment configuration to improve execution at top time.
iv). Adaptable help based design will be exceptionally alluring for future
expansion.
Software
Requirements
Specification
for
Table of content
1. Introduction
1.1 Purpose
1.2 Document Conventions
1.3 Intended Audience and Reading Suggestions
1.4 Product Scope
1.5 Scope
2. Overall description
2.1 Product Perspective
2.2 Product Function
2.3 Guest Interface
2.4 Train Management Interface
2.5 Operating Environment
2.6 Operations
2.7 User Interface
2.8 Hardware Interface
2.9 Software Interfaces
Downloaded by kumar gaurav ([email protected])
lOMoARcPSD|37546809
3.System Features
3.1 Functional Requirements
3.1.1 View Train Details
3.1.2 Search Train
3.1.3 Create Account
3.1.4 Customer Login
3.1.5 Purchase Ticket
3.1.6 Purchase History
3.1.7 Login Function
3.1.8 Staff Module
3.1.9 Reservation Module
3.1.10 Ticket Module
3.1.11 Membership Module
3.1.12 Train Module
3.1.13 Pricing Module
3.1.14 Availability Module
3.1.15 Branch Module
3.1.16 Report Module
3.1.17 Access Type
5. Non-functional Requirements
5.1 Performance Requirements
5.2 Safety Requirements
5.3 Security
Requirements
5.4 Design Constraint
1.1 Purpose:
The purpose of Railway Reservation System is to create Reservation, Cancel Reservation, Viewing Train
Information, Viewing Reservation Details, Updating Train Information, Updating Reservation Details and
generate reports.
1.5 Scope:
The extent of venture characterize the undertaking achievability the innovation ,
account , time and assets best characterize in innovation whether the
imperfections can be decreased in the task and up which level monetarily,
climate the general venture cost is moderate. Time portrays whether the
projection completing point will be accomplish on schedule or before time assets
required should be accessible at the pace of cost and time.
2.OVERALL DESCRIPION
2.2 PRODUCT FUNCTIONS: It will have two users interface layers, first one
is user interface and the second one is Train Management Interface.
2.6 OPERATIONS:
Book at ticket counter from 6 am to 11 pm anytimr.
Book well before 50 days of travel.
One-form for 4 people only.
To spare time and long lines of people at the booking counter, online reservation is a great tool.
SYSTEM DESIGN
USECASE ANALYSIS:
Use Case Analysis is an article situated technique for planning data
frameworks by separating necessities into client capacities. Each case is an
exchange or grouping of occasions performed by client. Use cases are concentrated
to figure out what items are needed to achieve them and how they connect with
different articles.
DFD graphically speaking to the capacities, or cycles, which catch, control, store, and convey
information between a framework and its current circumstance and between segments of a framework.
The visual portrayal makes it a decent specialized device among User and System creator. Structure of
DFD permits beginning from a wide outline and extend it to an order of definite charts. DFD has
regularly been utilized because of the accompanying reasons:
Level-0 DFD
LEVEL-1 DFD
Different
Functionalities in the
system
a. Username
b. Password
c. Confirm Password
d. First_name
e. Last_name
f. Card_number
g. Address
h. Zip_code
i. City
j. State
k. Country
l. Mobile_no.
• Sign In: When the user has already registered he/she just needs to enter the username and
password which he/she has created during registration process. The entered details would be requested
from the database server if it is found the user will be logged in to the system and if the entered details
are wrong the database server will not be able to find the details and would prompt invalid details or
record does not exist.
• Book Ticket the system will allow client to buy the train ticket from user interface. the system will
show all the train info. the framework will show the date time and cost of the ticket. the framework will
have confirm booking button. At the instant when confirm booking button is pressed/clicked, the
framework will provoke client to login or enlist account. If customer haven’t login prompt customer to login
and create account. The system will also ask the details such as Train no, Starting destination, Arrival
Destination, Booking Quota(General OR Tatkal), Booking date etc.
• Transaction History the customer can view all the transaction history from this function. All the
payment details like any transaction failed, information about the money etc would be recorded here and
whenever the user requests for it would be sent to the user.
• Staff Login: The system will allow only staff username and password to access the system. Access to
this module is decided by account-type and branch/department address. When the staff has been logged in
the system admin will have given the permission to the staff to perform CRUD operations. CRUD means
Create, Read, Update and Delete. Railway administration will have to login first to get to this module. the
system admin has the permission to add staff, update staff and erase staff. the system will request the
following details to be entered for the record :
a. Staff_Username
b. password
c. Account
d. First_Name
e. Last_Name
f. Address
g. City
h. State
• Reservation Module the system will permit counter representative, station director and station manager
of the specific station to get to this module. They ought to login first. The framework will restrict the
admittance to branch level in sequential manner.
TESTING: