i.

Functional requirement
This project will analyze functional requirements and for different stakeholders: clients
(see in Table 2.1), dealer (see in Table 2.2) and supervisor/owner (see in Table 2.3); each
requirement is labelled clearly with name and definition. Priority for each functional
requirement will also be discussed.
1. Clients
ID Name Definition
Non-registered and registered users could browse the list of
FR-1 Browsing available tours. Users could sort the available tour list based
on tour ratings and prices.
Non-registered user needs to register an account to enjoy
TourPlus mobile app’s complete services. Non-registered
user could use their mobile phone numbers or e-mail to
register and need to write down the user’s basic information
FR-2 Registration
such as name, address, age. Then set up a password.
System will send confirmation message to their mobile phone
or e-mail. Click the link in the confirmation message to confirm
user’s identity and the registration will be successful.
User could fill in the valid account ID (phone number/e-mail)
FR-3
and correct password to log in successfully.
If user forget their password. User could choose ’forgetting
password’, entering the valid account ID (phone number/e-
Log in
mail). System will send changing password message to
FR-4
phone/e-mail. Click the link in the message to set up new
password. After setting up new password, user could log in by
using account ID and new password.
Users select the tour they want to choose. If the tour is not
full, user choose the type of payment to pay. Once the
FR-5
payment is finished, it means that the tour booking is
successful.
Booking Users select the tour they want to choose. If the tour is full,
user will be added into the waiting list. The system will notify
FR-6 the users in the waiting list when the situation of someone
cancels the tour occurs, the first user finishing payment will
be added to the tour.
View and Users could browse their personal information include their
FR-7
manage name, telephone, address, e-mail and bank card they bind.
personal Users could modify their personal information include their
FR-8 information name, telephone, address, e-mail and bank card they bind.
Users could browse the information of past tours and booked
FR-9
tours, which include time, location, person, content .
Users could rate and evaluate the past tours. Users could
FR-10
View and browse the other users’ evaluation of tours.
manage Users could cancel booked tour. If user cancel the booked
booked tour tour more than one day before the tour starts, there will be no
FR-11 extra fee. If user cancel the booked tour less than one day
before the tour starts, an additional 20% handling fee will be
charged.
Table 2.1 functional requirement 1(users)

2. Merchant
ID Name definition
Apply to Registered user could apply to system to become merchant.
FR-12 become Applicant needs to submit their services, qualification.
merchant
 Applicant needs to wait for review by the system
administrator. After passing the review, applicant can become
a merchant.
Merchants can browse their own products that have been put
Browse
FR-13 on the shelves, including product information, sales volume,
available
products
and customer reviews.
FR-14 Merchants can reply to users’ comments on products
view and Merchants could browse and modify their own information,
manage including merchant name, merchant address, contact
FR-15
personal information, e-mail, products name.
information
If merchant want to launch new product or modify existing
product, they need to apply to the system. Merchant needs to
manage (add, submit new product information or modified information for
FR-16
modify or existing product to the system. After review and approval by
remove) the system administrator, new or modified products will be put
products on the shelves.
Merchants can remove products from the shelves. The
FR-17
premise is that no customer currently reserves this product.
Browse the Merchant could browse the basic information of those
FR-18 information of customers who booked its products, including service
customers information, customer’s name, contact information.
View Merchant could browse the information of completed orders,
FR-19 completed including product content, time, customer basic information,
orders price, customer’s comment.
After customer finished tour. The income from this tour will be
Cost
FR-20
settlement
automatically remitted to the bank account designated by
merchant.
Table 2.2 functional requirement 2(merchants)

3. Supervisor
ID Name Definition
System administrator could receive the application of
becoming merchant. The system administrator then submits
Review the the applicant's operating qualification to the qualification
application of
FR-21
becoming
certification system and waits for feedback from the
merchant certification system. Based on the feedback from the
certification system, system administrator decides whether
to approve the application.
System administrator could receive the application of
modifying/adding product. The system administrator then
Review the submits the applicant's new product information/changed
application of product information submitted by the applicant to the
FR-22
modifying/adding marketing department of TourPlus and waits for feedback
product from the marketing system. Based on the feedback from the
marketing system, system administrator decides whether to
approve the application.
View and System administrator could browse whole information
manage (add, (including basic and detailed, simple users do not have
FR-23 modify or delete) permission to access detailed information) of merchant.
the list of System administrator could also add/modify/delete the
merchants merchant/merchant information.
View and System administrator could browse the information of
FR-24 manage the list available tours. System administrator could also
of available tours add/modify/delete tour.
 View and System administrator could browse and modify whole
FR-25 manage the list information (not contain sensitive information) of users.
of users