Template2 SRS GR4

G4-STORE
Software Requirement Specification

Mentor - Quách Luyl Đa
Đặng Minh Triết - CE160156
Phạm Tiến Đạt- CE160107
Nguyễn Toàn Thắng- CE160815
Nguyễn Vũ Cường - CE170711
Vũ Huy Đại Phúc - CE160106
GAMS-SRS_v1.0 Page 1 / 20
Contents
Record of Changes.........................................................................................................................................2
I. Overview....................................................................................................................................................4
1. User Requirements.................................................................................................................................4
1.1 Actors...............................................................................................................................................4
1.2 Use Cases.........................................................................................................................................4
2. Overall Functionalities...........................................................................................................................5
2.1 Screens Flow....................................................................................................................................5
2.2 Screen Descriptions.........................................................................................................................5
2.3 Screen Authorization.......................................................................................................................5
2.4 Non-UI Functions............................................................................................................................6
3. System High Level Design....................................................................................................................6
3.1 Database Design...............................................................................................................................6
3.2 Code Packages.................................................................................................................................7
II. Requirement Specifications.......................................................................................................................8
1. <<Feature Name>>................................................................................................................................8
1.1 <<UseCaseCode_UC Name>>........................................................................................................8
2. Common Functions..............................................................................................................................11
2.1 UC-2_Login System......................................................................................................................11
3. Patron Feature......................................................................................................................................12
3.1 UC-5_Order a Meal.......................................................................................................................12
3.2 UC-6_Register for Payroll Deduction...........................................................................................13
III. Design Specifications.............................................................................................................................14
1. <<Feature Name>>..............................................................................................................................14
1.1 <<SubFeature Name>>..................................................................................................................14
1.2 System Access...............................................................................................................................15
IV. Appendix................................................................................................................................................19
1. Assumptions & Dependencies.............................................................................................................19
2. Limitations & Exclusions....................................................................................................................19
3. Business Rules.....................................................................................................................................19
4. ..............................................................................................................................................................19
I. Overview
G4-Shop is not only a premier online shopping destination for fashion enthusiasts but
also offers several features and functionalities to enhance your experience:
1. Diverse Brand Selection: G4-Shop proudly curates a diverse collection from
renowned brands, providing a wide range of styles and fashion trends.
2. Attractive Deals and Promotions: G4-Shop regularly updates special offers and
promotions, helping you save on your favorite fashion items.
3. Flexible Return Policy: In case of any issues with a product, our flexible return
policy ensures your rights and satisfaction in every purchase.
4. Membership Points and Benefits: G4-Shop's membership program offers special
benefits, allowing you to accumulate points with each purchase for enticing rewards.
5. Secure and Efficient Payment Integration: Our safe and convenient payment
system enables you to complete transactions easily and securely, anytime, anywhere.
1. User Requirements:
1.1 Actors:
I.2 Use Case
2. System Functions
a. Screen Flow
Figure 2.1: Screen Flow for user
Figure 2.2: Screen Flow for admin
Figure 2.3: Screen Flow for staff
b. Screen Details
# Feature Screen Description
1 Login Login Used to log in to the login
2 Sign Up Sign Up Customers can register to be able to use the website
3 Users can use the forgot password feature to find it
again. When clicking on forgot password, users will be
Forgot Password Login
able to receive a form to fill in customer information and
retrieve the password.
4 View account Account This page allows users to view their own profile
5 The home page allows users to view featured products in
Product home page the store
6 The menu feature is to display everything users want to
Menu Home page find so they can choose according to personal needs
7 Search Home page Users can search for functionality on search engines
8 shopping cart
Cart page Users can add products to their shopping cart
9 Delete products shopping cart
in cart page Users can delete products after adding to cart
10 shopping cart When the user clicks on the + or - sign, the product will
+- page increase or decrease
11 History History Page Can view purchase history
12 Update a product including name, price, sale-off, status,
Update product Update Product category, description.
13 Order Order page Display the dishes that customers have
14 Edit order Order page Customers can edit
15 Load list voucher including ID, description, status, sale
List voucher list voucher percent.
16 Update voucher including ID, description, status, sale
Update voucher Update voucher percent.
17 Load all users to the screen including ID, name, number
List user Manage user of order.
18 Delete user Manage user Convert user status to REMOVED and hide the screen.
19 Show detailed user information including name, phone
Show user profile Show user number, email, address, number of orders placed, and
total amount spent.
c. User Authorization
Admin Gues Staff
Screen User t
Logn in x x x
Sign up x
Log out x x x
Forget password x
View account x
View and edit profile (User) x
View order list x x x
View purchase history x
Home page for admin x
Shopping cart management x
Update product x
Add products x
Delete product x
Gross product x
Edit information product x
Add to cart x
View product x x x x
Search product x x x
View information product x x x
Payment system x
Buy now x
Add account x
Remove account x
Remove product in cart x
View cart x
View user information (Admin) x
In which:
 Customer: Customer accounts can view products and purchase products.
 Admin: Manage store sales according to the number of customers purchased.
 Guest: Can view products and product information.
d. Non-Screen Functions
# Feature System Function Description
Sign in Used to log in to This function allows customers to go to the store's login
1
the sales store page to see the products inside
Send email Send email when Send an email to the user when successful ordering with
2 succeeded order’s information: Order’s ID, Quantity, Product’s
ordering name, Product’s price, Ship price, Total.
Forget password Send a email to
This function helps users find forgotten passwords by
3 user to change
sending email
password
MD5 password MD5 encrypted
An important measure to protect users' personal
passwords have
4 information, prevent unauthorized access, and ensure data
high security
security.
features
3. Entity Relationship Diagram
Description:
# Entity Description
1 User Include email, password use for login and detail information of user.
2 Staff Include email, password use for login and detail information of staff.
3 Admin Include email, password use for login and detail information of staff.
4 Product Provide product information for user.
5 Cart Contain the product, size and quantity that user want to buy.
6 Order Provide total price of product and purchase date for user.
7 OrderDetail Provide detailed information for each product that customers order.
8 Comment Contain comment of users about the product.
9 Import Provide the information of the product, import date.
10 ImportDetail Provide detailed information of each product imported.
II. Requirement Specifications

1.1 UC-2_Login System
a. Functional Description
UC ID and Name: UC-2_Login System
Created By: DatPT Date Created: 11/Jun/2024
Primary Actor: Customer Secondary Actors: None
Trigger: User clicks Login button from the Login page
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: User account has been created & authorized
Postconditions:  User logs in the system successfully
 The system tracked successful login into the Activity Log
Normal Flow 2.0 Login System
1. User accesses the User Login screen
2. User types in the login details or choose other login options (see 2.1 and 2.2)
3. User clicks the Login button
4. System validates the login details (see 2.0.E1)
5. System allows user to access
6. System tracks user’s success login to the Activity Log
7. System accesses the Home Page (or the previous calling page if any)
Alternative Flows: None
Exceptions: 2.0.E1 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 UC-1_View Home Page
3. User clicks “Forgot Password?” link => change to UC-3_Reset Password
4. User clicks “Register” link => change to UC-4_Register User Account
Priority: Must Have
Frequency of
Use:
Business Rules: FR1, FR2
Other
Information:
Assumptions:
b. Business Rules
ID Business Rule Business Rule Description
FR1 Password Encoding User’s password must be encoded with MD5 hashing
FR2 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
1.2 UC-3_Forget Password

UC ID and Name: UC-3_Forget Password
Trigger: User clicks Forget Password button from the Login page
Description: As a user, I want to be able to reset my account password if I forget it, in order to
regain access to my personal account and utilize system features.
Preconditions: User account has been created & authorized
Postconditions:  User's request to reset the password is successfully processed.

 An email with instructions for password reset is sent to the user's
registered email address.
Normal Flow 3.0 Forget Password Process
1. User clicks the "Forget Password" link on the Login page.
2. System prompts the user to enter the registered email address.
3. User enters the email address and submits the form.
4. System validates the email address and sends a password reset link to
the user's email.
5. User checks their email, clicks the reset link, and is directed to the
password reset page.
6. User enters a new password and confirms it.
7. System validates the new password, updates the user's account, and
confirms the successful password reset.
Exceptions: 3.0.E1 Email Not Found:
1. The system cannot find the user's email address in the database.
2. An error message is displayed, prompting the user to check the entered
email address.
3. User can choose to re-enter the email or cancel the process.
Priority: Must Have
Frequency of Low to Moderate
Use:
Business Rules: BR1, BR2
Other
Information:
Assumptions:
b. Business Rules
BR1 Password Policy User's new password must adhere to a specified password
policy.
BR2 Email Delivery The system must ensure prompt delivery of the password reset
email to the user's registered email address.
1.3 UC-4_Register User Account

UC ID and Name: UC-4_Register User Account
Trigger: User clicks the "Register" link from the Login page
Description: As a user, I want to create a new account on the platform to access personalized
features, manage my preferences, and make online purchases.
Preconditions: User doesn’t have an existing account with the system.
Postconditions: User's account is successfully created and registered in the system.
Normal Flow 4.0 User Registration Process
1. User clicks the "Register" link on the Login page.
2. System displays the User Registration form.
3. User fills in the required information, including email, password, name,
and other relevant details.
4. User submits the registration form.
5. System validates the entered information.
6. If validation is successful, the system creates a new user account.
7. System sends a verification email to the user's registered email address.
8. User receives the verification email and clicks the verification link.
9. System verifies the email, activates the user account, and confirms
successful registration.
10. User is redirected to the Login page for authentication.
Exceptions: 4.0.E1 Email Already Registered:
1. The system detects that the entered email is already registered in the
system.
2. An error message is displayed, prompting the user to log in or initiate a
password reset.
Priority: Must Have
Frequency of Infrequent
Use:
Business Rules: BR3
Other
Information:
Assumptions:
b. Business Rules
BR3 Unique Email Requirement The system must enforce a rule that each name and email
address can only be associated with one user account.
1.4 UC-5_User Profile

UC ID and Name: UC-5_User Profile
Created By: Date Created: 13/Jun/2024
Trigger:User clicks the "User Profile" link or accesses the user profile section.
Description:As a user, I want to view my profile information to see a summary of my account
details and settings.
Preconditions: User is logged into the system
Postconditions: User views their profile information.
Normal Flow 5.0 View User Profile
1. User navigates to the "User Profile" section or clicks the "User" icon.
2. System displays the current user profile information, including name,
contact information and and 2 “Edit” and “Change Password” buttons.
Exceptions: None
Priority: Should Have
Frequency of High
Use:
Business Rules: BR4
Other
Information:
Assumptions:
b. Business Rules
BR4 User Authentication User's new password must adhere to a specified password
policy.
1.5 UC-6_Edit Profile

UC ID and Name: UC-6_ Edit Profile
Trigger: User clicks the "Edit Profile" link or button within the user account settings.
Description: As a user, I want to be able to edit my profile information to keep it up-to-date
and reflect any changes in my personal details.
Preconditions: User is logged into the system.
Postconditions: User's profile information is successfully updated and saved in the system.
Normal Flow 6.0 Edit Profile Process
1. User navigates to the account settings or clicks the "Edit" button .
2. System displays the current user profile information.
3. User modifies the desired fields such as name, contact information, or
other relevant details.
4. User click “Edit” to submits the updated information.
5. System validates the changes.
6. If validation is successful, the system updates the user's profile
information.
7. System confirms the successful profile update.
8. User is redirected to the “User Profile” page.
Exceptions: 6.0.E1 Validation Failure:
1. The system detects errors or invalid input in the updated information.
2. An error message is displayed, prompting the user to correct the issues.
3. User can choose to re-enter the information or cancel the process.
Priority: Must Have
Frequency of Moderate
Use:
Business Rules: BR5
Other
Information:
Assumptions:
b. Business Rules
BR5 Unique Email Requirement The system must enforce a rule that each email address can only
be associated with one user account.
1.6 UC-7_Change Password

UC ID and Name: UC-7_Change Password
Trigger: User clicks the "Change Password" button in “User Profile” or accesses the
password change section.
Description: As a user, I want to change my account password to enhance security or update
my login credentials.
Preconditions: User is logged into the system.
Postconditions: User's password is successfully changed and updated in the system.
Normal Flow 7.0 Change Password Process
1. User navigates to the "Change Password" section or clicks the "Change
Password" button.
2. System prompts the user to enter the current password, the new
password and confirm new password.
3. User enters the required information.
4. User submits the password change form.
5. System validates the entered passwords.
6. If validation is successful, the system updates the user's password.
7. System confirms the successful password change.
8. User is redirected to the “User Profile” page.
Exceptions: 7.0.E1 Validation Failure:
1. The system detects errors or invalid input in the entered passwords.
2. An error message is displayed, prompting the user to correct the issues.
3. User can choose to re-enter the passwords or cancel the process.
Use:
Business Rules: BR1
Other
Information:
Assumptions:
b. Business Rules
BR1 Password Policy User's new password must adhere to a specified password
policy.
1.7 UC-8_Cart Management

UC ID and Name: UC-8_Cart Management
Trigger:Customer adds, removes, or views items in the shopping cart.
Description:As a customer, I want to manage the items in my shopping cart, including adding
new items, removing existing items, and viewing the contents of the cart.
Preconditions:  Customer is logged into the system.
 Products are available for purchase.
Postconditions: Changes to the shopping cart (addition, removal, or viewing) are successfully
reflected.
Normal Flow 8.0 Cart Management Process
1. Customer navigates to the shopping cart section.
2. System displays the current items in the cart along with options to add,
remove, or view details.
3. Customer adds a new item to the cart by selecting the product and
specifying the quantity.
4. System updates the cart to include the new item.
5. Customer removes an existing item from the cart by selecting the delete
option.
6. System updates the cart to exclude the removed item.
7. Customer views the details of the items in the cart, including names,
quantities, and prices.
8. System displays the requested information.
Alternative Flows: 8.0.A1 Empty Cart:
1. Customer attempts to view or remove items from an empty cart.
2. The system informs the customer that the cart is empty.
Exceptions:
Priority: Must Have
Use:
Business Rules: BR5
Other
Information:
Assumptions:
b. Business Rules
BR5 User Authentication The system must ensure that only authenticated customers have
access to their own shopping carts.
1.8 UC-9_Load Order Management

UC ID and Name: UC-9_Load Order Management
Created By: Date Created:
Primary Actor: Staff Secondary Actors: None
Trigger:Staff accesses the order management section.
Description:As an staff member, I want to load and view the order management interface to
monitor and manage customer orders.
Preconditions: Staff member is logged into the system.
Postconditions: Order management interface is successfully loaded.
Normal Flow 9.0 Load Order Management Interface
1. Staff member navigates to the "Order Management" section.
2. The system loads the order management interface, displaying data
including invoice number, OrderID, Account, Date and total amount of
the order.
Exceptions: None
Frequency of High
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
BR6 Staff Access The system must ensure that only authenticated staff members
have access to the order management section.
1.9 UC-10_Monthly Revenue Management

UC ID and Name: UC-10_ Monthly Revenue Management
Trigger:Staff accesses the monthly revenue management section.
Description:As an staff member, I want to load and view the monthly revenue management
interface to analyze and manage the revenue generated by the system.
Postconditions: Monthly revenue management interface is successfully loaded.
Normal Flow 10.0 Load Monthly Revenue Management Interface
1. Financial analyst or admin member navigates to the "Monthly
Revenue Management" section.
2. System loads the monthly revenue management interface, displaying
revenue data for the specified month.
Exceptions: None
Priority: Must Have
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
have access to the monthly revenue management section.
1.10 UC-11_Product Management

UC ID and Name: UC-11_Product Management
Trigger:Staff accesses the product management section.
Description:As an staff member, I want to load and view the product management interface
to add, edit, or remove products from the system.
Postconditions: Product management interface is successfully loaded.
Normal Flow 11.0 Load Product Management Interface
1. Staff member navigates to the "Product Management" section.
2. System loads the product management interface, displaying a list of
products, their details contain ProductID, Image, Price, Total Quantity,
Category, Description, 2 “Update” and “Delete” button.
Exceptions: None
Priority: Must Have
Frequency of High
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
have access to the product management section.
1.11 UC-12_Add Product

UC ID and Name: UC-12_Add Product
Trigger:Staff initiates the process to add a new product.
Description:As an staff member, I want to add a new product to the system, providing all
necessary details for accurate representation and management.
Preconditions:  Admin or product manager member is logged into the system.
 The product to be added does not already exist in the system.
Postconditions: New product is successfully added to the system.
Normal Flow 12.0 Add Product Process
2. Staff selects the option to add a new product.
3. System presents a form for entering details such as product name,
image, size, description, price, and category.
4. Staff fills out the form with accurate details.
5. Staff submits the form.
7. If validation is successful, the system adds the new product to the
product list.
8. System confirms the successful addition of the new product.
Alternative Flows: 12.0.A1 Validation Failure:
1. The system detects errors or missing information in the entered details.
2. An error message is displayed, prompting the admin or product manager
to correct the issues.
3. Staff can choose to re-enter the information or cancel the process.
Exceptions: None
Priority: Must Have
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
BR6 Staff Access The system must ensure that only authenticated admin or product
manager members have access to the product management section.
1.12 UC-13_Update Product

UC ID and Name: UC-13_Update Product
Trigger:Staff initiates the process to update an existing product.
Description:As an staff member, I want to update the details of an existing product in the
system, ensuring that the information remains accurate and up-to-date.
 The product to be updated already exists in the system.
Postconditions: Product details are successfully updated in the system.
Normal Flow 13.0 Update Product Process
2. Staff selects the option to update an existing product.
3. System presents a form populated with the current details of the
selected product.
4. Staff modifies the desired fields with accurate information.
5. Staff submits the updated information.
7. If validation is successful, the system updates the product details.
8. System confirms the successful update of the product.
Exceptions: None
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
BR6 Staff Access The system must ensure that only authenticated staff members have
access to the product management section.
1.13 UC-14_Update Product

UC ID and Name: UC-14_Update Product
Trigger:Staff initiates the process to update an existing product.
Description:As an staff member, I want to update the details of an existing product in the
system, ensuring that the information remains accurate and up-to-date.
 The product to be updated already exists in the system.
Postconditions: Product details are successfully updated in the system.
Normal Flow 14.0 Update Product Process
10. Staff selects the option to update an existing product.
11. System presents a form populated with the current details of the
selected product.
15. If validation is successful, the system updates the product details.
16. System confirms the successful update of the product.
Exceptions: None
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
access to the product management section.
1.14 UC-15_Customer Management
UC ID and Name: UC-15_Customer Management
Trigger: Staff initiates the process to manage customer information.
Description: As a staff member, I want to manage customer information in the system to
ensure accurate and up-to-date records.
Preconditions: Admin or customer service staff member is logged into the system.
Postconditions: Customer information is successfully managed in the system.
Normal Flow 15.0 Customer Management Process
1. Staff member navigates to the "Customer Management" section.
2. Staff selects the option to manage customer information.
3. System presents a list of existing customers.
4. Staff selects a specific customer from the list to view/edit their details.
5. System displays the current information of the selected customer.
9. If validation is successful, the system updates the customer details.
10. System confirms the successful update of the customer information.
2. An error message is displayed, prompting the staff to correct the issues.
Exceptions: None
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
access to the customer management section.
1.15 UC-16_Staff Management
UC ID and Name: UC-16_Staff Management
Primary Actor: Admin Secondary Actors: None
Trigger: Admin initiates the process to manage staff information.
Description: As an admin, I want to manage staff information in the system to ensure accurate
and up-to-date records.
Preconditions: Admin is logged into the system.
Postconditions: Staff information is successfully managed in the system.
Normal Flow 16.0 Staff Management Process
1. Admin navigates to the "Staff Management" section.
2. Admin selects the option to manage staff information.
3. System presents a list of existing staff members.
4. Admin selects a specific staff member from the list to view/edit their
details.
5. System displays the current information of the selected staff member.
6. Admin modifies the desired fields with accurate information.
7. Admin submits the updated information.
9. If validation is successful, the system updates the staff details.
10. System confirms the successful update of the staff information.
2. An error message is displayed, prompting the admin to correct the
issues.
3. Admin can choose to re-enter the information or cancel the process.
Exceptions: None
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
BR6 Staff Access The system must ensure that only authenticated admin members have
access to the staff management section.
1.16 UC-17_Add New Staff
UC ID and Name: UC-17_Add New Staff
Trigger: Admin initiates the process to add a new staff member.
Description: As an admin, I want to add a new staff member to the system to maintain a
comprehensive list of staff.
Postconditions: A new staff member is successfully added to the system.
Normal Flow 17.0 Add New Staff Process
2. Admin selects the option to add a new staff member.
3. System presents a form for entering the details of the new staff member.
4. Admin fills in the required information for the new staff member.
5. Admin submits the entered information.
7. If validation is successful, the system adds the new staff member to the
database.
8. System confirms the successful addition of the new staff member.
issues.
Exceptions: None
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
1.17 UC-18_Update Staff Information
UC ID and Name: UC-18_Update Staff Information
Trigger: Admin initiates the process to update staff information.
Description: As an admin, I want to update existing staff information in the system to keep
records accurate and current.
Postconditions: Staff information is successfully updated in the system.
Normal Flow 18.0 Update Staff Information Process
2. Admin selects the option to update staff information.
3. System presents a list of existing staff members.
4. Admin selects a specific staff member from the list to view/edit their
details.
5. System displays the current information of the selected staff member.
6. Admin modifies the desired fields with accurate information.
7. Admin submits the updated information.
9. If validation is successful, the system updates the staff details.
10. System confirms the successful update of the staff information.
issues.
Exceptions: None
Use:
Business Rules: BR6
Other
Information:
Assumptions:
b. Business Rules
III. Design Specifications
1. Home Page
1.1 Home Page
a. Banner
Description: The banner displays large and impressive images, attracting customers' attention as soon as
they visit the website.
Related use cases:
Customers view the banner and click on the CTA button to explore the product or promotion.
UI Design
<<Mockup prototype>>
Field Name Field Type Description
Banner image Image Large, high-quality images that reflect brand's style
Banner title Text box Short, concise, attention-grabbing
CTA button Button Call to action, e.g. "Buy Now", "Discover"
Database Access
Table CRUD Description
<<Table Name>> <<transaction(s)>> <<Table access description: purpose, how,…>>
..
SQL Commands
 Get list of banners:
SELECT * FROM banners;
 Add new banner:
INSERT INTO banners (image, title, cta_text, cta_link)
VALUES (?, ?, ?, ?);
 Update banner information:
UPDATE banners
SET image = ?,
title = ?,
cta_text = ?,
cta_link = ?
WHERE id = ?;
 Delete banners:
DELETE FROM banners
WHERE id = ?;
b. Product list
Description: This section displays a list of main product categories, helping customers easily find
products according to their needs.
Related use cases:
Customers click on the category to view related products.
Customers click on the product to see product details.
UI Design
Category Text box List of product categories (can use dropdown if quantity is
large)
Product images Image Attractive product images
Product's name Text box Full product name
Price Text box Product selling price
CTA button Button Call to action, e.g. "See Details"
Database Access
..
SQL Commands
 Get the category list:
SELECT * FROM categories;
 Add new category:
INSERT INTO categories (name, description, image)
VALUES (?, ?, ?);
 Update category information:
UPDATE categories
SET name = ?,
description = ?,
image = ?
WHERE id = ?;
 Delete category:
DELETE FROM categories
WHERE id = ?;
 Get product list:
SELECT * FROM products;
 Add new products:
INSERT INTO products (name, description, price, image, category_id, quantity)
VALUES (?, ?, ?, ?, ?, ?);
 Update product information:
UPDATE products
SET name = ?,
description = ?,
price = ?,
image = ?,
category_id = ?,
quantity = ?
WHERE id = ?;
 Delete product:
DELETE FROM products
WHERE id = ?;
c. Introduction to the brand

Description: The banner displays large and impressive images, attracting customers' attention as soon as
they visit the website.
Related use cases:
Customers view the banner and click on the CTA button to explore the product or promotion.
UI Design
Introduce Text box Brief introduction of the brand
Highlights Text box List product highlights
Commit Text box Commitment to quality and service
Database Access
..
SQL Commands
 Get information about the brand:
SELECT * FROM about;
d. News & Promotions

Description: This section displays articles about fashion trends, styling tips, as well as ongoing
promotions and discounts.
Related use cases:
Customers read articles to update trends and find suitable products.
Customers click on promotions to see details and purchase.
UI Design
Field Name FieldType Description
Article title Text box Attractive article title
Summary of the Text box Summary of article content
article
Article image Image Illustration image for the article
Promotion title Text box Promotion title
Promotional
content Text box Detailed description of the promotion program
Database Access
..
SQL Commands
 Get list of posts:
SELECT * FROM news;
 Add new article:
INSERT INTO news (title, summary, content, image, author)
VALUES (?, ?, ?, ?, ?);
 Update article information:
UPDATE news
SET title = ?,
summary = ?,
content = ?,
image = ?,
author = ?
WHERE id = ?;
Delete posts:
DELETE FROM news
WHERE id = ?;
e. Footer
Description: This section contains contact information, policies, and links to the brand's social media
pages.
Related use cases:
Customers contact the brand through contact information.
Customers see return and warranty policies.
Customers follow brands on social networking sites.
UI Design
Contact Info Text box Address, email, phone number
Policy Hyperlink Link to return policy and warranty page
Social network Hyperlink Links to social networking sites
Database Access
..
SQL Commands
 Get contact information:
SELECT * FROM contact;
 Get policy information:
SELECT * FROM policy;
 Get social network information:
SELECT * FROM social;
1.2 System Access
a. User Login
This screen allows user to be authenticated to the system screens/functionalities.
Related use cases:
 UC02_Login System
UI Design

Email* Text Box This is for user to input valid email address for logging in
Password* Password Box This is for user to input password for logging in
Login Button User clicks to authenticate him/herself into the system with
provided email & password
Register Button User clicks to redirect to the User Register page for
registering new user account to access the system
Forgot Password? Hyperlink User clicks to redirect to the Password Reset page for
resetting his/her forgot password
Login with Google Hyperlink Allow user to login with his/her Google account
Login with Facebook Hyperlink Allow user to login with his/her Facebook account
Database Access
User R Verify UserName & Password information
Setting, User R Specify the authorizations of the logged-in user
SQL Commands:
1/ Verify UserName & Password information
SELECT user_id, full_name, email, image_url, status
FROM user WHERE user_name = ? AND password = ?
2/ Specify the authorizations of the logged-in user

SELECT mapped_values FROM setting WHERE setting_id = ?
SELECT setting_name, mapped_values FROM setting WHERE setting_id IN (?)
b. Setting List
UI Design

Search Fields
Setting Type Combo Box Filled with the list of current active setting types
Single-Choice Allow to filter the list by setting type;
Default value is “All Types”
Setting Status Combo Box Values: All Statuses (default), Active, and Inactive
Single-Choice Allow to filter the list by status
Default value: “All Statuses”
Search Phase Text Box Allow to search using the name or map values
String (30) Default value: blank
Search Button Click to refresh the list with the defined filter(s) and search
phrase.
Add New Hyperlink Click to open the Setting Details page for adding new setting
(master data)
Data Table
ID Integer Auto-increased identifier of the setting
Name Text Name of the setting
Mapped Values Text Supplementary information for the setting
Type Text Type of the setting
Order Integer Display order of the setting: the order of the setting type,
displayed among the list of settings with the same type
Data Actions
Edit icon Click to open the Setting Details page for updating the
relevant setting (master data)
Activate icon Shown when the data status is inactive. This is to activate the
Deactivate Ion Shown when the data status is active. This is to deactivate the
Database Access
Setting RU Query the list of current settings from the database
Update status of a specific setting
SQL Commands:
1/ Query the list of current settings from the database
SELECT setting_id, setting_name, mapped_values, type_id, display_order, status
FROM setting WHERE (setting_type = ?) AND (status = ?) AND (setting_name LIKE ?)
2/ Update status of a specific setting

UPDATE setting SET status = ? WHERE setting_id = ?
c. Setting Details
UI Design

Name* Text Box Name of the setting
String (20)
Type* Combo Box Type of the setting, filled with the list of setting types
(Single Choice) Default value: the first type in the list
Mapped Values Text Box Supplementary information for the setting (if any)
String (50)
Order Text Box Display order of the setting: the order of the setting type,
Integer (>=0) displayed among the list of settings with the same type
Status On/Off button Status of the setting: Active or Inactive
Default value: Active
Description Text Area Description of the setting
String (200)
Submit Button Click to store new or updated setting details
Reset Button Click to reset the changes use has made on the screen fields
back to the initial values when the screen is loaded
IV. 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.
>>
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]
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
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. ..

Template2 SRS GR4

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Template2 SRS GR4

Uploaded by

Copyright:

Available Formats

G4-STORE

Software Requirement Specification

Figure 2.1: Screen Flow for user

Figure 2.3: Screen Flow for staff

II. Requirement Specifications

1.2 UC-3_Forget Password

Postconditions:  User's request to reset the password is successfully processed.

1.3 UC-4_Register User Account

1.4 UC-5_User Profile

1.5 UC-6_Edit Profile

1.6 UC-7_Change Password

1.7 UC-8_Cart Management

1.8 UC-9_Load Order Management

1.9 UC-10_Monthly Revenue Management

1.10 UC-11_Product Management

1.11 UC-12_Add Product

1.12 UC-13_Update Product

1.13 UC-14_Update Product

c. Introduction to the brand

d. News & Promotions

Field Name Field Type Description

2/ Specify the authorizations of the logged-in user

Field Name Field Type Description

2/ Update status of a specific setting

Field Name Field Type Description

2. Limitations & Exclusions

You might also like