FALL SEMESTER 2021-22

Jth component
REQUIREMENTS ENGINEERING MANAGEMENT -SWE
2003
COURSE FACULTY - Prof. Dr.R. SUJATHA
SLOT - G1
By: LOKESH KUMARAN.R (20MIS0052)
KISHOTH KUMAR.A(20MIS0411)
 RAILWAY RESERVATION SYSTEM
INTRODUCTION:
 Railway reservation system helps the passenger to enquiry about the train available on
basis of source and destination ,booking and cancellation of tickets.
 Railway reservation system is a computerized system of reserving the seats of train
seats in advance.
 Passengers are using this system for travelling long routes. Also nowadays passengers
are using online mode for reservation which is easier than offline mode, because there
may problem occurs like during offline mode that to avoid in standing qeues and not
getting available of tickets.
 The system we found has been designed to provide a easy way for reserving tickets.
Also it shows the problem faced by passengers during the reservation of tickets.
As a result of our systems aim is to provide:

• easy way for reservation of tickets in offline.

• Comfort for people while travelling.

• Installation of more server.

• Easy interface and captcha so that login failure reduces.

FIVE STEP PROBLEM ANALYSIS
1)Gain agreement on problem definition:

ELEMENT DESCRIPTION

The problem of Limited amount of prebooking tickets.

Affects Passengers who travel in the train.

And results in 1. Damages for the train.ie, seats etc.

2. Passengers face uncomfortability.
Benefits of the solution 1. Reduces the rushes.
2. All passengers feels the basic comfortability.
2)Understand the Root Causes:
PARETO CHART:
 3)
USERS
Identifying the Stakeholders and
OTHER STAKEHOLDERS
Users:

Passengers who travel by pre-booking • System Engineers

• Railway Department Administration

Passenger who are travelling by taking tickets at the • Railway Department Administration
station • Railway Station staff

Passengers who are travelling by not taking the tickets • Ticket collector
• Railway Department Administration
4) Defining solution system boundary:
The system boundary defines between the solution and real worlds
that surrounds the solution.
 5)Identifying constraints to be improved on
the
SOURCE
solution: CONSTRAINTS RATIONALE

Operation No . of pre-booking seats to be Rush in people who are taking tickets

increased in a day

System Should contain details of passengers Limited memory

who prebooked

Equipment budget Should need to increase no . of Cost should be under control

compartments in train

Personal budget Passengers will get a ticket Show while checking

Technology Mandate New software should be used We believe this will reduce the rush
while travelling
Interviewing technique:
Introduction:

We have followed a 10 steps to gather information from

the user/passenger from/use railways train solve the
problems in the railway reservation system as a part of this.
Establishing the customer/user profile
Assessing the problem
Understanding the user requirement
Anlyst’s inputs on customer problem
Assessing the opportunity
Assessing the reliability, performance and
support needed
Other requirement
 WORKSHOP TECHNIQUE:
INTRODUCTION:
A requirement workshop can be told as a structure. It facilitated the
event of getting main stakeholders together to discover, refine,
prioritize, validate and discuss the necessary requirements.

The group of people who are going to attend this workshop are the
passengers who travel in the trains.
There is lots of benefits in the workshop like, we can know that the
passenger faces the problem while travelling, developing new process.
ORGANIZING EFFECTIVE
REQUIREMENTS:
• Who should participate:Passengers who travel on train/daily travellers
in trains are eligible participating in the workshop.
• Content participants: people who travel more on train, persons doing
research on the problem faced by the passengers and representative
users.
• Facilitators: skilled persons, lead the workshop.
• Recorder: person who have experience in this career.
• Observer: having interest to learn and process.
• Team: host, participant, technical member and facilitator.
Before the workshop:
• We ensure to sell/goes to many right person by making them to know
the benefits of this.
• We have make a list to the qualification needed to participate and we
have to identify the stakeholders who can contribute to this process
and completes the process.
• Logistic will be done by the team who travelling in the arrangement of
workshop process like, sturucturing the proper invitation, online access
codes.
• Doing all arrangements in advance.
• Giving all information to the host.
Setting the Agenda:
Time Agenda Description
8-8:30 am Introduction What we are going to do, benefits
8:30-9:00 am Context Project presentation, description
of benefits, existing system
9-11:00 am Brainstorming Discuss on what features needed
for the new system
11-1:00 pm Lunch
1-2:00 pm Brainstorming Continuation
2-3:00 pm Feature definition Write 2-3 description about this
3-4:00 pm Ideas and prioritize Feature are getting priotroize
4-4:30 pm Wrap-up Summarizing
Brainstorming technique and idea reduction:
• During this we session, we will try the best to make it more
interactive.
• We will give the max situation which consists of common problem
what a passenger face.
 AFFINITY DIAGRAM TECHNIQUE:
• An affinity diagram is a tool that gathers large amount of data and
organize them into grouping based on their relationships.
• This process is often used to ideas generated in brainstorming topics.
After the workshop:
• The result what we get that are documented, communicated,
validated and recorded as they help while giving idea to key
stakeholders.
• Any item identified in the workshop will be tracked until the
completion.
• At the end of workshop, we thank all the participants, stakeholders
who participate In this session for giving the opportunity to improve
the railway reservation system.
STORY BOARDING:
VISION DOCUMENT
1) INTRODUCTION 
                         The motive / aim of this vision document is to collect ,
analyse & give full insight of railway reservation system by defining the
problems in detail. This Document also concentrate on the requirement
of stakeholders their needs.
1.1 ) Purpose:
                      The purpose of this vision document it to develop ag design a
database where users can check train details (All necessary information) 
availability of seats in each train, The necessary information are train
details ( train number, name , add drop point, source), which day the train
are available. Maintain records of each train, shows the train status.
1.2 ) Design overview
                   This design is meant for passengers where passengers won't
have any errors while booking/ reserving tickets , the payment option
will be very easy. This design outcome will be very easy and simple to
access. data stored will be very secured, so no need to worry about the
information. During payment method the database won't store any of
your account details. In this process you will see what are the train
available for the destination you choose Ey once you clicked the train
symbol you will get all the info about the train i.e., time of arrival  you
can select the seat which are free / unreserved.

1.3) Reference :
• https://www.indianrail.gov.in/
2) USER DESCRIPTION:
                                     The users of this website are the passengers who
travel in train .
2.1 ) Market Demographics.
                                    IRCTC which is runed by government which is an
online railway reservation system. IRCTC has many problems where
people face while I trying to book ticket through this, So private
organization began / entered the online reservation. After this train
ticketing system grown massively . MakeMytTrip was the early and
first entrance to this area, which was founded in early 2000,  Not only
mean for train ticket. it was also available for different transport
system like flight, water(boat and ship) and bus .
2.2 ) User Profile and Environment
                                       Online railway reservation is mainly used by the
people ( passenger) who use train as their way of transport from one
place to another. Mainly people who travels for longer distance use this
way of booking. as it is the easiest and best way to book/ reserve seat
in train. While booking we need to upload all the necessary documents.
while coming to user environment. People can access through any form
of way - like google/ yahoo. the mandatory thing is
internet.                                                                                                              T
he system will have following:
• Detail : The name and id of train
• Seat : The users can check the available seats in train
• Schedule: The users can know the date of arrival y departure y also
the timings
2.3) Stakeholder Profile
                                    The stakeholder for this system are Requirement Engineer
who gets information from passengers about the requirement they needed &
they have the responsibility to specifies domain a functional requirement y
next stakeholder is the head who creates the plan, gives the necessary
resource etc. the next person  Architect, who is a software developer who
develops website in very well secured    manner

2.4 ) key user needs.

The needs what the passenger wants is :
⦁     Easy access
⦁     well secured payment
⦁     confirmation message
⦁     Regular update of booked seat details ( train details )
2.5 ) Alternatives and competition:
                           As you see, there are lots of private organization who
are in this buisness . they all the competition Some of them are :
                     ⦁    Make My trip
                     ⦁    True Detta
                     ⦁    Route founder
                     ⦁    Gis system
                     ⦁    Ride Scheduler
3) PRODUCT DESCRIPTION
• 3.1) Product Descriptive:
• 3.2) Product position statement:
• 3.3) Summary of capabilities:
3.4) Assumptions and dependencies: -
                              ⦁    The dependencies for the users are the user should
need internet as our system is kind of website.
                              ⦁    The user should log in to the website ( register) for
both of the convenience to make the upcoming process in an easy way
                              ⦁   The user should have bank account like debit /
credit card because Payment is done in online way
4 ) Feature[Product features ]
This system has lots of benefits. Compare to others day the features of
this system are:
   ⦁    A Easy Accessible
   ⦁    Can know the train details
   ⦁    Location of the train where you will be going
   ⦁    Easy and secured Payment Process
   ⦁    24 X 7 Availability can know Previous reservation
5) FEATURE ATTRIBUTE :-
    ⦁    Status (  Proposed )    
    ⦁    Priority ( High )
    ⦁    Risk ( Medium)
    ⦁    Stability (High )
    ⦁    Effort ( Teams in week )
    ⦁    Assigned to ( To all passengers who we) 
6) Use case :
7) Other Product Requirement:

7.1) Application Standard

                  The Standards that this system needs are
                             ⦁    FDA, UCC [fox legal things)
                             ⦁    TCP [communication).
                             ⦁    Any OS [ platform ] .
                             ⦁    UL , ISO [ safety ]
7.2 System Requirements
               ⦁    Andriod   [ Above 7 .0] 
               ⦁    window   [ Above 7]
               ⦁    I0S            [ Above 6 ]

7. 3 Performance Requirement
          Able to handle 1500 transactions per second.

7.4 Security Requirement:

              ⦁    It Should have captcha while log in
              ⦁    Allow to change password
               ⦁    Block if he fail to log-in 4- time in a row
8) DOCUMENTATION REQUIREMENT:
8.1 User manual.
                           It makes/ helps the user to understand the process on
how to use step by step. This user manual will be in online when you
click to the website.
The user manual should have system features
                ⦁    log in , log off
                ⦁    Customer support car
                ⦁    Installation of software and Software details.
REQUIREMENT TRACABLILITY MATRIX