Assumptions & Checklist

The Assumptions(Some are implied in data.)1.RESTAURANT.RestaurantName is unique.2.The combination of members’first and last names may not be unique.3.The company serves members and non-members (membership is not required to placeorders).Note1.Attributesof an entity must be realattributesor characteristics of the entity. a.An entity may not be an attribute of itself.b.An artificial number such as MemberID CAN NOTbe an attribute. There should be no surrogate key UNLESSthe existing attributes cannot uniquely identify an instance ofthe entity.You need to check the data to determine if the real attributes can uniquely identifyan entity.c.If removing an artificial ID will resultina loss of attributes, you mustadd back the real attributes represented by the artificial IDs.2.Entities have identifiers,NOTprimary keys. Please label the entities’ identifiers asshownin the following figure.3.SQL programming for triggers isnot required.Checklist for the Entity-Relationship Model1.All the attributes ofthe entity are the actual characteristics ofthe entity.There are noartificial IDs or numbers unless the entity cannot be uniquely identified without an artificial ID.2.Label the identifiers.3.The number of entities is no greater than the number of tables.4.The minimumand maximum cardinalities correctly reflectthe relationshipbetween the two entities.The cardinalities are identifiedeither from evidence in the data or based on the assumptions. Never invent any relationships.5.The expression for identifying and non-identifying is correct (solid vs. the dashed line).

Final ProjectCIS 3730 Summer 202226.Thereare NOtwo entities that have N:M maximum cardinality. All N:M relationships should have been replaced by introducing an intermediary entity, such as an entity for the association,intersection, or archetype/instance relationships.7.Organize theE-R diagram toensure that the relationship lines donot cross.Oratleastminimize the intersectionsto the best of your ability.Checklist for the Updated Database Design (Updated Schema)1)Table names are in capitalletters. Column namesarewith an initial uppercaseletter.2)Mark all the keys (primary key, foreign key, and alternative key), data types, and nullity constraints following the format of the figure below3)The tables’ relationships are consistent with those between entitiesbeforeadding surrogate keys.4)After adding the surrogate keys, the relationship notations are modified correctly to reflect the identifying non-identifying status.5)You have included a table specifying the minimum enforcement actions/restraints for each parent-child relationship(excluding optional parent optional child).Refer to Chapter 6 Part 2 slides for minimum enforcement actions/restraints.6)A relationship with a 1:N maximum cardinalityis likelyto be a parent-child relationship regardless of whether the child is identifying.7)Youmay use Crow’s Foot Notationfor the updated schema.When you use the Crow’s Foot Notation, there is no need to mark ‘1’for the primary key and ‘∞’for the foreign key.8)The updated schema contains all the necessary information for you to program the database with SQL. Make sure it has all the tables, columns, data types, nullity constraints, relationships (cardinalitiesand identifying), and minimum cardinality enforcement actions/constraints for the parent-child relationship, if applicable.9)Organize the schema to ensure that the relationshiplines donot cross.Oratleastminimize the intersectionsto the best of your ability.Checklist for theMembership Manager view or table Design1.You have included a hypotheticalanalytical task for the membership manager.2.Your hypothetical analytical task cannot be solelybasedon the data in MEMBER_MONTHLY_TOTAL.3.You did not truncateany data to make the view or table.If you did so, you need to justify it.