Online Railway Reservation

System

Version 1.0

Department of Computer Science

Symbiosis Institute of Technology

 Index

1. Abstract
2. Project Organization
3. Methods and Tools
4. Software Project Estimation using Function
Point
5. Risk Management
6. Scope
7. Requirement
8. Data Model
9. Function Model
10. Conclusion
11. Reference
Abstract (Problem Statement)
Information about the route, cancellation of tickets,
departure time, arrival time, number of trains available
and other such information are provided.
Store and retrieve information about the various
transactions related to Rail travel.
Keep track of all its passengers and thus schedule their
journey accordingly.
Maintains records of passengers travelling in the
different trains on different dates reaching different
destinations in the system.
User can enquire about the PNR status, seat availability
and trains on a route.
User friendly interface to administrator and customer.
 Spiral Model

Spiral Development Model

The spiral model is a software development process

combining elements of both design and prototyping-in-
stages, in an effort to combine advantages of top-
down and bottom-up concepts. This model of
development combines the features of the prototyping
model and the waterfall model. The spiral model is
intended for large, expensive and complicated
projects.

A spiral model is divided into a number of framework

activities Typically, there are between three and six
task regions. Fig depicts a spiral model that contains
six task regions:
  Customer Communication: Tasks required to
establish effective communication between
developer and customer.
 Planning: Tasks required to define resources,
timelines, and other project related information.
 Risk analysis: Tasks required to assess both
technical and management risks.
 Engineering: Tasks required to build one or more
representations of the application.
 Construction and release: Tasks required to
construct, test, install, and provide user support
(e.g., documentation and training).
 Customer evaluation: Tasks required to obtain
customer feedback based on evaluation of the
software representations created during the
engineering stage and implemented during the
installation stage.

The following diagram illustrates the information,

document and product flow between the lifecycle
process.
Work Breakdown Structure

Identify Activities
Project is divided into major activities. The activities should
be neither too small nor too long.
1. Communication: It involves meeting with stake
holders, and communicate their requirements,
information, and specific needs.
In this project the specified needs are:-
 Databases required
 Categories of trains
 Information about the working of the system
2. Planning: With reference to the information gathered
planning is done to determine how the system will
work.
It includes:-
 Planning about booking
 Planning about cancellation
 Planning about enquiry
 Planning about the availability status
 Planning about PNR Generation

3. Data Dictionary, ERD and DFD: Different databases of

the system are decided and the entity relationship and
data floe diagram is generated.
 Database of trains
 Database of PNR No.
 Database of registered accounts
 Transaction database

4. Design: Layout of the railway system is made which

acts as an interface to the user.

5. Testing and Construction: Testing is done to check the

reliability of the code and the project.
 6. Deployment: The project is developed at the
customer’s workplace explaining the user about the
functionality of the project.

Dependencies
Tasks and subtasks have dependencies based on their
sequencing that is, starting one task will depend on the
completion of another task.

In the Online Railway Reservation System the

dependencies will be

Communication  Planning
Planning  Data Dictionary, ERD, DFD and Design
Design  Testing and Construction
Testing and Construction  Deployment and User
Feedback
1.Dependency Diagram
Schedule Allocation
 Software project scheduling is an activity that
distributes estimated effort across the planned
project duration by allocating the effort to specific
software engineering tasks.
 Furthermore these activities are made concrete
and the schedule along with start date, end date
and duration is made.

Activity Time Allocated

 Resource Gathering 3 days
 Cost Estimation 2 days
 Project Scheduling 3 days
 Risk Management 3 days
 Backend Coding 10 days
 Frontend Coding 7 days
 Module Coding 7 days
 Testing 8 days
 Backend Refinement 4 days
 Frontend Refinement 3 days
 Deployment 3 days
Total 31 days
Resource Allocation

This distributes the work and responsibilities among the

team members. The Resource Allocation Table is as below:

Sr Phase of SDLC Team Responsibility

No. Members
Involved
 Resource Akshat Prepare report of the initial
Gathering Aman developer meeting, SRS
document
 Analysis Anubhav Project Plan with effort and cost
estimation
 Design Aman Prepare case diagram with
Akshat specifications, Data Flow Diagram,
Activity Diagram
 Implementation Aman Develop Source Code of the System
Akshat
Anubhav
 5Testing Akshat Prepare Testing document
.
 Deployment Anubhav Deliver System as an installable
Akshat package, User manual and guide
Aman
Timeline Chart

Activity Chart
Methods and Tools

Development Methodology:

The project shall use the spiral software development

methodology to deliver the software products.
The decision to use the Spiral methodology is due to
the following characteristics of the project:
 The product definition is stable
 Requirements and implementation of the
product are both very well-understood
 Technical tools and hardware technology are
familiar and well-understood
 Waterfall methodology has proven successful
for projects of this nature

Tools:

 MySQL for database creation

 OLEDB for integration of databases
 PHP and java script for web pages and interfacing
 Microsoft Office
Context Diagram

Effort and Cost Estimation: Function Point

Fi Calculation:

Factor Value
Backup and recovery 5
Data communications 5
Distributed processing 3
Performance critical 4
Existing operating environment 4
On-line data entry 5
Input transaction over multiple screens 4
Master files updated on-line 4
Information domain values complex 5
Internal processing complex 5
Code designed for reuse 4
Conversion/installation in design 4
Multiple installations 5
Application designed for change 5
Total 62

Count Total

Domain Count Complex Total

No. of user inputs 8 6 48
No. of user outputs 2 7 14
No. of user inquiries 2 6 12
No. of files 4 15 60
No. of external interfaces 1 10 10
Total 144

FP=Count Total (0.65+0.01*62)

FP=144*(1.27)
FP=182.88
FP~=183
Cost per FP=$500
Total Cost=Cost/FP*FP
Total Cost=$500*183
Total Cost=$91500
Productivity=5 FP/PM
Effort=FP/Productivity
Effort=183/5 PM
Effort=36.6 PM
Effort=~37 PM

The total cost is $91,500 and effort is 37 PM.

Risk Management

Risk Description

Project Risks Identifies potential budgetary,

schedule, personnel (staffing and
organization), resource, customer, and
requirements problems and their
impact on a software project. It
threatens
the project plan. That is, if project risks
become real, it is likely that project
schedule will slip and that costs will
increase.
Technical Risks Identifies potential design,
implementation, interface, verification,
and maintenance problems. Technical
risks threaten the quality and
timeliness of the software to be
produced. If a technical risk becomes a
reality, implementation may become
difficult or impossible.
Market Risks Building a excellent product or system
that no one really wants
Budget Risks Losing budgetary or personnel
commitment
Known Risks Those that can be uncovered after
careful evaluation of the project plan.
Predictable Risks Extrapolated from past project
experience
Unpredictable Risks They can and do occur, but they are
extremely difficult to identify in
advance.
Support Risks The degree of uncertainty that the
resultant software will be easy to
correct, adapt, and enhance.
Schedule Risks The degree of uncertainty that the
project schedule will be maintained
and that the product will be delivered
on time.
System Requirement Specification

Scope

The idea of efficient reservation is expected to prove very

useful in the daily life of passengers as compared to the
conventional system. If it turns out as expected, then it
would create a huge impact on the turnaround of
passengers toward the railways, increasing their level of
trust.

Specific Hardware Requirements

Intel Dedicated Server Family

High Speed Storage
Dedicated lines for connectivity
Network Storage
Printer
Monitor and other general peripherals
Data Model and Description

Entity Relationship Diagram

Functional Model and Description

User Level 1
Admin Level 1
User Level 2
Admin Level 2
Conclusion

The proposed system is error free, stable and capable of

Handling load at the server even in the peak hours without
losing stability or giving a down time.
The software provides security to the user, administrator
and the server.
As for the user, the task of booking, cancelling a ticket or
making an enquiry is made much easier and hassle free.

Reference

The material has been taken from the following places:

 www.wikipedia.org
 www.Scribd.com
 www.Handouts.org
 www.google.com