Requirement & Design Specification

Barber Shop
Version: 1.0

SWP391_SU24_G1

Group 2
Members
3

GAMS-SRS_v1.0 Page 1 / 20
 Nguyễn Văn An
Supervisor

– Hanoi, August 2022 –

Record of Changes
Version Date A* In charge Change Description
M,
D
V1.0 29/5 A LINHNTHE170290 Add 1.1, 1.2b
V1.0 29/5 A LINHNTHE170290 Add 2.2(1,2,5,6,8), 2.3
V1.0 29/5 A LINHNTHE170290 Add 3.1
V1.0 29/5 A LINHNTHE170290 Add II-2.1, 2.3, 2.4
V1.0 29/5 A LINHNTHE170290 Afdd II-3.5, 3.6
29/5/2024 A thienpdhe171979 Draw diagram use case Cashier
29/5/2024 A thienpdhe171979 Draw diagram use case Barber
29/5/2024 A thienpdhe171979 Add Screen description screen view list staff, add
staff, delete staff
29/5/2024 A thienpdhe171979 Add Requirement Specification View list staff, add
staff, delete staff

GAMS-SRS_v1.0 Page 2 / 20
 29/5/2024 A thienpdhe171979 Add Non-UI Functions
29/5/2024 A quypdhe173508 Add 2.2 Forgot PassWord
01/06/202 A quypdhe173508 Add 2.5 Change password
4
02/06/202 A quypdhe173508 Add III 1.2 d,e
4
29/05/202 A anhpqdhe172622 add I - 3.2 code packages
4
29/05/202 A anhpqdhe172622 add I - 1.2 draw use case admin
4
29/05/202 A anhpqdhe172622 add II - 3.1,4.1
4
29/05/202 A anhpqdhe172622 add III - 3.3,4.1
4
29/05/202 A trungpqhe173313 add II -3.3.2,3.3,3.4
4
29/05/202 A trungpqhe173313 add I - 1
4
29/05/202 A trungpqhe173313 add I - 2
4
*A - Added M - Modified D - Deleted

GAMS-SRS_v1.0 Page 3 / 20
Contents
Record of Changes.........................................................................................................................................2
I. Overview....................................................................................................................................................5
1. User Requirements.................................................................................................................................5
1.1 Actors...............................................................................................................................................5
1.2 Use Cases.........................................................................................................................................5
2. Overall Functionalities...........................................................................................................................6
2.1 Screens Flow....................................................................................................................................6
2.2 Screen Descriptions.........................................................................................................................6
2.3 Screen Authorization.......................................................................................................................6
2.4 Non-UI Functions............................................................................................................................7
3. System High Level Design....................................................................................................................7
3.1 Database Design...............................................................................................................................7
3.2 Code Packages.................................................................................................................................7
II. Requirement Specifications.......................................................................................................................9
1. <<Feature Name>>................................................................................................................................9
1.1 << UC Name>>...............................................................................................................................9
2. Common Functions..............................................................................................................................11
2.1 Login System.................................................................................................................................11
3. Patron Feature......................................................................................................................................12
3.1 Order a Meal..................................................................................................................................12
3.2 Register for Payroll Deduction......................................................................................................13
III. Screen Designs.......................................................................................................................................14
1. <<Feature Name>>..............................................................................................................................14
1.1 <<SubFeature Name>>..................................................................................................................14
1.2 System Access...............................................................................................................................14
IV. Code Designs.........................................................................................................................................17
1. <Feature/Function Name1>.................................................................................................................17
1.1 Class Diagram................................................................................................................................17
1.2 Sequence Diagram(s).....................................................................................................................17
1.3 Database Queries...........................................................................................................................18
2. <Feature/Function Name2>.................................................................................................................18
V. Appendix.................................................................................................................................................18
1. Assumptions & Dependencies.............................................................................................................18
2. Limitations & Exclusions....................................................................................................................18
3. Business Rules.....................................................................................................................................18

GAMS-SRS_v1.0 Page 4 / 20
 4. ..............................................................................................................................................................19

GAMS-SRS_v1.0 Page 5 / 20
I. Overview

1. User Requirements
1.1 Actors
[An actor is a person (or sometimes another software system or a hardware device) that interacts with
the system to perform a use case. Following are some questions you might ask to help user
representatives identify actors
● Who (or what) is notified when something occurs within the system?
● Who (or what) provides information or services to the system?
● Who (or what) helps the system respond to and complete a task?

This part gives the description of system actors, you can follow the table form as below]
# Actor Description
Booking a haircut via phone number, choosing a technician, and a haircut
time frame. Customers can register for a VIP account to receive special
1 Customer discount codes, accumulate points, see the machines that have cut their
hair, and see the hairstyles they have cut. Reschedule when busy. View and
edit personal information.
Log in to the system, view the appointment booking. Confirm order after
cutting is completed. See the number of customers in 1 month. View and
2 Barber
edit personal information, confirm payment invoice, Confirm payment
method

GAMS-SRS_v1.0 Page 6 / 20
 Staff manager. Manage monthly revenue, manage employee monthly
3 Admin salaries (based on customers). Manage the barber's work schedule during
the day. Create discount codes on special days.

1.2 Use Cases

[A use case (UC) describes a sequence of interactions between a system and an external actor that
results in the actor being able to achieve some outcome of value. The names of use cases are always
written in the form of a verb followed by an object. Select strong, descriptive names to make it evident
from the name that the use case will deliver something valuable for some user]
a. Diagram(s)
[Provide the UC diagram(s) to show the actor-UCs and UC-UC relationships like the sample below. You
can have multiple UC diagrams for the system]

Customer

GAMS-SRS_v1.0 Page 7 / 20
Cashier

GAMS-SRS_v1.0 Page 8 / 20
Barber

GAMS-SRS_v1.0 Page 9 / 20
GAMS-SRS_v1.0 Page 10 / 20
b. Descriptions
This part describes the use cases, you can follow the table form as below]
ID Feature Use Case Use Case Description
01 Common Sign up allows customers to create new accounts.
02 Login allows users to access the system using a
phone and password.
03 Change allows users to update their current password to
password a new one.
04 Reset allows users to regain access to their account if
password they have forgotten their password or if their
account's security has been compromised.
05 Logout ends a user’s current session, ensuring that no
one else can access their account on the same
device.
06 Customer View profile involves accessing detailed information about
customer the customer within a system
Management
07 View history allows customers’ to access information about

GAMS-SRS_v1.0 Page 11 / 20
 booking of their past bookings, reservations, or
customer appointments within a system.
08 Update allows authorized customers to modify and
profile update the information stored in a customer's
customer profile.
09 Booking Create enables customers to access information about
Booking bookings made by customers.
Management
10 View booking allows users to view their existing bookings.

11 Update allows customers to make changes or updates

Booking to existing bookings.
12 Create enables customers to access information about
Booking bookings made by customers again.
again
13 Cancel enables customers to cancel existing bookings.
booking
14 Staff View list staff provides the admin with a list of staff members
associated with the system or platform.
15 Management allows admin to add new staff members to the
Add staff system or platform.
16 allows admin to hide staff members that quit
Delete staff one's job from the system or platform.
17 View profile enables employees to access detailed profiles
staff of staff members.
18 Update allows employees to modify and update the
profile staff information stored in a profile.
19 Change
Password
Employees
Account
20 Employees
Resign
21 Recovery
Employees
Resign
22 View list provides barbers with access to the work
work schedules of staff members.
schedule
23 Request
leave
24 Confirm leave
request
25 Service View list provides users with a list of services offered by
service the system or platform.
management
26 View list allows users to view detailed information about
service detail each service offered.

GAMS-SRS_v1.0 Page 12 / 20
 27 Update enables admin to make changes or updates to
service existing services offered by the system or
platform.
28 Add service allows admin to add new services to the system
or platform.

29 View top provides users with information about the top-

service performing services based on criteria such as
popularity, revenue generated, or customer
ratings.
30 Delete
Service
31 Search
Service
Detail
32 Feedback FeedBack allows customers to provide feedback or
service reviews about the services they have
Management experienced.
33 View enables users to view and analyze feedback
feedback provided by customers about the services
offered.
34 Shop View provides the admin with information about the
revenue revenue generated by the system or platform.
Management
35 Export
monthly
revenue to
excel file
36 View Order
Detail
37 allows admin to view sales data and statistics
View sales related to products or services offered by the
system or platform.
38 provides admin with information about the
Store status status of the store or business operations.
39 Booking
chose barber
40 Chat
41 Homepage
42 Bill enables barber to create bills or invoices for
Create bill products or services purchased by customers. It
Management involves generating itemized bills that detail the
products or services provided, quantities,
prices, and total amounts due.
43 Update bill allows barber to make changes or updates to
existing bills or invoices by user requirement.
44 Check in enables barber to confirm and finalize customer
orders for products or services.

GAMS-SRS_v1.0 Page 13 / 20
 45
View detail
bill
46 allows users to view and access bills or invoices
View the bill generated for customer purchases.
47 Voucher
48 Create
voucher
49 Update
voucher
50 Update point
51 Accumulate
points
52 Time remind
53 Payment provides customers with options for selecting
method and managing payment methods for
transactions.
54 enables customers to complete their purchase
Check out transactions and proceed to checkout.

2. Overall Functionalities
2.1 Screens Flow
[This part shows the system screens and the relationship among screens. You can draw the Screens Flow
for the system in the form of diagram as below. Please note that beside the normal flat screen, we might
have the oval notation for pop-up screen (Orders Import) or a screen with multiple information tab
(Order Update), etc. You may also use text or background format for different visuality purpose]

2.2 Screen Descriptions

# Feature Screen Description
1 Common Sign up Enter phone
Enter and confirm password

GAMS-SRS_v1.0 Page 14 / 20
 Enter full name, email and choose
gender
Click create new account button to
summit
2 Login Enter phone
Enter password
Click login button
3 Change password -Enter email
-Click to send mail
4 Reset password - Enter old password
-Enter Password
-Enter confirm password
-Click to change password
5 Logout -Logout link

6 Customer View profile customer - Customer Profile link

- View Customer Profile
Management - Update button
7 View history booking of login
customer click view history booking
8 Update profile customer - Edit information of customer
profile
- Save update
9 Booking Login account
Booking Make an appointment
Management select time, barber and services
10 View booking Customs login account
Click Appointment Schedule
11 Update Booking Customs login account
Click Appointment Schedule
Edit information
Click Update
12 Create Booking again
13 Cancel booking Customs login account
Click Appointment Schedule
Click cancel
14 Booking choose barber
15 Staff View list staff
Management
Admin login account
View information of all staff in
system
16 Admin login account
Add staff Go to the view list staff
Click button add staff and fill
information
submit and a staff will be
created
17 Delete staff Admin login account
Go to the view list staff

GAMS-SRS_v1.0 Page 15 / 20
 Find staff want to delete from
system
Click delete and a staff will no
longer appear in the list

18 View profile staff

19 Change Password Employees

Account

20 Employees Resign

21 Recovery
Employees Resign

22 View list work schedule

23 Request leave

24 Confirm leave request

25 Service View list service

management

GAMS-SRS_v1.0 Page 16 / 20
266 View list service detail

27 Update service

28 Add service

29 View top service

30 Delete Service

31 Search Service Detail

32 Feedback Feedback service

Management

33 View feedback

34 Shop View revenue

Management

35 Export monthly revenue to

excel file

GAMS-SRS_v1.0 Page 17 / 20
36 View Order Detail

View sales

37

38
Store status

39 Booking chose barber

40 Chat

41 Homepage

42 Time reminder

43 Voucher

44 Create voucher

GAMS-SRS_v1.0 Page 18 / 20
45 Update voucher

46 Update point

47 Accumulate points

48 Bill
Create bill
Management

49 Update bill

50 Check in

51
View detail bill

52
View the bill

53 Payment method

54
Check out

GAMS-SRS_v1.0 Page 19 / 20
2.3 Screen Authorization
Screen Admin Customer Barber
Sign up X
Login X X X
Change password X X X
Reset password X X X
Logout X X X
View profile customer X
View history booking of X
customer
Update profile customer X
Booking X
View booking X X X
Update Booking

Cancel booking X
View list staff X

Add staff X

Delete staff X
View profile staff X
Update profile staff X
Change Password X
Employees Account
Employees Resign X
Recovery
Employees Resign X
View list work schedule X X
Request leave X
Confirm leave request X
View list service X X
X
View list service detail X X
X
Update service X
Add service X
View top service X X X
Delete Service X
Search Service Detail X X X
Feedback service X
View feedback X X X
View revenue X
Export monthly revenue to X

GAMS-SRS_v1.0 Page 20 / 20
 excel file
View Order Detail X

View sales X

Store status X
Booking chose barber X
Chat X X
Homepage X X X

Create bill X
Update bill X
Check in X
X
View detail bill X
X
View the bill X
Voucher X
Create voucher X
Update voucher X
Update point X
Accumulate points X
Time remind X
Payment method X
X
Check out

2.4 Non-UI Functions

[Provide the descriptions for the functions which have no UI (or not screens), i.e batch/cron job, service,
API, etc.]
# Feature System Function Description
Employee This function calculates salaries for employees based
Calculate
manager on the amount of work done by the barber or the
1 salaries for
preset salary of the cashier. Salary information will be
employees
compiled and updated in the system.
This function records the number and working hours of
Timekeeping employees, including the number of services that
2
management employees have performed. This information is used
to calculate salaries and track employee performance.
This function allows a new employee to be added in
Add employees
3 the store's employee list after the admin fills in all valid
to the list
information for a new employee.
This function allows an employee to be deleted from
Delete
the store's employee list after the admin selects that
4 employees to
employee in the list and the system will delete that
the list
employee based on that employee's account code.
5 Order Create invoices This function allows creating invoices for confirmed or

GAMS-SRS_v1.0 Page 21 / 20
 management completed orders, including information such as
for orders service details, total price, customer information and
service staff.
This function calculates and displays the barber shop's
Calculate revenue for specific periods of time such as daily,
6
revenue weekly or monthly, based on invoices created and paid
from customers.
This function will help if an employee is off work for a
Set up service day, the system will no longer appear that employee in
7
staff the booking site, helping customers choose employees
who are not served.
Service This function allows a new service to be added in the
Add employees
8 management store's service list after the admin fills in all valid
to the list
information for a new service.
Bill Charge
This function will automatically calculate the amount
management according to
9 the customer must pay based on the listed service
selected
price
service
This function will automatically reduce the price on the
10 extra discount customer's bill if the store has a discount program
added by the admin that day.

3. System High Level Design

3.1 Database Design
[Provide the tables relationship like example below]
a. Database Schema

GAMS-SRS_v1.0 Page 22 / 20
b. Table Descriptions
No Table Description
01 account - Primary keys: phone
- Foreign keys: roleId (references the table role(id))
02 role - Primary keys: id
- Foreign keys: none
03 employee - Primary keys: employeeId
- Foreign keys: phone (references the table account(phone)),
statusEmployee (references the table statusEmployee(id))
04 admin - Primary keys: adminId
- Foreign keys: phone (references the table account(phone))
05 customer - Primary keys: customerId
- Foreign keys: phone (references the table account(phone))
06 feedback - Primary keys: id
- Foreign keys: customerId (references the table customer
(customerId))
07 Chat - Primary keys: id
- Foreign keys: SenderID (references the table customer
(customerId)), adminId(references the table admin(adminId))
08 statusEmploy - Primary keys: id
ee - Foreign keys:none
09 shift - Primary keys: id
- Foreign keys: none
10 status - Primary keys: id
- Foreign keys: none
11 Orders - Primary keys: orderId
- Foreign keys: customerId(references the table
customer(customerId)), statusID(references the table status(id)),
employeeId (references the table employee(employeeId))
12 Services - Primary keys: servicesId
- Foreign keys: none
13 Order_services - Primary keys: servicesId, orderId
- Foreign keys: servicesId (references the table
Services(servicesId)), orderId (references the table
Orders(orderId))
14 Order_shift - Primary keys: ShiftID, OrderID
- Foreign keys: ShiftID(references the table shift(id)),
OrderID(references the table Orders(orderId))
15 - Primary keys: id
discount
- Foreign keys: none
16 store - Primary keys: id
- Foreign keys: none
17 Voucher - Primary keys: id
- Foreign keys: none
18 LoyaltyPolicies - Primary keys: PolicyID
- Foreign keys: none

GAMS-SRS_v1.0 Page 23 / 20
3.2 Code Packages
[Provide the package diagram for each sub-system. The content of this section including the overall
package diagram, the explanation, package and class naming conventions in each package. Please see
the sample & description table format below]

Package descriptions
No Package Description
01 Views This package contains classes related to the user
interface, displaying information to the user, and
receiving input from the user.
02 Controller This package contains control classes, handles requests
from users, and interacts with Model and View.
03 Model This package contains object classes that represent the
system's data and business logic.
04 Dal This package contains classes and methods for
connecting and manipulating the database.

GAMS-SRS_v1.0 Page 24 / 20
II. Requirement Specifications

1. Common Functions
1.1 Login
a. UC Specification
UC Name: Login
Author Nguyễn Thùy Linh - HE170290
Primary Actor: Customer, Barber, Admin Secondary None
Actors:
Trigger: User clicks Login button from the page header, or
User accesses an authenticated feature (from a link or type the page URL directly
into the address bar)
Description: As a user, I want to be able to log into the system so that I can use the system’s
authenticated features and access my personalized account.
Preconditions: - The system has been deployed and operates normally.
- The user already has a login account.

Postconditions: - If the login information is valid, the user will be included in the system.
- If the login information is invalid, the system will notify you of an error
and will not allow access.
Normal Flow Login
1. Users go to the website home page and click on Login.
2. User enters username and password.
3. The user clicks the login button.
4. The system verifies login information successfully.
5. The system redirects users to the website's homepage.

Alternative Flows: AF3.1. Username or Password Incorrect

[Link] system displays an error message indicating that the username or
password is incorrect.
2. The user can choose to re-enter their credentials or click on the "Forgot
Password" link.
3. If the user re-enters credentials, they return to step 2.
4. If the user clicks "Forgot Password," they are redirected to the password
recovery page.

Exceptions: E4.1. System can’t authenticate the user

1. The Error Message screen is shown to the user
2. User cancels the logging in => UC stops, change to other UC-Home Page
3. User clicks “Forgot Password?” link => change to the other UC-Reset Password
Business Rules: FR1, FR2

b. Business Rules
ID Business Rule Business Rule Description

GAMS-SRS_v1.0 Page 25 / 20
 FR1 Invalid Logging In User can’t be authenticated to login the system if below cases
● His/her logging-in details are incorrect
● His/her account has not been verified
● His/her account has been locked or blocked
FR2 Account Locking If user inputs wrong logging-in details 5 times continuously,
his/her account would be locked in 30 minutes

1.2 Forgot PassWord

a. UC Specification

UC Name: Forgot Password

Author Phạm Đạt Quý
Primary Actor: User Secondary Actors: None
Trigger: User clicks Forgot password link from the login page, or
User accesses an authenticated feature (from a link or type the page URL directly
into the address bar)
Description: Allows users to access the system by authenticating their identity through
information such as phone numbers and passwords.
Preconditions: User account has been created & authorized
Postconditions: ● Password update successfully
● The system move in login page
● Showing signs of success
Normal Flow Forgot Password
1. User click forgot password link in login page
2. System move in send link page
3. User enter email
4. System validates the email
5. System send the link in your mail
6. User click to the link in mail
7. System send redirect to the change password page
8. User enter new password and confirm password
9, System send redirect login page
Alternative Flows: 3.1. User enter a non exists email
1. User click to send button while email does not exist on the system
2. System show message You have not registered for this email!!
3. Return to step 3 of normal flow

8.1. New password and confirm password not match

1. System show message not match
2. Return to step 8 of normal flow.

Exceptions: None
Business Rules: BR4,BR5

b. Business Rules

GAMS-SRS_v1.0 Page 26 / 20
 ID Business Rule Business Rule Description
BREmail authentication When a user clicks the "Forgot Password" link on the login
4 page, the system should move to the "Send Link" page, where
the user will be prompted to enter their email address. Upon
entering the email, the system should validate the email. If the
email exists in the system, the system should send a password
reset link to the user's email. The user then clicks on the link in
the email, which redirects them to the "Change Password"
page. Here, the user can enter a new password and confirm it.
Upon successful password change, the system should redirect
the user to the login page, showing signs of success.
BRNon exits email In the alternative flow, if the user enters a non-existent email,
5 the system should display a message stating "You have not
registered for this email!!" and return the user to the step of
entering the email in the normal flow.

1.3 Logout
a. UC Specification

UC Name: Logout
Author Nguyễn Thùy Linh - HE170290
Primary Actor: Customer, Barber, Admin Secondary None
Actors:
Trigger: The user wants to end the session and exit the system
Description: Allows users to log in from their accounts.
Preconditions: The user is logged in to the system and is in a session.

Postconditions: - The user's session ends.

- All session information and user data has been deleted from the system
and browser.
Normal Flow Logout
[Link] user selects the logout option from the system interface.
[Link] system confirms the logout request.
[Link] system ends the user's session.
[Link] system deletes all session information and user data from the browser.
[Link] are redirected to the public home page.
Alternative Flows: AF3.1. The user closes the browser without selecting the sign out option:

When the user reopens the browser and accesses the system, if the previous
session has expired, the system will ask the user to log in again.

GAMS-SRS_v1.0 Page 27 / 20
 UC Name: Logout
Author Nguyễn Thùy Linh - HE170290
Exceptions: E2.1. Session Already Expired
The user selects the logout option from the system interface.
The system attempts to confirm the logout request but finds that the user's
session has already expired.
1. The system redirects the user to the login page.
2. The user can log in again if needed.

If the system encounters a technical or unknown error, the user will receive an
error message and may need to try logging out again or contact technical
support.
Business Rules: FR3, FR4, FR5

b. Business Rules
ID Business Rule Business Rule Description
FR3 Version management Each session is tracked and ends when the user logs in or when
the instance expires.
FR4 Information security After the user logs in, all working information and user data
must be deleted from the browser and system to ensure safety.
FR5 Automatically logout If the user is inactive for a certain period of time, the system
will automatically log the user in to ensure safety.

1.4 Signup
a. UC Specification
UC Name: Signup
Author Nguyễn Thùy Linh - HE170290
Primary Actor: Customer Secondary None
Actors:
Trigger: The user wants to create a new account to access the system
Description: Allows users to create a new account on the system, providing personal
information necessary to access and use the services of the application or
website.
Preconditions: - The system is operating normally.
- User does not have a previous account.

Postconditions: - A new account is created and stored in the system.

- Users can log in to the system using the newly created account.
Normal Flow Signup
1. Users access the registration page via the "Create new account" link on the
login page.
[Link] enters necessary information.
[Link] user presses the Create new account button
[Link] system checks the validity of entered information.
The system checks whether the phone number has been previously registered or
not.

GAMS-SRS_v1.0 Page 28 / 20
 UC Name: Signup
Author Nguyễn Thùy Linh - HE170290
[Link] the information is valid and not duplicated, the system saves the new
account information.
[Link] system activates the user's new account.
[Link] system returns to the login page.
[Link] can log in to the system using the newly created account.
Alternative Flows: AF4.1. Invalid Information:
If the information entered is invalid, the system will display an error message
and ask the user to re-enter the correct information.

AF4.2. Duplicate Information:

If the information entered is already used for another account (for example, a
previously registered phone address), the system will display an error message
asking the user to use unique information and not duplicated.

Exceptions: E1. System malfunction

If the system encounters a technical or unknown error, an error message will be
displayed to the user and they will be asked to try again later.
Business Rules: FR6, FR7, FR8

b. Business Rules
ID Business Rule Business Rule Description
FR6 Password The password must meet the requirements to be the same as
the re-pass.
FR7 Unique information Each phone number can only be registered once.
FR8 Privacy policy All personal information must be stored and handled according
to the system's security policy.

1.5 Change Password

a. UC Specification
UC Name: Change Password
Author Phạm Đạt Quý
Primary Actor: User Secondary None
Actors:
Trigger: The user click change pass in a profile page
Description: As a new user, I want to be able to change password so that I can create new
password
Preconditions: - The User login in page

Postconditions: - Change password successfully

Normal Flow Change Password

1. User click change pass on profile page
2. System move in change pass page

GAMS-SRS_v1.0 Page 29 / 20
 UC Name: Change Password
Author Phạm Đạt Quý
3. User enter old pass, new pass and confirm pass
4. System send message “Đặt lại mật khẩu thành công ”

Alternative Flows: 4.1. Users enter wrong old password

1. System send message “Sai mật khẩu cũ ”
2. Return to step 3 of normal flow

Exceptions: None
Business Rules: BR6,BR7

b. Business Rules

ID Business Rule Business Rule Description

BRValidate changes When the user clicks "Change password" on the "Profile" page,
6 the system will go to the "Change password" page, where the
user needs to enter the old password, new password and
confirm the password. Then, the system will send the message
"Reset password successful" when the password change is
successful.
BRWrong old password If the user enters the old password incorrectly, the system will
7 send the message "Incorrect old password" and return to step
3 in the normal flow.

2. Customer Management
2.1 View history booking of customer

a. UC Specification
UC Name: View history booking of customer
UC Name: View history booking of Author: Đức Anh- 29/05/2024
customer HE172622
Primary Actor: Customer Secondary Actors: none

Description: This use case describes how a customer views their past bookings through the
online system. The customer navigates to the booking history section of their
account, where they can see details of previous bookings, including orderId,name,
services,time, barber, customer contact, total amount, status .
Trigger: The customer initiates a request to view their booking history from their account
dashboard.

GAMS-SRS_v1.0 Page 30 / 20
 Preconditions: 1. The customer must be logged into their account.
[Link] customer must have previous bookings recorded in the system.

Postconditions: 1. The system displays the customer's booking history.

2. The customer can view details of each booking.
Normal Flow: View history booking of customer
1. The customer logs into their account.
2. The customer points to the account section on the navbar to display a
dropdown including personal information and booking schedule.
3. The customer clicks on the "booking schedule" link.
4. The system retrieves the customer's past bookings from the Booking System.
5. The system displays a list of past bookings, including orderId,name,
services,time, barber, customer contact, total amount, status .
Alternative Flows: AF1. No Previous Bookings:
1. If the customer has no previous bookings, the system displays a message
indicating no booking history is available.
Exceptions: E1. System Error:
1. The customer is advised to try again later or contact customer support.
Business Rules: BR3

b. Business Rules

ID Business Rule Business Rule Description

BRBooking Data Retrieval The system must accurately retrieve and display booking data
3 from the Booking System.

2.2 View Booking

a. UC Specification
UC Name: View Booking Author: Trung Date: 24/05/2024
Primary Actor: Customer Secondary Actors: none
Description: This use case describes how a customer views the details of an booking through
the online system. The customer navigates to the current bookings section of their
account to see the details of their upcoming appointment, including name, services,
time, barber, customer contact, total amount, and status.
Trigger: Point to the account and select Appointment Schedule
Preconditions: 1. The customer must be logged into their account.
[Link] must have their booking schedule recorded in the system.

Postconditions: 1. The system displays the customer's upcoming booking details.

2. The customer can view details of their booking.
Normal Flow: View booking
6. The customer logs into their account.

GAMS-SRS_v1.0 Page 31 / 20
 7. The customer navigates to the account section on the navbar to display a
dropdown including personal information and current bookings.
8. The customer clicks on the "Appointment Schedule".
9. The system retrieves the customer's upcoming bookings from the Booking
System.
10. The system displays the details of the upcoming booking, including orderId,
name, services, time, barber, customer contact, total amount, and status.
Alternative Flows: AF1. No Upcoming Bookings:
9.1 If the customer has no upcoming bookings, the system displays a message
indicating no current bookings are available.
Exceptions: E1. System Error:
The system encounters an error while retrieving booking data. The customer is
advised to try again later
Business Rules: BR3

b. Business Rules

ID Business Rule Business Rule Description

BRBooking Data Retrieval The system must accurately retrieve and display booking data
3 from the Booking System.

2.3 Update Booking

a. UC Specification
UC Name: Update booking Author: Trung Date: 25/05/2024
Primary Actor: Customer Secondary Actors: none
Description: This use case describes how a customer can update the details of an upcoming
booking through an online system. Customers navigate to an existing booking in
their account, select a booking to update, modify the booking details and confirm
the changes.
Trigger: Point to the account and select Appointment Schedule and change information and
click update
Preconditions: 1. The customer must be logged into their account.
[Link] must have their booking schedule recorded in the system.

Postconditions: 3. The system updates the booking details in the Booking System.
4. The customer can view the updated details of their booking.
Normal Flow: Update booking
The customer logs into their account.
5. The customer navigates to the account section on the navbar to display a
dropdown including personal information and current bookings.
6. The customer clicks on the "Appointment Schedule" .

GAMS-SRS_v1.0 Page 32 / 20
 7. The system retrieves the customer's upcoming bookings from the Booking
System.
8. The customer modifies the booking details (shifts, time, services, barber).
9. The customer confirms the changes.
10. The system updates the booking details in the Booking System.
11. The system displays the updated booking details.
Alternative Flows: AF1. No Upcoming Bookings:
7.1 .If the customer has no upcoming bookings, the system displays a message
indicating no current bookings are available.
Exceptions: E1. System Error:
The system encounters an error while retrieving booking data. The customer is
advised to try again later
Business Rules: BR3

b. Business Rules

ID Business Rule Business Rule Description

BRBooking Data Retrieval The system must accurately retrieve and display booking data
3 from the Booking System.

2.4 Cancel Booking

a. UC Specification
UC Name: Cancel booking Author: Trung Date: 29/05/2024
Primary Actor: Customer Secondary Actors: none
Description: This use case describes how a customer cancels an upcoming booking through the
online system. The customer navigates to the current bookings section of their
account, selects a booking to cancel.
Trigger: Point to the account and select Appointment Schedule and click cancel
Preconditions: 1. The customer must be logged into their account.
[Link] must have their booking schedule recorded in the system.

Postconditions: 3. The system updates the booking status to "Cancel" in the Booking System.
4. The customer can see the updated status of their booking.

Normal Flow: Update booking

5. The customer logs into their account.
6. The customer navigates to the account section on the navbar to display a 7
dropdown including personal information and Appointment Schedule.
[Link] customer clicks on the "Appointment Schedule" link.
[Link] system retrieves the customer's upcoming bookings from the Booking
System.

GAMS-SRS_v1.0 Page 33 / 20
 9. The customer confirms the cancellation.
10. The system updates the booking status to "Cancel" in the Booking System.
11. The system displays the updated status of the booking.
Alternative Flows: AF1. No Upcoming Bookings:
8.1 If the customer has no upcoming bookings, the system displays a message
indicating no current bookings are available.
Exceptions: E1. System Error:
The system encounters an error while retrieving booking data. The customer is
advised to try again later
Business Rules: BR3

b. Business Rules

ID Business Rule Business Rule Description

BRBooking Data Retrieval The system must accurately retrieve and display booking data
3 from the Booking System.

2.5 View Customer Profile

a. UC Specification
UC Name: View Customer Profile
Author Nguyễn Thùy Linh - HE170290
Primary Actor: Customer Secondary Actors: none
Description: Allows customers to view their personal information.
Trigger: The user wants to view or update his personal profile information.
Preconditions: The user is logged into the system.
Postconditions: [Link] user's profile information is displayed or updated successfully.
[Link] system stores new information if there are changes.
Normal Flow: View Customer Profile
[Link] access their personal profile page from the system interface.
2. The system displays the user's current profile information.
3. Users can view or edit personal information using the Update button.
4. The system updates information in the database if the user changes and the user
can review it to check.

Alternative Flows: AF2.1. Wrong personal information

1. User goes to profile
2. The user has updated their profile but when viewing it, the information is not
correct for the updated user
[Link] user notifies the customer consultant for support.
Exceptions: E1. System Error:
If the system encounters a technical or unknown error, an error message will be
displayed to the user and they will be asked to try again later.
Business Rules: BR4

GAMS-SRS_v1.0 Page 34 / 20
b. Business Rules

ID Business Rule Business Rule Description

BRProtection of personal data All personal information must be stored and handled according
4 to the system's security policy.
BRSession management Users must log in to access and change personal profile
5 information.

2.6 Update Customer Profile

a. UC Specification
UC Name: Update Customer Profile
Author Nguyễn Thùy Linh - HE170290
Primary Actor: Customer Secondary Actors: none
Description: Allows customers to update their profile .
Trigger: User wants to update his personal profile information.
Preconditions: The user is logged into the system.
Postconditions: [Link] user's profile information was successfully updated.
[Link] system stores new information if there are changes.
Normal Flow: Update Customer Profile
1. User accesses a personal profile page.
2. The system displays the user's current profile information.
[Link] edit personal information by pressing the update button to edit the
information.
4. The user presses the save changes button.
5. The system verifies the validity of new information.
6. The system updates information in the database.
[Link] system switches to the profile view page for the user to check whether the
information changes are correct or not.

Alternative Flows: AF3.1. Users who want to add or change their profile picture:
[Link] selects the option to change the avatar.
[Link] uploads a new photo from a computer or mobile device.
[Link] photo storage system and update avatar on user profile.

Exceptions: [Link] Error:

If the system encounters a technical or unknown error, an error message will be
displayed to the user and they will be asked to try again later.

GAMS-SRS_v1.0 Page 35 / 20
 [Link] information:
If the new information is invalid, the system will notify an error and ask the user to
re-enter the correct information.

Business Rules: BR4

b. Business Rules

ID Business Rule Business Rule Description

BRProtection of personal data All personal information must be stored and handled according
4 to the system's security policy.
BRSession management Users must log in to access and change personal profile
5 information.

3. Booking Management
3.1 Create Booking
a. UC Specification
UC Name Create Booking Author: Đức Anh- 29/05/2024
HE172622
Primary Actor: Customer Secondary Actors: Admin, Barber, Payment
System, Reservation
Management System
Description: This use case describes the process of a customer registering for a service with a
barber. Customers choose the service, choose the barber, choose the time, provide
the necessary information, and confirm the booking information. The system
processes the reservation, sending it to the cashier for confirmation. Admins can
monitor and manage the overall booking process.
Trigger: The customer initiates a booking request through the website.
Preconditions: [Link] customer must be logged into their account (if required).
[Link] customer must have access to the booking page.
[Link] services and barbers must be available for booking.
Postconditions: 1. The booking is recorded in the system.
2. The customer receives a booking confirmation after the cashier confirms.
Normal Flow: Register for Payroll Deduction
1. The customer logs into their account.
[Link] customer navigates to the booking page.
[Link] customer selects the desired service and barber.
[Link] system displays about the service, include pricing.
[Link] customer provides necessary information (e.g., date, time).
[Link] customer confirms the booking details.
[Link] system records the booking in the Reservation Management System.
[Link] system sends a booking request to the cashier for confirmation.
[Link] cashier confirms or declines the booking request.
[Link] system displays a booking confirmation page to the customer.
[Link] admin can view and manage the booking process.

GAMS-SRS_v1.0 Page 36 / 20
 Alternative Flows: Cashier Declines Booking:
If the cashier declines the booking request, the system notifies the customer.
The customer can choose to book with another barber or select a different time.
Exceptions: System Error:
The customer is advised to try again later or contact customer support.
Business Rules: BR1, BR2

b. Business Rules

ID Business Rule Business Rule Description

BRCustomer Authentication The customer must be authenticated to make a booking.
1
BRAvailability Check The system must check the availability of the service and
2 barber before confirming the booking.

3.2 View Booking

a. UC Specification
UC Name View Booking Author:
Primary Actor: Customer Secondary Actors: Admin, Barber, Payment
System, Reservation
Management System
Description:Displays the details of a customer's booking.
Trigger:Customer licks on the "View Booking" button.
Preconditions:Customer must be logged in.
Postconditions:Booking details are displayed.
Normal Flow: 1. User clicks "View Booking."
2. System retrieves booking details.
3. System displays the booking details, including booking ID, date, time,
services booked, and status.
Alternative Flows: Booking details not found: System displays an error message.
Exceptions: None
Business Rules: BR3, BR4

b. Business Rules
ID Business Rule Business Rule Description
BR3 Customers can only view their own bookings.
BR4 Booking details must include current status and any notes from
the service provider.

3.3 Update Booking

a. UC Specification
UC Name Update Booking Author:
Primary Actor: Customer Secondary Actors: Admin, Barber, Payment
System, Reservation

GAMS-SRS_v1.0 Page 37 / 20
 Management System
Description: Allows customers to update the details of their booking.
Trigger: Customer licks on the "View Booking" button.
Preconditions: Customer must be logged in and have an existing booking.
Postconditions: Booking details are updated.
Normal Flow: [Link] clicks "Update Booking" button.
[Link] retrieves current booking details.
[Link] displays an editable form with current details.
[Link] updates the booking details (e.g., date, time, services).
[Link] submits the form.
[Link] saves the updated details and displays a success message.
Alternative Flows: Update fails due to validation errors: System displays error messages for invalid
fields.
Exceptions: None
Business Rules: BR5, BR6, BR7

b. Business Rules
ID Business Rule Business Rule Description
BR5 Customers can only update bookings up to 24 hours before the
scheduled time.
BR6 Any changes to the booking must adhere to current availability
and pricing.
BR7 Customers cannot reduce the number of services below the
minimum requirement for the booking type.

3.4 Create Booking again

a. UC Specification
UC Name Create Booking again Author:
Primary Actor: Customer Secondary Actors: Admin, Barber, Payment
System, Reservation
Management System
Description: Allows customers to recreate a previous booking with similar details.
Trigger: Customer licks on the " Create Booking Again" button.
Preconditions: Customer must be logged in and have at least one previous booking.
Postconditions: A new booking is created with similar details to a previous one.
Normal Flow: [Link] clicks "Update Booking" button.
2. System retrieves previous booking details.
3. System displays a form pre-filled with previous booking details.
[Link] reviews and modifies details if necessary.
[Link] confirms the booking.
6. System saves the new booking and displays a success message.
Alternative Flows: -User cancels the booking process: System returns to the previous screen
without creating a new booking.
-System fails to retrieve previous booking details: System displays an error
message and returns to the previous screen.

GAMS-SRS_v1.0 Page 38 / 20
 Exceptions: None
Business Rules: BR8, BR9

b. Business Rules
ID Business Rule Business Rule Description
BR8 Only past bookings from the last 24 h can be recreated.
BR9 Booking recreation must adhere to current pricing and
availability..

3.5 Cancel Booking

a. UC Specification
UC Name Cancel Booking Author:
Primary Actor: Customer Secondary Actors: Admin, Barber, Payment
System, Reservation
Management System
Description: Allows customers to cancel their existing booking.
Trigger: Customer licks on the "Cancel Booking"button.
Preconditions: Customer must be logged in and have an existing booking.
Postconditions: Booking is canceled.
Normal Flow: 1. User clicks "Cancel Booking" button.
2. System displays a confirmation dialog.
3. Customer confirms the cancel.
4. System cancels the booking and displays a success message.
Alternative Flows: Customer cancels the process: System returns to the previous screen without any
changes.
Exceptions: None
Business Rules: BR10, BR11, BR12, BR13

b. Business Rules
ID Business Rule Business Rule Description
FR10 Customers can only cancel bookings up to 24 hours before the
scheduled time.
FR11 Cancellation policies, including any potential fees, must be
displayed to the user before confirmation.
FR12 Customers can only cancel their own bookings.
FR13 Canceled bookings should update the availability for other
customers to book the same time slot.

GAMS-SRS_v1.0 Page 39 / 20
4. Staff Management
4.1 View list staff
a. UC Specification
UC Name: View list staff
Author Phạm Đức Thiện
Primary Actor: Admin Secondary
Actors
Description: This is used by the admin to be able to view the list of all staff in the system
and that list includes staff information.
Trigger: The user wants to see a list of his staffs
Preconditions: The person logging into the system must have admin rights
There must be a list of staff in the data
Postconditions: Admin can view staff information
Normal Flow: 1. Admin logs into the system with his account from the home page
2. Go to the staffs section in the control bar
3. After clicking, a list of all staffs in the system will appear
4. Admin can view staff information in the system
Alternative if no people in the list this will current outline no people in list
Flows:
Exceptions: system error: Contact software support for resolution
Business Rules: BR1, BR2

b. Business Rules

ID Business Rule Business Rule Description

B Access and Data Only admins can access the comprehensive staff list,
R1Management which includes all staff members and their essential
information
B Functionality and The system must support exporting the staff list, provide a
R2Security user-friendly interface, and log all admin actions for audit
purposes

4.2 Add staff

a. UC Specification
UC Name: Add Staff
Author Phạm Đức Thiện

GAMS-SRS_v1.0 Page 40 / 20
 Primary Actor: Admin Secondary
Actors:
Description: When more employees are accepted to work, they need to be added to the
system for management. This use case is then used by the administrator to
add new employees to their employee list.
Trigger: The user add a new employee to the list
Preconditions: The person logging into the system must have admin rights
Postconditions: Admin can add new staff information
Normal Flow: 1. The admin logs into the system using an account with admin rights
2. Admin goes to the staff page to view employee lists
3. Admin clicks on the add employee button
4. admin fill in the information (phone, fullName, password, role,
birthday, gender, address)
5. After filling in the information, the admin clicks submit
6. Then the system will return to the employee list page
7. Admin can see the new employee he just added
Alternative If the add fails, it will return to the employees list page and display a
Flows: notification
Exceptions: system error: Contact software support for resolution
Business Rules: BR1, BR2

b. Business Rules

ID Business Rule Business Rule Description

B Access and Required Only admins can add new employees, ensuring all
R1Information necessary details are provided and validated.
B Process and Security The system must confirm successful addition
R2

4.3 Delete staff

a. UC Specification
UC Name: Delete Staff
Author Phạm Đức Thiện

GAMS-SRS_v1.0 Page 41 / 20
 Primary Actor: Admin Secondary
Actors:
Description: When an employee quits or is fired, the admin will use this function to delete
that employee from the system's employee list and that employee will no
longer appear on the list.
Trigger: Admin needs to delete employees from the list
Preconditions: The person logging into the system must have admin rights
Postconditions: Admin can delete employees in the employee list
Normal Flow: 1. The admin logs into the system using an account with admin rights
2. Admin goes to the staff page to view employee lists
3. Admin clicks on the delete employee button in the row of the
employee you want to delete
4. Then that employee's information will no longer appear in the list and
the system will return to the employee list page.
Alternative If the employee cannot be deleted due to a system error, an error message
Flows: will appear
Exceptions: system error: Contact software support for resolution
Business Rules: BR1, BR2

b. Business Rules

ID Business Rule Business Rule Description

B Access and Action Only admins can delete employees from the system,
R1 ensuring the employee no longer appears on the
employee list.
B Process and Security The system must confirm the deletion action, log it for
R2 audit purposes, and provide meaningful error messages if
any issues occur.

4.4 View profile staff

a. UC Specification
UC Name: View profile staff
Author
Primary Actor: Barber Secondary
Actors:
Description: Allows barbers/admin to view information about their personal profile
Trigger: User clicks on the "Thông tin cá nhân" link for staff.
Preconditions: User must be logged in with barber privileges.

GAMS-SRS_v1.0 Page 42 / 20
 Postconditions: Staff profile details are displayed.
Normal Flow: 1. User clicks " Thông tin cá nhân."
2. System retrieves staff details.
3. System displays staff profile, including personal information, job details,
and contact information.
Alternative Staff profile not found: System displays an error message.
Flows:
Exceptions:
Business Rules:

b. Business Rules
 BR3: Only admin and manager roles can view staff profiles.
 BR4: Staff personal information must be protected according to privacy policies.
4.5 Update profile staff
a. UC Specification
UC Name: Update profile staff
Author
Primary Actor: Barber Secondary
Actors:
Description: Allows updating the profile details of a selected staff member.
Trigger: User clicks on the "Cập nhập" link for staff.
Preconditions: User must be logged in with barber privileges.
Postconditions: Staff profile is updated with new details.
Normal Flow: 1. User clicks "Cập nhập"
2. System retrieves staff details.
3. System displays staff profile, including personal information, job details,
and contact information.
4. User updates the details.
5. User submits the form.
6. System saves the updated details and displays a success message.
Alternative Update fails due to validation errors: System displays error messages for invalid
Flows: fields.
Exceptions:
Business Rules:

GAMS-SRS_v1.0 Page 43 / 20
b. Business Rules
 BR3: Only admin and manager roles can update staff profiles.
 BR4: Validation rules must ensure data accuracy (e.g., valid email format).

4.6 Change Password Employees Account Screen

a. UC Specification
UC Name: Change Password Employees Account Screen
Author
Primary Actor: Barber Secondary
Actors:
Description: Allows users to change their account password.
Trigger: User clicks on the "Thay đổi mật khẩu" button.
Preconditions: User must be logged in.
Postconditions: Password is updated.
Normal Flow: 1. User clicks "Thay đổi mật khẩu" button.
2. System displays a form to enter the current password, new password, and
confirm new password.
3. User enters the current password, new password, and confirms the new
password.
4. System validates the current password and matches the new password with
the confirmation.
5. System validates the current password and matches the new password with
the confirmation.
Alternative - Current password is incorrect: System displays an error message.
Flows: - New password and confirmation do not match: System displays an
error message.
Exceptions:
Business Rules:

b. Business Rules
 BR4: Password must be at least 8 characters long and contain a mix of letters and numbers.
 BR5: Users cannot reuse their last 5 passwords.
4.7 Employees Resign Screen
a. UC Specification
UC Name: Employees Resign Screen
Author
Primary Actor: Barber Secondary
Actors:

GAMS-SRS_v1.0 Page 44 / 20
 Description: Allows marking an employee as resigned.
Trigger: User clicks on the "Employees Resign" link.
Preconditions: User must be logged in with admin or manager privileges.
Postconditions: Employee is marked as resigned in the system.
Normal Flow: 1. User clicks "Employees Resign."
2. System displays a confirmation dialog.
3. User confirms the resignation.
4. System updates the employee status to resigned and displays a success
message.
Alternative User cancels the resignation process: System returns to the previous screen without
Flows: any changes.
Exceptions:
Business Rules:

b. Business Rules
BR6: Employees can only be marked as resigned if they have no pending tasks.
4.8 Recovery Employees Resign Screen
a. UC Specification
UC Name: Recovery Employees Resign Screen
Author
Primary Actor: Barber Secondary
Actors:
Description: Allows reactivating a previously resigned employee.
Trigger: User clicks on the "Recovery Employees Resign" link.
Preconditions: User must be logged in with admin or manager privileges.
Postconditions: Employee status is updated to active.
Normal Flow: 1. User clicks "Recovery Employees Resign."
2. System retrieves resigned employee details.
3. System displays a form to confirm reactivation.
4. User confirms the reactivation.
5. System updates the employee status to active and displays a success
message.
Alternative User cancels the reactivation process: System returns to the previous screen without
Flows: any changes.
Exceptions:

GAMS-SRS_v1.0 Page 45 / 20
 Business Rules:

b. Business Rules
BR7: Reactivation can only occur within 6 months of resignation.

4.9 Request leave

a. UC Specification
UC Name: Request leave
Author
Primary Actor: Barber Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

4.10 Confirm leave request

a. UC Specification
UC Name: Confirm leave request
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

GAMS-SRS_v1.0 Page 46 / 20
b. Business Rules

4.9 View List Work Schedule

a. UC Specification
UC Name: View List Work Schedule
Author
Primary Actor: Admin, Barber Secondary
Actors:
Description: Displays the work schedule for all employees.
Trigger: User clicks on the "View List Work Schedule" link.
Preconditions: User must be logged in with admin or manager privileges.
Postconditions: Work schedules are displayed.
Normal Flow: 1. User clicks "View List Work Schedule."
2. System retrieves work schedule data.
3. System displays the work schedules in a calendar or tabular format.
Alternative No work schedules available: System displays a message indicating no schedules
Flows: found.
Exceptions:
Business Rules:

b. Business Rules
BR8: Work schedules must be updated daily.

5. Service management
5.1 View list service
a. UC Specification
UC Name: View list service
Author
Primary Actor: Admin, Barber, Customer Secondary
Actors:
Description: Displays a list of available services.
Trigger: User clicks on the "View List Service" link.
Preconditions: User must be logged in.
Postconditions: List of services is displayed.
Normal Flow: 1. User clicks "View List Service."
2. System retrieves service data.
3. System displays the services in a list format.

GAMS-SRS_v1.0 Page 47 / 20
 Alternative No services available: System displays a message indicating no services found.
Flows:
Exceptions:
Business Rules:

b. Business Rules
BR9: Services list must include current availability status.

5.2 View list service detail

a. UC Specification
UC Name: View list service detail
Author
Primary Actor: Admin, Barber, Customer Secondary
Actors:
Description: Displays detailed information about a selected service.
Trigger: User clicks on a service from the "View List Service" screen.
Preconditions: User must be logged in.
Postconditions: Detailed service information is displayed.
Normal Flow: 1. User clicks on a service from the list.
2. System retrieves detailed information about the selected service.
3. System displays the detailed information.
Alternative Service details not found: System displays an error message.
Flows:
Exceptions:
Business Rules:

b. Business Rules
BR10: Detailed information must include service description, pricing, and availability.

5.3 Update service

a. UC Specification
UC Name: Update service
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:

GAMS-SRS_v1.0 Page 48 / 20
 Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

5.4 Add service

a. UC Specification
UC Name: Add service
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

5.5 View top service

a. UC Specification
UC Name: View top service
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.

GAMS-SRS_v1.0 Page 49 / 20
 Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

5.6 Delete Service

a. UC Specification
UC Name: Delete Service
Author
Primary Actor: Admin Secondary
Actors:
Description: When an employee quits or is fired, the admin will use this function to delete
that employee from the system's employee list and that employee will no
longer appear on the list.
Trigger: Admin needs to delete employees from the list
Preconditions: The person logging into the system must have admin rights
Postconditions: Admin can delete employees in the employee list
Normal Flow: 1. The admin logs into the system using an account with admin rights
2. Admin goes to the staff page to view employee lists
3. Admin clicks on the delete employee button in the row of the
employee you want to delete
4. Then that employee's information will no longer appear in the list and
the system will return to the employee list page.
Alternative If the employee cannot be deleted due to a system error, an error message
Flows: will appear
Exceptions: system error: Contact software support for resolution
Business Rules:

b. Business Rules

5.7 Search service detail

a. UC Specification
UC Name: Search service detail
Author
Primary Actor: Admin Secondary
Actors:

GAMS-SRS_v1.0 Page 50 / 20
 Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

6. Feedback Management
6.1 Feedback service
a. UC Specification
UC Name: Feedback service
Author
Primary Actor: Customer Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

6.2 View feedback

a. UC Specification
UC Name: View feedback
Author
Primary Actor: Customer, Admin, Barbers Secondary
Actors:
Description:

GAMS-SRS_v1.0 Page 51 / 20
 Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7. Shop Management
7.1 View revenue
a. UC Specification
UC Name: View revenue
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.2 Export monthly revenue to excel file

a. UC Specification
UC Name: Export monthly revenue to excel file
Author
Primary Actor: Admin Secondary
Actors:
Description:

GAMS-SRS_v1.0 Page 52 / 20
 Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.3 View Order Detail

a. UC Specification
UC Name: View Order Detail
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.4 View sales

a. UC Specification
UC Name: View sales
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:

GAMS-SRS_v1.0 Page 53 / 20
 Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.5 Store status

a. UC Specification
UC Name: Store status
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.6 Booking choose barbers

a. UC Specification
UC Name: Booking choose barbers
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:

GAMS-SRS_v1.0 Page 54 / 20
 Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.7 Chat
a. UC Specification
UC Name: Chat
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

7.8 Homepage
a. UC Specification
UC Name: Homepage
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative

GAMS-SRS_v1.0 Page 55 / 20
 Flows:
Exceptions:
Business Rules:

b. Business Rules

8. Bill Management
8.1 Create bill
a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

8.2 Update bill

a. UC Specification
UC Name: Update bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative

GAMS-SRS_v1.0 Page 56 / 20
 Flows:
Exceptions:
Business Rules:

b. Business Rules

8.3 Check in
a. UC Specification
UC Name: Check in
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

8.4 View detail bill

a. UC Specification
UC Name: View detail bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:

GAMS-SRS_v1.0 Page 57 / 20
 Business Rules:

b. Business Rules

8.5 View the bill

a. UC Specification
UC Name: View the bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

8.6 Voucher
a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

GAMS-SRS_v1.0 Page 58 / 20
b. Business Rules

8.7 Create voucher

a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

8.8 Update voucher

a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

GAMS-SRS_v1.0 Page 59 / 20
8.9 Update point
a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

8.10 Accumulate points

a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

GAMS-SRS_v1.0 Page 60 / 20
8.11 Time remind
a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

8.12 Payment method

a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

GAMS-SRS_v1.0 Page 61 / 20
8.13 Check out
a. UC Specification
UC Name: Create bill
Author
Primary Actor: Admin Secondary
Actors:
Description:
Trigger:
Preconditions:
Postconditions:
Normal Flow: 1.
Alternative
Flows:
Exceptions:
Business Rules:

b. Business Rules

III. Screen Designs

[Link]
1.1 Sign up
This screen allows users to sign up for a new account.

GAMS-SRS_v1.0 Page 62 / 20
 Field Name Field Type Description
<- Quay lại trang chủ Hyperlink User clicks to redirect to the Home Page

GAMS-SRS_v1.0 Page 63 / 20
 SỐ ĐIỆN THOẠI* String(10) This is for user to input phone for signing up
MẬT KHẨU* String This is for user to input password for signing up
XÁC THỰC MẬT String This is for user to input password to check password for
KHẨU* signing up
HỌ VÀ TÊN* String This is for user to input full name for signing up
EMAIL* String(2,6) This is for user to input email for signing up
ẢNH ĐẠI DIỆN File This is for user to select file for signing up
GIỚI TÍNH Boolean This is for user to select gender for signing up
ĐĂNG KÝ Button User clicks to signing in new account
ĐĂNG NHẬP Hyperlink User clicks if he/she already have an account

Database Access

Table CRUD Description

account C Create a new account
customer C Create a new account for customer

1.2 Sign in
a. Login
This screen allows users to be authenticated to the system screens/functionalities.

GAMS-SRS_v1.0 Page 64 / 20
 Field Name Field Type Description
<- Quay lại trang chủ Hyperlink User clicks to redirect to the Home Page
SỐ ĐIỆN THOẠI* String(10) This is for user to input phone for signing in
MẬT KHẨU* String(8-20) This is for user to input password for logging in
ĐĂNG NHẬP Button User clicks to authenticate him/herself into the system with
provided email & password
Quên mật khẩu? Hyperlink User clicks to redirect to the Password Reset page for
resetting his/her forgot password
Đăng ký Hyperlink User clicks to redirect to the Signup page for create new

GAMS-SRS_v1.0 Page 65 / 20
 account

Database Access
Table CRUD Description
account R Read accounts from database

b. Logout
This screen allows the user to exit the account with system screens/functions.

Field Name Field Type Description

LOGOUT Hyperlink Users clicks to logout their account

Database Access

Table CRUD Description

account
customer

c. Forgot password

GAMS-SRS_v1.0 Page 66 / 20
 Field Name Field Type Description
Email* Text Box Registered email
String (30)
Cancel Button Back to login page

Enter Button Send mail

Database Access
Table CRUD Description
account U Update password

d. Change password

GAMS-SRS_v1.0 Page 67 / 20
 Field Name Field Type Description
Old Password Text Box Current password of the account
String (20)
New Password Text Box New password of the account
String (20)
Confirm Text Box Confirm Password
Password String (20)
Change Pass Button Update new password

Database Access
Table CRUD Description
account U Update password

2. Customer Management
2.1 View profile customer

GAMS-SRS_v1.0 Page 68 / 20
 Field Name Field Type Description
Update Button Update users profile
ChangePass Button Change password by users

Database Access
Table CRUD Description
customer R View information of user profile

GAMS-SRS_v1.0 Page 69 / 20
2.2 Update profile customer

Field Name Field Type Description

Full Name String This is for user to update full name for user profile
Email* String(2,6) This is for user to update email for user profile
Avarta File This is for user to select file for user profile
Gender Boolean This is for user to update gender for user profile
Update Button Update users profile and return to users profile

Database Access
Table CRUD Description
customer R View information of user profile

2.3 Views history booking

3. Booking Management
3.1 Create Booking

GAMS-SRS_v1.0 Page 70 / 20
 Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description
orders C Create booking
accounts R Read account customer, read account barber
Services R Read the services available in the store
Shifts R take the empty shift

3.2 View Booking

This screen displays information about the booking schedule such as day, shift, worker and translation.
Users can update information or cancel orders

GAMS-SRS_v1.0 Page 71 / 20
 Field Name Field Type Description
Date select The user can choose new day for booking
Barber select The user can choose new barber for booking
Shifts select The user can choose new shift for booking

Database Access

Table CRUD Description

Booking R List all information booking

3.3 Update booking

Field Name Field Type Description

Date select The user can chose new day for booking
Barber select The user can chose new barber for booking
Services Checkbox The user can change services for booking
Shifts select The user can chose new shift for booking

GAMS-SRS_v1.0 Page 72 / 20
Database Access

Table CRUD Description

Booking D Delete unselected services
Booking U Update new booking
Booking R List all information booking

3.4 Create Booking

3.5 Cancel booking

Field Name Field Type Description

Cancel Button Customs cancel booking

Database Access

Table CRUD Description

Booking U Update status order became cancel

GAMS-SRS_v1.0 Page 73 / 20
4. Staff Management
4.1 View list staff

Field Name Field Type Description

Họ và tên label A label column displaying the full name of the employees.
Số điện thoại label A label column displaying the phone of the employees.
Giới tính label A label column displaying the gender of the employees.
Email label A label column displaying the email of the employees.
Trạng thái label A label column displaying the status of the employees.
Xóa button Used to delete employees
Thêm nhân viên button Used to add employees
Đã nghỉ việc button Used to view list of employees has resigned

Database Access
Table CRUD Description
employees R Read all employees from database
statusEmployee R Read all employees ‘s status from database

4.2 Add staff

GAMS-SRS_v1.0 Page 74 / 20
 Field Name Field Type Description
Số điện thoại text This is for admin to input phone for employee
Họ và tên text This is for admin to input full name for employee
Mật khẩu text This is for admin to input password for employee
Email text This is for admin to input email for employee
Avatar Select This is for admin to select picture for employee
Vai trò Select This is for admin to select role for employee
Gửi Submit Add new employee

Database Access
Table CRUD Description
account C Create new account for database
employee C Create new employee for database

GAMS-SRS_v1.0 Page 75 / 20
4.3 Delete staff

Field Name Field Type Description

Xóa button Used to delete employees

Database Access
Table CRUD Description
employee D Delete employee from database

4.4 View profile staff

GAMS-SRS_v1.0 Page 76 / 20
 Field Name Field Type Description
Họ và tên label This is for barber to read full name of profile
Số điện thoại label This is for barber to read phone of profile
Email label This is for barber to read email of profile
Chức vụ label This is for barber to read role of profile
Giới tính label This is for barber to read gender of profile
Chỉnh sửa button Used to update information of barber
Đổi mật khẩu button Used to change password for barber

Database Access
Table CRUD Description
employee R Read employee from database

4.5 Update profile staff

Field Name Field Type Description

Họ và tên text This is for barber to update full name of profile

GAMS-SRS_v1.0 Page 77 / 20
 Số điện thoại label Phone can not be change
Email text This is for barber to update email of profile
Chức vụ label Role can not be change
Giới tính label Gender can not be change
Lưu submit Used to save the update information of barber
Đổi mật khẩu button Used to change password for barber

Database Access
Table CRUD Description
employee U Update employee for database

GAMS-SRS_v1.0 Page 78 / 20
4.6 Change Password Employees Account

GAMS-SRS_v1.0 Page 79 / 20
 Field Name Field Type Description
Checkbox
Select
Select
Select
Submit

Database Access
Table CRUD Description

4.7 Employees Resign

Field Name Field Type Description

Checkbox
Select
Select
Select
Submit

Database Access
Table CRUD Description

4.8 Recovery Employees Resign

Field Name Field Type Description

Checkbox
Select
Select
Select
Submit

Database Access
Table CRUD Description

GAMS-SRS_v1.0 Page 80 / 20
4.9 View List Work Schedule

Field Name Field Type Description

Checkbox
Select
Select
Select
Submit

Database Access
Table CRUD Description

4.10 Request leave

Field Name Field Type Description

Checkbox
Select
Select
Select
Submit

Database Access
Table CRUD Description

4.11 Confirm leave request

Field Name Field Type Description

Checkbox
Select
Select
Select
Submit

Database Access
Table CRUD Description

GAMS-SRS_v1.0 Page 81 / 20
5. Service Management
5.1 View list service

Field Name Field Type Description

name label This is the name of service
image label This is the image of service
description label This is the description of service
price label This is the Listed price of service

Database Access
Table CRUD Description
Services R Read all services from database

5.2 View list service detail

Field Name Field Type Description

Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

GAMS-SRS_v1.0 Page 82 / 20
Database Access
Table CRUD Description
accounts R Read accounts from database

5.3 Update service

Field Name Field Type Description

Tên dịch vụ text This is for admin to update name for service
Giá text This is for admin to update price for service

GAMS-SRS_v1.0 Page 83 / 20
 Mô tả text This is for admin to update description for service
Hình ảnh Select This is for admin to update picture for service
Cập nhập Submit Update service
Quay lại Button Return to list of service

Database Access
Table CRUD Description
Services U Update service

5.4 Add service

GAMS-SRS_v1.0 Page 84 / 20
 Field Name Field Type Description
Tên dịch vụ text This is for admin to input name for service
Giá text This is for admin to input price for service
Mô tả text This is for admin to input description for service
Hình ảnh Select This is for admin to input picture for service
Thêm Submit Add new service
Quay lại Button Return to list of service

Database Access
Table CRUD Description
Services C Create new service

5.5 View top service

Field Name Field Type Description

Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description
accounts R Read accounts from database

5.6 Delete Service

Field Name Field Type Description

Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description
accounts R Read accounts from database

GAMS-SRS_v1.0 Page 85 / 20
5.7 Search service detail

Field Name Field Type Description

Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description
accounts R Read accounts from database

6. Feedback Management
6.1 Feedback service

Field Name Field Type Description

Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

6.2 View feedback

Field Name Field Type Description

Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

GAMS-SRS_v1.0 Page 86 / 20
7. Shop Management
7.1 View revenue
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

7.2 Export monthly revenue to excel file

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

7.3 View Order Detail

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

7.4 View sales

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date

GAMS-SRS_v1.0 Page 87 / 20
 Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

7.5 Store status

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

7.6 Booking choose barbers

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

7.7 Chat
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

GAMS-SRS_v1.0 Page 88 / 20
7.8 Homepage
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8. Bill Management
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.2 Update bill

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.3 Check in
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment

GAMS-SRS_v1.0 Page 89 / 20
 Appointment

Database Access
Table CRUD Description

8.4 View detail bill

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.5 View the bill

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.6 Voucher
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.7 Create voucher

Field Name Field Type Description
Services Checkbox store services for customers to choose from

GAMS-SRS_v1.0 Page 90 / 20
 Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.8 Update voucher

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.9 Update point

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.10 Accumulate points

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

GAMS-SRS_v1.0 Page 91 / 20
8.11 Time remind
Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.12 Payment method

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

8.13 Check out

Field Name Field Type Description
Services Checkbox store services for customers to choose from
Barber Select The store's Barber is for customers to choose from
date Select appointment date
Shift Select Available shift of the day and selected barber
Make an Submit Make an appointment
Appointment

Database Access
Table CRUD Description

IV. Code Designs

0. <Feature/Function Name1>
[Provide the detailed design for the function <Feature/Function Name1>. It includes class diagram and
sequence diagram(s)]

GAMS-SRS_v1.0 Page 92 / 20
0.1 Class Diagram
[This part presents the class diagram for the relevant feature]

0.2 Sequence Diagram(s)

[Provide the sequence diagram(s) for the feature/function, see the sample below. Sequence diagrams
with similar message flow can be omitted, but you need to mention the appropriate reference to the
similar sequence diagram]

GAMS-SRS_v1.0 Page 93 / 20
0.3 Database Queries
[Provide the detailed SQL (select, insert, update...) which are used in implementing the function/screen]

1. <Common>
1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

2. <Customer Management>
1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

3. <Booking Management>
1.1 Class Diagram

1.2 Sequence Diagram(s)

GAMS-SRS_v1.0 Page 94 / 20
1.3 Database Queries

4. <Staff Management>
1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

5. <Service management>
1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

6. <Feedback Management>
1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

7. <Shop Management>

1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

8. <Bill Management>

1.1 Class Diagram

1.2 Sequence Diagram(s)

1.3 Database Queries

GAMS-SRS_v1.0 Page 95 / 20
V. Appendix
1. Assumptions & Dependencies
[Record any assumptions that were made when conceiving the project and writing this vision and scope
document. Note any major dependencies the project must rely upon for success, such as specific
technologies, third-party vendors, development partners, or other business relationships.]
<<Sample:
AS-1: Systems with appropriate user interfaces will be available for cafeteria employees to process
the expected volume of meals ordered.
AS-2: Cafeteria staff and vehicles will be available to deliver all meals for specified delivery time slots
within 15 minutes of the requested delivery time.
DE-1: If a restaurant has its own on-line ordering system, the Cafeteria Ordering System must be able
to communicate with it bi-directionally.
>>
*************************************************************************************
AS-1: The online appointment booking system will operate stably and can handle multiple requests
simultaneously without technical problems.
AS-2: Store staff will be trained to use the appointment management system and have the ability to
confirm appointments quickly.
AS-3: Customers have a stable internet connection to access the website and book appointments
online.
AS-4: The store is staffed sufficiently to accommodate all booked appointments, ensuring there are no
staffing shortages at any time.
AS-5: The website will be periodically maintained to ensure security and stable operation, without
service interruption.
2. Limitations & Exclusions
[Identify any product features or characteristics that a stakeholder might anticipate, but which are not
planned to be included in the new product]
DE-1: The online appointment booking system depends on successful integration with the store's existing
HR management system.
DE-2: The website depends on a third-party hosting service to ensure the website is always available and
operates continuously.
DE-3: The website depends on the online payment services of third-party payment providers such as
PayPal or local banks to process payment transactions.
DE-4: The website depends on cooperation with email and SMS delivery service providers to send
appointment confirmations and customer reminders.
DE-5: The website depends on compliance with data security regulations and standards to protect
customers' personal information as required by law.
3. Business Rules
[Provide common business rules that you must follow. The information can be provided in the table
format as the sample below]
<<Sample

GAMS-SRS_v1.0 Page 96 / 20
 ID Category Rule Definition
BR-01 Constraints Delivery time windows are 15 minutes, beginning on each quarter
hour
BR-02 Constraints Deliveries must be completed between 10:00 A.M. and 2:00 P.M. local
time, inclusive.
BR-03 Facts All meals in a single order must be delivered to the same location.
BR-04 Facts All meals in a single order must be paid for by using the same payment
method.
BR-11 Constraints If an order is to be delivered, the patron must pay by payroll
deduction.
BR-12 Computations Order price is calculated as the sum of each food item price times the
quantity of that food item ordered, plus applicable sales tax, plus a
delivery charge if a meal is delivered outside the free delivery zone.

>>

4. ..

GAMS-SRS_v1.0 Page 97 / 20