SOFTWARE REQUIREMENT

SPECIFICATION
FOR

SHOP
MANAGEMENT
Instructor: Phạm Ngọc Hà
Class: SE1218
Group: 6
Member: Nguyễn Ngọc Phước – SE05665
Nguyễn Quang Huy – SE06034
Đỗ Văn Công – SE06058
Software Requirement Specification – Shop Management 2

CONTENTS
1 Introduction ............................................................................................................................. 3
2 Scope ....................................................................................................................................... 3
3 Overall description .................................................................................................................. 3
4 Specific requirement ............................................................................................................... 3
4.1 Functional requirement ................................................................................................... 3
4.1.1 Use case diagram .................................................................................................... 3
Admin usecase .................................................................................................................... 5
Seller Use Case ................................................................................................................... 9
Buyer use case................................................................................................................... 13
4.2 Non-functional requirement .......................................................................................... 22
4.2.1 Usability ................................................................................................................ 22
4.2.2 Performance .......................................................................................................... 22
4.2.3 Modifiability ......................................................................................................... 23
4.3 Design constraints ......................................................................................................... 23
4.4 Assumption and dependencies ...................................................................................... 23
4.5 Interfaces ....................................................................................................................... 23
4.5.1 User interfaces ...................................................................................................... 23
4.5.2 Hardware interfaces .............................................................................................. 23
4.5.3 Software interfaces................................................................................................ 23
4.5.4 Communication interfaces .................................................................................... 23
5 Entity relationship diagram ................................................................................................... 23
Software Requirement Specification – Shop Management 3

1 INTRODUCTION
The SRSFSM document will provide developers, testers a complete overview of both the
functional requirement and non-functional requirements of the Shop Management system.
Developers base on this document to develop the system, and tester base on this to assure the
quality of the output system. Project manager base on this document to create schedule and
assign task to team members.

2 SCOPE
The project team will create an e-commerce site that connects buyers and sellers. Buyers will get
an overview of the product they want to make a decision to buy. Sellers can bring their products
to consumers more quickly and conveniently.

3 OVERALL DESCRIPTION
The system includes information of all products from thousands of sellers around the world, a
place for consumers to compare prices and reviews from different vendors for the same product
to may have the best decision. We have two customers:

- Seller

- Buyer

4 SPECIFIC REQUIREMENT
4.1 FUNCTIONAL REQUIREMENT

4.1.1 USE CASE DIAGRAM

Software Requirement Specification – Shop Management 4

Figure 1 - Usecase Overview

Software Requirement Specification – Shop Management 5

ADMIN USECASE

Figure 2 - Admin usecase

USE CASE SPECIFICATION

UC 01: Login

Admin Login UC-01

Pre/event Admin is in the Admin Login page
Post/description Admin logged into Shop Management System
System Shop Management
Actors Admin
Related use case None
Normal flow
Actor’s event System response
1. Enter username and password and click
“Login” button
2. Redirects actor to Admin Homepage
Exceptions
At step 1, actor don’t enter username and password
1. Don’t enter any information but still
click “Login” button
Software Requirement Specification – Shop Management 6

2. Display error message “Please fill all of

field”
At step 1, actor enter wrong username or password
1. Enter wrong username or password
2. Display error message “Wrong username
or password. Try again!”
Alternative flow
Actor chooses to log in with Facebook account
1. Click on the “Login with Facebook”
button
2. Redirects actor to “Sign in with
Facebook” page
3. Choose Facebook account belong to actor
4. Redirects actor to Admin Homepage
Actor chooses to log in with Google account
1. Click on the “Login with Gmail” button
2. Redirects actor to “Sign in with Google”
page
3. Choose Google account belong to actor
4. Redirects actor to Admin Homepage

UC 02: Add Seller

Add Seller UC-02

Pre/event Admin is in the Admin Homepage
Post/description Admin logged into Shop Management System
System Shop Management
Actors Admin
Related use case None
Normal flow
Actor’s event System response
1. Click on the “Add an account” button
2. Forward actor to Add Seller page
3. Enter seller’s username and choose rank
then click “Add” button
4. Add the new seller to the database
Exceptions
At step 3, actor enters a exist username
1. Enter a seller’s username which existed
in the database and click “Add” button
2. Display error message “This username is
existed. Please try again with another
username”
At step 3, actor don’t enter user name
1. Don’t enter username and click “Add”
button
2. Display error message “Please enter the
username”
Software Requirement Specification – Shop Management 7

Alternative flow

UC 03: Delete Seller

Delete seller UC-03

Pre/event Admin is in the Admin Homepage
Post/description The seller is deleted from database
System Shop Management
Actors Admin
Related use case None
Normal flow
Actor’s event System response
1. Click a staff in the staff list table whose
status is deactived
2. Forward actor to the Update Seller page
3. Click “Delete” button
4. The seller is deleted from database
Exceptions
At step 3, the seller’s status is still active
1. Click a seller in the seller list table

2. Forwards actor to the Update Seller page

3. Click “Delete” button
4. Display error message “Please deactived
the seller before delete it”
Alternative flow

UC 04: View seller list:

List seller UC-04

Pre/event Admin is in the Admin Homepage
Post/description Display list of seller accounts
System Shop Management
Actors Admin
Related use case None
Normal flow
Actor’s event System response
1. Click on “Seller List” button
2. Display list of seller accounts
Exceptions
Alternative flow
Software Requirement Specification – Shop Management 8

UC 05: Search seller:

Search seller UC-05

Pre/event Admin is in the Admin Homepage
Post/description The search result is displayed
System Shop Management
Actors Admin
Related use case None
Normal flow
Actor’s event System response
1. Click on the search bar at the top right
corner of the seller list table and enter the
keyword
2. The search results contain the keyword is
displayed
Exceptions
Alternative flow

UC 06: Change admin account password

Edit seller UC-06

Pre/event Admin is in the Admin Homepage
Post/description The admin password is changed
System Shop Management
Actors Admin
Related use case None
Normal flow
Actor’s event System response
1. Click on the “Change Password” link
2. Forwards actor to the “Change
Password” page
3. Enter the old password and the new
password and click “Change” button
4. The password is changed
Exceptions
At step 3, don’t enter anything
1. Don’t enter password into text field and
click ”Change” button
2. Displays error message
At step 3, enter the new password the same as the old one
1. Enter the same password in the text field
2. Displays error message
Software Requirement Specification – Shop Management 9

Alternative flow

SELLER USE CASE

Figure 3 – Seller use case

USE CASE SPECIFICATION

Software Requirement Specification – Shop Management 10

UC07: Seller Login

Seller Login UC-07

Pre/event Seller is in the Seller login page
Post/description Seller logged into Seller management page
System Shopping management
Actors Seller
Related use case None
Normal flow
Actor’s event System response
5. Click on the “Login” button
6. Forward seller to Seller management page
Exceptions
At step 1, actor doesn’t enter username and password
3. Don’t enter information but still clicks
“Login” button
4. Display error message
At step 1, actor enter wrong username or password
3. Enter wrong username or password
4. Display error message
Alternative flow
Actor chooses to log in with Gmail account
1. Click on the “Sign In with Gmail” button
2. Redirects actor to “Sign in with Google”
page
2. Choose Gmail account belong to actor
3. Redirects actor to Seller management page

UC08: Post a product

Post a product UC-08

Pre/event Seller is in the Seller add products page
Post/description Seller add a new product
System Shopping management
Actors Seller
Related use case None
Normal flow
Actor’s event System response
1. Click on the “Add” button
2. Forward seller to Seller management page
Exceptions
At step 1, actor doesn’t enter necessary information of product
1. Don’t enter information but still clicks
“Add” button
2. Display error message
Alternative flow
Software Requirement Specification – Shop Management 11

UC09: View all products

View all product UC-09

Pre/event Seller is in the Seller management page
Post/description Seller view all products
System Shopping management
Actors Seller
Related use case None
Normal flow
Actor’s event System response
1. Click on the “View all” button
2. Forward seller to All products page
Exceptions

Alternative flow

UC10: Confirm Order

Confirm Order UC-10

Pre/event Seller is in the Order management page
Post/description Seller confirm order
System Shopping management
Actors Seller
Related use case None
Normal flow
Actor’s event System response
At step 1, seller click on the “Confirm” button
1. Click on the “Confirm” button
2. Forward seller to Order management page
At step 1, seller click on the “Denied” button
1. Click on the “Denied” button
2. Forward seller to Order management page
Exceptions
Software Requirement Specification – Shop Management 12

Alternative flow

UC11: Seller Logout

Seller Logout UC-11

Pre/event Seller is in the Home page
Post/description Logout
System Shopping management
Actors Seller
Related use case None
Normal flow
Actor’s event System response
1. Click on the “Account” button
2. Show all options of “Account” menu
3. Click on the “Logout” button
4. Logout successfully
Exceptions

Alternative flow
Software Requirement Specification – Shop Management 13

BUYER USE CASE

Figure 4 – Buyer use case

Software Requirement Specification – Shop Management 14

USE CASE SPECIFICATION

UC12: Login with Gmail

Log in UC-12
Pre/event User is in the home page
Post/description User Log in Shop management
System Shop management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Enter phone or email and password and
click “Login” button
2. Redirects actor to Homepage
Exceptions
At step 1, actor don’t enter username and password
1. Don’t enter information but still clicks
“Login” button
2. Display error message
At step 1, actor enter wrong username or password
1. Enter wrong phone or email or password
2. Display error message
Alternative flow
Actor chooses to log in with Gmail account ( Facebook similar)
1. Click on the “Login with Gmail” button
2. Redirects actor to “Sign in with google”
page
3. Choose Gmail account belong to actor
4. Redirects actor to Homepage

UC13: Login with Facebook

Log in UC-13
Pre/event User is in the home page
Post/description User Log in Shop management
System Shop management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Enter phone or email and password and
click “Login” button
2. Redirects actor to Homepage
Exceptions
At step 1, actor don’t enter username and password
Software Requirement Specification – Shop Management 15

1. Don’t enter information but still clicks

“Login” button
2. Display error message
At step 1, actor enter wrong username or password
1. Enter wrong phone or email or
password
2. Display error message
Alternative flow
Actor chooses to log in with Facebook account ( Facebook similar)
1. Click on the “Login with Facebook”
button
2. Redirects actor to “Sign in with Facebook”
page
3. Choose Facebook account belong to
actor
4. Redirects actor to Homepage

UC14: Logout

Log out UC-14

Pre/event User is in home page
Post/description User log out in homepage
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click “Username of account Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
”span link in menu 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.5" +
Indent at: 0.75", Tab stops: Not at 0.5"
2. Forward actor to menu of this span link
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
3. Click “Logout” text link in menu 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.5" +
4. Forward actor to home page Indent at: 0.75", Tab stops: Not at 0.5"
Exceptions Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
Alternative flow 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.5" +
Indent at: 0.75", Tab stops: Not at 0.5"
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
3, … + Start at: 1 + Alignment: Left + Aligned at: 0.5" +
Indent at: 0.75", Tab stops: Not at 0.5"

UC15. Show product list by category

Show product list of a category UC-15

Pre/event User is in home page
Post/description User show product list in homepage
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
Software Requirement Specification – Shop Management 16

1. Click “Any category ”span link in Formatted: Indent: Left: 0.22", Hanging: 0.2", Numbered +
menu Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 +
Alignment: Left + Aligned at: 0.5" + Indent at: 0.75", Tab
2. Forward actor to list product of this span link stops: Not at 0.5"
3. Click “Any product” text link in menu Formatted: Indent: Left: 0.23", Numbered + Level: 1 +
4. Forward actor to category page Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
Exceptions
Formatted: Indent: Left: 0.22", Hanging: 0.2", Numbered +
Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 +
Alternative flow Alignment: Left + Aligned at: 0.5" + Indent at: 0.75", Tab
stops: Not at 0.5"
Formatted: Indent: Left: 0.23", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"

UC16. Advanced Search

Advance search UC-15

Pre/event User is in category page
Post/description User use advance search in category page
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click ”Attitude” checkbox Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
2. Forward actor to category page Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 1" + Indent at: 1.25", Tab stops: Not at 0.5"
Exceptions
Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Alternative flow Aligned at: 1" + Indent at: 1.25", Tab stops: Not at 0.5"

UC17. Change the order of priority

Change the order of priority UC-2.2

Pre/event User is in category page
Post/description User change the order of priority in category page
System Shopping management
Actors User
Software Requirement Specification – Shop Management 17

Related use case None

Normal flow
Actor’s event System response
1. Click ”attitude” list box Formatted: Indent: Left: 0.16", Numbered + Level: 1 +
2. forward actor to category page Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 1" + Indent at: 1.25", Tab stops: Not at 0.5"
Exceptions
Formatted: Indent: Left: 0.16", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Alternative flow Aligned at: 1" + Indent at: 1.25", Tab stops: Not at 0.5"

UC18. Change the view

Change the view UC-18

Pre/event User is in category page
Post/description User change the view in category page
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click ”View” icon Formatted: Indent: Left: 0.16", Numbered + Level: 1 +
2. Forward actor to category page Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 1" + Indent at: 1.25", Tab stops: Not at 0.5"
Exceptions
Formatted: Indent: Left: 0.16", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Alternative flow Aligned at: 1" + Indent at: 1.25", Tab stops: Not at 0.5"

UC19. Add to cart

Add to cart UC-19

Pre/event User is in the information product page
Software Requirement Specification – Shop Management 18

Post/description User choose type of product, Choose quantity

System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1.1 + Choose the span card equal with type Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
product 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" +
+ Choose the unelectable card equal Indent at: 0.5", Tab stops: Not at 0.5"
with quantity
+ Click “Add to cart” button
2. Redirects actor to Card page
Exceptions
At step 1, actor click the type pro duct and quantity out of stock
1. actor click the type pro duct and quantity Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
out of stock. click “add to cart” button. 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.2" +
Indent at: 0.45", Tab stops: Not at 0.5"
2. Display error message
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
Alternative flow 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.2" +
Actor chooses to Indent at: 0.45", Tab stops: Not at 0.5"
1. Click “Add to Wishlist” Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
2. Icon wish list is turn on in the information Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.79" + Indent at: 1.04", Tab stops: Not at 0.5"
product page.
Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.79" + Indent at: 1.04", Tab stops: Not at 0.5"

UC20. Rating

Rating UC-20
Pre/event User is in the information product page
Post/description User choose rating in the information page
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click ”Number of Rating” span link Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
near icon 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" +
Indent at: 0.5", Tab stops: Not at 0.5"
2. Forward to the bottom of product page
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
Exceptions 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" +
Indent at: 0.5", Tab stops: Not at 0.5"
Alternative flow
Software Requirement Specification – Shop Management 19

UC21. Review

Review UC-21
Pre/event User is in the information product page
Post/description User watching review for product
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click “Number of Review” span link near
icon stars
2. Forward actor to the bottom of product
page
Exceptions

Alternative flow

UC22. Ask question

Ask question UC-22

Pre/event User is in the information product page
Post/description User ask question with seller
System Shopping management
Actors User
Related use case None
Normal flow Formatted: Indent: Left: 0.17", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Actor’s event System response Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
1. Enter question in “question” text area Formatted: Indent: Left: 0.23", Numbered + Level: 1 +
Click “Ask” button Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
2. Forward actor to the information product page Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
Exceptions Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
At step 1, actor don’t enter question Aligned at: 0.54" + Indent at: 0.79", Tab stops: Not at 0.5"
1. Don’t enter information but still
clicks “Ask” button Formatted: Indent: Left: 0.23", Numbered + Level: 1 +
2. Display error message Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.54" + Indent at: 0.79", Tab stops: Not at 0.5"
Alternative flow
Software Requirement Specification – Shop Management 20

UC23. Chat with seller

Chat with Seller UC-23

Pre/event User is in the information product page
Post/description User chat with seller
System Shopping management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click “Chat” span link on the right body page Formatted: Indent: Left: 0.17", Numbered + Level: 1 +
2. Display actor to the “Message” dialog Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
3. Enter “Message” text area and click “Send”
Formatted: Indent: Left: 0.18", Numbered + Level: 1 +
icon Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
4. Forward actor to the “Message” dialog Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
Exceptions Formatted: Indent: Left: 0.17", Numbered + Level: 1 +
At step 3, actor don’t enter message Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
1. Don’t enter information but still clicks
“Send” icon Formatted: Indent: Left: 0.2", Hanging: 0.23", Numbered +
Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 +
2. Display error message Alignment: Left + Aligned at: 0.5" + Indent at: 0.75", Tab
Alternative flow stops: Not at 0.5"
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" +
Indent at: 0.5", Tab stops: Not at 0.5"
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" +
Indent at: 0.5", Tab stops: Not at 0.5"

UC24. Buy a product

Buy a Product UC-24

Pre/event User is in the buy page
Post/description User bye a product
System Shopping management
Actors User
Related use case None
Normal flow Formatted: Indent: Left: 0.17", Numbered + Level: 1 +
Actor’s event System response Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
1. Enter “Discount” text Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
area + click ”Apply” Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
button
Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
2. Forward actor to the buy page
Formatted: Indent: Left: 0.17", Numbered + Level: 1 +
3. Click ”Pay” button Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
4. Redirect actor to pay page Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
Exceptions Formatted: Indent: Left: 0.26", Numbered + Level: 1 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
At step 1, actor don’t enter Discount Aligned at: 0.5" + Indent at: 0.75", Tab stops: Not at 0.5"
Software Requirement Specification – Shop Management 21

1. Don’t enter Formatted: Indent: Left: 0.17", Numbered + Level: 1 +

information but still Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left +
Aligned at: 0.25" + Indent at: 0.5", Tab stops: Not at 0.5"
clicks “Apply” button
2. Display error message Formatted: Numbered + Level: 1 + Numbering Style: 1, 2,
Alternative flow 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" +
Indent at: 0.5", Tab stops: Not at 0.5"

UC25. Change Password

Change User Password UC-25

Pre/event User is in the User page
Post/description The user password is changed
System Shop management
Actors User
Related use case None
Normal flow
Actor’s event System response
1. Click on the “Change Password” link
2. Forwards actor to the “Change Password”
page
3. Enter the old password and the new
password and click “Change” button
4. The password is changed
Exceptions
At step 3, don’t enter anything
1. Don’t enter password into text field and
click ”Đổi” button
2. Displays error message
At step 3, enter the new password the same as the old one
3. Enter the same password in the text field
4. Displays error message
Alternative flow

UC26. Edit Information

Edit user information UC-26

Pre/event User is in the User Homepage
Post/description The User’s info is changed
System Shop management
Actors user
Related use case None
Normal flow
Actor’s event System response
1. Click “user name” span link in the menu
2. Forward actor to the user page
Software Requirement Specification – Shop Management 22

3. Change staff’ account name or role and

click “Update” button
4. The User’s info is changed
Exceptions
At step 3, don’t enter account name
1. Don’t enter user account name and click
on “Update” button
2. Display error message
At step 3, enter account name which existed
1. Enter an account name which existed in
database
2. Display error message

UC27: Buyer Logout

Seller Logout UC-27

Pre/event Seller is in the Home page
Post/description Logout
System Shopping management
Actors Buyer
Related use case None
Normal flow
Actor’s event System response
1. Click on the “Account” button
2. Show all options of “Account” menu
3. Click on the “Logout” button
4. Logout successfully
Exceptions

Alternative flow

4.2 NON-FUNCTIONAL REQUIREMENT

4.2.1 USABILITY
The UI will be clear, simple, easy to use.

4.2.2 PERFORMANCE
1. The loading time of a page will be less than 2 seconds. It still largely depends on the Internet
connection strength and the computer’s speed.
1. The time it takes for the search engine to display results will be less than 2 seconds.
Software Requirement Specification – Shop Management 23

4.2.3 MODIFIABILITY
The code will be organized base on coding standard so that it can be easily modify and improve
in the future.

4.3 DESIGN CONSTRAINTS

 The system will be implemented in Window operating system (version 7,8,10)

 The system will only be implemented to support Vietnamese and English
 Default date format will be: DD/MM/YYYY (example: 16/02/2019)
 The product shall be based on web and has to be run from a web server

4.4 ASSUMPTION AND DEPENDENCIES

It is assumed that the users access the site through a desktop or laptop not a mobile phone device.

It is assumed that the users have at least basic computer skill and knowledge how to access a
website.

4.5 INTERFACES

4.5.1 USER INTERFACES

The Shop Management system website will be accessed through a web browser by the users
from their computer. The user interface for the software shall be compatible to any browser such
as Google Chrome, Safari or Firefox by which user can access to the system.

4.5.2 HARDWARE INTERFACES

Since the application must run over the internet, all the hardware shall require to connect
internet.

4.5.3 SOFTWARE INTERFACES

The Shop Management system authenticates users by using OAuth 2.0 to login with Facebook or
Gmail.

4.5.4 COMMUNICATION INTERFACES

The system shall use the HTTP protocol for communication over the internet.

5 ENTITY RELATIONSHIP DIAGRAM

Software Requirement Specification – Shop Management 24

ENTITY DETAIL

Product
ProductID varchar

ProductName nvarchar
CategoryID varchar
Software Requirement Specification – Shop Management 25

Price float
UnitPrice float
UnitInStock int
UnitOnOrder int
Image varchar
Discount float
SellerID varchar

Seller
SellerID varchar

SellerName nvarchar
CompanyName nvarchar
Address nvarchar
Email nvarchar
Phone varchar
Image varchar
RankID varchar

Seller_Account
SellerID varchar

Username varchar
Password varchar

Buyer
BuyerID varchar

BuyerName nvarchar
Sex bit
Software Requirement Specification – Shop Management 26

Birthday date
Address nvarchar
Email nvarchar
Phone varchar
Image varchar
RankID varchar

Buyer_Account
BuyerID varchar

Username varchar
Password varchar

Order
OrderID varchar

BuyerID varchar

OrderDate date
ShipCompanyID varchar
ShipDate date

OrderDetail
OrderID varchar

ProductID varchar
ProductName nvarchar
Quantity int
Software Requirement Specification – Shop Management 27

ShipCompany
ShipCompanyID varchar

ShipCompanyName nvarchar

Address nvarchar
Email nvarchar
Phone varchar

Category
CategoryID varchar

CategoryName nvarchar

Description nvarchar
Image varchar

Seller_Rank
RankID varchar

RankName nvarchar

Fee float

Buyer_Rank
RankID varchar

RankName nvarchar

Discount float

Review
Software Requirement Specification – Shop Management 28

ReviewID varchar

ProductID varchar

BuyerID varchar

Time date
Rating int
Content nvarchar

Question
QuestionID varchar

ProductID varchar

BuyerID varchar

BuyerID varchar

Time date
Content nvarchar