TABLE OF CONTENTS · table of contents table of contents.....i
Table of Contents
Transcript of Table of Contents
Table of Contents
1. Purpose ………………………………………………………………………………………….
1.1 Introduction
1.2 Motivation and Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
2. Use Cases……………………………….………………………………………………….
2.1 Use Case Diagram
2.2 Use Case Statements
2.2.1 Reservation of Seat
2.2.2 Cancellation of Seat
2.2.3 Searching
2.2.4 Updating
3. Functional Specifications…………………………….………………………………………………….
3.1 Primary Functionalities
3.1.1 Reservation of Seats
3.1.2 Cancellation of Seats
3.2 Extended Functionalities
3.2.1 Database Search Option
3.2.2 Updation Option
3.3 Middleware Services
3.3.1 Communication
3.3.2 Fault tolerance
3.3.3 Persistence
4. Project Plan……………………….………………………………………………….
4.1 System overview
4.2 Conceptual model
5 Definitions, Acronyms, and Abbreviations………………………………………..………
1. Purpose
1.1 Introduction
The Pakistan Railways Reservation System (PRRS) – a commercial GUI based distributed application would run on Windows operating system and is developed in view to provide our client with automated and user friendly tool for handling reservation related activities as per customer requirements.
1.2 Motivation
Presently Pakistan Railways uses console based application to manage its database. System currently uses primitive Graphical user interface. Reservations can only be made locally i.e for any particular “source city” X to “destination city” Y, reservation is done only at city X.
We aim to provide them with a user friendly GUI based application on dotNET platform using Oracle 8i for database management so that a customer can make reservations from any source to destination from any city.
Later on, if user needs, software can be enhanced by making it a web based application with enhanced search features and direct controlled customer interaction with PRRS.
1.3 Definitions, Acronyms and Abbreviations
Please refer to Section 5 for definitions, acronyms and abbreviations used in this document for Pakistan Railways Reservation System
1.4 References
IEEE std 830-1998
Initial requirements Report
2Use Cases
2.1 Use Case Diagram
2.2 Use Case Statements
2.2.1 Reserving
2.2.1.1Booking
Passenger arrives at the booking counter and specifies the Source &
Destination Stations along with the date on which he/she wants to travel
in a specific class. The Booking clerk checks the availability of seats and
in case of affirmation, asks the passenger to give in the fare of the ticket.
Passenger pays the fare and booking clerk updates the data and prints the
ticket
2.2.1.2 Canceling
Passenger arrives at the booking counter with the ticket and asks the
clerk to cancel his reservation. The Booking clerk checks the record of
his seat and deletes the record .Passenger gives back ticket and takes
money back.
2.2.2 Searching
Booking clerk feeds a particular query and get the required data.
2.2.3 Updating
Administrator updates the record for the inclusion and deletion of
routes ,changing train attributes and schedules in the current railway network.
The route information will be updated to all the servers for consistency.
3Functional Specifications
The PRRS will be used by the operator to book/cancel seats from any source to destination from any
client computer by communicating with the local server. Secondly it will provide different statistics
about passengers ,routes ,trains and schedules w.r.t various scenarios as specified in the query.
3.1Primary Functionalities
3.1.1Reservation of seats
The user will be provided with detailed information about the seats available in a certain train. The seats
presented will be primarily sorted by the classes (class A, class B etc present in that train). The charges
associated with each class and the facilities available in that will be shown against each class. The user
can book a seat or may even confirm that. User will enter his brief description in the system, to be used
for record keeping and his preferred seat to be allocated to him if available. Seat will be only confirmed
once the payment is made for that seat. The information of that booking will be updated to all the servers
immediately. In case all the seats are reserved, user will be placed in a waiting queue and there status will
be notified to them at regular intervals.
3.1.2Cancellation of Seat
A seat may be canceled in a specific period of time or must be confirmed else wise.A non confirmed seat
may be canceled after some predefined time automatically and allotted to any other passenger in the
waiting queue. The cancellation will be notified to all the local servers and the main server. Incase of
automatic cancellation, the customer will also be notified about the action.
3.2Extended Functionalities
3.2.1Database search option
Traveling details will be present in the respective local servers. The database can be queried using options
Details of trains and passengers departed from and arrived to a particular location
Details of passengers in a particular train or for a specified time frame
Preferred train classes, routes and timings for a specified time frame
These options will be used for future policy making and scheduling work. The information will not be
available to public domain and will be for internal use only.
3.2.2Updation Option
Network administrator will have a provision for the inclusion and deletion of routes ,changing train
attributes and schedules in the current railway network. The route information will be updated to all the
servers for consistency.
3.3Middleware Services
Our main aim will be to implement fault tolerance feature of middleware. However ,if time allows we
will implement following services as well
3.3.1Communication
Client(local) accesses central server which in turn becomes a client and accesses the remote local servers
to retrieve and update data and provides it to the client(local).
3.3.2Fault Tolerance
Standby central server will be used in Listening mode and monitors the state of active server .As soon as
the active server goes down, it will restore the current state and will act as an active server.
3.3.3Persistence
Any changes made to local servers data will be and updated in remote local servers via central server to
give a single consistent state.
4Project Plan
4.1 System overview
4.2 Conceptual model
Definitions, Acronyms, and Abbreviations
PRRS : Pakistan Railways reservation system
Primitive GUI: Basic level Graphical user interface
Controlled Customer Interaction : Customer will only be allowed to make reservation and will
not be able do any other changes