Professional Documents
Culture Documents
Railway Reservation Case Study
Railway Reservation Case Study
PROBLEM STATEMENT
4. LOGIN: Only the user with specified login id & password can get
access to the system. This provides security from unauthorized access.
::CONTEXT DIAGRAM::
The context diagram shows the interaction between the external
entities and the system.Here we don’t deal with the internal
subprocesses of the system.
DATA DICTIONARY:
Data dictionary ensures that the customer and the developer use
the same definition and terminologies.
Passenger : information maintained about each
passenger
Passenger-details = courtesy title + passenger-name +
passenger-address + phone-no.
PNR No. = information maintained about particular
ticket.
Passenger-name= courtesy title + first-name +
(middle-name) + last-name.
Passenger-address = h-no +street-address + city +
postal-code + (country).
It enables us to maintain the railway details like t.1Product Perspective :heir timing
number of seat available,and reservation billing and canceling the ticket.
2.1.1User Interface:
Key Board and Mouse.
2.1.2Hardware Interface:
Printer
Normal PC
2.1.3.Communication Interfaces
Indian railway’s website www.indianrailway.gov.in offeres PRS enquiries on the internet
Berth/Seat availability,Passenger status ,fare,train schedule etc.
Mobile telephone based SMS inquiry service.
Setting up of voice response system.
2.1.4Operating Environment:
The OS types are:
Windows NT
Windows XP
Windows Vista
Windows 7
2.1.5Operations:
Any reservation counter from 8 pmto 8am.
Prior to 60 days of journey.
One form for six persons.
Reserved ticket done through pre defined logic.
2.2Product Functions:
It tells the short note about the product.
2.2.1Train Details:
Customers may view the train timing at a date their name and number of tickets.
2.2.2Reservation:
After checking the number of seats available the customers reserve the ticket.
2.2.3Billing:
After reserving the required amount of tickets,the customer paid the amount.
2.2.4Cancelation:
If the customer want to cancel the ticket then 10% of the amount per person is deducted.
2.3 User characteristics:
Knowledge user
No voice user
Expert user
2.4.Constraints
Less than 1 sec for local transactions.
3 sec for network trasnsaction.
Uptime of PRS is 99.5+%.
SOFTWARE CONSTRAINTS:
Designing->Rational Rose
3.SPECIFIC REQUIREMENTS
3.1.EXTERNAL INTERFACES
Train Delay Alert Service.
Booking Terminals
Interactive voice Response System.
3.2.PERFORMANCE REQUIREMENTS:
It is available during all 24 hours.
Offered through Mail express, superfast,Rajdhani& Shatbdi Trains.
About 1600 trains run 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 and complexities:
44 types of quotas.
8 types of trains.
9 types of class.
162 types of concessions.
127 types of bogies.
3.3Software system Attributes:
Reliable.
Available.
Secure.
4.Document Approval
The bill passed on any proposal related to railway management needs approval of
ministry of railway department.