logo

Introduction to ERD Diagram

   

Added on  2019-10-12

6 Pages1099 Words602 ViewsType: 602
 | 
 | 
 | 
Introduction to the ERD diagram An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.An entity in this context is a component of data. In other words, ER diagrams illustrate the logical structure of databases.Entity Relation Attribute weak entityPK attribute
Introduction to ERD Diagram_1

ER Diagram Scenario explanation according to my ER diagram When customer call or request to the company staff so customer staff create a log than give information about the delivery option and delivery cost to the customer when customer confirm the log so stuff take information about the customer (customer name, cutomer_Emial, customer address, and if customer from a company than company name) than log start shipment according to the customer delivery choice and create an ID for shipment that customer can track the shipment. Log also save information about time and location of shipment. Than shipment delivered by HD team to the recipient and they get confirmation id from recipient as a prove thanthey update the log.
Introduction to ERD Diagram_2

Relation schema Customer (cu_name, cu_ID, cu_address, cus_Email, company_name, Shp_ID)Staff (S_name, S_ID, S_phone,)Log (Log_ID, PK_address, Pk_time, Delivery_option,) Shipment (carr_location, carr_time, weight, Shp_ID,)Handling Team (HD_id, HD_name)Recipient (R_ID, R_Phone, R_Name, Confirmation_ID)NormalizationCustomer In Customer table there is not any repeating group within the table with multiple values and thereis no partial dependency due to not having two primary keys in the table. The normalization of 2nf relations to 3nf involves the removal of transitive dependencies. If a transitive dependency exists but in this table transitive dependency is not exists.Cu_IDCu_nameCu_addCu_emailCompany_nameShip_IDPK FKStaff In Staff table there is not any repeating group within the table with multiple values and there is not partial dependency due to not having two primary keys in table. The normalization of 2nf relations to 3nf involves the removal of transitive dependencies. If a transitive dependency existsbut in this table transitive dependency is not exists. S_IDS_nameS_phonePK
Introduction to ERD Diagram_3

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Normalization of Customer Service Professional Database
|3
|690
|400

Normalization of Customer Service Database
|3
|690
|381

Normalization of Bank, Manager, Branch, Customer, Employees, Deliveries and Products
|3
|574
|54

ER diagram & Normalization
|9
|1683
|96

Design, Normalization and Data Dictionary for Festival Database
|14
|2021
|90

Entity Relationship Diagram : PDF
|10
|1685
|236