Upload
vijayantpanda
View
77
Download
13
Tags:
Embed Size (px)
DESCRIPTION
rail
Citation preview
1 | P a g e
RAILWAY RESERVATION SYSTEM
2 | P a g e
INDEX:
Topic Page No.
1. Problem Statement 3
2. Identification of Actors and Justification 4
3. Use Case Model 5
4. Use Case Documentation 6
5. Activity Diagram 10
6. Sequence Diagram 11
7. Class Diagram 12
3 | P a g e
PROBLEM STATEMENT: RAILWAY RESERVATION
SYSTEM:
Indian Railways provides for advance reservation on all long-distance travel. The passenger seeking reservation of berth or seats should purchase tickets from Railway Reservation Offices.
To make an advance booking, the passenger is expected to fill in a prescribed application form
and submit it to the reservation counter with the appropriate amount.
Indian Railways wishes to develop a ticketing and reservation system. This must support
advance booking of tickets, cancellation of tickets and change of class of a ticket. All these are handled by
a Reservation Clerk.
The system will also have a querying facility that allows user to check train time-tables, fares and
availability of tickets.
4 | P a g e
IDENTIFICATION OF ACTORS AND JUSTIFICATION:
1. PASSENGER / TRAVELLER:
The Passenger/Traveller is a passive user-actor who initiates the process and obtains the tickets, a
goal of measurable value. The passenger enquire ticket availability and other details, reserve seats ,
berths, tickets and cancel tickets.
2. RESERVATION CLERK:
The Reservation Clerk is an active user-actor, who triggers the system and has the role of issuing
the tickets with the responsibility of collecting the correct fare amount from the passenger , which is a
measurable value. The Reservation Clerk process requisition for booking, process ticket to print and
submits ticket data for updation.
3. RESERVATION DATABASE:
The Reservation Database plays the role of system server. It processes reservation data, process
ticketing, process cancellation and update the status by date, time, etc.,
5 | P a g e
USE CASE MODEL:
c
6 | P a g e
USE CASE DOCUMENTATION:
1. ENQUIRIES ON AVAILABILTY:
Description: The main purpose of using this use case is to know the details of a particular train is
available or not. Along with reservation type, check train time-tables, fares, date and availability of
tickets.
Primary Actor: Reservation Database
Secondary Actor: Passenger / Traveller
Main Flow: The user enquires booking clerk. The booking clerk checks the database. On success the
traveller makes reservation.
Pre-Condition: The passenger should have a train for destination place.
Post-Condition: On success the traveller makes reservation and the reservation database is modified after
reservation.
7 | P a g e
2. RESERVATION AND TICKETING:
Description: Reserving the ticket(s) on a particular train on particular date for a destination by requesting
through a reservation form.
Primary Actor: Reservation Clerk
Secondary Actor: Passenger / Traveller
Main Flow: The passenger writes the reservation requisition form and submits it to the reservation clerk.
The clerk enters the form data and processes it and triggers ticket printing and issues ticket to passenger.
Pre-Condition: The passengers request should be available.
Post-Condition: The reservation database is modified after successful reservation.
8 | P a g e
3. CANCELLATION:
Description: Cancelling the tickets after issuing and payment.
Primary Actor: Passenger /Traveller
Secondary Actor: Reservation Clerk
Main Flow: The passenger fills the cancellation form with the train number, date and ticket number and
submits it to the reservation clerk. The clerk cancels the reservation and updates the database. Finally the
clerk returns the money.
Pre-Condition: The passenger should have performed a reservation.
Post-Condition: The reservation database is updated after cancellation and the availability moves to the
immediate waiting list.
9 | P a g e
4. CHANGE OF CLASS OF A TICKET:
Description: The main purpose is to change the class of a ticket i.e., sleeper class, AC class, general, etc.,
Primary Actor: Reservation Clerk
Secondary Actor: Passenger / Traveller
Main Flow: The passenger will fill the upgrade form and submit it to the reservation clerk. The
reservation clerk processes it. If availability exists the clerk changes the class and issues the new ticket.
Pre-Condition: The passenger should have performed some reservation.
Post-Condition: The database is upgraded and a new ticket is issued.
10 | P a g e
ACTIVITY DIAGRAM
11 | P a g e
SEQUENCE DIAGRAM
12 | P a g e
CLASS DIAGRAM