EXPERIMENT-6

AIM: To prepare use case description of e-railway ticketing system

REQUIREMENTS:
 I7 processor
 USB DRIVER
 SCREEEN RESOLUTION OF 800X600
 MICROSOFT WORD
 WINDOWS 10

THEORY:

1. LOGIN:

1.1 INTRODUCTION-
This use case describes for logging into E-Ticketing system based on user
previleges

1.2 ACTORS-

The following actors interact and participate in use case Passenger admin and
clerk

1.3 FLOW OF EVENTS

1.3.1 BASIC FLOW:

 This use case starts when actor wishes to log into E-Ticketing System.
 The system requests that actor enters his user id, password and role
 Actor passes his credentials
 System validates the credentials
1.3.2 ALTERNATIVE FLOW:
Invalid name/password/role
If in basic flow, actor enters wrong credentials then the system throws error
message. The actor can decide to return to basic of beginning of login page.
1.4 SPECIAL REQUIREMENTS:
None
1.5 PRE CONDITIONS
All actors must have userId , Password ,role created for them on system
1.6 POST CONDITIONS:
 If use case is successful, user is logged into system successfully.
1.7 RELATED USE CASE:
None

2. CHECK FOR AVAILIBILITY

2.1 INTRODUCTION-
This use case allows actor to view seat availability and view status of waiting
tickets in different coaches.

2.2 ACTORS-

Passenger

2.3 FLOW OF EVENTS

2.3.1 BASIC FLOW:

 This use case starts when actor waits to check for availibility
 The system requests that actor enters his user id, password and role
 Actor passes his credentials
 Info is saved into db
 System validates the credentials
2.3.2 ALTERNATIVE FLOW:
Train Seat is not available
If in basic flow, actor enters wrong credentials then the system throws error
message. The actor can decide to return to basic of beginning of login page.

2.4 SPECIAL REQUIREMENTS:

None

2.5 PRE CONDITIONS

All actors must have userId , Password ,role created for them on system

2.6 POST CONDITIONS:

If use case is successful, user knows the status successfully.

2.7 RELATED USE CASE:
Book Ticket

3. BOOK TICKET
 3.1 INTRODUCTION

This use case allows actor with role of passenger to view seat availability and view
status of waiting tickets in different coaches. He can do bookings by choosing seat
numbers and coaches.

3.2ACTORS-
Passenger

3.3 FLOW OF EVENTS

3.3.1 BASIC FLOW:

 This use case starts when passenger wishes to view availability of seats
 The system requests that actor enters his user id, password and role
 List of trains with names is provided to passenger where he checks for
availability of seats.
 Passenger info is saved
 System validates the credentials
3.3.2 ALTERNATIVE FLOW:
No seat is available
If in basic flow, actor enters wrong credentials then the system throws error
message. The actor can decide to return to basic of beginning of login page.

3.4 SPECIAL REQUIREMENTS:

None

3.5 PRE CONDITIONS

Passenger must be logged into system
3.6 POST CONDITIONS:
If use case is successful, bookings can be done successfully with
registration in seat id
3.7 RELATED USE CASE:
Payment

4. PAYMENT

4.1 INTRODUCTION

This use case allows actor with role of passenger for booking payment. Payments can
be done online or by credit cards

4.2 ACTORS-
Passenger, Bank
 4.3 FLOW OF EVENTS

4.3.1 BASIC FLOW:

 This use case starts when passenger wishes to view availability of seats
 The system requests that actor enters his user id, password and role
 List of trains with names is provided to passenger where he checks for
availability of seats.
 Passenger info is saved in db and transaction is done online with actor “Bank”
 System validates the credentials
4.3.2 ALTERNATIVE FLOW:
Card details entered are incorrect
If in basic flow, actor enters wrong credentials then the system throws error
message. The actor can decide to return to basic of beginning of login page.

4.4 SPECIAL REQUIREMENTS:

None

4.5 PRE CONDITIONS

Passenger must be logged into system
4.6 POST CONDITIONS:
If use case is successful, bookings can be done successfully with
registration in seat id and coaches
4.7 RELATED USE CASE:
Cancel Ticket

5. CANCEL TICKET

5.1 INTRODUCTION

This use case allows actor with role of passenger for cancelling previously booked
tickets. Cancellations of reserved tickets causes 20% reduction in original fees

5.2 ACTORS-
Passenger, Bank, Admin

5.3 FLOW OF EVENTS

4.3.1 BASIC FLOW:

  This use case starts when passenger wishes to cancel the ticket
 The system requests that actor enters his user id, password and role
 List of trains with names is provided to passenger where he checks for
availability of seats which he wishes to cancel.
 Passenger info is saved in db and transaction is done online with actor “Bank”
 System validates the credentials and cancels the ticket
4.3.2 ALTERNATIVE FLOW:
Card details entered are incorrect
If in basic flow, actor enters wrong credentials then the system throws error
message. The actor can decide to return to basic of beginning of login page.

5.4 SPECIAL REQUIREMENTS:

None

5.5PRE CONDITIONS

Passenger must be logged into system and ticket booking must be done

5.6 POST CONDITIONS:

If use case is successful, cancellation of bookings can be done successfully

with 20% deduction in fare.

5.7RELATED USE CASE:

None

6. CHECK THE TRAIN STATUS

6.1 INTRODUCTION

This use case allows actor with role of passenger for checking the status of train like
whether it is right on time, its arrival time and departure time. Payments can be done
online or by credit cards

6.2ACTORS-
Passenger, Bank, Admin

6.3 FLOW OF EVENTS

6.3.1 BASIC FLOW:

 This use case starts when passenger wishes to view availability of seats
  The system requests that actor enters his user id, password and role
 List of trains with names is provided to passenger where he checks for
availability of seats.
 Passenger info is saved in db and transaction is done online with actor “Bank”
 System validates the credentials and admin checks the details of train
passenger wishes to take update on
6.3.2 ALTERNATIVE FLOW:
Train not available
If in basic flow, actor enters wrong credentials then the system throws error
message. The actor can decide to return to basic of beginning of login page.

6.4 SPECIAL REQUIREMENTS:

None

6.5 PRE CONDITIONS

Passenger must be logged into system

6.6 POST CONDITIONS:

If use case is successful, bookings can be done successfully with

registration in seat id and coaches and delay of timings if any can be
viewed
6.7 RELATED USE CASE:
Update Train Schedule

7. UPDATE TRAIN SCHEDULE

7.1 INTRODUCTION

This use case allows actor with role of passenger for checking the status of train like
whether it is right on time, its arrival time and departure time. Admin updates the
required info on web page

7.2ACTORS-
Admin

7.3 FLOW OF EVENTS

7.3.1 BASIC FLOW:

 This use case starts when admin wishes to see all the timings
 The system requests that actor enters his user id, password and role
  List of trains with names is provided to passenger where he/she checks for
availability of seats.
 Passenger info is saved in db
 System validates the credentials and admin checks the details of train
passenger wishes to take update on
7.3.2 ALTERNATIVE FLOW:
Train not available

7.4 SPECIAL REQUIREMENTS:

None

7.5 PRE CONDITIONS

Admin must be logged into system

7.6 POST CONDITIONS:

If use case is successful, admin can update all the scheduling of train
7.7 RELATED USE CASE:
None

CONCLUSION: The use case description was written successfully