detailed-erd-the-erd-must-be-done-using-an-approved-design-software-e-g-mysql-workbench-1

SECTION 7: DETAILED ERD (1.75 points)

• Starts on a new page.
• The ERD must be done using an approved design software (e.g. MySQL Workbench)
• You must include a picture (or more) of the design in the document. Be sure it is big enough so all text is clearly readable.
• Attach also the source file for your design.

Please be sure your diagram includes:

• ENTITIES (0.75 points)
  • Entity name (follow conventions, relevant) 0.25 points
  • Attributes 0.25 points
  • Constraints (PK, UQ, NN) 0.25 points
• RELATIONSHIPS (1 point)
  • Relationship names (0.2 points)
  • Relationship types (0.2 points)
  • Relationship strength (0.2 points)
  • Relationship participation for each entity (0.2 points)
  • FK in the child entity (0.2 points)

SECTION 8: SAMPLE 3 ENTITIES EXPLANATIONS (0.75 points)

• Starts on a new page.
• Pick 3 complex entities that are directly connected by relationships.
• For each entity answer the following in different sub-section (8.1, 8.2 and 8.3) (0.25 points each)
  • the name of the entity – why you choose that name
  • the requirements that are related to that entity
  • the PK of the entity, what type is composite or simple and why, and why you choose it (why is good)
  • for each attribute:
    • The name of the attribute (why you choose it)
    • Simple or composite attribute (why it is)
    • Single value or multi value attribute (why it is)
    • Required or optional and why
    • Unique or not unique and why

SECTION 9: SAMPLE 3 RELATIONSHIPS EXPLANATIONS (0.75 points)

• Starts on a new page.
• Pick 3 relationships, related to the presented entities.
• For each relationship answer the following in different sub-section (9.1, 9.2 and 9.3) (0.25 points each)
  • Relationship names and inverse names
  • All requirements related to that relationship
  • Relationship types and why you selected that type
  • Relationship strength and why you selected that strength
  • Relationship participation for each entity and why you selected that participation
  • FK in the child entity, explain what it references