Shoes Your case study MUST include all of the following items. 

1. Complete Entity-Relationship Diagram (ERD) for the database design. Include all maximum and minimum cardinalities on your diagram. The ERD CANNOT be hand-drawn; you must use a computer. Microsoft Visio is a suitable program for this. If you have access to a different graphical program that will accomplish the desired results, feel free to use it. 

2. Each entity will eventually be a table in your database. With this in mind, identify all the attributes you will need for each entity. Create a domain specification for each entity, which will be a table that will show the following for each domain (field): 

3. Domain name 

4. Data type 

5. Semantic description of the domain (written description of what the domain represents) 

6. Physical description of the domain. Example: Domain Name Data Type Size Physical Description Address Text 35 House or building number, street name, and Apartment number (if needed) City Text 30 City Name First Name Text 15 Customer’s first name Phone Text 14 Phone number using (999) 999-9999 format 

7. You must include all business rules that will affect your database design. Business rules are constraints, or restrictions that limit how you develop your database. For example, in a sales-oriented database, quantities purchased cannot be negative. Identify all business rules that you believe will affect your database design. 

8. Create dependency diagrams for all entities (tables) in your database. Be sure that each entity (table) is in at least 2NF; 3NF is preferable. These cannot be hand-written/drawn; use Word, PowerPoint, or other program to accomplish this. 

9. Write out all the relations as described in Chapter 6 of the text. Be sure to identify the primary and foreign keys in each relation. Include a descriptive note on the system you are using to identify the primary and foreign keys. This should also be done in a word processing program. 

10. Identify information that is, or could be, regarded as important to the company for which the database is being designed. For example, if you have a database design for a production environment, then information that would be important to this company might be total production per day, total production by department for a given period, or a comparison of production and sales from one month to the next. This information will be the basis for queries, forms, and reports in the development stage of your project. 

11. Write a short report that describes the following: 

• Purpose of the database 
• Why you chose the entities you did and why they are important to the company
• Why you chose the attributes for each of the entities 
• A general description of the limitations placed on the design of the database (business rules) 
• Expected size of the resulting database (number of records) o Projected growth of the company.

Answer rating: 100% (QA)

here is a suggested approach for completing this case study on a database design for a shoe company EntityRelationship Diagram ERD The ERD should represent the entities and relationships within the da... View the full answer