UTS Fine Dining Online Reservation System: Business Analysis and Bug Detection

UTS Fine Dining Online Reservation System
Overview
The following report is a business analysis of the new UTS Fine Dining online reservation
system. The aim is to minimise the cost of developing the system by detecting all possible
bugs.
Task plan
The test objective is to find as many bugs as possible in the UTS Fine Dining system. The
test deliverables will be a list of all bugs detailed and ordered by highest risk to lowest risk
level. Severity or risk level will be determined by the degree to which the bugs cause failure
to the system.
Task allocation
Compliance (standards & legal) (high)
Infrastructure (high)
Configuration (medium)
Localization low
Environment low
Power & Heat low
Training low
Networks low
Capacity & Volume low
Stress test (break test) low
The strategy of finding bugs has been to allocate the tasks by assigning each team member a
software testing stage. Each team member then analysed the document focusing on bugs that
related to their assigned stage.
 User acceptance testing
 Implementation testing
Bugs
Index of bugs: The following bugs are listed from highest risk to lowest risk level.
Bug Id Short description
Bug 001 Database
modification(page
4,2.1.1 ii(a) view
database)
The restaurant personnel has to be viewing and updating the
database which we are not shown in the diagram. e.g. The menu has
to be regularly updated by restaurant personnel
Bug 002: User
reservationpage 4,
From the general page the customer can make reservations. A bug
seems to exist since how can a customer make reservation without

login in to the system using password and the user name. Or a user
can make reservation and he will get system prompt to login and
proceed making reservations.
Bug 003 user
requirements (login
patron) page 4 A
patron must log on
to the system before
making a
reservation.
In the explanation regarding the system does not show that the user
has to register to be a user. We are not told from the report that the
fields are mandatory. The system should not proceed with the
registrations unless all the fields are filled.
Bug 004 page 5
Email accounts and
passwords
The bug is that during the registration process, the customer is not
prompt to verify the email address. A good system must verify the
account during the registration by letting the users to confirm the
email account verification
Bug 005 page 6
order cancelation
From the report we are told that the user can cancel the order. In
case the customer has to cancel the order it should prompt the user
if sure to cancel the order by bringing the dialogues box. This will
prevent clients from making simple mistake like accidentally clicking
on the cancel button
Bug 006 page 7
Field validation
and password
validation
Validation is done so that it can prevent users from entering the
wrong format. Despite the fact that the email is validated, password
and phone numbers were not told that it has been validated. This is a
likelihood of bug
Bug008 page 5
customer
registration
It is not clear which format is the customer allowed to login. For
example he or she must fill a form so that he can be successfully
registered. Also the customer has to provide name
Bug 008 page 6 If
the adjustment
fails, the system
must show an error
message to the user
notifying him or her
of the failure
The customer is not prompt what may be missing in case the order
submission fails. The error message should direct the customer to
check what may be missing to allow the customer to start from
where he left the application
Bug 009
page 6
The system must
display the
following
information of the
reservation:
The system must show the customer name and the contacts in the
database so that the restaurant personnel is able to view and update
the customer details in the database
Bug 010 page 7
Once the user
submits the
information, he/she
will be taken a page
that shows the floor
plan of the
restaurant.
Here we are not told that the patron can make more than one
bookings. Maybe mistakenly the patron made a mistake of booking
the order and book twice mistakenly. The system has to understand
any similarity in the booking of the orders.

Appendix 1 –
Defect template
Bug ID B001
Location User reservation(page 4, 2.1.1, i (a) General page)
Priority (1-5) 2
Severity (1-5) 1
Software Testing Stage Implementation and acceptance testing
Test Domain Compliance (standards & legal) (high)
Description: In the explanation regarding the system does not show that the user has to
register to be a user. We are not told from the report that the fields are mandatory. The
system should not proceed with the registrations unless all the fields are filled.
Issue: The report should show that the system must filled all the fields in order for the
customer to be allowed to register as a user of the UTSFD system. In the report we are not
sure if the user has to filled all the fields or leave other fields. The mandatory fields has to
be marked with asterisks
Expected Result: the user should fill all the fields in order to move to the next step for
reservation. So in this case the fields must be validated to enhance system integrity and
confidentiality