Business Requirement Document

Business Requirement Document

Tour Management System

Contents
1. Document Revisions............................................................................................................................4
2. Approvals.............................................................................................................................................4

V1.0 Confidential only for internal purpose Page 1

 Business Requirement Document

3. RACI Chart for This Document.............................................................................................................5

Codes Used in RACI Chart....................................................................................................................5
RACI Chart............................................................................................................................................5
4. Introduction.........................................................................................................................................6
4.1. Business Goals.............................................................................................................................6
4.2. Business Objectives.....................................................................................................................6
4.3. Business Rules..............................................................................................................................6
4.4. Background..................................................................................................................................6
4.5. Project Objective.........................................................................................................................6
4.6. Project Scope...............................................................................................................................6
4.6.1. In Scope Functionality..........................................................................................................6
4.6.2. Out Scope Functionality.......................................................................................................6
5. Assumptions........................................................................................................................................7
6. Constraints..........................................................................................................................................7
7. Risks.....................................................................................................................................................7
Technological Risks..................................................................................................................................7
Skills Risks................................................................................................................................................7
Political Risks...........................................................................................................................................7
Business Risks..........................................................................................................................................7
Requirements Risks.................................................................................................................................7
Other Risks..............................................................................................................................................7
8. Business Process Overview..................................................................................................................8
8.1. Legacy System (AS-IS)..................................................................................................................8
8.2. Proposed Recommendations (TO-BE)..........................................................................................8
9. Business Requirements........................................................................................................................8
10. Appendices......................................................................................................................................8
10.1. List of Acronyms......................................................................................................................8
10.2. Glossary of Terms....................................................................................................................8
10.3. Related Documents..................................................................................................................8

V1.0 Confidential only for internal purpose Page 2

 Business Requirement Document

1. Document Revisions
Version
Date Document Changes
Number
05/02/20xx 0.1 Initial Draft

2. Approvals

Role Name Title Signature Date

Project Sponsor xyz 2/5/2020
Business Owner xyz 2/5/2020
Project Manager xyz 2/5/2020
System Architect xyz 2/5/2020
Development Lead xyz 2/5/2020
User Experience xyz 2/5/2020
Lead
Quality Lead xyz 2/5/2020
Content Lead xyz 2/5/2020

V1.0 Confidential only for internal purpose Page 3

 Business Requirement Document

3. RACI Chart for This Document

RACI Chart
Name Position * R A S C I
xxx Project manager A
xxx BA R
xxx Project sponsor I
xxx Stakeholder C
xxx Sr.BA S I

4. Introduction

4.1. Business Goals

The tour management system provides facilities to the customers such as tour schemes provided by
organization through online. This tour management system provide complete details like
accommodation at the visiting places and information about the destination and its history, and they
can know the total amount of money needed, so that it would be easy for the customers to plan
accordingly. If the customer is satisfied then they can make booking and there are different payment
methods available cash, credit card, debit card or by cheque.

4.2. Business Objectives

To achieve the business goals the proposed IT solution is incorporated with needed functionalities.
These functionalities which are present in software are listed below:

 Customer can check complete tours schemes through online which remove the existing manual
process where customer comes to office enquiry about each scheme.
 If the customer is new then the system asks for registration
 System generates unique username and password which can be used for making reservation
 System allows customer to update personal details, cancel tour reservation.
 System allows customer to pay online or can pay personally
 Customer can make payments using different payment methods like cash, credit card, debit card
or by cheque
 System allows customer to view details of reservation.

V1.0 Confidential only for internal purpose Page 4

 Business Requirement Document

4.3. Business Rules

 System should allow only valid staff to reserve ticket for the customer who choose by personally going to
office to make payment
 Only administrator can add, delete, or modify tour scheme.
 Existing customers can make changes to tour reservation.
 Organization should have permission from state or central tourism ministry.

4.4. Background
People who are interested in visiting places or planning vacation with friends and family has to manually
search for the destination, sometime they might have faced difficulties while planning a perfect trip.
Issues may be regarding selecting destination, accommodation or regarding money because of which
they might have not enjoyed and has a negative impact.

The proposed IT solution will provide multiple tour schemes with each having all the information
regarding tour like information about the destination like culture and history, history and money
packages, where customer can make choice and plan perfect trip. This will remove manual process and
provides different payment methods as well. It provides complete transparency from very start of the
business between organization and customer.

4.5. Project Objective

 The system captures the personal details of the customer and generates unique username and
password.
 It reduces the existing manual process of reservation tour
 Customers can select tour schemes of their choice
 It simplify the payment process
 Customer can update personal details or view reservation details or cancel reservation
 The system allows administrator to add, modify or delete tour scheme.
 Project saves both time and energy for the customer by providing all the tour details like
accommodation, duration and cost.

4.6. Project Scope

4.6.1. In Scope Functionality
 Recording Customer personal details and selected tour schemes.
 Providing ID and password to each new customer at the time of registration.
 Complete transparency regarding tour details like duration, cost , accommodation, knowledge of
visiting place.
 Customer can reserve and pay for tour through online
 Facilitates payment through cash, credit, debit and cheque.
 Allows customer to update their existing personal details in the system.
 Allows customer to cancel reservation for the tour.
 Customer can use system provided ID and password for future transactions also.
 Validates staff and only valid staff can reserve the ticket for tour.
 After reservation customer can view his reservation details.

V1.0 Confidential only for internal purpose Page 5

 Business Requirement Document

 Allows the administrator to add, modify and delete tour schemes provided by business.
 Customer can access the system by using mobile, computer.
 Enables individual customer, an agent behalf of the group of customers to reserve a tour.

4.6.2. Out Scope Functionality

 Generating email or SMS about new tour schemes for existing customers.

5. Assumptions
 Additional security for the application to protect confidential customer data.
 Internet access to the system must be 24/7 or else the application will not work.
 Customer can gain access to the system by using computer or mobile
 Allows multiple numbers of concurrent users to access at a particular time.

6. Constraints
 Data base should store huge volume of customer’s personal details and tour schemes details.

7. Risks
Technological Risks
There are no high end technologies used in this project so there is no technological risk associated with
it.

Skills Risks
There is no skill risks associated with this project because user can access and work on system if they
have working experience on computer.

Political Risks
 Tour management system must renew its permission from state or central tourism ministry.
 Proper Acknowledgment of the changing political conditions in tourist visiting place.

Business Risks
Cancelling the project not only incur loss in terms of cost and time already dedicated towards it up till
cancelation point and cannot improve the quality of service provided to customers.

Requirements Risks
 Providing complete tour package information which allows customer to take wise decision in tour
package selection.
 Providing correct knowledge about visiting place such as historical and cultural significance.
 Creating tour package that fits for wide range of people.

Other Risks
None

V1.0 Confidential only for internal purpose Page 6

 Business Requirement Document

8. Business Process Overview

This process begins when customer access the system through online, system asks for registration if the
customer is new and for registered customer login details If he wants to check the availability of a
desired tour package. To complete the registration customer gives personal details and then system
provides with unique user Id and password to customer. Customer checks the available tour packages
and if satisfied customer confirms the tour package and chooses payment by online or goes personally
to office and pays through staff by cash, credit, debit or cheque and staff reserves the ticket. After
reserving a tour the customer can view his reservation details and can also cancel his reservation.

8.1 Legacy System (AS-IS)

Customer himself chooses visiting place and make reservation for the tour. Customer does not have
detailed information about the destination like cultural and historical details. After visiting place
customer has to manually search for accommodation during the stay which consumes time and include
lot of effort due to which customer might not enjoy the trip to the fullest.

V1.0 Confidential only for internal purpose Page 7

 Business Requirement Document

start

Customer
personally going to
office and enquire
about tour

Administrator
provides tour
scheme

Customer select
tour pacakge

Make payment by
cash to staff

Staff makes
reservation

Manually searches
Customer visit the
for
destination
accommodation

Acquires the
historical and Completes tour
cultural details

End

V1.0 Confidential only for internal purpose Page 8

 Business Requirement Document

8.2 Proposed Recommendations (TO-BE)

In the proposed system manual process is completely removed. The customer access system online and
check availability of the tour package. If the customer is new then he has to complete registration
process. The system generates unique username and password. The existing customer can login and
select tour package and if satisfied make payment by selecting any payment method like cash, credit
card, debit card or cheque, customer can even make payment by going personally to the valid staff.
Existing customer can update his personal details, view reservation details or cancel reservation.
Administrator can add, modify or delete tour scheme.

V1.0 Confidential only for internal purpose Page 9

 Business Requirement Document

validate User

Customer staff

[New User] [Existing User] Admin

Receive payment by cash

Enter Personal Details Accept Login tour scheme

Make ticket reservation

Generate ID

Tour_info
Cust_info

View Package Details

Update personal details
make changes Cancel reservation

[Not Available] Display Availability

view tour details

[If Available]

Accept Booking

Authorize Payment

Credit card Cheque

Make ticket Reservation

V1.0 Confidential only for internal purpose Page 10

 Business Requirement Document

9. Business Requirements
Sr.n Business requirement Functionality Priority
o
1 System home page should display the rules Customer interface High
and regulations issued by tourism ministry
2 System should display complete tour Customer interface High
information such as accommodation, cost,
duration and destination details.
3 System should capture personal details of the Database functionality High
new customer to generate unique username
and password
4 Existing customer should be able to use Customer interface High
username and password for future
transactions
5 Existing customer can update personal details Customer interface High
6 Existing customer can view reservation Customer interface High
details
7 Customer must be able to pay by cash, credit Customer interface High
card, debit card or by cheque
8 Customer should be able to access system System functionality Medium
using computer, mobile, tablet
9 System should check staff validity while System functionality High
making reservation
10 Administrator can add, modify or delete tour Admin functionality High
scheme

10. Appendices

10.1 List of Acronyms

10.2 Glossary of Terms

10.3 Related Documents

V1.0 Confidential only for internal purpose Page 11