need crows foot diagram logical data model sample data dictionary amp amp physical database design for the given erd diagram

1.Crows Foot diagram

Using Visio or another modeling tool of your choice, reproduce the diagram from your Modern Database Management text that is on page 94 Figure 2-22.

Data model for Pine Valley Furniture Company in Microsoft Visio, submission

  • Complete the assignment offline and save it to your local hard drive or flash drive.

2. Logical Data Model

  • In a logical data model, primary keys are present.
  • In a logical data model, all attributes are specified within an entity.
  • Relationships between entities are specified using primary keys and foreign keys in a logical data model.

3. Two sample data dictionary formats are provided here.

  • Decide on one of the provided sample data dictionary format.
  • Use the logical data model that you developed in week 3.
  • Identify the entities from the draft of your data model submitted during Week 3.
  • Provide a sample data dictionary of all entities and their attributes selected for your model.

4. Use the Data Dictionary that you developed in week 4 for your selected scenario.

  • From the data dictionary tables, build MS Acess tables.
  • Via “Database Tools” create table relationships
  • Submit assignment via blackboard

Physical Database Design Submission:

  • Complete the assignment offline and save it to your local hard drive or flash drive.

Physical data model represents how the model will be built in the database. A physical database model shows all table structures, including column name, column data type, column constraints, primary key, foreign key, and relationships between tables. Features of a physical data model include:

  • Specification of all tables and columns.
  • Foreign keys are used to identify relationships between tables.
  • De-normalization may occur based on user requirements.
  • Physical considerations may cause the physical data model to be quite different from the logical data model.
  • Physical data model will be different for different RDBMS. For example, data type for a column may be different between MySQL and SQL Server.

The steps for physical data model design are as follows:

  1. Convert entities into tables.
  2. Convert relationships into foreign keys.
  3. Convert attributes into columns.
  4. Modify the physical data model based on physical constraints / requirements.