Experiment 5 AIM: To make Use case diagram of Railway Reservation System.

Use case diagram:

Use Cases 1.Login:

1.1Discription; login module is to logged in the railway reservation system 1.2 Actors: Passanger,Admin,Staff 1.3 Flow of events: 1.3.1 Basic flow: This use case starts when actor wishes to login to railway reservation system the system request to actor to enter username and password Actors enter username and password System validates username and password from the account database. 1.3.2 Alternative flow: Invalid username or password: if entered login details is incorrect than it generates error 1.4 Pre conditions; All users must have a user account created by admin. Prior to executing user cases. 1.5 Post- conditions: If the use case is successful,actor is logged into system,if not the system state is unchanged

2.Train info:
2.1 Discription; this modules shows a description of trains- train no,arrival time,departure time ,fare,kms etc. 2.2 Actors: Passanger,Staff 1.3 Flow of events: 2.3.1 Basic flow: This use case starts when staff or passenger wish to view trains details Actor can view train info by entering train no,train name or station 2.3.2 Alternative flow: if search criteria doesnt match then it displays message to search again. 2.4 Pre conditions; train info must be updated by the admin of the system prior to executing this case 2.5 Post- conditions:

If search criteria match ,will display information,otherwise system state will not changed. 3. Reservation: 3.1Discription; this modules allow actor to reservation of seat 3.2 Actors: Passanger,Staff 3.3 Flow of events: 3.3.1 Basic flow: This use case starts when staff or passenger wish to reserve seat in the train 1. Actor(passenger) has to enter train info then debit or credit info for payment. 2. staff confirms the ticket for reservation . 3.Provides a pin no for modifications. 3.3.2 Alternative flow: if seats are full or payment not successful ,system displays a message about it. 3.4 Pre conditions; Transactions maintaninance and database handling operations must be maintained by admin or staff prior to executing this case. 3.5 Post- conditions: If reserve confirms then it will notify,otherwise system state will not changed.

4. Cancellation:
4.1Discription; this modules allow actor to cancellation of seat 4.2 Actors: Passanger,Staff 4.3 Flow of events: 4.3.1 Basic flow: This use case starts when staff or passenger wish to cancel seat in the train 1. Actor(passenger) has to enter train info and pin no provided in reservation. 2. if cancellation criteria matches,system will response of cancellation message and transactions will be done . 3.notifies passenger about cancellations,payment back details. 4.3.2 Alternative flow: if date is extended ,system displays a message about it. 4.4 Pre conditions; Transactions maintaninance and database handling operations must be maintained by admin or staff prior to executing this case.

4.5 Post- conditions: If cancellation confirms then it will notify,otherwise system state will not changed.

5.Reservation status:
5.1Discription; this modules allow actor to check reservation status . 5.2 Actors: Passanger,Staff 5.3 Flow of events: 5.3.1 Basic flow: This use case starts when staff or passenger wish to check reservation status 1. Actor(passenger) has to enter train info and pin no provided in reservation. 2. If pin no matches it will displays full info about reservation. 5.3.2 Alternative flow: if pin not matches or expires it will display erroe. 5.4 Pre conditions; Passanger must be reserved a ticket and has a valid pin no before executing this phase 5.5 Post- conditions: If pin no matches system will display status ,otherwise system state will not changed.

6 Report Generator:
6.1Discription; this modules allow actor to generate transaction reports,reservation report 6.2 Actors: Admin,Staff 6.3 Flow of events: 6.3.1 Basic flow: This use case starts when actor wish to generate reports 6.3.2 Alternative flow: If actor is permissible report will be generated. 6.4 Pre conditions; Actor should be logged into system. 6.5 Post- conditions: If actor is logged in then report will generate ,otherwise system state will not be change.