FUNCTIONAL REQUIREMENT DOCUMENT

CONTENTS

1. DOCUMENT VERSION CONTROL LIST

2. DISTRIBUTION LIST
3. BUSINESS RULES

4. SYSTEM RULES

5. CONTROL FLOW

6. PURPOSE

7. PROJECT BACKGROUND

8. PROJECT OBJECTIVE

9. BUSINESS REQUIREMENTS

9.1 STAKEHOLDER REQUIREMENST

10. CONSTRAINTS & ASSUMPTIONS

11. USE CASE DIAGRAMS

11.1 ACTOR SPECIFICATION USE CASE DIAGRAM

11.2 USE CASE SPECIFICATIONS

12. ACTIVITY DIAGRAM

12.1 PROCESS SPECIFICATION ACTIVITY

DIAGRAM

12.2 ACTIVITY SPECIFICATIONS

12.2.1 BASIC FLOW

 12.2.2 ALTERNATE FLOW

12.2.3 EXCEPTIONAL FLOW

13. FUNCTIONAL REQUIREMENTS

14. NON FUNCTINAL REQUIREMNTS

15. PROTOTYPING

16. MASTER TABLES

17. NOTES
1. DOCUMENT VERSION CONTROL LIST

DATE VERSION Author Description

NUMBER

13/02/2020 0.1 xxxxx

16/02/2020 0.2 xxxxx

19/02/2020 0.3 xxxxx

2. DISTIBUTION LIST

ROLE NAME VERSION DISTRIBUTION DATE

PURPOSE

PROJECT XXXXX 0.1 ***** 13/02/2020

SPONCER

BUSINESS XXXXX 0.2 ***** 13/02/2020

OWNER

PROJECT XXXXX 0.3 ***** 14/02/2020

MANAGER

SYSTEM XXXXX 0.4 ***** 20/02/2020

ARCHITECT

DEVELOPEMENT XXXXX 0.5 ***** 27/02/2020

LEAD

3. BUSINESS RULES

1. Provide better customer service

2. Improve employee training

 3. Increase efficiency

4. Increase profit margin

4. SYSTEM RULES

1. Single page/quick book services are not available between 8am and 12am

2. Only 6 tickets can be booked in a month from a single user ID

3. If the user is Adhar verified, he can book 12 tickets in a month

4. Once can book only 2 tickets during hours between 8am and 10am

5. A user can have only one login session at a time

6. The standard time to fill up passengers details in 25sec

7. A man will get 10sec to make the payments

8. The mini input time for captcha on passengers details page and payment page is 5 sec

9. To net banking, otp system has been made mandatory for all banks and users

10. Tickets brokers or agents are allowed to reserve tickets between 8am to 8.30 am,10am to

10.30am and 11am to 11.30 am

5. CONTROL FLOW

TRAIN GENERATE

MGT TRAIN TICKET

BOOKING GENERATE
BOOKING
MGT

TICKET GENERATE
RAILWAY TRAIN REPORT
MGT
RESERVATION
SYSTEM
 ROUTE GENERATE ROUT
REPORT
MGT

GENERATE
LOGIN LOGIN REPORT
MGT

SYSTEM GENERATE
SYSTEM USER
USER REPORT
6. PURPPOSE

purpose of RRS is

1. Provides searching facilities based on various factors such as Train, Payment, Tickets, Seat

2. Its tracks the all the information of booking,customer, seat etc

3. Shows the information and description of train, payment

4. Its generates the report on train,booking, customer

5. Provides filter reports on payment, seat, ticket

7. PROJECT BACKGROUND

8. PROJECT OBJECTIVE

The objective of the project is to describe the RRS which provides the train timing

details, reservation, billing, and cancellation on various types of reservation namely,

1. Confirm reservation for confirm seat

2. Reservation against cancellation

3. waiting list reservation

4. Online reservation

5. Tatkal reservation

9. BUSINESS REQUIREMENT

9.1.1 STAKEHOLDER REQUIREMENT

STAKEHOLDER REQUIREMENTS

ACTOR:-1 CUSTOMER 1. Customer login

2. Customer can login using the password
and username
3. System should have system username and
password recovery function

ACTOR:-2 CLERK 1. Clerk login

2. The system should allow the counter clerk

username and password to access the system

3. Clerk should login first to access the system

ACTOR:-3 SYSTEM 1. System administration login

ADMINISTRATION 2. The system should allow the administrator to

login first

3. The system should allow the administrator to

add staff,to update staff and delete staff

10. ASUMPTIONS AND CONSTRAINTS

System also requires some parameters and we assume them as fulfilled before using this, which

ASSUMPTIONS CONSTRAINTS

1. Booking agent will be having his own 1. Less than 1 sec for local transaction

username registered before booking of any

ticket,else they will have to register

 themselves on our website

2. This is software needs booking agent to 2. 3 sec for network transaction

have compute knowledge of RRS and its

working

3. Capable for providing transaction for 22

times per day

11. USECASE DIAGRAM

11.1 ACTOR SPECIFICATION USECASE DIAGRAM

rss use case.vsd

11.2 USECASE SPECIFICATIONS

RSS
DOCUMENT.docx

12. ACTIVITY DIAGRAM

12.1 PROCESS SPECIFICATION ACTIVITY DIAGRAM

 rss activity.vsd

12.2 ACTIVITY SPECIFICATION

12.2.1 BASIC FLOW:- PROCESS STEPS:-

1. Customer should login into the system

2. Check availability of train

3. To book a ticket, customer should fill a

form

4. Customer will fill the form

5. Submit the form

6. Customer will select a payment method

7. Customer choose to pay by credit or

debit or cheque

8. Money will deduct from costumer

account

9. Customer booked the ticket successfully

10. Print the ticket

12.2.2 ALTERNATE FLOW PROCESS STEPS:-

1. If username and password is incorrect

system should prompt the message

 2. If tickets are unavailable, schedule for

another day

3. While customer booking the ticket,

without validate username and password

system should prompt the message

4. Customer choose to pay by credit but

enter the wrong pin

5. In card the cash is insufficient, the system

should prompt the message

6. Unable to print the form because printer

is unavailable or not working

7. To print the form no ink is available,

system should prompt the message

12.2.3 EXCEPTIONAL FLOW PROCESS STEPS:-

1. User can search ticket,view description

of a selected ticket,add ticket, update

ticket and delete ticket

2. It shows the activity of flow of editing,

updating of customer

3. User will able to search and generate

report of payment,booking,train

schedule

4. All objects such as ticket,customer,train

 schedule are interlinked

13. FUNCTIONAL REQUIRMENTS

S.NO REQUEST DESCRIPTION PRIORITY

ID
1 REQ-1 the user will be able to search for train high
through a standardized screen. Advanced
option will be available by clicking
appropriate links
 2 REQ-2 Through the standard trains search method high
the user shall be able to specify the
departure and return date of their trains

3 REQ-3 Through an advanced train search method medium

the user shall be specify the available train
time

4 REQ-4 The standard train search method will low

allow the user to specify a preferred
railine. This optional I,e the user may or
may not specify the railine of preference

5 REQ-5 The user to select any hour on the hours(I.e high

trains at 12am, 11am, 2am etc)

6 REQ-6 When the user is searching for a train he medium

may select one of the following present
train ranges.

7 REQ-7 The user may specify anywhere from 1 to high

6 passengers will not be treated separately
as minors

8 REQ-8 Any user in entry of system will stop the high

system from processing the search. An
error message will be presented to the user

GUEST INTERFACE:-

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, 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 system 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.


TRAIN MANAGEMENT INTERFACE:-

Login Function
The system should allow only staff username and password to access the
system. access to the module determined by account 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 allow 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 the 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
the system should allow the clerk to check 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 text box 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.
c) If you select the Tatkaal Quota and the date is day after tomorrow in the sense, you
can’t book
d) 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 flex
grid.
f) By clicking the train number or train name in the flex grid, the “Route” button
enabled. By clicking the rout 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 Text box 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.

14. NON FUNCTIONAL REQUIREMENTS

S.NO REQUEST ID DESCRIPTION

1 REQ-01 PERFORMANCE REQUIREMENT

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.
2. 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

2 REQ-02 SAFETY REQUIREMENTS

No safety requirements have been

identified.

3 REQ-03 SECURITY REQUIREMENTS

1. Usersshall be required to log in to the

RRS for their own reservation
information and modification with email
address and password.

2. The system shall permit only

authorized members who are on the list
of authorized Menu Managers to do
administrator’s task.

3. The system shall permit customers to

view only their own previously placed
orders, not orders
 4. 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.

15. PROTOTYPING

RSS AUXRE.rp