TASK OVERVIEW:

In this scenario, continue with conceptual database model of your retail

store that sales bikes from Unit 1 and take this model and expand into the

logical database model. When expanding into the logical database model, do

keep in mind database normalization.

To do this, create attributes for each of your entities from the Unit 1

assignment. For example, if I were creating attributes from customers, I

may have attributes like:

Customer_ID

First Name

Last Name

Customer_Phone

And so on.

The Customer ID in the list above would be the Primary key and could be

the foreign key in a possible relationship to another entity maybe like

Customer_Orders.

Below is an example logical database model and in this example when

compared to the previous conceptual model example from unit 1, notice the

added entity attributes. Also note that ID fields would be primary and

foreign keys used to primarily relate the tables.

In this example, you will also notice a 5th entity has been introduced

called Reunion_Family. This additional entity is known as an associative

entity which is needed to eliminate or resolve the many-to-many

relationship between the Families and Family Reunions. Many-to-many

relationships are determined typically during the conceptual database

modeling phase and are resolved and converted into one-to-many

relationships in the logical to physical database modeling phases to work

properly in an actual live database.

Ideally, Microsoft Visio should be used but using other drawing and design

software is welcome. A good example other drawing software would be ERD

Plus. Links to an external site.

When using Microsoft Visio, upload and attach the Microsoft Visio file

itself and when using other drawing software like https://erdplus.com/,

take a screen capture of the logical database model and paste into a

Microsoft Word document for official submission. Converting any of these

files to a PDF file is also acceptable.