Plan out how this new table will relate to at least one other existing entity. Show the relationship using crows foot style of notation. Identify appropriate field names for each table in your diagram.

Assignment Question

Part 1: 1. For this first step take the data provided previously, IT163_Data1, and put it into a tabular format. See the example document for an idea of how you might organize the data into a table. (word or spreadsheet) Note: Organizing all of the data into a single table does not represent a database nor a normalized design. This data store helps to visualize the data in one place. This is just where you’ll begin the process. 2. Put the data into first normal form. Use a simple table in Word or an Excel spreadsheet to show your attributes in first normal form with a partial data example. (word or spreadsheet) 3. Looking at your first normal form and the data examples, identify problems that need to be addressed to put this data into second normal form. Use a simple table in Word or an Excel spreadsheet to show this data in second normal form. (word or spreadsheet) 4. Taking your second normal form of the data, analyze the issues that prevent it from being in third normal form. Use a simple table in Word or an Excel spreadsheet to show this data in third normal form. 5. Now that you’ve worked through the normalization of the data, use Microsoft Visio to create your logical diagram to show the normalized design. The diagram should represent relationships using crow’s foot notation. The diagram should include the entity names, attributes and notation of primary and foreign keys for each entity.

Part 2: You will use Microsoft Visio to build your physical ERD diagram which will include the following. You may start with your existing logical diagram and modify it as follows: As an additional challenge for this phase of the design, you will add one more table to the database design. Think of some other aspect of this business model that you could bring into the design at this point. You must plan out how this new table will relate to at least one other existing entity. Show the relationship using crows foot style of notation. Table names. Include those from your conceptual diagram and the new table from the previous step. Remember to use meaningful names and consistent naming conventions. Hint: these started out as entities Field names. Identify appropriate field names for each table in your diagram. Remember to use consistent naming conventions. (i.e. clientID, petID, breedID might all be primary key fields).

Reference: http://www.databasedev.co.uk/database_field_names.html Primary keys/foreign keys. Notate the primary and foreign keys in each table as applicable. Remember to be consistent. Hint: the primary key in the “one” table matches to the foreign key in the related table. Reference: Access 2019 for Dummies. Chapter 5: “Table Tune Ups/The Primary Key to Success” Data types and field sizes. Identify appropriate data types for each field and field sizes as applicable. Hint: right-click your entity block and choose show attribute types to add a column to the right of your field names. Reference: Access 2019 for Dummies. Chapter 4: “Sounds Like a Plan / Determining Data Types” Nullability. Identify those fields that can be left blank. Hint: You may simply identify those fields that may be left blank with a null indicator as shown in the example. Assignment Requirements You will build your diagram using Microsoft Visio. You may use the ERD template with crow’s foot notation as referenced previously. You will submit your Visio diagram file (*.vsd).