Rahul

Introduction
Purpose of Documentation:The Indian Railways (IR) carries about 5.5 lakh passengers in reserved accommodation every day. The computerized Passenger Reservation System (PRS) facilitates booking and cancelling of tickets from any of the 4000 terminals (i.e PRS booking windows) all over the country. These tickets can be booked or canceled for journeys commencing in any part of India and ending in any other part, with travel times as long as 72 hours and distances up to several thousand kilometers. This Documentation is used for fast processing like:Confirm reservation for confirm seat. Reservation against cancellation. Waiting list reservation. Online reservation. Immediate reservation.
y y y y y
The project makes a sincere effort to provide all the above-mentioned features to meet the requirements of the Railway system.
1 Jagannath Gupta Institute of Engineering and Technology Plot no. IP-2&3,Phase IV,Sitapura Industrial Area, Opp.Chokhi Dhani,Jaipur.
Scope of Documentation:This project aims at development of an On-line Railway Reservation Utility which facilitates the Railway customers to manage their reservations on-line, and the Railway administrators to modify the back end databases in a User-Friendly manner. The Customers are required to register on the server for getting access to the database and query result retrieval. Upon registration, each user has an account which is essentially the view level for the customer. The account contains comprehensive information of the user entered during registration and permits the customer to get access to his past reservations, inquire about travel fare and availability of seats, make afresh reservations, update his account details, etc. The Railway Administrator is the second party in the transactions. The administrator is required to login using a master password, once authenticated as an administrator, one has access and right of modification to all the information stored in the database at the server. This includes the account information of the customers, attributes and statistics of stations, description of the train stoppages and physical description of coaches, all the reservations that have been made, etc. The railway administrator has the right to modify any information stored at the server database.
Overview:A computer reservations system (or central reservation system)[1] (CRS) is a computerized system used to store and retrieve information and conduct transactions related to air travel. Originally designed and operated by airlines, CRSes were later extended for the use of travel agencies. Major CRS operations that book and sell tickets for multiple airlines are known as global distribution systems (GDS). Airlines have divested most of their direct holdings to dedicated GDS companies, who make their systems accessible to consumers through Internet gateways. Modern GDSes typically allow users to book hotel rooms and rental cars as well as airline tickets. They also provide access to railway reservations in some markets although these are not always integrated with the main system.
Sabre
Holdings was purchased by private investors Silver Lake Partners
and Texas Pacific Group on March 30, 2007, for about US$5 billion. Full year 2008 Sabre Holdings revenues were about US$3 billion.
In
December 2006, Travelport, which owns Galileo, agreed to buy and
merge with the Worldspan GDS. The combined company would then control a 46.3% market share using 2002 airline booking data.
Worldspan's
market share is 16.9% globally and 31% in the U.S.
according to 2006 MIDT airline transaction data.
In
March 2007, KLM Royal Dutch Airlines switched from its own
reservations system (CORDA) to Amadeus as a result of the merger with Air France.
In
February 2010, JetBlue converted its reservation system over to the
SabreSonic Customer Sales and Service platform.
Business Context:
Single screen, rich Internet application. Login not required for checking availability, only for booking, and can be done after booking. Station code lookup while the user types the name. Train availability select multiple trains, and click once to get availability in all. Single date field, automatic format conversion. In line contextual help available. Visual effects to show the progress of the process. Single spot for advertisement can rotate. Can change any parameter at any time, and the remaining will update automatically e.g. Change In date, will automatically check availability for selected train Payment options one chosen by default, others available on request. Advertisements can still be delivered, you can even deliver contextual ads as the user plans their travel. Other pages of the site can also be integrated.

The General Description
Product Functioning:The railway Reservation system works for customers reliability and support for on-line reservation and the queries of the customer. This system Functions as the supporting system for the customers to get Reservation Easily. Some Functionalities are : Add new train services or update the existing train services, e.g. modifying their stopping stations, stoppage times, tariffs, etc. Add or update the physical description of trains, like number of coaches, type of coaches, number of berths, etc. Update information about addition of railway stations, add new railway stations, drop existing railway stations, etc. Access and modify customer accounts or customer reservations. Create an account by registering, modify account details, deregister from the services Make afresh multi passenger reservations, the customers are provided to choose their berths/reservation spots rather than being randomly allocated positions View , modify or cancel past reservations Customers are provided with different reservation status, just as in real life systems Consumers are informed, through emails, about updates in the reservations and trains
Consumers are informed about the various seasonal offers and discounts.
User Problem statements:A software has to be developed for automating the manual railway reservation system. The system should have distributed functionalities as described below:-
1.RESERVE SEAT :A passenger should be able to reserve a seat in the train specified by him if available. For this he has to fill a reservation form with the details about his journey. The clerk checks for the availability of the seat in the train and if the seat is available then he makes entries regarding train name, train number, date of journey, boarding station, destination. The passenger is the asked to pay the fair .After making payment the passenger can collect the ticket from the clerk.
2.CANCEL RESERVATION:There may arise a case when the passenger wants to cancel his reservation .For this he has to fill a cancellation form providing all the details about the ticket reserved by him. The clerk then checks for the entries from the database and cancels the reservation finally returning the ticket amount with some deduction.
3.UPDATE
TRAIN
INFORMATION
&
REPORT
GENERATION :Only the Administrator has theright to make changes in train details(train name, train no. etc.).The system should also be able to generate report when needed in the form of reservation charts , train schedule charts etc.
4.LOGIN: Only the user with specified login id & password can get access to the system. This provides security from unauthorized access.
5.VIEW RESERVATION STATUS & TRAIN SCHEDULE: All the users should be able to see the information about the reservation status & train schedule, train name, train number etc
User Objective:
ONLINE BOOKING: With the help of this people can book their tickets online through internet, sitting in their home by a single click of mouse. Using their credit cards people can easily get their tickets done within minutes. There are certain charges for online booking as well.
COUNTER BOOKING: This is the oldest method of booking the tickets. The reservation counters are there at railway department from where people can get the tickets to their respective destinations. a b. c. If you wish to know the route and the timings ,click on Show Route. If you want to know the availability of seats/berths, click on Show To get the fare, click on Get Farebutton. The fare appearing is for a the service charges charged by IRCTC and
Availability. single adult Passenger excluding d. e.
by the Bank(Credit Card/Direct Debit). To book tickets, click on Book Ticketbutton. If you wish to select other train, click on Select Other Train button.
SYSTEM ANALYSIS
Functional Requirements:
Log In Function: Description: This function ensures that only authorized users gain access to the Reservation databases. An authorized user is a user who has an account on the system. Users include passengers, train officials. The user must type a valid username and password to gain access. Rationale: Logging into the system provides security and confidentiality to the system. It reduces the chance that someone can taper any individuals personal information and prevents unauthorized users from modifying the confidential information such as reports for train schedule information. Specification: Allows access to ORRS Username, password User inputs username and password Successful login; unsuccessful login None Authorized User No change to Passenger Accounts Database Failures and successful logins are sent to Reservation Database
Description Inputs Source Outputs Destination Precondition Post Condition Side Effects
Make a Reservation Function: Description: This function allows the user to make a reservation for a particular train on a particular date for a certain number of tickets. If the user does not already have a reservation, then a new reservation is created. If the user already has a previous reservation, a new reservation is added to the list of current reservations, and the passenger account balance gets updated. Rationale: A user must have the ability to add a reservation to his/her account. This function makes this process simple and easy. Specification: Adds a reservation to the users account From city, to city, seat type, travel date, return date and time User inputs from city, to city, seat type, travel date, return date and time Modified reservation Computer screen Reservation database Passenger Account database Valid information; train route and tickets available; user does not have another reservation at the same time Reservation added to passenger account Users current reservations adjusted Balance due adjusted
Description Inputs Source Outputs Destination
Precondition
Post Condition Side Effects
Drop Reservation Function: Description: This function allows the user to drop a reservation for a particular train on a particular date for a certain number of tickets. If the user does not already have a reservation, then all reservations are dropped. If the user already has a previous reservation, a chosen reservation is dropped from the list of current reservations, and the passenger account balance gets updated. Rationale: A user must be able to remove a reservation from his/her account. This function makes this process simple and easy. Specification: Remove a reservation from a users account From city, to city, seat type, travel date, return date and time User inputs from city, to city, seat type, travel date, return date and time Modified reservation Computer screen Reservation database Passenger Account database Reservation must be a part of users current reservations Reservation is removed from users account Users current reservations adjusted Balance due adjusted Ticket availability updated
Description Inputs Source Outputs Destination
Precondition Post Condition Side Effects
Display Current Reservations Function: Description: This function allows the user to see a list of all his/her current reservations. If the user does not have any reservations at the time (assuming that the user has a valid account on the Reservation system), and empty list with a message No Reservations Have Been Made is displayed. Rationale: This function will be used primarily as a device to verify reservations during and after the reservation process. Specification: Description Inputs Source Outputs Destination Precondition Post Condition Side Effects Allow user to check reservations Name, address, phone number Log In function Date, train #, from city, to city, seat type, # of tickets, total Computer screen Successful login to secure network Reservation balance is displayed on computer screen None
Display Train Schedule Information Function: Description: This function allows the user to see a list of all scheduled train departures including train name, city from and to which the train is going, the number of seats available, and the prices for different ticket types. Rationale: A list of train departures helps the user to decide what information to enter to the Make a Reservation and Drop a Reservation functions.
Specification: Description Allow user to check train availability by city from and to which the train is going, number of seats available, and ticket price None Log In Function Train schedule and availability status Computer screen Web Access Reservation remains unchanged None
Inputs Source Outputs Destination Precondition Post Condition Side Effects
Display Balance Function: Description: This function provides a listing of the current balance due and payments received in the past. This information is presented in an easy to follow format and separately displays each reservation. Rationale: This function allows the user to keep accurate financial records on his/her total reservations paid. This information is also useful in figuring out how much the user has spent in train travel. Specification: Provides a listing of current balance due and past payments received Log In Function Passenger Reservation Database Name, address, phone number, date, train #, City from, city to, seat type, # of tickets, subtotal, total Computer screen Successful login to secure network
Description Inputs Source Outputs
Destination Precondition
Post Condition Side Effects
No change to payment information None
Pay Reservation Function: Description: This function allows the user to pay his/her current reservation cost. The user may either pay entire balance due or select to pay in person within 48 hours. The user must also input a valid credit card number. Rationale: This function allows the user to pay online rather than to pay in person. To pay online is both more convenient and less time consuming, because the user is not subject to the hours of operation of the Travel Agent Office. Specification: Allow user to pay reservation via a credit card. Type of credit card, credit card number, expiration date, cardholder name, cardholder phone number User provides all the necessary inputs Passenger balance Computer screen and Passenger Account Database Valid credit card number. Account balance updated None
Description Inputs
Source Outputs Destination Precondition Post Condition Side Effects
Display Report Function: Description: This function allows the user to display the following reports: y Number of Reservations for Each Departure Date/Train
y y y y
Number of Customers Turned Away Number and Name of the People who are Wait-Listed Number and Names of People who are Confirmed Number of Seats available
Rationale: The Chinese Railway Ministry must be able to generate reports to keep track of ticket sales and reservations. This function makes this process simple and easy. Specification: Display a system report Log In Function Passenger Account Database and Reservation Database Requested report Computer screen Successful login to secure network No change to reservation information None
Description Inputs Source Outputs Destination Precondition Post Condition Side Effects
System Requirements:
The passenger has a prior knowledge of the reservation and ticketing system. The passenger arrives at the railway ticket counter and interacts with the counter clerk first through an enquiry and then follows the process of form filling, tendering, payment and collecting the tickets. Passenger accepts the ticket or leaves the counter. Passenger seeks information on fare, train timings and availability of tickets. Passenger can have single ticket or multiple tickets. Journey begins on a day and will be over with one break in between. Passenger is identified by name, age, sex and address. Trains are identified by name and number. No receipt is issued for money transacted. Output of the system is ticket(s) with details. The process is triggered through a form filled by the passenger detailing the requirements of tickets, train, date, etc. A form is used for each train. If the journey requires use of multiple trains,Separate forms are used for each train.
Software Requirements:
C Language. C++ Language. Java. Dot-net.
Operating Environment: Windows NT. Windows Vista. Windows Xp. Windows 7.
Stability And Speed:

System Must be stable and fulfill all the requirements of the user.
System have to work Efficiently and speedily and must enable all software
components which are used in the system.
Feasibility Study :
An initial investigation in a proposal that determines whether an alternative system is feasible. A proposal summarizing the thinking of the analyst is presented to the user for review. When approved, the proposal initiates feasibility study that describes and evaluates candidate systems and provides for the selection of best system that meets system performance requirements.
To do a feasibility study, we need to consider the economic, technical factors in system development. First a project team is formed. The team develops system flowcharts that identify the characteristics of candidate systems, evaluate the performance of each system, weigh system performance and cost data and select the best candidate system for the job. The study culminates in a final report to the management.
Operational Feasibility:
Train Details: Customers may view the train timing at a date their name and number of tickets. Reservation: After checking the number of seats available the customers reserve the ticket. Billing: After reserving the required amount of tickets ,the customer paid the amount. Cancelation: If the customer want to cancel the ticket then 10% of the amount per person is deducted
Technical Feasibility:
If you believe that the requirement is substantially met but in a way that appears to be different from the descriptive statement, please explain the difference. If the requirement is not provided as part of the base system but you propose to deliver it as a customization, please describe the customization required and include costs associated within the customization in your proposals cost schedule. If you take exception to a requirement, please state the exception, its reason, and propose an alternative approach and solution.
Economical Feasibility:
The System must be economically beneficially and user friendly.
SYSTEM DESIGN Scope:

This system is basically concerned with the reservation and cancellation of railway tickets to the passengers. The need of this system arose because as is the known fact that India has the largest railway network in the whole of the world and to handle it manually is quite a tough job. By computerizing it, we will be able to overcome many of its limitations and will be able to make it more efficient. The handling of data and records for such a vast system is a very complex task if done manually but it can be made much easier if the system is computerized.
Database Design: 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. These functions will be handled with the help of following sub functions: It reserves and cancels seats for the passenger. It contains information about the trains. It contains information about the passenger. It contains the details of reservation fees, any concessions etc. It makes entries for reservation, waiting, cancelled tickets. It will update for uptime and downtime trains.
DATA FLOW DIAGRAMS: The data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data moves from input to output. The DFD may be used to represent a system or software at any level of abstraction. In fact DFD may be partitioned into levels that represent increasing information flow and functional detail. Level 1 data flow diagram: The level 1 DFD or a context model represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows, respectively. In level 1 diagram shown below, the passenger fills either the reservation or cancellation form as input. He gets the ticket as the output and the report is sent to the administration.
Up/down train info Fill cancellation form Passenger Fill reservation form Ticket info
Railway Reservation
resva/cancle info passenger info Waiting info
Admin
Level 1 DFD Or Context Free Diagram

Level 2 data flow diagram
Reservation storage file Ticket generation process Passenger
Reservation Process Report To Admin
Enquiry
Down Storage
Up Storage
A level 2 DFD is the furthur refinement of level 1 DFD showing greater details and functionalities. In this, the single bubble of level 1 DFD is refined furthur . Each of the processes depicted at level 2 is a subfunction of the overall system depicted in the context model. As shown in the DFD above, the passenger either enquires about the trains or goes directly for the reservation or the cancellation processes as a
result of which he gets the ticket generated. The reports are then sent to the administration. Level -3 data flow diagram:
Reservation Report Confirmation Process
Reservation
Reservation
Query Process Searching Reservation process Passenger Waiting Ticket Generation process Waiting Process
Inquiry Railway dept
Cancellation Process
Generate Ticket Cancel table
Reservation table
Waiting table Generate report 23 Jagannath Gupta Institute of Engineering and Technology Plot no. IP-2&3,Phase IV,Sitapura Industrial Area, Opp.Chokhi Dhani,Jaipur.
The level 3 DFD is the further refinement of the level 2 DFD. As shown in the DFD above the passenger has many options like he can directly go to the reservation counter or can first inquire and then go to the reservation counter or he can just inquire and return back. If the passenger wants reservation then the seats are checked for availability and if the seats are available the confirmation ticket is generated otherwise he is asked for waiting and waiting ticket is generated if he wants. If the user wants tickets to be cancelled he is given the cancellation ticket and the reports of all the transactions are sent to the administrator.
Entity Relationship Diagram:

Entity relationship diagram expresses the overall logical structure of a database graphically. It shows the relationship between different entities. The entities can have composite, multivolume or derived attributes. The entities and their attributes are: 1 Passenger #. Name *. First name *. Middle name *. Last name #. Gender #. Address *. House no. *. Street *. City #. Age #. Phone no. 2 Form #. Form no. 3 Ticket #. Ticket no. *. Waiting *. Confirmed *. Cancelled 4 Reservation counter 5 Administrator 6 Train #. Train no #. Train name #. Source #. Destination 7 Seat #. Seat no. #. Compartment no.
First Name
Middle Last Name Gender
H.No
Street City
Name
Address Form No.
Ph No. Age Passenger Fills Form
Issue Ticket No. Generate
Submit Send Info.
Ticket Status Wait Cancel Train Res.
R.C.
Administra tor
Chec k Allotted
Seat
Seat No.
Destination T No. Source
Compartment No.
T Name
ENTITY RELATIONSHIP DIAGRAM

Module Description:
1. 2. 3. 4. 5. 6. Fill: The passenger fills the form. Submit: The form is submitted to the reservation counter. Check: The reservation counter checks the seats. Generate: Reservation counter generates the ticket. Issue: Reservation counter issues ticket to the passenger. Send info: The reservation counter sends information to the administrator. 7. Allotted: The seat is allotted in the train.
Symbols
Meanings Data flow Process Data store Entity
INTERFACE REQUIREMENTS Graphical Interface: This is used to describe a user friendly environment which uses graphical images (such as icons) instead of a command line to interact with the computer, GUIs have made computers more user friendly and more accessible to any user no matter what experience they may have, a typical GUI is the Windows operating system. A GUI uses a combination of technologies and devices to provide a platform the user can interact with, for the tasks of gathering and producing information. A series of elements conforming a visual language have evolved to represent information stored in computers. This makes it easier for people with few computer skills to work with and use computer software. The most common combination of such elements in GUIs is the WIMP ("window, icon, menu, pointing device") paradigm, especially in personal computers. The WIMP style of interaction uses a physical input device to control the position of a cursor and presents information organized in windows and represented with icons. Available commands are compiled together in menus, and actions are performed making gestures with the pointing device. A window manager facilitates the interactions between windows, applications, and the windowing system. The windowing system handles hardware devices such as pointing devices and graphics hardware, as well as the positioning of the cursor. In personal computers all these elements are modeled through a desktop metaphor, to produce a simulation called a desktop environment in which the display represents a desktop, upon which documents and folders of documents can be placed. Window managers and other software combine to simulate the desktop environment with varying degrees of realism
Command Line Interface: A command-line interface (CLI) is a mechanism for interacting with a computer operating system or software by typing commands to perform specific tasks. This text-only interface contrasts with the use of a mouse pointer with a graphical user interface (GUI) to click on options, or menus on a text user interface (TUI) to select options. This method of instructing a computer to perform a given task is referred to as "entering" a command: the system waits for the user to conclude the submitting of the text command by pressing the "Enter" key (a descendant of the "carriage return" key of a typewriter keyboard). A command-line interpreter then receives, parses, and executes the requested user command. The command-line interpreter may be run in a text terminal or in a terminal emulator window as a remote shell client such as PuTTY. Upon completion, the command usually returns output to the user in the form of text lines on the CLI. This output may be an answer if the command was a question, or otherwise a summary of the operation. Hardware Interface: The ARRS includes two major hardware components: cellular phones and regular PC's. The cell phones require WAP (wireless application protocol) network protocol, which is already programmed in the latest phones. This is similar to the seven layers of network protocol, except that they are broken down into five protocols. The WAP protocol is able to communicate with the servers known as Gateway servers, which listen to requests made using these phone frequencies. The request is then transmitted to the regular server. Furthermore, the servers respond to these "air" requests and format the data to be displayed on the mini window that is available on the phone. The cellular phone has a processor, which is designed to process a language known as WML (wireless markup language). Therefore, the server formats the data in WML format, and passes these pages to the Gateway servers, which transmits the WML pages
to the cellular phones. The processor on these phones then translates the WML into a simplified version of the actual web page. The second component involves the regular PCs, which communicate with the server. The server then communicates with the database. The protocol involved between the PC's and the server is the HTTP protocol, which allows communication between the PC's and the Server. The remote PC's, such as someone accessing the ARRS from home using the Internet, are able access the information through the CGI. The requests come in through the HTTP protocol, and using an ODBC the database results are returned and processed using Perl to give an HTML web page. The format of the output is displayed as web pages. Software interface: The database engine can be embedded on a platform using i. An active my SQL server ii. A browser which acts as a client iii. An Apache HTTP server All the mentioned resources are free source and can be obtained easily from the internet.
PERFORMANCE REQUIREMENTS
The following sections list the performance requirements for the system. User Requirements: User Requirements
Location(s) and Number(s) of Users Expected Growth in Number of Users After 1 Year After 2 Years After 3 Years User Expectation Interactivity Reliability Adaptability Security Cost / Funding
Description of Requirement For Design Environment

Guangzhou, Nanjing, Shanghai 50% TBD TBD User expect that it provides a very easy to use graphical user interface For some applications, reliability must be 100% during the application session Network must adapt to user additions, deletions and changes Encryption software would be used for Credit Card transactions Less than $250K
Application Requirements: Since no specified service is indicated, then we have listed the applications as best efforts. This may change as we learn more about the application. The communication package is determined to be bursty in nature, with small data sizes and frequent transmissions. We can consider this application to be interactive-burst, while the database transactionprocessing application is described by the CRM as transferring large amounts of data (initial estimates are 1 MB/transaction), we have listed this application as interactive-bulk.
Categorizing Applications
Best-Efforts
Application Locations
Guangzhou and Nanjing All Locations All Locations
Communication 100 Kb/s Database Access 400 Kb/s Database Transaction processing 1.5 Mb/s
3.3.3 Host Requirements
Type of Host or Equipment

Host A Host B Host C PC Database Server Application Server
Numbers and Locations

Guangzhou (10), Nanjing(7), Shanghai(10) Shanghai Nanjing
It is available during all 24 hours. Offered through Mail express, super fast , Rajdhani & Shatabdi Trains. About 1520 Trains runs daily. Variety of compartments based on comfort : AC first class. AC sleeper. First class. AC three tier. AC chair car. Sleeper class Ordinary chair car.
Types of concerns & complexities: 44 types of quotas. 8 types of trains. 9 types of classes. 162 types of concessions. 127 types of bogies.
Non Functional Attributes

Security: The Railway reservation system should not compromise the customer information at any time. The user information will never be sold to other parties and will be kept secure at all times. Users will be authenticated to ensure that no unauthorized users gain access to private information. Reliability: The system should be capable of processing a given number of reservations within a give time frame with no errors and the system should be available and operational all the time. During the development of the prototype for the 3 cities, the system will be tested in its actual environment to ensure that it can handle the load of reservations that occur during a regular workday. Maintainability: The RRS source code will be kept well structure and documented so that it is easier to maintain and extend the system. All changes to the system shall be documented. Portability: The Railway reservation system will be developed using HTML and Java so that it can be accessed from any type of system using just a regular web browser. It will also be available to users that have web access on their cellular phones. The system will be tested on all types of hardware before being released to ensure that is it compliant with this requirement. Reusability: The Railway reservation system will be developed so that it is an easy to use system that requires the least amount of user input possible. Every input will be validated. The user should only have general computer use knowledge. Error messages will be displayed if the user enters an invalid value or tries to access a function without the required permissions. An easy and well-structured user manual will be provided to the CRM and the system will include descriptive help for all operations allowed.
Resource Utilization: The Railway reservation system will be developed so that it uses all type of functions and fulfill all the requirements of the system it uses the class hierarchy and pre inbuilt library functions which is completely utilized in the system designing and coding. Stable & Speed: The RRS system will be considered correct when the CRM approves the prototype presented and agrees that all the functions they require are implemented as stated in the Software Requirements Specification.
SECURITY
From security point of view, authentication will be done by password checking. If correct password has been entered by the user, the user will get further access to the system, otherwise he will have to re-enter the password. The facility to change the password has also been provided but for that the user will have to first enter the old password. The password can be four characters long.
Technical Issues: -
Data redundancy: It means that same data fields appear in many different files and often in different formats. In manual system, it poses quite a big problem because the data has to be maintained in large volumes but in our system, this problem can be overcome by providing the condition that if the data entered is duplicate, it will not be entered, otherwise, updating will take place. Difficulty in accessing the data: In manual system, searching information is time consuming but in our system, any information can be accessed by providing the primary key. Unsatisfactory security measures: In manual system, no security measures were provided but in this system, password security has been provided. The person can access the system by providing the correct password otherwise he is denied the access.
Cost & Schedules:

The cost of the system designing must me low and efficient.System must works with all its functionalities efficiently in lowest cost.The system updation must be scheduled time to time to better working of the system
Risks:
There are many risks involved with the system. y y y y y Unauthorized Access. Data Ambiguity. Data redundancy. Data Damage. Other Risks.
CONCLUSION
LIMITATION OF THE PROJECT: 1. The most significant limitation of over project is its dependency over the server because of this when is fail then whole work is to be stopped. 2. Response time of the system may vary because of variable network speed. 3. Another limitation of our project is that in this software and hardware requirement is high comparison of existing system. DIFICULTIES ENCOUNTERED: 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. 1. Real time transfer of the file with minimum time delay. 2. Searching an efficient security package and studying its usage. 3. Enabling the multi user environment and simultaneous usage of files. FUTURE ENHANCEMENT: 1. Extra and user defined security needs can be employed during request and response. 2. Records of client activities can be maintained. 3. Another enhancement would be to add more modules to cover all information off the system.
Rather than designing manually we have made use of computer as once that datas are input it performs accurate function. There is no chance of fault or miscalculation if the data are feeded 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 Railway Reservation System 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.
REFERENCES
Henry F Korth, Abraham Silberschatz, Database system concepts, McGrsw-Hill Internation editions, Computer Science Series (1991). Second Ed. Software Engineering ,McGrsw-Hill Internation editions. http://studentwebsite.blogspot.com/2009/05/implement-railway-reservationsystem_13.html. http://en.wikipedia.org/wiki/Command-line_interface. http://www.encyclo.co.uk/define/Gui.
Introduction Chinese Railway Passenger Reservation System Prototype
http://www.cs.swt.edu/~donshafer/project_documents/5391_Case.html
Situation Update Chinese Railway Passenger Reservation System
http://www.cs.swt.edu/~donshafer/Marketing Update(1).html
China 2000
http://www.china2thou.com
Pressman, Roger S., Software Engineering: A Practitioner s Approach, McGraw-Hill Companies, Inc., 1997.
PDFs: 1533OOAofRailwayTicketReservationSystem.pdf. databasesreport.pdf. 38642993-SRS-Documentation-for-Railway-Reservation-System.pdf.

43170803-Online-Railway-Reservation-System-Report.pdf. 44643342-This-Project-Introduces-Railway-Reservation-System.pdf. 45696254-Online-Railway-Reservation-System.pdf. 47643843-Railway-Reservation-System.pdf. 49068127-45696254-Online-Railway-Reservation-System.pdf. 52990271-railway-reservation-system.pdf.

Rahul

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rahul

Uploaded by

Copyright:

Available Formats

Introduction

Holdings was purchased by private investors Silver Lake Partners

December 2006, Travelport, which owns Galileo, agreed to buy and

market share is 16.9% globally and 31% in the U.S.

according to 2006 MIDT airline transaction data.

February 2010, JetBlue converted its reservation system over to the

SabreSonic Customer Sales and Service platform.

The General Description

Availability. single adult Passenger excluding d. e.

Description Inputs Source Outputs Destination

Post Condition Side Effects

Description Inputs Source Outputs Destination

Precondition Post Condition Side Effects

Inputs Source Outputs Destination Precondition Post Condition Side Effects

Description Inputs Source Outputs

Post Condition Side Effects

No change to payment information None

Source Outputs Destination Precondition Post Condition Side Effects

Operating Environment:     Windows NT. Windows Vista. Windows Xp. Windows 7.

Stability And Speed:

SYSTEM DESIGN Scope:

resva/cancle info passenger info Waiting info

Level 1 DFD Or Context Free Diagram

Level 2 data flow diagram

Reservation storage file Ticket generation process Passenger

Reservation Process Report To Admin

Reservation Report Confirmation Process

Inquiry Railway dept

Generate Ticket Cancel table

Entity Relationship Diagram:

Middle Last Name Gender

Address Form No.

Ph No. Age Passenger Fills Form

Issue Ticket No. Generate

Submit Send Info.

Ticket Status Wait Cancel Train Res.

Destination T No. Source

ENTITY RELATIONSHIP DIAGRAM

Meanings Data flow Process Data store Entity

Description of Requirement For Design Environment

3.3.3 Host Requirements

Type of Host or Equipment

Numbers and Locations

Non Functional Attributes

Cost & Schedules:

PDFs: 1533OOAofRailwayTicketReservationSystem.pdf.  databasesreport.pdf.  38642993-SRS-Documentation-for-Railway-Reservation-System.pdf.

You might also like

Operating Environment: Windows NT. Windows Vista. Windows Xp. Windows 7.

PDFs: 1533OOAofRailwayTicketReservationSystem.pdf. databasesreport.pdf. 38642993-SRS-Documentation-for-Railway-Reservation-System.pdf.