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 Qualification BTEC Level HND Diploma in Computing and Systems Development Unit number and title Unit 04: Database Design & Development Assignment submitted 10/3/2022 Đào Vĩnh Khang Assessor name Lam Thuy GCS200222 Submission number GCS0905B Assignment due Learner’s name Learner’s ID Learner declaration: I certify that the work submitted for this assignment is my own and research sources are fully acknowledged Learner signature Khang Date 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 Task no Assessor’s Feedback Assessment criteria Expected evidence 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 LO4 Produce technical and user documentation - Code snippets to create each table & to insert some sample data for each table P2 Develop the database system with evidence of user interface, output and data validations, and querying across multiple tables 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 system - Queries to support the functionalities (insert, update, delete) - Queries to support the enhancement of the interface to the above functionalities 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 execute the test cases) - Technical documentation - User documentation P5 Produce technical and user documentation M2 Implement a fully functional database system which includes system security and database maintenance 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 Date Table of Contents INTRODUCTION PART 1: DATABASE DESIGN Database system architecture Register Error! Bookmark not defined User main menu Error! Bookmark not defined Salesperson main menu Error! Bookmark not defined Management main menu Error! Bookmark not defined Function “Invoice” Error! Bookmark not defined Function “Customer” Error! Bookmark not defined Function “Supplier” Error! Bookmark not defined Function “Salespersons” Error! Bookmark not defined Entity Relationship Diagram (ER Diagram): Database creation tables Diagram 15 PART 2: INTERFACE DESIGN, QUERY, TEST CASE 16 Login 10 Function “Items” 40 11 Function customer report 44 12 Function Sales report 47 13 Function Items report 50 CONCLUSION 53 How Interface Design and Database Design assessments meet user requirements 53 Advantages and Disadvantages 57 Remedial solutions 59 APPENDIX: Survey Form 61 References 62 TABLE OF TABLES Table 1- The third normal form (3NF) Table - Fully Database system normal form Table Customer table Table - Example Customer table Table Salespersons table Table Example Salespersons table Table - Supplier table Table - Example Supplier table Table - Items table 10 Table 10 Example 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 13 Table 15 - Example Customer Login Table 14 Table 16 - Customer Login Table 14 Table 17 - Customer Login Table matching ID and password 17 Table 18 - Test case function login 17 Table 19 - Result of query for register 19 Table 20 - Test case of Register 19 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 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 - Purchase invoice ElectroShop 2|Page 3|Page 4|Page Entity Relationship Diagram (ER Diagram): Figure - ElctroShop Entity Relationship Diagram 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 5|Page CREATE TABLE customers( customer_id INT PRIMARY KEY, customer_name VARCHAR(100), customer_mail VARCHAR(100), customer_address VARCHAR(100), customer_zipcode VARCHAR(100), customer_phone VARCHAR(100), ); Table - 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 6|Page Table - Example Customer table 3.2 Salespersons table: This table is used to store information of ElectroShop’s employee information would help to determine which salesperson is in charge of selling which order Many orders can be sold by one salesperson so it will have many relationships Table - 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 7|Page 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 Table - Example Salespersons table 3.3 Supplier table This table is used to store information of ElectroShop’s supplier Table - Supplier table 8|Page 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 - Example Supplier table 9|Page 3.4 Item table This table is used to store information of ElectroShop’s orders That also contains information about items that are being sold The items are shown in the items table and in order details Table - Items 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 10 | P a g e Table 10 - Example Items table 3.5 Order table This table is used to store information of ElectroShop’s orders It is an important table to connect and reference by many others: A customer who order that items, a salesperson who sold that items, specially that connect with that CR EATE 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) REFERENCES salespersons ( salesperson_id ), ); Table 11 - Orders table detail table as know as invoice This orders table includes: 11 | P a g e Order 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 o Order day (order_day): Store the day that customer order information 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 Table 12 - Example Orders table 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 12 | P a g e Table 13 - Order detail 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 Table 14 - Example Order detail table 3.7 Customer login table 13 | P a g e This table used to store information about login id and login password of each customer Base on that customer can log in to the ElectroShop system Table 16 - Customer Login Table Table 15 - Example Customer Login Table Diagram 14 | P a g e Figure - Database System Diagram References evampsaanga (n.d.) Retrieved from evampsaanga: https://evampsaanga.com/productsservices/websolutions/uiux-design/ ( access date: 8/3/2022 ) 15 | P a g e THIRU (2018) myreadingroom Retrieved from myreadingroom: http://www.myreadingroom.co.in/notesandstudymaterial/65-dbms/462-advantages-and-disadvantagesof-dbms.html ( access date: 8/3/2022 ) vissicompcodder (2015, 3) Retrieved from vissicompcodder: ( access date: 8/3/2022 ) https://vissicompcodder.wordpress.com/category/advantages-and-disadvantages-of-database-systems/ 16 | P a g e