SRS documentation Online railway
Content
IT-2
BATCH-B
120410116060
RAILWAY RESERVATION
SYSTEM
Submitted To :
PARTH A. BHATT
Submitted By:
HARSH SHAH(120410116038)
VISHWA SHINDE(120410116056)
KAUSHAL SHAH(120410116060)
JAYESH HOTCHANDANI(120410116066)
1
IT-2
BATCH-B
Table of content
1. Introduction
1.1 Purpose
1.2 Document Conventions
1.3 Intended Audience and
Reading Suggestions
1.4 Definations,Acronyms and
Abbreviations
1.5 Scope
1.6 Reference
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 Memory Constrains
2.7 Operations
2.8 User Interface
2.9 Hardware Interface
2.10Software Interfaces
2.11Assumptions, Dependencies &
Limitations
3.System Features
3.1 Description & Priority
3.2 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
2
120410116060
IT-2
BATCH-B
3.1.13
3.1.14
3.1.15
3.1.16
3.1.17
Pricing Module
Availability Module
Branch Module
Report Module
Access Type
4.External Interface Requirements
4.1 User Interface
4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communication Interface
5.Non-functional Requirements
5.1 Performance Requirements
5.2 Safety Requirements
5.3 Security Requirements
5.4 Design Constraint
3
120410116060
IT-2
BATCH-B
120410116060
1. INTRODUCTION
1.1 PURPOSE
The purpose of this source is to describe the railway reservation system which provides the train
timing details,reservation,,billing,cancelaation on various types of reservation namely.
Confirm Reservation for confirm Seat.
Reservation against Cancellation
Waiting list Reservation.
Online Reservation.
Tatkal Reservation
1.2 DOCUMENT CONVENTIONS:
main heading:Bold
not applicable
1.3 INTENDED AUDIENCE AND READING SUGGESTIONS:
the different types of readers are
customer
Developers
Management
Passengers
Counter clerk
1.4 DEFINATIONS,ACRONYMS AND ABBREVIATIONS
NTES- National Train Enquiry System
IVRS-Interactive Voice Response System
PRS-Passenger Resevation System
consist of
train details
reservation form
billing
cancellation
1.5 SCOPE
Freight Revenue enhancement.
Passenger Revenue enhancement.
Improved & optimized service.
This project designs and implements RRS to fulfill all the vision statements. Supported by a
well designed database, all available air train information is integrated together and can be
accessed easily through a single point. A friendly user interface is provided so that various
combinations of search criteria can be fetched from user and generates corresponding database
search statements. RRS provided both customer and administration interfaces with the latter used
for administration purposes. If time permits, RRS will support frequent user registration and
personal information management.
4
IT-2
BATCH-B
1.6 REFERNCES
www.scribd.com
www.yatra.com
www.google.com
www.info.com
http://www.cise.ufl.edu/~mschneid/Teaching/COP5725_Fall2008/project_spec.pdf
5
120410116060
IT-2
BATCH-B
120410116060
2. OVERALL DESCRIPION
2.1 PRODUCT PERSPECTIVE
It enables us to maintain the railway train details like their timings, number of seat available
and reservation billing and cancelling the tickets.
2.2 PRODUCT FUNCTIONS:
OMBS will have two users interface layers,first one is guest interface and the second
one is Train Management Interface.
2.3 GUEST INTERFACE:
View Train Details
Search Train
Create Account
Customer Login
Purchase Ticket
Purchase History
2.4 TRAIN MANAGEMENT INTERFACE:
Login Function
Staff Module
reservation Module
Ticket Module
Membership Module
Train Module
Pricing Module
Availability Module
Branch Module
report module
Access Type
2.5 OPERATING ENVIRONMENT
The OS
Windows NT
Linux
Windows XP
Windows 98
2.6 MEMORY CONSTRAINTS
A maximum of 42 laces hits per day have been recorded.
2.7 OPERATIONS:
6
IT-2
BATCH-B
120410116060
any
reservation counter from 8 am to 8 pm.
prior to 60 days of journey.
One form for 6 persons only.
Reserved ticket done through pre defined Logic.
To save time and queues agents is others guides.
2.8 User Interfaces
The system shall provide a help (explanation) link from each displayed HTML page to
explain how to use that page.
The Web page of RRS shall permit complete navigation, train selection, ticket reservation
and ticket/train information query view using keyboard and mouse combinations.
2.9 Hardware Interfaces
No hardware interface specified for RRS.
2.10 Software Interfaces
Train/ticket inventory/database system:
The RRS should transmit and store the detailed properties (quantities, train number,
departure/return time/date, seat, location) of ticket items for the potential requests from
users.
(2)
The Train/ticket inventory/database system should keep updated information about the
availability of ticket and train information to determine whether a requested reservation is
available or not.
(3)
When the RRS make the query about ticket information with constrains, Train/ticket
inventory/database system should provide all the information that satisfy the query.
(4)
The Train/ticket inventory/database system should accept information update operation
flows
coming from the administrator interface system.
(1)
User query/view system:
The user query/view system should communicate with Train/ticket inventory/database
system through a programming interface for the following operations.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
To allow a user post various query about ticket information available at present. User can use
any combination available
To show the user the resulting list of query. This should allow users to further sort the list by
subfields of the ticket information (e.g. price). The view should be friendly and flexible.
To allow a user place a reservation
To detect the conflict if a user placed two incompatible reservations.
To allow a user view his/her reservation
To allow user modify his/her reservation
To allow user to manage his/her account in RRS
7
IT-2
BATCH-B
120410116060
2.11 ASSUMPTIONS,DEPENDENCIES AND LIMITATIONS
AS-1: Users of RRS are assumed to have a computer with internet access.
AS-2: Credit and debit card authorization services are assumed to be
available.
DE-1: RRS has collaboration with every airline’s databases thus it must be able to communicate
with these systems. Also it has to obey airline’s business rules.
8
IT-2
BATCH-B
120410116060
3. SYSTEM FEATURES
3.1 DESCRIPTION AND PRIORITY
The search feature allows the user to search for an railline train on a variety of dimensions.
3.2 FUNCTIONAL REQUIREMENTS
Req #
REQ-S1
REQ-S2
REQ-S3
REQ-S4
REQ-S5
Description
Priority
The user will be able to search for trains through
a
[Priority = High]
standardized screen. Advanced options will be
available
by clicking appropriate links.
Through the standard trains search method the user will
be
[Priority = Medium]
able to search one-way, round-trip, or multi-destination
trains. The screen by default will display options
for
searching round trip trains. The search criteria can
be
modified by the user by selecting one-way and
multidestination options which would be displayed on a new
window.
Through the standard trains search method the user
shall be
[Priority = High]
able to specify the departure and return date of their
trains.
Through an advanced train search method the user
shall be
able to specify the arrival train times.
The standard train search method will enable the user
to
search both precise dates as well as a range of arrival
and
departure dates.
[Priority = Medium]
[Priority = Medium]
REQ-S6
The standard train search method will allow the user to [Priority = Low]
specify a preferred railline. This is optional, i.e. the
user
may or may not specify the railline of preference.
REQ-S7
The user will have the option to express a preference of [Priority = Low]
9
IT-2
REQ-S8
REQ-S9
REQ-S10
REQ-S11
REQ-S12
REQ-S13
BATCH-B
120410116060
non-stop train; otherwise both non-stop trains and
trains
with stopovers will be treated equally.
User can only search for a train in the future and within
one
[Priority = High]
year of the current date. (The cutoff time can be
applied,
i.e. user cannot make the reservation for the train
which
will take off in 2 hours.)
The user to select any hour on the hour (i.e. trains at
12am,
[Priority = High]
11am, 2pm etc.).
When the user is searching for a train he may select
one of
[Priority = Medium]
the following preset time ranges: Morning,
Afternoon,
Evening, Night, or Anytime.
User should be able to search by Train number and
railline.
[Priority = Low]
This will allow him to see the particular train for the
particular railline.
The user may specify anywhere from 1 (one) to 6 (six) [Priority = High]
passengers. Passengers will not be treated separately as
minors or seniors.
Any error in entry of the system will stop the system from
processing the search. An error message will be presented
to the user.
GUEST INTERFACE:
[Priority = High]
View Train Details
The system shall enable customer or visitor to view list of trains.
Search Train
the system shall have search function.customer can search train based on source and
destination station details with date and time.
Create Account
the system shall function to create an account.the system shall record all the following
data from the customer.
a. User name
b. password
c. password confirmation
d. first name
e. last name
f. identify card number
g. address
10
IT-2
BATCH-B
120410116060
h. zip code
i. city
j. state
k. country
l. mobile no.
Customer Login
the system shall have customer login functions,once activated,customer can login using
username and password.
the syatem shall have username and password recovery function.
Purchase Ticket
the system shall enable customer to purchase the train ticket from guest
interface. the system shall display all the train details.
the system shall display the date time and price of the ticket.
the system shall have book now button. when book now button is pressed,the system
shall prompt customer to login or register account.
the system shall allow customer who have login only to continue to purchase ticket.if
customer haven’t login,prompt customer to login and create account.
Purchase History
the customer can watch all the purchase history from this module.
TRAIN MANAGEMENT INTERFACE:
Login Function
The system should allow only staff username and passwd to access the
system. access to the module determined by acc type and branch office
Location.
Staff Module
the system shall allow system administration only to access the module.System
administration shall login first to access this module.
the system shall aalow the system administration to add staff,update staff and delete
staff. the system shall record all the following details:
a. Staff Username
b. password
c. Account
d. First Name
e. Last Name
f. Address
g. City
h. State
Reservation Module
the system shall allow counter clerk, station manager and station supervisor of the particular
station to access this module.they should login first.
the
system shall limit the access to branch level only.
the system shall display the seating arrangements for
customers. the system shall display the total amount of
ticket.
11
IT-2
BATCH-B
120410116060
the system shall allow station manager or clerk to check the details.
Ticket Module
Ticket booking:
The Ticket Booking is user (Employee of Railway Dept.) side module. The user can book
the ticket using this module. The user should follow the steps for the ticket booking.
First you should select the Source And Destination.
Next, you should select the Date. While the date textbox got focus, the calendar will display.
By clicking the calendar, the date will be selected. And you can’t select the yesterday and
before date.
a) Select the Quota (General or Tatkaal).
b) Click the Find button to find the trains which are available.
Note:
If you select the Tatkaal Quota and the date is day after tomorrow in the sense, you can’t book
the ticket for Tatkaal Quota for that day. The Tatkaal Quota will enable only today and tomorrow
only.
e) After clicking the find button, the available train list will be displayed in the flexgrid.
f) By clicking the train number or train name in the flex grid, the “Route” button enabled. By
clicking the route button, the corresponding train route, timings, and kms.
g) By clicking the class column to the corresponding train whichever you want to travel, then
“Book” button will enable.
h) Click the “Book” button to enter the Name, Age, Sex and Berth.
i) After Enter the details, Click the Proceed Button.
j) The frame will display the overall details like Source, Destination, Travel Date, Booked
Date, Total Members, Quota and Total Fare.
k) Click the “Confirm” Button to confirm the details. Then only the Booking details will
be stored and PNR Number will be generated
Ticket cancellation:
The Ticket Canceling is also user (Employee of Railway Dept.) side module. The user can
cancel the ticket using this module. The user should follow the steps for the ticket Cancel.
a) Enter the PNR Number in the Textbox and Click Find.
b) It will show the details like Train No., Train Name, Booked Date, Travel Date, Source,
Destination, Class, Quota, Total Fare, Kms in the Frame.
c) It also shows the passenger names, Age, Sex, Berth, Class, Fare and status in the flex grid.
d) Click the Name in the flex grid which you want to cancel and where the status is “Booked”.
e) Click the “Cancel” Button to cancel the ticket.
Membership Module
the system shall allow station master and branch manager and branch suoervisor of the
particular staioon to access this module.
the system shall record the following data for the customer:
a. first name
b. last name
c. address
12
IT-2
BATCH-B
120410116060
d. city
e. state
f. country
Train Module
the system shall allow head office personnel only to add and update new train timing details
in the system.Head office personnle shall login first to acces this module.
the system shall record the following details of each train
g. Train Name
b. Train timings
c. Train description,duration on each station
d. Train stations
Pricing Module
the system shall allow branch manager and branch supervisor of the branch only to access
this module.
the system shall limit access to branch level only.
the system shall allow branch manager to add pricing tables and deleting pricing
tables. the prising is based on adult or children or senior citizen parameters.
Availability Module
the system shall allow branch manager and branch supervisor of the branch only to access
this module.
the system shall limit access to branch level only.
the system shall allow branch manager to add availability tables and deleting availabilty
tables.
the availabilty is based on adult or children or senior citizen parameters.
Report Module
The system shall generate report based on account type.
a. Branch Report
b. Head Office Report
c. Customer Refund List
Access Type
access to the modules is determine by staff account type and branch office
location. types of account are as follow:
Counter Clerk
Station Master
Station supervisor
Head office
Personnel Ticket
Checker System
Administrator
13
IT-2
BATCH-B
4. EXTERNAL INTERFACE REQUIREMENT
4.1 USER INTERFACES
keyboard,mouse,printer
4.2 HARDWARE INTERFACES
SERVER SIDE
Operating System: Windows 7
Processor:Intel i5
Memory: 4 GB
Hard Drive Capacity: 750GB
CLIENT SIDE
Operating
System:Windows XP, Windows Vista or Windows7
Browser:Internet
Explorer and above.Mozilla or Google Chrome.
Memory:512 MB
4.3 SOFTWARE INTERFACES
Database
Microsoft office Access
Web Server
Apache server version 2.2.6
Programing Languages
.net
Java
4.4 COMMUNICATION INTERFACES
Dial Up Modem
Broadband Internet
14
120410116060
IT-2
BATCH-B
120410116060
5. NON FUNCTIONAL REQUIREMENTS
5.1 PERFORMANCE REQUIREMENTS
PE-1: The system shall accommodate 400 users during the peak usage time window of 8:00am to
10:00am local time, with estimated average session duration of 45 minutes.
PE-2: All Web pages generated by the system shall be fully downloadable in no more than 10 seconds
over a 40KBps modem connection.
PE-3: Responses to queries shall take no longer than 10 seconds to load onto the screen after the user
submits the query.
PE-4: The system shall display confirmation messages to users within 4 seconds after the user submits
information to the system.
variety of compartments based on comfort:
1. AC first class
2. AC sleeper
3. First class
4. AC three tier
5. sleeper class
6. Ordinary chair car
types of concerns and complexicities:
1. 44 types of quotas
2. 8 types of trains
3. 9 types of classes
4. 162 types of concessions
5. 127 types of bogies
5.2 SAFETY REQUIREMENTS
No safety requirements have been identified.
5.3 SECURITY REQUIREMENTS
SE-1: Users shall be required to log in to the RRS for their own reservation information and
modification with e-mail address and password.
SE-2: The system shall permit only authorized members who are on the list of authorized Menu
Managers to do administrator’s task.
SE-3: The system shall permit customers to view only their own previously placed orders, not orders
placed by other customers.
5.4 DESIGN CONSTRAINT
The system shall be web based system that runs on different type of browsers such as Internet
Explorer,Mozilla,Google chrome.
There are a number of factors in the client’s environment that may restrict the choices of a designer.
Such factors include standards that must be followed, resource limits, operating environment,
reliability and security requirements and policies that may have an impact on the design of the
15
IT-2
BATCH-B
120410116060
system. An SRS (Software Requirements Analysis and Specification) should identify and specify all
such constraints.
Standard Compliance: - This specifies the requirements for the standards the system must follow.
The standards may include the report format and accounting properties.
Hardware Limitations :- The software may have to operate on some existing or predetermined
hardware, thus imposing restrictions on the design. Hardware limitations 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 constraint 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 for
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.
16
BATCH-B
120410116060
RAILWAY RESERVATION
SYSTEM
Submitted To :
PARTH A. BHATT
Submitted By:
HARSH SHAH(120410116038)
VISHWA SHINDE(120410116056)
KAUSHAL SHAH(120410116060)
JAYESH HOTCHANDANI(120410116066)
1
IT-2
BATCH-B
Table of content
1. Introduction
1.1 Purpose
1.2 Document Conventions
1.3 Intended Audience and
Reading Suggestions
1.4 Definations,Acronyms and
Abbreviations
1.5 Scope
1.6 Reference
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 Memory Constrains
2.7 Operations
2.8 User Interface
2.9 Hardware Interface
2.10Software Interfaces
2.11Assumptions, Dependencies &
Limitations
3.System Features
3.1 Description & Priority
3.2 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
2
120410116060
IT-2
BATCH-B
3.1.13
3.1.14
3.1.15
3.1.16
3.1.17
Pricing Module
Availability Module
Branch Module
Report Module
Access Type
4.External Interface Requirements
4.1 User Interface
4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communication Interface
5.Non-functional Requirements
5.1 Performance Requirements
5.2 Safety Requirements
5.3 Security Requirements
5.4 Design Constraint
3
120410116060
IT-2
BATCH-B
120410116060
1. INTRODUCTION
1.1 PURPOSE
The purpose of this source is to describe the railway reservation system which provides the train
timing details,reservation,,billing,cancelaation on various types of reservation namely.
Confirm Reservation for confirm Seat.
Reservation against Cancellation
Waiting list Reservation.
Online Reservation.
Tatkal Reservation
1.2 DOCUMENT CONVENTIONS:
main heading:Bold
not applicable
1.3 INTENDED AUDIENCE AND READING SUGGESTIONS:
the different types of readers are
customer
Developers
Management
Passengers
Counter clerk
1.4 DEFINATIONS,ACRONYMS AND ABBREVIATIONS
NTES- National Train Enquiry System
IVRS-Interactive Voice Response System
PRS-Passenger Resevation System
consist of
train details
reservation form
billing
cancellation
1.5 SCOPE
Freight Revenue enhancement.
Passenger Revenue enhancement.
Improved & optimized service.
This project designs and implements RRS to fulfill all the vision statements. Supported by a
well designed database, all available air train information is integrated together and can be
accessed easily through a single point. A friendly user interface is provided so that various
combinations of search criteria can be fetched from user and generates corresponding database
search statements. RRS provided both customer and administration interfaces with the latter used
for administration purposes. If time permits, RRS will support frequent user registration and
personal information management.
4
IT-2
BATCH-B
1.6 REFERNCES
www.scribd.com
www.yatra.com
www.google.com
www.info.com
http://www.cise.ufl.edu/~mschneid/Teaching/COP5725_Fall2008/project_spec.pdf
5
120410116060
IT-2
BATCH-B
120410116060
2. OVERALL DESCRIPION
2.1 PRODUCT PERSPECTIVE
It enables us to maintain the railway train details like their timings, number of seat available
and reservation billing and cancelling the tickets.
2.2 PRODUCT FUNCTIONS:
OMBS will have two users interface layers,first one is guest interface and the second
one is Train Management Interface.
2.3 GUEST INTERFACE:
View Train Details
Search Train
Create Account
Customer Login
Purchase Ticket
Purchase History
2.4 TRAIN MANAGEMENT INTERFACE:
Login Function
Staff Module
reservation Module
Ticket Module
Membership Module
Train Module
Pricing Module
Availability Module
Branch Module
report module
Access Type
2.5 OPERATING ENVIRONMENT
The OS
Windows NT
Linux
Windows XP
Windows 98
2.6 MEMORY CONSTRAINTS
A maximum of 42 laces hits per day have been recorded.
2.7 OPERATIONS:
6
IT-2
BATCH-B
120410116060
any
reservation counter from 8 am to 8 pm.
prior to 60 days of journey.
One form for 6 persons only.
Reserved ticket done through pre defined Logic.
To save time and queues agents is others guides.
2.8 User Interfaces
The system shall provide a help (explanation) link from each displayed HTML page to
explain how to use that page.
The Web page of RRS shall permit complete navigation, train selection, ticket reservation
and ticket/train information query view using keyboard and mouse combinations.
2.9 Hardware Interfaces
No hardware interface specified for RRS.
2.10 Software Interfaces
Train/ticket inventory/database system:
The RRS should transmit and store the detailed properties (quantities, train number,
departure/return time/date, seat, location) of ticket items for the potential requests from
users.
(2)
The Train/ticket inventory/database system should keep updated information about the
availability of ticket and train information to determine whether a requested reservation is
available or not.
(3)
When the RRS make the query about ticket information with constrains, Train/ticket
inventory/database system should provide all the information that satisfy the query.
(4)
The Train/ticket inventory/database system should accept information update operation
flows
coming from the administrator interface system.
(1)
User query/view system:
The user query/view system should communicate with Train/ticket inventory/database
system through a programming interface for the following operations.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
To allow a user post various query about ticket information available at present. User can use
any combination available
To show the user the resulting list of query. This should allow users to further sort the list by
subfields of the ticket information (e.g. price). The view should be friendly and flexible.
To allow a user place a reservation
To detect the conflict if a user placed two incompatible reservations.
To allow a user view his/her reservation
To allow user modify his/her reservation
To allow user to manage his/her account in RRS
7
IT-2
BATCH-B
120410116060
2.11 ASSUMPTIONS,DEPENDENCIES AND LIMITATIONS
AS-1: Users of RRS are assumed to have a computer with internet access.
AS-2: Credit and debit card authorization services are assumed to be
available.
DE-1: RRS has collaboration with every airline’s databases thus it must be able to communicate
with these systems. Also it has to obey airline’s business rules.
8
IT-2
BATCH-B
120410116060
3. SYSTEM FEATURES
3.1 DESCRIPTION AND PRIORITY
The search feature allows the user to search for an railline train on a variety of dimensions.
3.2 FUNCTIONAL REQUIREMENTS
Req #
REQ-S1
REQ-S2
REQ-S3
REQ-S4
REQ-S5
Description
Priority
The user will be able to search for trains through
a
[Priority = High]
standardized screen. Advanced options will be
available
by clicking appropriate links.
Through the standard trains search method the user will
be
[Priority = Medium]
able to search one-way, round-trip, or multi-destination
trains. The screen by default will display options
for
searching round trip trains. The search criteria can
be
modified by the user by selecting one-way and
multidestination options which would be displayed on a new
window.
Through the standard trains search method the user
shall be
[Priority = High]
able to specify the departure and return date of their
trains.
Through an advanced train search method the user
shall be
able to specify the arrival train times.
The standard train search method will enable the user
to
search both precise dates as well as a range of arrival
and
departure dates.
[Priority = Medium]
[Priority = Medium]
REQ-S6
The standard train search method will allow the user to [Priority = Low]
specify a preferred railline. This is optional, i.e. the
user
may or may not specify the railline of preference.
REQ-S7
The user will have the option to express a preference of [Priority = Low]
9
IT-2
REQ-S8
REQ-S9
REQ-S10
REQ-S11
REQ-S12
REQ-S13
BATCH-B
120410116060
non-stop train; otherwise both non-stop trains and
trains
with stopovers will be treated equally.
User can only search for a train in the future and within
one
[Priority = High]
year of the current date. (The cutoff time can be
applied,
i.e. user cannot make the reservation for the train
which
will take off in 2 hours.)
The user to select any hour on the hour (i.e. trains at
12am,
[Priority = High]
11am, 2pm etc.).
When the user is searching for a train he may select
one of
[Priority = Medium]
the following preset time ranges: Morning,
Afternoon,
Evening, Night, or Anytime.
User should be able to search by Train number and
railline.
[Priority = Low]
This will allow him to see the particular train for the
particular railline.
The user may specify anywhere from 1 (one) to 6 (six) [Priority = High]
passengers. Passengers will not be treated separately as
minors or seniors.
Any error in entry of the system will stop the system from
processing the search. An error message will be presented
to the user.
GUEST INTERFACE:
[Priority = High]
View Train Details
The system shall enable customer or visitor to view list of trains.
Search Train
the system shall have search function.customer can search train based on source and
destination station details with date and time.
Create Account
the system shall function to create an account.the system shall record all the following
data from the customer.
a. User name
b. password
c. password confirmation
d. first name
e. last name
f. identify card number
g. address
10
IT-2
BATCH-B
120410116060
h. zip code
i. city
j. state
k. country
l. mobile no.
Customer Login
the system shall have customer login functions,once activated,customer can login using
username and password.
the syatem shall have username and password recovery function.
Purchase Ticket
the system shall enable customer to purchase the train ticket from guest
interface. the system shall display all the train details.
the system shall display the date time and price of the ticket.
the system shall have book now button. when book now button is pressed,the system
shall prompt customer to login or register account.
the system shall allow customer who have login only to continue to purchase ticket.if
customer haven’t login,prompt customer to login and create account.
Purchase History
the customer can watch all the purchase history from this module.
TRAIN MANAGEMENT INTERFACE:
Login Function
The system should allow only staff username and passwd to access the
system. access to the module determined by acc type and branch office
Location.
Staff Module
the system shall allow system administration only to access the module.System
administration shall login first to access this module.
the system shall aalow the system administration to add staff,update staff and delete
staff. the system shall record all the following details:
a. Staff Username
b. password
c. Account
d. First Name
e. Last Name
f. Address
g. City
h. State
Reservation Module
the system shall allow counter clerk, station manager and station supervisor of the particular
station to access this module.they should login first.
the
system shall limit the access to branch level only.
the system shall display the seating arrangements for
customers. the system shall display the total amount of
ticket.
11
IT-2
BATCH-B
120410116060
the system shall allow station manager or clerk to check the details.
Ticket Module
Ticket booking:
The Ticket Booking is user (Employee of Railway Dept.) side module. The user can book
the ticket using this module. The user should follow the steps for the ticket booking.
First you should select the Source And Destination.
Next, you should select the Date. While the date textbox got focus, the calendar will display.
By clicking the calendar, the date will be selected. And you can’t select the yesterday and
before date.
a) Select the Quota (General or Tatkaal).
b) Click the Find button to find the trains which are available.
Note:
If you select the Tatkaal Quota and the date is day after tomorrow in the sense, you can’t book
the ticket for Tatkaal Quota for that day. The Tatkaal Quota will enable only today and tomorrow
only.
e) After clicking the find button, the available train list will be displayed in the flexgrid.
f) By clicking the train number or train name in the flex grid, the “Route” button enabled. By
clicking the route button, the corresponding train route, timings, and kms.
g) By clicking the class column to the corresponding train whichever you want to travel, then
“Book” button will enable.
h) Click the “Book” button to enter the Name, Age, Sex and Berth.
i) After Enter the details, Click the Proceed Button.
j) The frame will display the overall details like Source, Destination, Travel Date, Booked
Date, Total Members, Quota and Total Fare.
k) Click the “Confirm” Button to confirm the details. Then only the Booking details will
be stored and PNR Number will be generated
Ticket cancellation:
The Ticket Canceling is also user (Employee of Railway Dept.) side module. The user can
cancel the ticket using this module. The user should follow the steps for the ticket Cancel.
a) Enter the PNR Number in the Textbox and Click Find.
b) It will show the details like Train No., Train Name, Booked Date, Travel Date, Source,
Destination, Class, Quota, Total Fare, Kms in the Frame.
c) It also shows the passenger names, Age, Sex, Berth, Class, Fare and status in the flex grid.
d) Click the Name in the flex grid which you want to cancel and where the status is “Booked”.
e) Click the “Cancel” Button to cancel the ticket.
Membership Module
the system shall allow station master and branch manager and branch suoervisor of the
particular staioon to access this module.
the system shall record the following data for the customer:
a. first name
b. last name
c. address
12
IT-2
BATCH-B
120410116060
d. city
e. state
f. country
Train Module
the system shall allow head office personnel only to add and update new train timing details
in the system.Head office personnle shall login first to acces this module.
the system shall record the following details of each train
g. Train Name
b. Train timings
c. Train description,duration on each station
d. Train stations
Pricing Module
the system shall allow branch manager and branch supervisor of the branch only to access
this module.
the system shall limit access to branch level only.
the system shall allow branch manager to add pricing tables and deleting pricing
tables. the prising is based on adult or children or senior citizen parameters.
Availability Module
the system shall allow branch manager and branch supervisor of the branch only to access
this module.
the system shall limit access to branch level only.
the system shall allow branch manager to add availability tables and deleting availabilty
tables.
the availabilty is based on adult or children or senior citizen parameters.
Report Module
The system shall generate report based on account type.
a. Branch Report
b. Head Office Report
c. Customer Refund List
Access Type
access to the modules is determine by staff account type and branch office
location. types of account are as follow:
Counter Clerk
Station Master
Station supervisor
Head office
Personnel Ticket
Checker System
Administrator
13
IT-2
BATCH-B
4. EXTERNAL INTERFACE REQUIREMENT
4.1 USER INTERFACES
keyboard,mouse,printer
4.2 HARDWARE INTERFACES
SERVER SIDE
Operating System: Windows 7
Processor:Intel i5
Memory: 4 GB
Hard Drive Capacity: 750GB
CLIENT SIDE
Operating
System:Windows XP, Windows Vista or Windows7
Browser:Internet
Explorer and above.Mozilla or Google Chrome.
Memory:512 MB
4.3 SOFTWARE INTERFACES
Database
Microsoft office Access
Web Server
Apache server version 2.2.6
Programing Languages
.net
Java
4.4 COMMUNICATION INTERFACES
Dial Up Modem
Broadband Internet
14
120410116060
IT-2
BATCH-B
120410116060
5. NON FUNCTIONAL REQUIREMENTS
5.1 PERFORMANCE REQUIREMENTS
PE-1: The system shall accommodate 400 users during the peak usage time window of 8:00am to
10:00am local time, with estimated average session duration of 45 minutes.
PE-2: All Web pages generated by the system shall be fully downloadable in no more than 10 seconds
over a 40KBps modem connection.
PE-3: Responses to queries shall take no longer than 10 seconds to load onto the screen after the user
submits the query.
PE-4: The system shall display confirmation messages to users within 4 seconds after the user submits
information to the system.
variety of compartments based on comfort:
1. AC first class
2. AC sleeper
3. First class
4. AC three tier
5. sleeper class
6. Ordinary chair car
types of concerns and complexicities:
1. 44 types of quotas
2. 8 types of trains
3. 9 types of classes
4. 162 types of concessions
5. 127 types of bogies
5.2 SAFETY REQUIREMENTS
No safety requirements have been identified.
5.3 SECURITY REQUIREMENTS
SE-1: Users shall be required to log in to the RRS for their own reservation information and
modification with e-mail address and password.
SE-2: The system shall permit only authorized members who are on the list of authorized Menu
Managers to do administrator’s task.
SE-3: The system shall permit customers to view only their own previously placed orders, not orders
placed by other customers.
5.4 DESIGN CONSTRAINT
The system shall be web based system that runs on different type of browsers such as Internet
Explorer,Mozilla,Google chrome.
There are a number of factors in the client’s environment that may restrict the choices of a designer.
Such factors include standards that must be followed, resource limits, operating environment,
reliability and security requirements and policies that may have an impact on the design of the
15
IT-2
BATCH-B
120410116060
system. An SRS (Software Requirements Analysis and Specification) should identify and specify all
such constraints.
Standard Compliance: - This specifies the requirements for the standards the system must follow.
The standards may include the report format and accounting properties.
Hardware Limitations :- The software may have to operate on some existing or predetermined
hardware, thus imposing restrictions on the design. Hardware limitations 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 constraint 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 for
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.
16
