Open customer Order PK CUS ID CUS NAME places PK, FK FK CUs address Order_no CUS ID Order_date includes ITEM ITEM Code Order no. ITEM name ITEM_quantity ITEM price Registered Customer Nong stereo customer Pad order COD Oth Electrical appliances clothes Shoes receives prepares Order continuation Tracking FK Order 10 Hatto Rent Date Department SITEM NO Packaging ITEM PUTEM.COM sends Onscription Pequantity ships Check av Delivery Delivery Delivery Date D 1- Business rules: Properly document and verify all business rules with the end users. Ensure that all business rules are written precisely, clearly, and simply. The business rules must help identify entities, attributes, relationships, and constraints. Identify the source of all business rules, and ensure that each business rule is justified, dated, and signed off by an approving authority 2- Data modeling Naming conventions: all names should be limited in length (database-dependent size) 3. Entity names: Should be nouns that are familiar to business and should be short and meaningful. Should document abbreviations, synonyms, and aliases for each entity. Should be unique within the model. For composite entities, may include a combination of abbreviated names of the entities linked through the composite entity 4 Attribute names: Should be unique within the entity. Should use the entity abbreviation as a prefix. Should be descriptive of the characteristic. Should use suffixes such as ID. NUM, or CODE for the PK attribute. Should not be a reserved word. Should not contain spaces or special characters such as @...or & 5. Relationship names: Should be active or passive verbs that clearly indicate the nature of the relationship 6- Entities: Each entity should represent a single subject. Each entity should represent a set of distinguishable entity instances. All entities should be in 3NF or higher. Any entities below 3NF should be justified. Granularity of the entity instance should be clearly defined. PK should be clearly defined and support the selected data granularity 7- Attributes: Should be simple and single-valued (atomic data). Should document default values, constraints, synonyms, and aliases. Derived attributes should be clearly identified and include source(s). Should not be redundant unless this is required for transaction accuracy, performance, or maintaining a history. Nonkey attributes must be fully dependent on the PK attribute 8- Relationships: Should clearly identify relationship participants. Should clearly define participation, connectivity, and document cardinality 9- ER model: Should be validated against expected processes: inserts, updates, and deletions Should evaluate where, when, and how to maintain a history. Should not contain redundant relationships except as required Should minimize data redundancy to ensure single-place updates. Should conform to the minimal data rule: All that is needed is there, and all that is there is needed I Please check the above erd diagram and make sure that it follows above 9 rules and also below instructions. Supertype and Subtype entities, Specialization Hierarchy is Disjoint or Overlapping and if the constraints are Partial or Complete are correctly drawn and mentioned. 2- Make sure your tables are Normalized. I 3- Recursive relationship is correctly drawn. If you see any mistake, correct it. Do corrections as soon as possible