Vous êtes sur la page 1sur 36

FPT ACADEMY INTERNATIONAL

FPT – APTECH COMPUTER


EDUCATION

Centre Name: ACE-HCMC-2-FPT.


Address: 590 Cach Mang Thang 8, District 3, Ho Chi Minh City, Viet Nam.

Game Store

Supervisor:
Semester:
Batch No:
Group No:
Order: Full name Roll No.
1.
3.
2. Nguyễn Ahn Seung Student981907
Man
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.1/36

Month: 4 Year: 2019

Menu:
REVIEW 1 3
I. 3
II. Error! Bookmark not defined.
1. Error! Bookmark not defined.
2 Error! Bookmark not defined.
III. 7
1. 7
2. Sofware requiments 10
Task Sheet Review 1 11
REVIEW 2 12
I. Error! Bookmark not defined.
1. Error! Bookmark not defined.
2. Error! Bookmark not defined.
3. Error! Bookmark not defined.
II. Error! Bookmark not defined.
1. Error! Bookmark not defined.
2. Error! Bookmark not defined.
Task Sheet Review 2 21
REVIEW 3 22
A. Error! Bookmark not defined.
1. Error! Bookmark not defined.
2. Error! Bookmark not defined.
3. Error! Bookmark not defined.
4. Error! Bookmark not defined.
A. Error! Bookmark not defined.
1. Error! Bookmark not defined.
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.2/36

2. Error! Bookmark not defined.


3. Error! Bookmark not defined.
4. Error! Bookmark not defined.
5. 11
6. Error! Bookmark not defined.
Task Sheet Review 3 33

REVIEW 1
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.3/36

I. Problem definition:
1 Set the prolem
- Due to the current technological advances, more and more hightech game
are emerging and the need to buy and learn about the game of everyone
also increase. As a result, Game Shop was born to solve this problem.
- Game Shop is an online shopping application provided the newest game
for customers.Game Shop helps customers to view information and
purchase plenty of populars game anytime, anywhere with just a phone or
a laptop connected to the internet.

2 Determine customer requirements:


- Customers can view the list and information of products and manufacturers.
Customers can search for products easily with keywords.
- When registering to become a member of the website, members can edit
personal information registered with the web, send feedback on services on the
web. Members can order products directly on the web
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.4/36

II. Require Function:


❖ Login to the system
● Input
o email, password, role
● Output
o Show message of login status
o Logged in successfully
● Validation
o Email and password must be valid
o Email required
o Password required
❖ Change the password
● Input
o Old password and new password
● Output
o Show message success
● Validation
o New password and old password must equal
o New password required
❖ Search Product
● Input
○ game name , game price
● Output
○ game information
A . Admin
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.5/36

❖ See product
● Show
o All games information
❖ See customer
● Show
o All customer information

❖ Create, edit, delete Game


● Input
○ Game id, game name, game price, game description, game image, game
discount if it has, game category , game brand
● Validation:
○ Game id is not blank and must have format G + six numbers (example:
G000001)
○ Game name is not blank and length must larger than 5
○ Game price is a number and cannot lower than 0
○ Game description is not blank and length must larger than 5
○ Game image is a file must have format png, jpg and can’t null
○ Game discount can not larger than 50
○ Game category cannot be null
○ Game brand cannot be null
● Output:
○ Show message to confirm create, edit game successful
❖ Search Customer
● Input
○ customer name
● Output
○ customer information
B . Customer
❖ Registration
● Input
o First name, Last name, gender, address , email, password, phone, avatar
● Output
o Show message success
o Go to the home page
● Validation
o First name and last name can not be blank and length must larger than 5
characters
o Gender is required
o Address cannot be blank and length must larger than 5 characters
o Customer email cannot be blank and have a format abc@gmail.com
o Password is required
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.6/36

o Phone can not be blank and must have 10-12 digits


o Avatar is a file must have format png, jpg and can’t null
❖ See row
● Show
o All game information
❖ Search product
● Input
o Game name, brand name, price
● Output
o Show the selected item information
● Validation
o Already exhausted or not available
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.7/36

I. System requirements

1. Hardware requirements
- Pentium IV 1.4 Ghz or higher.
- Ram 512 MB or higher.
- HDD 200MB or higher.

2. Sofware requiments

Server:
- Window 7 or higher( Recommend).
- Glassfish Server 1.4.2
- SQL server 2014
- Netbeans 7.4
-
Client:
- Window XP or higher( Recommend).
- IE 9.0 or higher.

Range :
- Provide information about products and other services
- Allows users to feedback
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.8/36

Task Sheet Review 1

Members Group Date Preparation Of Activity Plan

No Name Description Start Date End Date Status


Task

1 Nguyễn Ahn Set the problem, 12/04/2019 12/04/2019 Completed


Seung Man determine
customer
requirements

2 Lưu Trung Tú Require 12/04/2019 12/04/2019 Completed


Function

3 Lâm Thiện Quang System 12/04/2019 12/04/2019 Completed


Requirements

Teacher Team Leader

Lưu Trung Tú
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.9/36

REVIEW 2
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.10/36

DFD

Level 0
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.11/36

Level 1

Products Management
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.12/36

Login
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.13/36

Use case and Sequence Diagram

1.User
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.14/36

Register Customer

Author Luu Trung Tu

Use Case Register


Name
Actor Guest

Description Guest registers an account on the website and becomes


a member (customer)

Post- Success: Guest creates a Customer account in this


Condition website
Fail : Refill Information

Pre-Condition N/A

Actors Action : System’s responses:

1. Actor clicks ‘Register’ 2. System redirects to


Basic flows link on Home Page. Register page and
displays Registration
form with the following
controls:
- ‘First Name’ text field
- ‘Last Name’ text field
3. Actor inputs register’s - ‘Email’ text field
information and click - ‘Address’ text field
‘Register’ button. -‘Gender’ select
-‘Phone’ text field
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.15/36

-‘avatar’ Link
- ‘Register’ button

4. System validates the


information.
5. System inserts the
account into database
6. System show success
message.

Exception Actor’s actions: System’s responses:

- Actor left ‘Phone’ text System displays message


field blank. to actor:
- Input phone is not - ‘Name cannot be blank’.
numeric format or phone - ‘Phone is invalid’.
length is not between 8 - ‘The phone number
and 14 characters. should be numeric only
- Actor left ‘Email’ text and must be between 8
field blank or input an and 14 digits’.
invalid email address. - ‘Email is invalid’.
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.16/36

Login as Customer

Author Luu Trung Tu

Use Case Login


Name
Actor Customer

Description Customer login into website with registered account

Post- Success: Guest creates a Customer account in this


Condition website
Fail : Refill Information

Pre-Condition Customer must register an account


Customer had provide email and password

Actors Action : System’s responses:


Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.17/36

1. Actor clicks ‘Login’ 2. System redirects to


button Login Page with the
Basic flows
following controls
- Email text field
- 'Password' text field
- 'Login' button

3. Actor inputs Email and


Password, then click the 4. System checks the
‘Login’ button. information.
5. System redirects to
User’s dashboard.

6. System show success


message.

Exception Actor’s actions: System’s responses:

1. Actor inputs invalid System redirects to Login


Email and password page with the following
controls:
- ‘Email text field
- ‘Password’ text field
- ‘Login’ button.
System shows message:
“Invalid Username and
password”.
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.18/36
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.19/36
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.20/36

1.3 Forgot Password


Author Luu Trung Tu
Use Case Change Password
Name
Actors Customer
Description Customer can change the password
Pre- Actor must be logged on
conditions
Success: Actor can change their password
Post- Fail: Refill information
conditions
Actor’s actions: System’s responses:
1. Actor clicks on ‘Forgot 2. System redirects to
Password’ button. Password Page with the
following controls:
- 'Email' text field
3. Actor inputs Email and - 'Submit' button
clicks ‘Submit’. 4. System checks the
informaedirects to
Passwortion and sends a reset
5. Actor inputs reset token in
token to user.
Basic flow Password Page and click
6. System rd form with the
‘Submit’.
following controls:
- ‘New Password’ text field
- ‘Confirm Password’ text field
- ‘Save’ button
8. System
validates password
7. Actor inputs new
password and click then updates password in
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.21/36

‘Save’. database.
9. Systemshows message:
‘Your password has been
changed successfully’.

Actor’s actions: System’s responses:


1. Actor inputs an email System shows messages:
Exceptions which does not exist in - ‘Invalid email’.
database.
- ‘Invalid code’.
2. Actorinputs code
incorrectly.
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.22/36
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.23/36

Product

2.1 Search Product


Author Luu Trung Tu
Use Case
Search products by name
Name
Actors Guest/Customer
Description Guest/Customer wants to search for products by name
Pre-
N/A
conditions
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.24/36

Post- Success: Show products that matches search keywords


conditions Fail: No product is shown
Actor’s actions: System’s responses:
1. Actor inputs search 2. System show list of products
product. that match the search product.

3. Actor clicks product’s


name in list or view every 4. The system allows to search
product that matches search for products by Category and
Basic flow product. Brands
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.25/36

Filter Product

Author
Product Filter
Use Case
Name
Guest/Customer
Actors
Guest/Customer wants to filter products by one
Description or multiple Price
N/A
Pre-
conditions
Success: Products that matches Price are shown
Post- Fail: No product is shown
conditions
Actor’s actions: System’s responses:
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.26/36

1. Actor input price want to


search
2. System show products
that satisfy the
Basic flow
condition(s)
3. System allows actor to
sort products by:
- Lowest Price
- Highest Price
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.27/36

3. Admin

Category

Chapter 2
Author Luu Trung Tu
Use case Add categories
name
Actors Admin
Description When admin wants to add a new category in the database
Requireme Actor provides category’s information
nts
Pre- Actor is logged in as admin
conditions
Success: category is added in the database
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.28/36

Post- Fail: refill information


conditions
Actor’s actions: System’s responses:
1. Actor click Category Tab on 2. System redirects to
menu. 'Category List' page and
Basic flow display a list of existing
categories.
3. Actor clicks ‘Create new
Category’. 4. System displays a form with
the following fields.
- Category’s Name
- Button ‘Choose image’
5. Actor inputs
information to create 6. System validates inputs.
category.
7. Systemcreate category into
database.
8. System
displays
confirmation message or
error message.
Actor’s actions: System’s responses:
1. Actor left ‘Category’s Name’ System displays messages:

Exceptions field blank. - ‘Category’s Name cannot be


blank’.
2. Category’s Name existed in
- ‘Category’s Name must be
database.
unique’.

Disable Category
Author Luu Trung tu
Use case Disable category
name
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.29/36

Actors Admin
Description When a admin wants to Disable a category
Requireme
nts
Pre- Actor is logged in as admin
conditions
Success: category is Disable
Post- Fail: category is not disable
conditions
Actor’s actions: System’s responses:
1. Actor chooses Category Tab 2. System redirects to
on menu. 'Category List' page and
Basic flow display a list of existing
categories.
3. Actor clicks on ‘Disable’
4. System Disable category.
button and confirm.

Report
4.1 View Product Report
Author Luu Trung Tu
Use case View Product Report
name
Actors Admin
Description When admin wants to view report on products
Requireme N/A
nts
Pre- Actor is logged in as admin
conditions
Post- Success: Display a report on products
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.30/36

conditions
Actor’s actions: System’s responses
Basic flow 1. Actor chooses 2. System redirects to ‘Product Report’
‘Product Report’ page.
in menu.
4.2 View Customer Report
Author Luu Trung Tu
Use case View Customer Report
name
Actors Admin
Description When admin wants to view report on customers
Requireme N/A
nts
Pre- Actor is logged in as admin
conditions
Post- Success: Display a report on customers
conditions
Actor’s actions: System’s responses
Basic flow 1. Actor chooses 2. System redirects to ‘Customer Report’
‘Customer Report’ page.
in menu.
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.31/36

ERD

Tables Definition
1. Admins

Table Admins
No. Column Name Date Type Constraint Description
1 AdminID Varchar(10) Not Null ID of Admin
Primary
key
2 Email Varchar(100) Not null Email of Admin
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.32/36

3 [Password] Varchar(30) Not null Password of Admin


4 FullName Nvarchar(30) Not null FullName of Admin
5 Avatar Varchar(200) Not null Avatar Of Admin
6 CreatedDate Date Default Stores
Date
7 IsStatus Bit Default(1) The Status of Admin

2 Customer

Table Customer
No. Column Name Date Type Constraint Description
1 cusId Varchar(10) Not null ID of Customer
Primary
key
2 cusFirstName Varchar(200) Not null First Name of Customer
3 cusLastName Varchar(200) Not null Last Name of Customer
4 cusGender Bit Default(1) Gender of Customer
5 cusAddress Varchar(200) Not null Address of Customer
6 cusEmail varchar(200) Default(1) Email of Customer
7 cusPass Varchar(200) not null Pass of Customer
8 cusPhone Nvarchar(max) not null Phong of Customer
9 Avatar Varchar(200) Not null Avatar of Customer
10 CreateDate Date Default The date at create
Date
11 IsStatus Bit Default(1) The Status of Customer
1.3 Products

Table Products
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.33/36

No. Column Name Date Type


Constraint Description
1 productId Varchar(10)
Not null Id of Products
Primary
key
2 productName Nvarchar(100) Not null Name of Products
3 productPrice Int Not null Price of product
4 productDescriptio Int Not null Descriptions
n
5 productImage Varchar(max) Not null Image of Product
Foreign
Key
6 productStatus Bit Default(1) Status of Product
7 productDiscount int Default Discount of Product
(0)
8 cate_id int Not null Category of Product
Foreign
Key
9 brand_id int Not null Brands of Product
Foreign
Key
Orders

Table Order
No. Column Name Date Type Constraint Description
1 orderId Varchar(10) Not null Id of Order
Primary
key
2 totalPrice int Not null Total Price of Order
3 OrderDate date Not null Date of Order
4 ProcessStatus varchar(50) Not null Process of Order
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.34/36

5 OrderStatus bit default(1) Status of Order


6 cus_id varchar(10) Not null Id of Customer Order
Foreign
Key

1.5 Orders Details

Table Orders Details


No. Column Name Date Type Constraint Description
1 OdID Int Not null ID of Order Details
Identity(1,1) Primary
key
2 OrderID Varchar(10) Not null ID of Orders
Foreign
Key
3 ProductID Varchar(10) Not null ID of product
Foreign
Key
4 SellingPrice Int Not null Selling price of product
5 Quantity Int Not null Quantity of product
6 IsStatus bit Default(1) IsStatus of Order Details
1.6 Ratings

Table Ratings
No. Column Date Type Constraint Description
Name
1 RatingID Int Not null ID of Rating
Identity(1,1) Primary key
Design Plan: BBS Document Name: Problem Definition Document SWD/Form No. 1
Effective Date:20-2-2019 Version: 1 Page no.35/36

2 ProductID Varchar(10) Not null ID of Products


Foreign Key
3 CustomerID Varchar(10) Not null Id of Customer
Foreign Key
4 Rate Int Not null Rating of product
5 Content Nvarchar(max) Null Content of Rating
6 RatingDate Date Default(date) Date of rating
Categories

Table Categories
No. Column Name Date Type Constraint Description
1 cate_id int identity Id of category
Primary
key
2 cate_name Nvarchar(200) Not null Name of category
3 IsStatus Bit default IsStatus of category
Brands

Table Brands
No. Column Name Date Type Constraint Description
1 brandId Varchar(10) Not nul Id of brand
Primary
key
2 brandName Nvarchar(200) Not null Name of brand
3 brandImage Nvarchar(max) Null Image of brand
4 IsStatus Bit Default(1) IsStatus of Brand