Database Design and Development for AGC Company, Assignments of Database Management Systems (DBMS)

Database Design and Development

Typology: Assignments

2021/2022

Uploaded on 03/08/2022

nhat-do-long
nhat-do-long 🇻🇳

5

(1)

11 documents

1 / 42

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
PROGRAM TITLE: ……………………………………………
UNIT TITLE: …………………………………………………….
ASSIGNMENT NUMBER: 1
ASSIGNMENT NAME: Database Design and Development
SUBMISSION DATE: ……………………………………….
DATE RECEIVED: …………………………………………….
TUTORIAL LECTURER: ……………………………………
WORD COUNT: 1952
STUDENT NAME:
STUDENT ID:
MOBILE NUMBER:
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a

Partial preview of the text

Download Database Design and Development for AGC Company and more Assignments Database Management Systems (DBMS) in PDF only on Docsity!

PROGRAM TITLE: …………………………………………… UNIT TITLE: ……………………………………………………. ASSIGNMENT NUMBER: 1 ASSIGNMENT NAME: Database Design and Development SUBMISSION DATE: ………………………………………. DATE RECEIVED: ……………………………………………. TUTORIAL LECTURER: …………………………………… WORD COUNT: 1952 STUDENT NAME: STUDENT ID: MOBILE NUMBER:

Summative Feedback: Internal verification:

A. INTRODUCTION.

On the market today, there are many business companies that are not using technologies to manage the company's operating systems or have old technologies that do not meet the growing needs. company development. And AGC is one of them. Until now, AGC has managed its business using a computer system developed by a university student 5 years ago. The system is currently too slow and no system documentation is generated when it is deployed that changes to the system cannot be easily made. Therefore, AGC has hired a team of Database Developers at a large IT consulting company to advise on document building and Database design for a new system to meet the current needs of customers. The company can also develop the system in the future if needed.

B. SYSTEM REQUIREMENTS

I. Real world scenario

To date, AGC has operated its company utilizing a computerized system created by a college student five years ago. The system is currently too slow, and because no system documentation was created when it was developed, it is difficult to make improvements. The CEO of AGC believes that, since their business needs have evolved, they must adapt in order to expand and operate their company successfully

II. Data requirements for storage

  1. Account Entity Description of entity Attribute Description of attribute Account accoutId Id of the account userName User name of the account password Password of the account typeAccount Type of the account
  2. Employee Entity Description of entity Attribute Description of attribute

Employee employeeId Id of employee name Name of employee address Address of employee phoneNumber Phone number of employee email Email of employee

  1. Customer Entity Description of entity Attribute Description of attribute Customer customerId Id of the customer name Name of customer address Address of customer phoneNumber Phone number of customer
  2. Category Entity Description of entity Attribute Description of attribute Category categoryId Id of the category name Name of the category description Description of the category
  3. Product Entity Description of entity Attribute Description of attribute Product productId Id of the product name Name of the product price Price of the product image Image of the product quantity Quantity of the product

III. Relationship between entities

 An account belongs to an employee and 1 cx employee has only an account => the relationship between Account and Employee is One to One.  An account belongs to a customer and 1 cx customer has only an account => the relationship between Account and Customer is One to One.  A category can have products but a product can only belong to one category => the relationship between Category and Product is One to Many  One employee can import many products and one product can be imported by many employee => the relationship between Employee and Product is Many to Many  A customer can have many orders, but an order can only belong to one customer => the relationship between Customer and Order is One to Many  A product can have many orders and an order can also have many products => the relationship between Product and Order is Many to Many

C. DATABASE DESIGN

I. ERD Diagram

ERD is a diagram, showing the entities in the database, and the relationship between them.  Some tools features to draw ERD:  DeZign for Databases:  Drag-and-drop user interface  Entity Relationship Diagramming  Multiple display modes  Industry-standard design notations  Multiple display modes  Pan and zoom window  ER-Modeling  Forward engineering  Reverse engineering  Gleek.io

 Keyboard-based user interface  Rapid Diagramming  Version Control  Live Collaboration  Diagram export  Design templates  Customization  dbdiagram.io  Generates SQL statements  Exports to images and PDFs  One-click sharing  Integrates with SQL databases  ERDPlus  User-friendly interface, easy to use  Full EDR vẽ drawing features  Very convenient to use can draw right on the website: https://erdplus.com/ Through the above features, I use ERDPlus to draw Diagram to Relation Diagram.

 A table (relation) is said to be in 1NF normal form if and only if all the domains of the columns present in the table (relation) contain only atomic (prime) values. b. 2NF  Is 1NF  Non-key attributes must be fully functionally dependent on the primary key c. 3NF  Is 2NF  Non-key attributes must depend directly on the primary key

3. For example Table Employee( name, email, phoneNumber, address, city, hiredate, accountId).  1NF:  Each cell must contain only a single (atomic) value.  Every column in the table must be uniquely named.  All values in a column must pertain to the same domain.  Eg:  2NF: Tables in 2NF must be in 1NF and not have any partial dependency  3NF: Tables in 3NF must be in 2NF and have no transitive functional dependencies on the primary key.

IV. Relational database system

1. Design Database. a. A database management system (DBMS) DBMS is a software package designed to define, manipulate, retrieve, and manage data in a database. The DBMS usually manipulates its own data. Data format, field names, record structure, and file structure. It also defines rules for validating and manipulating these data b. The most popular database management systems today:  Oracle  Advantages: o There will be improvements and new features. Because Oracle tends to set the bar for other database management tools. o Oracle's database management tools are also extremely powerful. You might find a tool that can do what you want.  Disadvantages: o The cost of Oracle is quite high, especially for small organizations. o The system will require quite a lot of resources after installation. So it is necessary to upgrade the hardware  MySQL  Advantages:

Conclude: From the above priority points, we will choose the site using SQL Server to deploy the project's database

**2. Database Diagram:

  1. Implement a query language** a. Select  Insert normally:

Select with PROCEDURE: compact and can be reused many times

c. Update  Insert normally: