Indian Railway Reservation System Revised
PROBLEM STATEMENT:
This RAILWAY RESERVATION MANAGEMENT SYSTEM should be able to manage all the reservation related functions. The system should be distributed in nature. This system is divided into five zones.
NORTH ZONE
SOUTH ZONE
EAST ZONE
WEST ZONE
CENTRAL ZONE
Each zone should have same functionalities. Each zone will stores the information about train name, train schedules, availability. The administrator should be able to enter any change related to the train information like change in train name, number etc.
The system should be able to reserve seat in a train for a passenger. First the clerk will check for availability for the seats in a particular train on a specified date of journey. If it is available the clerk will reserve seats. The passenger will be given a unique PNR no.
The system should be able to cancel a reservation. The clerk will delete the entries in the system.
The passenger can check their reservation status online by entering their PNR no. The system will display his current status like confirmed, RAC or waiting list. They are also able to see information related to the train schedules.
The system should be able to print the report like it should be able to generate reservation chart, train report, reservation ticket which will have train no and name, date of journey, boarding station, destination station, person name, age, sex, total fare and a unique PNR no. The system should be able to print the cancellation ticket which will have total fare and the amount deducted. | |
2.1.6. MEMORY CONSTRAINTS
A maximum of 42 laces hits per day have been recorded.
OPERATING ENVIRONMENT:
The OS types are
Windows NT
Windows XP
Windows 98
Linux
2.4. CONSTRAINTS
Less than 1 sec for local transactions.
3 sec for network transaction.
Capable for providing transaction for 22 hrs per day.
Uptime of PRS is 99.5 + %
3.2. PERFORMANCE REQUIREMENTS:
It is available during all 24 hours.
Offered through Mail express, super fast ,
This RAILWAY RESERVATION MANAGEMENT SYSTEM should be able to manage all the reservation related functions. The system should be distributed in nature. This system is divided into five zones.
NORTH ZONE
SOUTH ZONE
EAST ZONE
WEST ZONE
CENTRAL ZONE
Each zone should have same functionalities. Each zone will stores the information about train name, train schedules, availability. The administrator should be able to enter any change related to the train information like change in train name, number etc.
The system should be able to reserve seat in a train for a passenger. First the clerk will check for availability for the seats in a particular train on a specified date of journey. If it is available the clerk will reserve seats. The passenger will be given a unique PNR no.
The system should be able to cancel a reservation. The clerk will delete the entries in the system.
The passenger can check their reservation status online by entering their PNR no. The system will display his current status like confirmed, RAC or waiting list. They are also able to see information related to the train schedules.
The system should be able to print the report like it should be able to generate reservation chart, train report, reservation ticket which will have train no and name, date of journey, boarding station, destination station, person name, age, sex, total fare and a unique PNR no. The system should be able to print the cancellation ticket which will have total fare and the amount deducted. | |
2.1.6. MEMORY CONSTRAINTS
A maximum of 42 laces hits per day have been recorded.
OPERATING ENVIRONMENT:
The OS types are
Windows NT
Windows XP
Windows 98
Linux
2.4. CONSTRAINTS
Less than 1 sec for local transactions.
3 sec for network transaction.
Capable for providing transaction for 22 hrs per day.
Uptime of PRS is 99.5 + %
3.2. PERFORMANCE REQUIREMENTS:
It is available during all 24 hours.
Offered through Mail express, super fast ,