USE CASE SPECIFICATION DOCUMENT

<TOUR MANAGEMENT SYSTEM >

COEPD
SR NAGAR
HYDERABAD, TELANGANA, 500038

DATE

1
2
3
CHECK FOR THE AVAILABILITY OF SCHEME

Name of Use Case: Check for the availability of tour scheme

Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: This use case describes the functionality of how the customer searches for
the tour scheme and how he checks for the availability of tour.
Actors: Customer
Preconditions: 1. Customer must have valid login credentials in tour management system.
2. Active network connection.

Postconditions: Successful post condition

1.search for tour package successfully performed, Available tours are
displayed.

Failure Post Condition

1.unable to perform search.

4
 Flow: Search for the availability of tour.
1.This use case begins when customer signals the system that he/she
wants to search for the availability of tour.
2.The system displays search form.
3.system prompts the customer to enter his desired location.
5.customer enters the desired location.
6.system prompts the customer to submit the search form.
7.upon submission system displays the available tour packages.
Use case ends.

Alternative Flows: In step 7 of the normal flow, if the tour packages are not available as per
the customer preferences.

1. System should display a message “sorry no tour packages available

at this time as per your preferences”.
2. System should prompt the customer to reenter his modified
preferences.

Exceptions: 1. NA

Special Requirements: 1. The system must support simultaneous customers.

5
RESERVE TOUR USE CASE

Name of Use Case: Reserve Tour Use Case

Created By: Coepd Last Updated By: Raghavendra Kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: This use case describes the functionality of how the staff reserve tickets
online tour management system.
Actors: Staff
Preconditions: 3. Active network connection.
4. Search for availability of package use case has to be performed.
5. Make payment has to be performed.

Postconditions: Successful post condition

1.Staff reserved tour package successfully.

Failure Post Condition

1.Staff couldn’t reserve tour package successfully.

6
 Flow: Book tickets.
1. The use case begins when the staff signals the system that he/she wants
to reserve tickets.
2. System displays reserve tour screen.
3. System prompts the staff reserve tour.
4. staff enters required information and reserves tour.

use case ends.

Alternative Flows: In step 4 of the normal flow, if the staff enters irrelevant details or submits
in complete form

3. System should display a message “Please provide all valid details”.

4. Use case ends.

Exceptions: 2. NA

Special Requirements: 2. The system must support simultaneous staff.

7
MAKE PAYMENT USE CASE

Name of Use Case: Make payment

Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: This use case describes the functionality of how the customer makes
payment after booking tickets in the tour management system.
Actors: Customer
Preconditions: 1.Customer has valid login credentials.
2.Active network connection.

Postconditions: Successful post condition

1.Payment successful.

Failure Post Condition

2.Payment failed.

8
 Flow: 1. The use case begins when the customer signals the system that he/she
wants to make payment to desired tour package.
2. System displays may payment screen.
3. System prompts the customer to enter the payment information,
account details.
4. customer submits the account details.
5. System validates the payment.
6. System records the payment information in the database.
Use case ends.

Alternative Flows: In step 5 of the normal flow, if the customer enters the invalid details.

1.The system should send an error message “please enter the valid details”.

Exceptions: 3. NA

Special Requirements: 5. The system must support simultaneous users(admin).

9
VIEW RESERVED TOUR DETAILS

Name of Use Case: VIEW RESERVED TOUR DETAILS

Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: The use case describes the functionality of how the customer views his
details.
Actors: customer
Preconditions: 1.customer has valid login in credentials.
2.Active network connection.

Postconditions: Successful post condition

1.able to view his reserved tour details
Failure Post Condition
1.unable to view his reserved tour details.

10
 Flow: View tour
1.The use case begins when the customer signals the system that he/she
wants to view his reserved tour.
2.customer will select view reservation option.
3.System will display the reserved tour package details
4.Use case ends.

Alternative Flows:
Use case ends.

Exceptions: 4. NA

Special Requirements: 6. The system must support simultaneous users.

11
LOGIN USE CASE

Name of Use Case: Login Use case

Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: This use case describes the functionality of how the user login to the
system.
Actors: customer
Preconditions: 1.Active network connection.
2.customer should be a registered user.

12
 Postconditions: Successful post condition.
1.customer logged in successfully.
Failure Post Condition.
1.customer unable to login.

Flow: 1.The use case begins when the customer wants to login to the tour
management system.
2.system prompts the customer to enter his/her registered id/password.
3.customer enters his details.
4.systems displays home page on successful login.

Use case ends.

Alternative Flows: In step 3 of the normal flow
1.if customer enters invalid details.
2.system should send a message “please enter valid credentials”

Use case ends

Exceptions: NA.

Special Requirements: System should support simultaneous users.

13
14
15
16