system design of online ticketing system

SYSTEM DESIGNUSE CASE DESIGN AND ANALYSIS

Ticketing Automation Bangladesh Team- Wild Spider

This Presentation will cover

I. All Actors of the System

II. Subsystems of the system

III. Use case with all actors with all subsystem

IV. Separate use case diagram of all subsystems with all actors

V. Separate table of all use case of all sub systems with actors

VI. Define the action of actors and system response for all use case.

Actors of the System

Primary business actor

Primary system actor

External server actor

External receiver actor

Sub Systems of the system

Sub Systems

Maintenance Module

Reservation Module

Buy Module

Payment Module

Stuff MaintenanceMember MaintenanceBus Maintenance

Ticket ReservationTicket confirmation

Ticket Buy

Make PaymentPayment ProcessPayment Record

Bus Schedule Module

Add, Edit, View, Delete Schedule

Use cases for Maintenance ModuleUse Case Name Actor

Stuff Maintenance- Add New Stuff- Delete Stuff- Edit Stuff- View Stuff

System AdministratorSystem AdminSystem AdminSystem AdminSystem Admin

Member Maintenance- New Member- Edit Member Details- View Member Details- Delete Member

System Admin, MembersSystem Admin, MembersSystem Admin, MembersSystem Admin, MembersSystem Admin

Bus Maintenance- Add New Bus- Edit Bus Details- View Bus Details- Delete Bus Details

System Admin, Bus Company AdminSystem Admin, Bus Company AdminSystem Admin, Bus Company AdminSystem Admin, Bus Company Admin, MembersSystem Admin, Bus Company Admin

Use cases for Maintenance ModuleUse Case Name Actor

Schedule Maintenance- Add New Schedule- Delete Schedule- Edit Schedule- View Schedule

System Admin, Bus Company AdminSystem Admin, Bus Company AdminSystem Admin, Bus Company AdminSystem Admin, Bus Company AdminSystem Admin, Bus Company Admin, Members

Use cases for Reservation ModuleUse Case Actors

Add Reservation Member, System Admin

Cancel Reservation Member, System Admin

Add Reservation Payment Member, System Admin

Use Case Actors

Add Buy Order Member, System Admin

Confirm Buy Member, System Admin

Make Payment Member, System Admin

Use cases for Buy Module

Use cases for Payment ModuleUse Case Actors

Add New Payment Member, System Admin

Payment Processing Third party gateway

Invoice Creation Gateway, System Admin

Invoice Copy Delivery Member, System admin, Bus admin

Payment Reservation/Record System Admin, Bus Admin, Gateway provider

i. Use Case Diagram for TABTicketing Automation Bangladesh

Maintenance Module

Reservation Module

Buy Module

Payment Module

Bus Schedule Module

Use Case Diagram for Maintenance ModuleMaintain Stuff Details

Add New Stuff

Delete Stuff

Edit Stuff Details

View StuffDetails

Staff Maintenance

Use case of a subsystem with actors in a tableUse Case Name: Add new Staff

Brief Description: This use case allow the administrator to add new stuff to the company

Actor: Administrator

Main Flow:

Actor Action System Response

1. Display Maintenance Menu

2. Click “Update Staff Information” Button

3. Display Stuff Maintenance Form

4. Click “Add” Button

5. Key in Staff IC

6. Click “Check” Button

7. Verify Staff IC

8. Enter Staff Login Details


10. Verify Staff Login Details

11. Enter Staff Details

12. Click “Save” Button

13. Verify Staff Details

14. Save Record into Database

15. Show Message Box “Record Added”

16. Click “Ok” Button

Alternative Flows:

A-7 Step 5: If the staff IC exist in the database- System prompt “Invalid Applicant”

A-10 Step 8: If the staff login details not correct- System prompt “Please key in the correct data”

A-10 Step 8: If the staff details does not fill in and the wrong data- System prompt “Please enter correct data in the fields”

Use case of a subsystem with actors in a tableUse Case Name: Edit Staff Details

Brief Description: This use case is allow the administrator to edit the staff details


Main Flow:





4. Select Staff ID

5. Click “Search” Button

6. Display Staff Details

7. Click “Edit” Button

8. Change Staff Details


10. Verify Staff Details

11. Save record into database

12. Show Message Box “Record Updated”


Alternative Flows:

A-10 Step 8: If have empty field and the data not correct- System prompt “The field cannot leave it blank and key in the correct data”

Use case of a subsystem with actors in a tableUse Case Name: Delete Staff

Brief Description: This use case is allow the administrator to delete those staff already resign


Main Flow:





4. Select Staff ID



7. Click “Delete” Button

8. Show Message Box “Confirm Delete Staff”


10. Delete record from database

11. Show Message Box “Record Deleted”


Alternative Flows:

A-9 Step 10: If user click cancel button- Record remain in database

Use case of a subsystem with actors in a tableUse Case Name: View Staff Details

Brief Description: This use case is let the administrator to view the staff details


Main Flow:





4. Select Staff ID



Use Case Diagram for Maintenance ModuleMaintain Member Details

New Member

Edit MemberDetails

Delete Member

View MemberDetails

Member Maintenance

Use case of a subsystem with actors in a tableUse Case Name: Add New Member

Brief Description: This use case allow the administrator to add new members for the company

Actor: Administrator, Member

Main Flow:



2. Click “Update Member Information” Button

3. Display Member Maintenance Form


5. Key in Member IC


7. Verify Member IC

8. Enter Member Login Details


10. Verify Member Login Details

11. Enter Member Details


13. Verify Member Details




Alternative Flows:

A-7 Step 5: If the Member IC exist in the database- System prompt “Invalid Applicant”

A-10 Step 8: If the Member login details not correct- System prompt “Please key in the correct data”

A-10 Step 8: If the member details does not fill in and the wrong data- System prompt “Please enter correct data in the fields”

Use case of a subsystem with actors in a tableUse Case Name: Edit Member Details

Brief Description: This use case is allow the administrator to edit the Member details


Main Flow:





4. Select Member ID


6. Display Member Details


8. Change Member Details


10. Verify Member Details




Alternative Flows:

A-10 Step 8: If the data incorrect and blank data- System prompt “Please key in the correct data and data cannot leave it blank”

Use case of a subsystem with actors in a tableUse Case Name: Delete Member

Brief Description: This use case is allow the administrator to delete member


Main Flow:





4. Select Member ID




8. Show Message Box “Confirm Delete Member”





Alternative Flows:


Use case of a subsystem with actors in a tableUse Case Name: View Member Details

Brief Description: This use case is let the administrator to view the member details


Main Flow:





4. Select Member ID



Use Case Diagram for Maintenance Module

Maintain Bus Details

Add New Bus

Edit BusDetails

Delete Bus

View BusDetails

Bus Maintenance

Use case of a subsystem with actors in a tableUse Case Name: Add New Bus

Brief Description: This use case allow the administrator to add new bus for the company

Actor: Administrator & Administrator (Bus Company)

Main Flow:



2. Click “Update Bus Information” Button

3. Display Bus Maintenance Form


5. Key in Bus Number


7. Verify Bus Number

8. Enter Bus Details


10. Verify Bus Details




Alternative Flows:

A-7 Step 5: If the Bus number exist in the database- System prompt “Invalid Bus Number”

A-10 Step 8: If bus details not correct and have blank data- System prompt “Please key in the correct data and fill in the blank data”

Use case of a subsystem with actors in a tableUse Case Name: Edit Bus Details

Brief Description: This use case is allow the administrator to edit bus details


Main Flow:





4. Select Bus ID


6. Display Bus Details


8. Change Bus Details


10. Verify Bus Details




Alternative Flows:

A-10 Step 8: If bus detail incorrect and have blank data- System prompt “Please key in the correct data and fill in the blank data”

Use case of a subsystem with actors in a tableUse Case Name: Delete Bus

Brief Description: This use case is allow the administrator to delete bus for company


Main Flow:





4. Select Bus ID




8. Show Message Box “Confirm Delete Member”





Alternative Flows:


Use case of a subsystem with actors in a tableUse Case Name: View Bus Details

Brief Description: This use case allow the administrator to view the bus details

Actor: Administrator & Administrator (Bus Company), members

Main Flow:





4. Select Bus ID



Use Case Diagram for Bus Scheduling Module

Maintain Bus Schedule

View ScheduleDetails

Delete Schedule

Edit ScheduleDetails

Add New Schedule

Use case description for bus schedule moduleUse Case Name: View Schedule Details

Brief Description: This use case allow the administrator to view the bus schedule

Actor: Administrator & Administrator (Bus Company), Members

Main Flow:


1. Display Scheduling Menu

2. Click “ View Schedule Details” Button


4. Select Driver Name


6. Display Schedule Details

Use case description for bus schedule module

Use Case Name: Add New Schedule

Brief Description: This use case is let administrator to add the new schedule for member and staff


Main Flow:



2. Click “ Assign Schedule” Button

3. Display Scheduling Form


5. Key in New Destination


7. Verify New Destination

8. Enter Destination Details


9. Enter Schedule Details


11. Verify Schedule and Destination Details




Alternative Flows:

A-7 Step 5: If the destination exist in the database- System prompt “Invalid Destination”

A-11 Step 8: If destination details and schedule details incorrect- System prompt “Please key in the correct data”

A-11 Step 9: If the schedule details exist in the database- System prompt “This Schedule already exist in the database”

Use case description for bus schedule moduleUse Case Name: Edit Schedule Details

Brief Description: This use case is let administrator to edit the Schedule details


Main Flow:



2. Click “Assign Schedule” Button


4. Select Package ID




8. Change Schedule Details


10. Verify Schedule Details




Alternative Flows:

A-10 Step 8: If the data incorrect and blank data- System prompt “Please key in the correct data and data cannot leave it blank”


Use Case Name: Delete Schedule

Brief Description: This use case is let administrator to delete the schedule


Main Flow:



2. Click “Assign Schedule” Button


4. Select Package ID




8. Show Message Box “Confirm Delete Schedule”






Alternative Flows:



Use Case Diagram for Reservation Module

Reservation Module

Add Reservation

Add ReservationPayment

Cancel Reservation

Use case description for reservation module

Use Case Name: Add Reservation

Brief Description: This use case allow the member to add reservation

Actor: Member, Admin

Main Flow:


1. Display Reservation Form

2. Select Member ID

3. Select Departure Destination

4. Display Arrival Destination

5. Select Arrival Destination

6. Select Date



Use case description for reservation module


10. Select a time

11. Click “Next” Button

12.Select Seat

13. Click “Add as reserved” Button

14. Show Message “Seat Added as Reserved”

Use Case Diagram for Buy ModuleBuy Module

Select SeatAvailable

Add Payment

Use case description for buy module

Use Case Name: Buy Ticket

Brief Description: This use case allow the member to buy ticket

Actor: Member

Main Flow:


1. Display Buy Ticket Form

2. Select Member ID

3. Select Departure Destination

4. Display Arrival Destination

5. Select Arrival Destination

6. Select Date



Use case description for buy module9. Display Schedule Details

10. Select a time


12. Display Seat

13. Select Seat Number


15. Calculate Total Amount

16. Display Payment Form

17. Key in Payment Details

18. Click “Paid” Button

19. Verify Payment Details


21. Show Message “Record Added”

22. Display Reservation Confirmation

Alternative Flows:

A-8 Step 3: If the destination do not have schedule- System prompt “This Destination do not have any schedule”

A-19 Step 17: If the payment details incorrect and have blank value- System prompt “Please key in the correct data and fill in the blank value”

Use Case Diagram for Payment Module

Maintain Payment Module

Add New Payment

Payment Reservation/

Record

Payment Processing

Single InvoiceCreation

Use Case Name: Add New Payment

Brief Description: This use case is let administrator to add the new service for the bus

Actor: Members

Main Flow:


1. Display Payment Menu Options

2. Select Payment Method Option

3. Display Needed Details Form

4. Fill Up the Form Info and give Data

5. Click “Pay Now” Button

6. Display Confirmation ox

7. Click “Confirm” Button

8. Verify Payment Details

Use case description for repairing module


9. Process the payment by third party

10. Display Success Message

Use Case Name: Payment Process

Brief Description: This use case is let administrator to edit the Service details

Actor: Third Party System Provider

Main Flow:


1. Processing notification message

2. Processing Steps

3. Confirm Payment is OK

4. Click “Success” button to end the process


Use Case Name: Payment Record/Reservation

Brief Description: This use case is let administrator to edit the Service details

Actor: Third Party System Provider, Administrator, Admin (Bus Company)

Main Flow:


1. Click “Success” button to end the process

2. “System is reserving transaction” notification

3. Progress of the process

4. “Progress Completed” confirmation message show.


Thank You!

system design of online ticketing system

Education