Railway Reservation System

“On line Railway Reservation System”

Abstract
In this emerging world of computers all most all manual system automated and
computerized but maximum of them are so complex and a common user is
unable to operate that software system. We are developing the “Online Railway
Reservation System” to model the present system and to remove the drawbacks.
This project explores how computer technology can be used to solve the
problem of user. We specifically props way to computerize the administration
and engineering offices of Indian Railway Online. A high speed communication
network needs to be developed for interconnecting the offices of railways. This
same communication network can be used to provide high speed internet
connection to the public and leas out network capacity to internet service
providers. Railway Reservation System
TABLE OF CONTENTS
1. INTRODUCTION
a. Current system
b. Need of proposed system

2. SYSTEM DEVELOPMENT LIFE CYCLE

3. ANALYSIS
a. Requirement analysis

b. Requirement Specification
4. DESIGN
a. System Flow Diagram
b. Modules identified
c. Database Design
i. E-R Diagram

5. IMPLEMENTATION
a. Platform Used
i. Hardware Platform

ii. Software Platform

b. Implementation
c. Testing
i. Testing Technique used

6. CONCLUSION
a. Important Features
b. Limitations
c. Future Work
Railway Reservation System
Introduction Railway Reservation System
1. Introduction
1.1 Current System
India is the 7th largest country in terms of geographical size. This means there
is a need for efficient means for long distance transportation. The long distance
road network is very poorly developed in most parts of India. Bulk of long
distance traffic is carried by the Indian Railway as a result Indian railways.
Therefore forms a backbone of public transport in India. The efficiency of the
railway will increase result of computerization due to dramatic reduction in
communication time among geographically dispersed offices. For the
reservation of the ticket a person go to ticket counter of the railway reservation
office and expend its valuable time in standing queue. Now to save that time we
have a facility of Online Reservation now we can book cancel or search other
train information just by click on computer.
1.2 Need of proposed system
To reduce complexity of existing system.
Effective management of time.
To make work easy, simple and error free.
Effective utilization of available resource.
To enhance the efficiency and diversification of services activities.
User friendly.
Interactive graphical user interface.

The scope of project define the project feasibility the technology , finance , time
and resources best define in technology weather the defects can be reduced in
the project and up which level financially, weather the overall project cost is
affordable. Time describe the weather the projection finishing point will be
achieve on time or before time resources required should be available at the
rate of cost and time. Railway Reservation System
System Development Life Cycle Railway
Reservation System
2. System development life cycle
2.1 Definition
A software process model or a software engineering is an abstract
representation of a software process. It is a software development strategy that
encompasses the process, methods and tools layers plus the generic phases
namely definition phase, development phase and support phase. A process
model is chosen based on the nature of the project and application, the
methods and tools to be used and the controls and deliverables that are
required.
2.2 Spiral Model
The spiral model, also known as the spiral lifecycle model, is a systems
development lifecycle model used in information technology (IT). This model of
development combines the features of the prototyping model and the waterfall
model. The spiral model is favored for large, expensive, and complicated
projects.
The steps in the spiral model iteration can be generalized as follows:
1. The system requirements are defined in as much detail as possible. This
usually involves interviewing a number of users representing all the external or
internal users and other aspects of the existing system.
2. A preliminary design is created for the new system. This phase is the most
important part of "Spiral Model". In this phase all possible (and available)
alternatives, which can help in developing a cost effective project are analyzed
and strategies to use them are decided. This phase has been added specially in
order to identify and resolve all the possible risks in the project development. If
risks indicate any kind of uncertainty in requirements, prototyping may be used
to proceed with the available data and find out possible solution in order to deal
with the potential changes in the requirements.
3. A first prototype of the new system is constructed from the preliminary
design. This is usually a scaled-down system, and
Railway Reservation System
represents an approximation of the characteristics of the final product.
4. A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weaknesses, and
risks;
2. Defining the requirements of the second prototype;
3. Planning and designing the second prototype;
4. Constructing and testing the second prototype.

Spiral Model:- Railway Reservation System

Analysis Railway Reservation System
3. Analysis
3.1 REQUIREMENT ANALYSIS:
Requirements are a feature of a system or description of something that is
capable of doing in order to fulfill the system‟s purpose. It provides the
appropriate mechanism for understanding what the customer wants, analyzing
the needs, assessing feasibility, negotiating a solution, specifying the solution
unambiguously, validating the specification and managing the requirements as
they are translated into an operational system. Requirement Analysis is a task
done under software engineering and software design. While requirements
engineering specifies software‟s operational characteristics i.e. function, data
behavior, indicates software‟s interface constraints, requirements analysis let
the software engineer (called analysis) to refine the software allocation and
construct models of data, functional and behavioral domains. Moreover,
requirements analysis provides software developer with a representation of
data, function and behavior that can be converted to data, architectural,
interface and component-level designs. At last, we can say that the requirement
specification makes available, the developer and the customer, a means to
assess quality, once the software has been built.
Software requirements analysis can be categorized into four areas of effort, as
follows-
Evaluation and synthesis
Modeling
Specification
Review
Railway Reservation System
The analyst starts with the studies of system specification and the software
project plan. It is then important to understand the software in a system
context. Also, the review of the software scope, used to generate planning
estimate, is necessary. Next, communication for analysis must be established,
so as to ensure problem recognition. The reason behind is to recognize the basic
problem elements perceived by customer.
The next major area of effort for analysis is problem evaluation and solution
synthesis. The engineer (or analyst) must define all data objects that are
extremely observable. He must evaluate the content and flow of information.
Also, he must define and describe all software functions, understand software
behavior in the context of the system affected events, establish the
characteristics of system interface, and uncover additional design constraints.
After evaluating the current problems and desired information (i.e., input and
output), the engineer and analyst synthesizing one or more solutions. Initially,
the data objects, processing functions and the system behavior are defined in
detail. Once establishing this information, the analyst then considers basic
architectures for implementation. Thus the process of evaluation and synthesis
proceeds until both analyst and the customer are sure that software can be
adequately specified for subsequent development steps.
During the evaluation and synthesis activity, the analyst creates the system
model so as to better understand data and control flow, functional processing,
operational behavior and the information content. The model provides a base
for software design and the creation of specifications for the software.
3.2 REQUIREMENT SPECIFICATION:
A Software Requirements Specification (SRS) is a complete description of the
behavior of the system to be developed. It includes a set of use case that
describes all the interactions that the users will have with the software. Use
cases are also known as Functional Requirements. Non-Functional
Requirements are requirements which impose constraints on the design or
implementation (such as performance requirements, quality standards, or
design constraints). Railway Reservation System
3.2.1 FUNCTIONAL REQUIREMENTS:
In software engineering, a functional requirement defines a function of a
software-system or component. A function is described as a set of inputs, the
behavior and outputs. Functional requirements may be calculations, technical
details, data manipulation and processing and other specific functionality that
show how a use case to be fulfilled.
Typically, a requirements analyst generates functional requirements after
building use cases. However, this may have exceptions since software
development is an iterative process and sometime certain requirements are
conceived prior to the definition of the use case. Both artifacts (use cases
documents and requirements documents) complement each other in a
bidirectional process.
A typical functional requirement will contain a unique name and number, a
brief summary, and a rationale. This information is used to help the reader
understand why the requirement is needed, and to track the requirement
through the development of the system.
The core of the requirement is the description of the required behavior, which
must be a clear and readable description of the required behavior. This
behavior may come from organizational or business rule, or it may be
discovered through elicitation sessions with users, stakeholders and other
experts within the organization. Software requirements must be clear, correct
unambiguous, specific and verifiable. Railway Reservation System
Detailed Description of Functional Requirements:
Template for describing a description of the functional
functional requirements. requirement its reason(s)
Purpose
Inputs what are the input; in what form
will they arrive; from what sources
can the input come; what are the
legal domains of each input
Processing Describes the outcome rather than
the implementation; includes any
validity checks on the data, exact
timing of each operation (if needed),
how to handle unexpected or
abnormal situations
Outputs The form, shape, description and
volume of output; output timing;
range of parameters in the output;
unit measure of the output; process
by which the output is stored or
destroyed; process for handling
error message produced as output