STE Report 51
STE Report 51
Chapter 1
SYNOPSIS
Project Title
None
Prof.Gunjal.T.S
Chapter 2
ABSTRACT
The railway reservation system facilitates the passengers to enquiry about the trains
available on the basis of source and destination, booking and cancellation of tickets, enquiry
about the status of the booked ticket, etc. The aim of case study is to design and develop a data
base maintaining records of different trains, train status and passengers.This project contains
introduction to the railways reservation system. It is the computerized system of reserving the
seats of train seats in advance. It is mainly used for a long route. Online reservation has made
the process for the reservation of seats very much easier than ever before.
In our country India, there are number of counters for the reservation of the seats
and one can easily make reservations and get tickets. Railway reservation system, has described
above, can lead to error free, secure, reliable and fast management system. It can assist the user
to concentrate on their other activities rather to concentrate on the record keeping. Thus it will
help organization it better utilization of resources. Administrator of the project, with the help of
a password, can enter new train record, display all train records, modify train records and delete
train records. The record of train includes its number, name, source, destination, and days on
which it is available, whereas record of train status includes dates for which tickets can be
booked, total number of seats available, and number of seats already booked.
Chapter 3
INTRODUCTION
Railway reservation system is developed for to automate the railways reservation system. It
includes modules required to successfully operate railways reversion process smoothly. It has train
master to add modified train information, train schedule to enter train journey details include all
the station name, arrival time and departure time. It includes automatic fair calculation as per the
distance between two stations. Reservation module consists of automatic seat number and coaches
no allocation system. Daily schedule for updating of not conform seat and coach no. All master
like train master, Train schedule, reservation fees, cancellation fees, charges can be modified
individually from front end and changes reflect in all modules immediately.
Therefore proposed “Railway reservation system” has been designed to automate the process
of railway for ticket reservation and back office activities. System can make the daily activities
efficient and provide the fast response. The “Railway reservation system” has been developed to
override the problems prevailing in the practicing manual system. This software is supported to
eliminate and in some cases reduce the hardships faced by this existing system. Moreover this
system is designed for a particular need of a company to carry out operations in a smooth and
effective manner.
The application is reduced has much as possible to avoid errors while entering the data. It also
provides error messages while entering invalid data. No formal knowledge is needed for the user
to use this system. Thus by this all it proves it is user friendly. Railway reservation system, has
described, can lead to error free, and secure, reliable and fast managing system. It can assist the
user to concentrate on the other activities rather to concentrate on the record keeping. Thus it will
help organization in better utilization of resources.
Chapter 4
OVERVIEW OF THE PROJECT
This project will give us the information about railway reservation. This system is
basically concerned with the reservation and cancellation of railway tickets to the passengers. To
be more specific, our system is limited in such a way that a train starting from a particular source
will have a single destination. The basic functions being performed by our system are reservation
and cancellation. Customers can find the proper and correct information about the railway and
shows the
• Reservation Possibilities.
• User friendly.
EXISTING SYSTEM
In the existing system exams are done only manually but in proposed system we have to
computerize the exams using this application. The existing system has the following problems:
• Time consuming.
Chapter 5
PROPOSED SYSTEM
• Security of data.
• Ensure data accuracy.
• Proper control of the higher officials.
• Minimize manual data entry.
• Minimum time is needed for various processes.
• Greater efficiency.
• Better service.
• User friendliness and interactive
FEASIBILITY STUDY
• Operational feasibility
• Technical feasibility
• Economical/financial feasibility
OPERATIONAL FEASIBILITY
Operational feasibility measures how well the solution will work in the organization and how will
end-user and management feels about the system. Proposed system is helpful for all the users
associated with the organization. It will allow the administrator to have upto-date information
regarding all the aspects of their users, the decision-making process will also become faster with
the use of data integration, consolidation. So it is feasible to implement the system.
TECHNICAL FEASIBILITY
This involves questions such as whether the technology needed for the system exists, how difficult
it will be to build, and whether the firm has enough experience using that technology. This system
required minimum hardware equipment to run efficiently
ECONOMICAL FEASIBILITY
Economically to find out whether this project is economically feasible or not for that used
feasibility analyses. In this stage list direct costs or indirect costs associated with the project.
OBJECTIVES
The objective of this project is to provide tickets to public in the comfortsto their home or residence
and to save them from hassles to visit ‘Railway Reservation Centres’. By doing this, we are not
only saving time of public but also saving their cost of traveling or parking to these centres. For
Railways it is saving on their infrastructure i.e. Buildings, Air-Conditioning, Electricity, Furniture,
Staff etc.
Chapter 6
SYSTEM ANALYSIS
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
Chapter 7
TEST CASES
SR.NO TEST CASE TEST CASE I/P DATA EXPECTED AUCTUAL STATUS
ID OBJECTIVE RESULT RESULT
1 TC-1 Login field Any valid log It should The login Pass
name (abcd accept the log name is
xyz) name accepted
Chapter 8
TEST DEFECT REPOET
Product:
Railway Reservation System
Components:
Mapping. ICS develops geolocation apps leveraging available map data
( e.g. Google Maps, Navteq Maps or Open Street Map) to access a location -
based service or navigate to a point of interest.
Social Networking. ...
Specialized Devices. ...
E Reader. ...
Games.
Defect Type:
Network related issues.
Memory leakage.
Slow responses.
Network related issues.
Permission issues (camera, video, audio)
Environmental:
Railway reservation system
User/customer
Steps:
1. Idea creation:
2. Sketching :
3. Wire framing:
The goal: Create a clear visualization of how the app will look.
4. Graphic designing:
The goal: Make the user experience friendly.
The goal: Launch the project as fast as possible without any mistakes
Status: New
Severity: Low
Priority: Medium
Chapter 9
SYSTEM REQURIMENTS & SPECIFICATION
REQUIREMENTS SPECIFICATION
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).
FUNCTIONAL REQUIREMENTS
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 behaviour, which must be a clear and
readable description of the required behaviour. This behaviour 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.
NON-FUNCTIONAL REQUIREMENTS
• Evolution qualities, such as extensibility and scalability, embody in the static structure of the
software system.
SOFTWARE REQUIREMENT
HARDWARE REQUIREMENT
Chapter 10
SYSTEM DESIGN
In the system design process, the primary objective is to identify user requirements and to build a
system that satisfies these requirements. Basically, the design phase concentrates on "how" the
system is developed. Design describes a final system and the process by which it is developed. It
refers to the technical specification that will apply in implementing the candidate system.
The design phase is the second important steps in the system development life cycle. During this
phase the analyst does the following:
• Works with the user to determine the different data inputs to the system.
• Draws the model of new system, using data flow diagram & entityrelationship diagrams.
• Identifies and orders any hardware and software that the system design phase
LEVEL 1 DFD
LEVEL 2 DFD
ER DIAGRAM
SCHEMA
Chapter 11
SYSTEM TESTING
TESTING Software testing is a critical phase of software quality assurance. It indicates the
ultimate review of specification, design and code generation. Once source code has been
generated, software must be tested to uncover and correct maximum possible errors, before being
delivered. Testing emphasizes on a set of methods for the creation of test cases that fulfil overall
testing objectives. The primary objectives of software testing are as follows:
• A good test case should have a high probability of finding an as yet-undiscovered error.
1) UNIT TESTING
Unit testing aims the verification effort on the smallest unit of software design i.e., a software
component or module. It uses procedural design as a guide to test major control paths and uncover
errors within the module boundary. It is a White box oriented and the step can be conducted in
parallel for multiple components. Unit testing is a dynamic method for verification, where the
program is actually compiled and executed. It is one of the most widely used methods, and the
coding phase is sometimes called “coding and unit testing phase”. The goal of unit testing is to test
modules or “units”, not the whole software system. Unit testing is most often done by the
programmer himself/herself. The goal of Unit testing is to isolate each part of the program and
show that the individual parts are correct. A unit test provides a strict, written contract that the
piece of code must satisfy. As a result, it affords several benefits.
2) INTEGRATION TESTING
Integration testing is a phase of software testing in which individual software modules are
combined and tested as a group. It follows snit testing and precedes system testing. The major
objective of integration testing is to tackle the problem of integration i.e. putting all the modules
together. One module can have an inadvertent, adverse effect on another, sub functions, when
combined, may not be magnified to unacceptable levels; global data structure can cause problems
and to truncate this list of problems we use integration testing. Integration testing strategy used is
Bottom-Up Integration Testing. In it all the bottom or low level modules, procedures or functions
are integrated and then tested. After the integration testing of lower level integration modules, the
next level of modules will be formed and can be used for integration testing. This approach is
helpful only when all or most of the modules of the same development level are ready. This method
helps to determine the levels of software development and makes easier to report testing progress
in the form of a percentage.
3) VALIDATION TESTING
At the climax of integration testing, software is developed as a package having all the errors
uncovered and corrected. At this time, a final series of software test May be in process. It is called
validation testing. Validation succeeds when software function in a reasonably expectable manner.
Validation attempts to uncover errors, but the emphasis is on the requirements level i.e. the things
that will be immediately apparent to the customer
Chapter 12
RESULT & DICUSSION
Chapter 13
CONCLUSION
Rather than designing manually we have made use of computer as once that data’s are input
it performs accurate function. There is no chance of fault or miscalculation if the data are fed
correctly. Use of the computers has solved many problems, which are faced while manual
calculation. This is not the end but beginning of the versatile, efficient and outsourcing railway
reservation system. This is the one which is compatible to all operating system. By making this
we project we made a small footstep towards the path of progress of platform independent railway
reservation system
Chapter 14
REFERENCE
https://docshare.tips/online-railway-reservation.com
https://www.slideshare.net/shashankkarnati/railway-management-system-database.com
https://www.geeksforgeeks.org/railway-reservation-system-in-c/