Railway Reservation System

Only available on StudyMode
  • Topic: Unified Modeling Language, UML diagrams, Indian reservation
  • Pages : 10 (1039 words )
  • Download(s) : 1266
  • Published : January 19, 2013
Open Document
Text Preview
|Ex.No:4 |ONLINE TICKET RESERVATION SYSTEM | | | |

PROBLEM STATEMENT:

The “Any Where Any Time Advance Reservation” system is the online ticket reserving system where the passengers can reserve the tickets for their travel, cancel the reserved ticket and they can view the status of the ticket before travelling.

The passenger who is reserving the ticket in AWATAR unless they are the member of AWATAR .The passenger can reserve the ticket by giving the required detail in the form and submit it for the processing .They can reserve for at the max for five members and a single ticket is provided for them. The administrator the AWATAR can control the ticket reservation and the accounts of the passengers who are signing up in AWATAR. The administrator can reset the seats, fares of the tickets, and generates the PNR number for the ticket that are reserved.

The sole control of the system is handled by the administrator. The printer prints the tickets that are reserved by the passenger. The passenger can sign-up for only one time and he can sign in for any number of times for reserving, cancelling and viewing the tickets.

The AWATAR system provides flexibility for the persons based on the age, the passengers are fared based on the age and the place of travelling. This makes ease of use in using AWATAR system. The system tracks for the database any number of times for reserving, cancelling and status viewing.

The passenger can see the status of the classes that are available in the train which he is going to travel by noticing the number of seats details from the display board.
The cancellation of the tickets is also very easy so that the passenger can cancel the tickets that he has booked.

PROBLEM REQUIREMENTS:

1. Basic Requirements:

1) Source place.

2) Destination place.

3) Date of journey.

2. Functional Requirements:

1) Details of passengers.

2) Details of the coach.

3) Pay the amount using visa card or debit card.

4) Give out the balance

5) Show the detail of ticket.

3. Non-Functional Requirements:

1) Trading system failure.

2) Unavailability of date.

3) Coach Unavailability

4) Insufficient amount for making payment.

5) Unavailability of berth.

MODELING:

UML DIAGRAMS:

Use case Diagram:

[pic]

Figure1: Use Case diagram for Online reservation system

Class Diagram:

[pic]

Figure2: Class Diagram for Login

[pic]

Figure3: Class Diagram for Reservation

Activity Diagram:

[pic]

Figure4: Activity Diagram for Login

[pic]

Figure5: Activity diagram for Reservation

Sequence Diagram:

[pic]

Figure6: Sequence diagram for Login

[pic]

Figure7: Sequence diagram for Reservation

Collaboration Diagram:

[pic]

Figure8: Collaboration diagram for Login

[pic]

Figure9: Collaboration diagram for Reservation

Component Diagram:

[pic]

Figure10: Component diagram for Online Reservation System

Deployment Diagram:

[pic]

Figure11: Deployment diagram for Online Reservation System

SOFTWARE DEVELOPMENT:

CODE IMPLEMENTATION:

LOGIN FORM:
MAIN FORM:
Private Sub Command1_Click()
Form2.Show
Form1.Hide
End Sub
Private Sub Command2_Click()
End
End Sub

ENTRY FORM:
Public a As New NewClass
Private Sub Command1_Click()
a.viewdetails
End Sub
Private Sub Command2_Click()
Form4.Show
Form2.Hide
End Sub
Private Sub Command3_Click()
Form5.Show
Form2.Hide
End Sub
Private Sub Command4_Click()
End
End Sub
Private Sub Form_Load()
Set a = New NewClass
End Sub

TRAIN DETAILS FORM:
Private...
tracking img