Unit Number and Title 4: Database Design and Development

Academic Year 2018

Unit Tutor Lưu Văn Trung Hiếu
Assignment Title Assignment 2
Issue Date
Submission Date
 Table Of Contents
Table Of Contents ......................................................................................................................................... 2
I. Contexts: .................................................................................................................................................... 3
II. Problem:.................................................................................................................................................... 3
III. Criteria: .................................................................................................................................................... 4
1.Database: ............................................................................................................................................... 4
2.Function: ................................................................................................................................................ 4
3.Security: ................................................................................................................................................. 4
IV. Diagram Flow: .......................................................................................................................................... 4
V. Mock up: ................................................................................................................................................... 5
VI. Database Design: ..................................................................................................................................... 8
1. Database normalization: ....................................................................................................................... 8
2.ER Diagram:.......................................................................................................................................... 10
3.Create Table: ........................................................................................................................................ 11
4.Test Case: ............................................................................................................................................. 15
VII. Use: ....................................................................................................................................................... 20
VIII. Evaluation: ........................................................................................................................................... 24
I. Contexts:
- ElectroShop is a company that sells major technology products who acquire and sell electronic
devices to customers around the world. They are looking to apply their current data store
system with a relational database. ElectroShop takes orders from customers, who can order any
quantity of many items that they have in their current catalogue. The catalogue includes TV,
Phone and more product relate to technology.
- When selling, ElectroShop will storage customer information such as: customer code,
customer name, address, telephone number. For each sale: the store will create sales invoices
to store information. These invoices include: invoice number, item name, sales date, sales
quantity, unit price, sales amount. So, ElectroShop needs a database so they can
storage all the customer information.
- This image below show example about a invoice of a customer when they buy product at
ElectroShop:

In this Invoice we can see almost information related to customer and product such as: Name
of customer, address of customer, telephone of customer, name of the products, quantity,
price, purchase date or can be knows more information.
II. Problem:
As a programmer, I had to design a database for a company, namely designing a database with
evidence of user interface, output and data validations, and querying across multiple tables for
ElectroShop, one of the largest technology product sales companies in Vietnam.The purpose of
this database is to help the user, such as the manager can manage, statistics information
related to the customer, the number of products sold, the item which customers like and buy
the most, and also for the purpose of increasing sales productivity, increasing revenue for
ElectroShop and continue to make ElectroShop standing firmly in the business market of
technology products in Vietnam.
III. Criteria:
1.Database:
I created the database in order to help ElectroShop manage all information of customers and
products such as customer name, phone number or other information related to products such
as product name, price of the product. This database can also add, update and delete data,
which can help managers easily control the sales of the shop.
2.Function:
There are three basic functions: Add, Update and Delete data. It helps managers can be manage
information of ElectroShop.
+Add: Managers can add customer information or add product information.
+Update: Managers can easily change, update information if the information is wrong.
+Delete: Managers can remove one or more redundant or invalid information.
3.Security:
In order to ensure the security of the database, each client or manager has only one login
account and a unique password and password that is MD5-encrypted. This can limit the theft of
information and the loss of user data.
IV. Diagram Flow:
In order to better understand the purchase process of customers at ElectroShop, I have drawn a
diagram of the purchase activity at ElectroShop.
This image below is a diagram:
V. Mock up:
This image below shows four mock-up of four table I created base on requirement of customer:
We can see that each table contains all the information related to purchase invoices and each
table has three basic functions: Add, Update and Delete. In addition to have Login tables:
VI. Database Design:

1. Database normalization:
Data normalization is a technique for organizing data attributes so that they are grouped into
non-redundant, stable, flexible and adaptable entities:
• There is no iteration of attributes in different tables, except the key attribute and the
connection attribute.
• Does not contain values that are worth the calculated result of other attributes. For example,
the cost attribute is the result of the quantity attribute multiplied by the unit price attribute
and should be eliminated.
• There is no similar role between entities
Some common types of data normalization are:
-First Normal Form (1NF)
-Second Normal Form (2NF)
-Third Normal Form (3NF)

Third Normal Form(3NF):

To meet the 3NF standard, the following conditions must be satisfied:
- Each table cell should contain a single value.
- Each record needs to be unique.
- Single Column Primary Key.
- Has no transitive functional dependencies.
Transform Second Normal Form (2NF) data into Third Normal Form (3NF):
+ Removing transitive dependent attributes from the relationship and separating them from
the private key is a bridging attribute.
+ The remaining attributes form a key relationship as the primary key.
-In my database, I've split the tables in 2NF into 4 tables:
Customers, ORDER1, Items, Order_Items. The customer table contains only customer-related
information and does not contain non-customer related information.
-There are some differences in 3NF versus 2NF. I've separated the PayMethods, OrderID,
OrderDate columns from the Order table into a new table named ORDER1, and contains the
CustomerID column in the Customers table with the CustomerID as the foreign key that
connects the ORDER1 table and the Customers table.
- This image below is an example of 3NF:

This image show data types of each column in table.

Customer Table
 ORDER1 Table

Items Table

Order_Items Table

2.ER Diagram:
After reviewing the information from the invoice, I proceeded to design the database diagram. It
consists of four tables (ORDER1, Customer, Order_Items, Items).
The 1st: Customer tables, its have CustomerID (the customer buy anything on Tiki),
CustomerName, Address, City and Phone.
The 2nd: ORDER1 tables, it have OrderID, OrderDate(day customer buy product on Tiki),
customerID and PayMethods( Customer's payment method when buying products on Tiki).
The 3rd: Items table, it shows ItemID, ItemName, and Price.
The 4th : The next table is Order_Items table, it show three information: OrderID, ItemID and
Quantity.
The 5th : The Last table is Customer_Login table, it have three information CustomerID,Gmail
and Password
Explain:
Each invoice can have many products, many prices, but each invoice has only one code and one
customer can buy multiple products at the same time or there may be many customers with
the same name buy the same product but each the customer has only one unique ID, as well as
a single product code and each have only one Gmail account and one password.

3.Create Table:
Based on the normalization section above, I have to create 5 tables, include the Customers
table, ORDER1 table, Items table, Order_Items table, and Customer_Login table.
In order to create a table, we first have to use the database created using the command "USE
ASM1"
a. Create table customer:

I also use the same method as when creating the database to create the Customer table but
there is a difference in the command , instead of using the "CREATE DATABASE ASM1"
command, I use the "CREATE TABLE Customers" command (Enter the "CREATE TABLE
Customers" command then highlight the command and press Excute (or press the F5 shortcut))
to create the table.

Customers table have four column: CustomerID,CustomerName,Address,City and Phone. I have

defined a NOT NULL for CustomerID and CustomerID as a Primary Key, it connects to the
ORDER1 table that will be created later.
b.Create table ORDER1:

The ORDER1 table creation method is similar to creating a Customer table, just replacing the
command “CREATE TABLE Customers” with command “CREATE TABLE ORDER1”

ORDER1 Table have four column: OrderID,OrderDate,CustomerID,PayMethods with OrderID is a

Primary Key , CustomerID is a Foreign Key. The CustomerID in table ORDER1 has the effect of
connecting the ORDER table and the Customers table.
c. Create table Items:

The ORDER1 table creation method is similar to creating a Customer table, just replacing the
command “CREATE TABLE Customers” with command “CREATE TABLE Items”
For the Items table, there are only three columns: ItemID, ItemName, Price with ItemID is
Primary Key.
d. Create Table Order_Items:
The next table is Order_Items table. The way to create table is almost the same as the table
above, just replace command “CREATE TABLE Customers” with the command “CREATE TABLE
Order_Items”.

The Order_Items table contains the columns OrderID, ItemID, Quantity. Special, OrderID,
ItemID have role is a foreign key that connects tables that have OrderID and ItemID as primary
keys (namely is connect ORDER1 table and Items table).
I use the statement "FOREIGN KEY (name of key) REFERENCES <name of table> (name of key)"
to refer to Primary Key from another table. And the statement "PRIMARY KEY (name of key)" is
used to create the Primary Key.
e. Create table Custumer_Login:
The last table is Customer_Login table. The way to create table is almost the same as the table
above, just replace command “CREATE TABLE Customers” with the command “CREATE TABLE
Customer_Login”.
 4.Test Case:
Desc Input Expected Result Status

1 Test data Insert into Successful Pass

type INT correct inserted
intergers value
Insert
CustomerID=1 Result:

2 Test data Insert into Can not Pass

type INT number with insert
alphabet
CustomerID=1a
Result:

3 Test Unicode Insert Unicode Can not Pass

characters characters display
Unicode
character
 Result:

4 Test data Insert into Successful Pass

type Date correct Date in inserted
SQL(mm/dd/yyy
y)
mm: Month Result:
dd: Day
yyyy: Year.

Insert
OrderDate=
11/22/2017

5 Test data Insert into Can not Pass

type DATE incorect DATE in Insert
SQL(
dd/mm/yyyy) Result:
Insert
OrderDate=
19/12/2017

6 Test data Insert incorrect Insert failed Pass

type DATE month
OrderDate=
13/12/2017 Result:

7 Test data Insert incorrect Insert failed Pass

type DATE day
OrderDate=
12/32/2017 Result:

8 Check the Insert the date Can not Pass

date of of purchase insert
purchase wrong with the information
conditions
set(Day
 purchase is Result: 6
bigger than
today)

9 Check the Insert correct Successfull Pass

date of the date of inserted
purchase purchase with
the conditions
set(Day Result:
purchase is
smaller than
today)

10 Check the Insert correct Successful Pass

price of the price with
product conditions inserted
set(Price>100)

Result:

11 Check the Insert incorrect Can not Pass

price of the price with insert
product conditions
set(insert Price
<100)
Result:

12 Check the Insert incorrect Insert failed Pass

price of the price with
product conditions
set(insert
price<0) Result:
13 Check the Insert incorrect Can not Pass
quantity the quantity insert
product with conditions
set(quantity<0)

Result:

14 Check the Insert correct Successful Pass

quantity the quantity Inserted
product with conditions
set( Insert
quantity >0)
Result:

15 Check email Insert correct Successful Pass

email inserted

Result:

16 Check email Insert incorrect Can not Pass

email (Insert insert
redundant
“.vn”)
Result:
17 Check email Insert miss “@” Insert failed Pass

Result:

18 Check email Insert miss ”.” Insert failed Pass

Result:

19 Check Insert correct Successful Pass

telephone of telephone( inserted
customer insert all 10
numbers)
Result:

20 Check Insert Insert failed Pass

telephone of redundant
customer telephone(
Insert 11
numbers)
Result:

21 Check Insert incorrect Can not Pass

telephone of telephone( insert
customer Insert 9
numbers) Result:
22 Check Insert incorrect Can not Pass
telephone of telephone( Insert
customer Insert
alphabet to
phone number Result:
numbers)

23 Check Insert correct Successful Pass

CustomerID CustomerID(Cus inserted
tomerID is a
positive and
non-negative Result:
integer)

24 Check Insert Insert failed Pass

CustomerID CustomerID(
insert negative
mumber)
Result:

VII. Use:

After completing the database design, we conducted add some customer information from
the company, we determined the functionality of this database system with queries and results.
This image below shows ADD function:

Result:
We will update customer information if any information is wrong or store employees enter the
wrong data.
This image below show information in Customers Table before update data:

Customers Table
This image below show information after update:

Customers Table

We will delete purcharse product information if the customer want to cancel the
purcharse.This image below illustrate funtion delete:
 Order_Items Table

This image below shows purchase invoice information.

Result:

Invoices Information

VIII. Evaluation:
After completing the database design based on customer requirements, I conducted a review of
the benefits and disadvantages to find good solutions to this database system.Here are some
advantages and disadvantages.
1.Advantages:
- User information security: Each user has only one account and one password. Customer
passwords are MD5-encrypted, which helps to prevent data theft and user data loss.
This image below how the encrypted password after entering the password 123456.

Result:

- With the storage of a large amount of information that ElectroShop products business users
just need to find the website or application of ElectroShop to find the product that you want
and order and process the rest ElectroShop will be responsible, this is very convenient and save
time for ElectroShop customers.
- For the manager they can easily control the user information also the product information
through the application we design, they can easily add new product information ,add picture of
product, add user information, add picture of customers, update information, delete the wrong
information.
This image below show some function :

Result:

Delete Function

Result:

Update Function
- Because the database has been standardized by 3NF, there is no duplication of data that will
make it easier for managers to statistically and analyze data.
-Customers can login to the system to check personal information or check the purchase
history. Customers can login by email or telephone number. If the customer forgot the
password, then click on "Forgot Password " and they can also sign in other ways such as login
by Facebook, login with Google account or Twitter account, it is very convenient if user does
not register for ElectroShop account.

- Because the test case has been identified, it is possible to identify instances where the user
entered incorrectly or entered missing data, thus limiting at least the errors when the user use
the database system to store data.
2.Disadvantages:
In addition to the benefits that database systems bring to the user, there are some limitations
that need to be addressed:
- MD5 security is still not the best security type for this database, others can still steal user
information. can use Bcrypt encryption, because Bcrypt encryption is safer than MD5, but users
will have to pay additional costs.
This image below shows 1 solution to steal information:

- Because we use Microsoft SQL Server as a database for ElectroShop, so it will take up a lot
of
computer memory, long-term use will cause slowdown of the device. To limit this situation just
need upgrade hardware and more RAM to make computer run smoother.