1622 assignment 2 (pass)

1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) 1622 assignment 2 (pass) FPT Greenwich

ASSIGNMENT FRONT SHEET <No.1>

Unit number and title Unit 04: Database Design & Development

Learner declaration:

I certify that the work submitted for this assignment is my own and research sources are fully acknowledged

Grading grid P2 P3 P4 P5 M2 M3 M4 M5 D2 D3

In this assignment, you will have opportunities to provide evidence against the following criteria

Indicate the page numbers where the evidence can be found

no

Assessor’s Feedback

Assignment title Understand databases and data management systems

LO2 Develop a fully functional relational database system, based on an existing system design

LO3 Test the system against user and system requirements

P2 Develop the database

system with evidence of user interface, output and data validations, and querying across multiple tables

- Code snippets to create each table & to insert some sample data for each table

- Generated Database Diagram - Explanations about any changes comparing to your design -Use the range of tools and

techniques used to design (working

or prototyping) user interfaces for these above system’s functionalities

P3 Implement a query language

into the relational database

P4 Test the system against user

and system requirements

Produce a test plan and execute it

You must include:

• Normal scenario

• Data validation

• Extremes of data

• Query execution (the queries to

P5 Produce technical and user documentation

M3 Assess whether meaningful

data has been extracted through the use of query tools to produce appropriate

management information

M4 Assess the effectiveness of

the testing, including an explanation of the choice of test data used

M5 Produce technical and user

documentation for a fully functional system, including

ER Diagram and normalization statements and describing how

the system works

D2 Evaluate the effectiveness

of the database solution in relation to user and system requirements, and suggest

improvements

D3 Assess any future

improvements that may be required to ensure the continued effectiveness of the database system

Summative feedback

Assessor’s Signature

2 Register Error! Bookmark not defined

3 User main menu Error! Bookmark not defined

4 Salesperson main menu Error! Bookmark not defined

5 Management main menu Error! Bookmark not defined

6 Function “Invoice” Error! Bookmark not defined

7 Function “Customer” Error! Bookmark not defined

8 Function “Supplier” Error! Bookmark not defined

9 Function “Salespersons” Error! Bookmark not defined

2 Entity Relationship Diagram (ER Diagram):

Table 1- The third normal form (3NF)

6 Table 4 - Example Customer table 7 Table 5 -

Salespersons table 7 Table 6 - Example Salespersons table 8 Table 7

- Supplier table 9 Table

8 - Example Supplier table 9 Table

9 - Items table

10 Table 11 - Orders table 11 Table 12 - Example Orders table 12

Table 13 - Order detail table

13 Table 14 - Example Order detail table

Table 18 - Test case function login

17 Table 19 - Result of query for register

19

Table 20 - Test case of Register

19

Table 21 - Show information about customer is using

Table 30 - Result of function Search supplier

34 Table 31 - Test case function supplier

35

Table 32 - Test case function salesperson

39 Table 33 - Test case function Items

Table 36 - Test case function customer report

46 Table 37 - Result of function bonuses for employees

Table 40 - Test case function sales report

49 Table 41 - Result of function List of items and price

Table 44 - Evaluate the responsiveness of Database with user requirements

54 Table 45 - Interface Design and Database Design assessments user requirements

56

Figure 1 - Purchase invoice ElectroShop

2 Figure 2 - ElctroShop Entity Relationship Diagram

Figure 8 - Interface Management main menu

24 Figure 9 - Interface function Invoice

Figure 12 – Interface function Supplier

32 Figure 13 - Interface function Supplier - Add New

33

Figure 14 - Interface function Salespersons

36

Figure 15 - Interface function Salespersons - Add New

37 Figure 16 - Interface function Items

1 | P a g e

INTRODUCTION

Use an appropriate design tool to design a relational database system for substantial problem Base on Assignment Brief that ElectroShop company sell electronic devices and they want to create a database to store system This system will store the store’s necessary data, which are: Customer Information, Seller (Employee) Information,

Product & Provider Information, Invoice Information Designed by using Relational Database and 3NF Normalization Process, this System will provide a fully functional

Database which includes: Data validations, Data normalization Data interfaces for different situations, Data modification, Calculate Seller’s (Employee) bonus Requirement of ElectroShop’ application:

- The database will store the information and security data b This system will store the store’s necessary data, which are:

o Seller information o Customer

Invoice o Product information o Supplier information

- Designed by using Relational Database and 3NF Normalization Process, this System will provide a fully functional Database which includes:

o Data validations o Data normalization o Data modification

o Calculate Seller’s (Employee) bonus

PART 1: DATABASE DESIGN

1 Database system architecture

2 | P a g e

The Database system’s requirement additional steps should be taken so that no attribute can be transitively dependent on the primary key That means they cannot be dependent on a non-primary key attribute in the same table

Upon inspection, a name of supplier is actually retrievable from supplier information and similarly to item information, customer information and salesperson information are dependent on item_id, customer_id, salesperson_id

One customer can buy many items and one item can be bought by many customers so the Database system need to have 1 table order_detail include item_id, order_id and order_quantity to solve that problem In the beginning, ElectroShop has a small database system and is limited to paperwork by getting information from this Invoice:

Figure 1 - Purchase invoice ElectroShop

3 | P a g e

4 | P a g e

Figure 2 - ElctroShop Entity Relationship Diagram

3 Database creation tables

3.1 Customer table:

This table used to store information of ElectroShop’s customer information, customer’s email will be used to send offers, product or promotions

6 | P a g e

Table 3 - Customer table

This table includes:

o Customer’s identity (customer_id - PK): This is primary key of customer table to make sure that a

customer has a unique and non-duplicate ID

o Customer’s Name (customer_name): Store customer name information

o Customer’s Email (customer_mail): Store customer mail information and send product

information as well as the completion process when customers buy products

o Customer’s Address (customer_addressDocument shared on www.docsity.com): Store customer address information

o Customer’s Zip code (Downloaded by: KhangDao (khangbabyboy113@gmail.com)customer_zipcode): Store customer zip code information o Customer’s Phone number (customer_phone): Easily contact customers when

needed

CREATE TABLE customers (

customer_id INT PRIMARY KEY,

Table 5 - Salespersons table This table includes:

o Salesperson’s identity (salesperson_id - PK): Each salesperson just only has one ID that make

sure that salesperson has a unique and non-duplicate ID so this must be primary key o

Table 4 - Example Customer table

8 | P a g e

Salesperson’s name (salesperson_name): Store salesperson name information o Salesperson’s Age (salesperson_age): Store salesperson age information

o Salesperson’s phone number (salesperson_phone): Store salesperson phone number information

o Salesperson’s email (salesperson_mail): Store salesperson email information

9 | P a g e

This table includes:

o Supplier’s Identity (supplier_id - PK): This is primary key of supplier table to make sure that a

supplier has a unique and non-duplicate ID

o Supplier’s name (supplier_name): Store supplier name information o Supplier’s mail

(supplier_mail): Store supplier mail information o Supplier’s address (supplier_address): Store supplier address information o Supplier’s phone number (supplier_phone): Store supplier phone

information

Table 8 - Example Supplier table

This table includes:

o Item identity (item_id – PK): This is primary key of items table to make sure that item has a unique

and non-duplicate ID

o Kind of Items (item_kind): Store kind of items information o Price (item_price): Store price of

items information

o Supplier Identity (fk_supplier_id): This is foreign key to link with supplier_id at supplier table

This allow people can know what specific items originated

CREATE TABLE orders(

order_id INT P RIMARY KEY

, order_day date , fk_customer_id int , CONSTRAINT fk_customer_id

FOREIGN KEY ( fk_customer_id )

REFERENCES customers customer_id ) , order_salesperson_id

INT , CONSTRAINT fk_order_salesperson_id

FOREIGN KEY ( order_salesperson_id)

12 | P a g e

o Order’s identity (order_id – PK): This is primary key to confirm that when customer order

something this order’s identity exist only and non-duplicate ID

o Order day (order_day): Store the day that customer order information

o Customer’s identity (fk_customer_id - FK): This is foreign key references to customer table It

will allow people know information about customer is ordering

o Salesperson identity (fk_salesperson_id - FK): This is foreign key references to supplier table

That indicates employee who sell items to customer

3.6 Order detail table

This order detail table know as invoice and this dataset stores all the invoices that are made through sale One order will generate one invoice

Table 12 - Example Orders table

Order detail table includes:

o Item’s identity (fk_item_id -PK, FK): This is one of two primary key with order identity that allow customer can offer more than one item And it also foreign key references with item_id in items table to show what items customer order

o Order’s Identity (fk_order_id – PK, FK): this is a last primary key with item identity that allow person can offer more than one item and foreign key references with order_id in orders table this

is the main of function let customer can offer more than one item

o Order quantity (order_quantity): Store a number of each items that customer order information

15 | P a g e

evampsaanga (n.d.) Retrieved from evampsaanga:

https://evampsaanga.com/productsservices/websolutions/ui-ux-design/ ( access date: 8/3/2022 )

Figure 3 - Database System Diagram

16 | P a g e

THIRU (2018) myreadingroom Retrieved from myreadingroom:

of-dbms.html ( access date: 8/3/2022 )

https://vissicompcodder.wordpress.com/category/advantages-and-disadvantages-of-database-systems/