Professional Documents
Culture Documents
Abstract
TABLE OF CONTENTS
1. INTRODUCTION
a. Current system
b. Need of proposed system
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
2.1 Definition
Spiral Model:-
Railway Reservation System
Analysis
Railway Reservation System
3. Analysis
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.
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
Time:-
Cost:-
Usability:-
Reliability:-
Performance:-
A use case name provides unique identifiers for the use case. It
should be written in verb-noun format, should describe an achievable
goal and should be sufficient for the end user to understand what the
use case is about.
3.4.2 GOAL:
3.4.3 ACTORS:
3.4.4 PRECONDITIONS:
3.4.5 POSTCONDITION:
The post conditions section describes what the change in the state
of the system will be after the use case completes. Post conditions are
guaranteed to be true when the use case ends.
USER
SYSTEM
ADMINISTRATOR
VALIDATE USER
VIEW TRANSACTION
Railway Reservation System
DESIGN
Railway Reservation System
4. DESIGN
4.1 SYSTEM FLOW DIAGRAM:
CHACK
DATABASE
PROCESS CANCELATION
CANCELLATION AUTHORITY
DATABSE
CHECK ENQUIRY
STATUS AUTHORITY
DATABSE
Railway Reservation System
Here are 6 steps which can be used as a guide for completing flow
diagrams:
4. Go with the main flow i.e. when we reach a point at which the
flowchart branches into a number of alternatives, and the resulting
complexity threatens to overwhelm the exercise, choose the most
important alternative to continue flowcharting with.
SYSTEM FLOWCHART:
START
IF VALID GO BACK
ENTER LOCATION
Start
Input User
Name
Yes Is User No
Valid
No
Stop
Is Train
X
Available
Railway Reservation System
Is Access
User Denied
Authorized
Is Option
Reservati No
on of
Ticket
Yes
Is Option
Cancel of
Ticket
Book Ticket
No
Yes
Cancel Ticket
Y
Railway Reservation System
Yes Is Option No
Other
Information
Request Server
System User Server Response
Password Request
Services to
User Server
System User User Validation
Response
RUNNING_DAY
SOURCE
TRAIN
SECOND
DISTANCE _CLASS
BELONG_TO
TRAVEL
STATION
TRAVEL FARE
DATE CHARGE
DISTANCE
BELONG_TO
SLEEPER
TRAIN_NO FIRST_CLASS
CLASS
TIME
RESRVATION
SEAT
STATUS DATE_OF_JRNY
PNR_NO.
SOURCE
PASSENGER_DTL
Railway Reservation System
IMPLEMENTATION
Railway Reservation System
5. IMPLEMENTATION
5.1 Platform Used
RAM: 64 MB
Server side:
RAM: 64 MB
PNR_Number Numeric
Source Varchar
Destination Varchar
Train_name Varchar
Train_number Varchar
Departure_from_source Varchar
Arrival_at_destination Varchar
Date_of_journy Numeric
Name_of_passenger Char
Sex Char
Age Numeric
Address Nvarchar
Telephone_number Numeric
Class Varchar
Distance Numeric
Seat_no. Numeric
Railway Reservation System
5.3 Testing:
1. UNIT TESTING:-
2. INTEGRATION TESTING:-
3. VALIDATION TESTING:-
CONCLUSION
Railway Reservation System
2. CONCLUSION
6.1 LIMITATION OF THE PROJECT:
There were many difficulties that came in our way in the process of
development of this real time project some of them are illustrated below.
6.4 CONCLUSION:
This is not the end but beginning of the versatile, efficient and
outsourcing railway reservation system. This is the one which is
Railway Reservation System