Based on your selected scenario from Hands-On Database, complete the "To Do" activities. Please check your own work to be sure it includes the elements in the list.To doReview all the requirements and business rules.Define your entities and attributes and the relations that exist between them.Create a logical model using crow’s feet notation in Visio or hand draw it on graph paper if you prefer.Add all the entities and their attributes. You don’t need to worry about data types for now.Identify the key fields for each entity and the foreign keys.Analyze the diagram. Identify which role (i.e., domain, linking, lookup, or weak) each entity plays in your database.Review it for the following:Are all the major components of the Wildwood Apartments business model represented by domain entities?Does each entity contain the appropriate attributes to fully describe it and meet the business rules you have gathered so far?Does every entity have an appropriate primary key defined?Are all many-to-many relationships resolved into one-to-many relationships by linking tables?Are the relationships valid (no cross relationships)? Is the appropriate entity is defined as the one side of a one-to-many relationship? Do the tables have appropriate foreign keys? Also check for other such issues.Are lookup tables used for attributes that have a set list of values?Documentation: Be sure to store your ERDs in your database notebook.

  There are several tools and techniques featured in the textbook that are used for quality control in IT projects. A Pareto chart is a type of histogram that can be used to define quality problems in a system. It allows you to see what areas need improvement. Create a Pareto chart based on the information below. Use the Pareto Chart template. You can also do the math and create the graph in Excel, but people who do get it wrong more often than the ones who use the template. List the most frequent customer problems first. On the graph, it should be the tallest bar first, then the next largest, and so on. The second item in the graph, after the bars, is the cumulative line and it should always go up from left to right, all the way to 100%. If you see a dip in the line, your problems are not listed in the correct order. Check your entries so your resulting chart looks like the one in Figure 8-7 in the textbook. Customer Complaints; Frequency/Week Customer is on hold too long; 90 Customer gets transferred to wrong area or cut off; 20 Service rep cannot answer customer’s questions; 120 Service rep does not follow through as promised; 40