The document describes an assignment to design an entity relationship diagram (ERD) reflecting the data in an invoice. It lists the objectives of understanding how to design ERDs and defines the key elements that must be included in the assignment: entities, attributes, unique identifiers, relationships (optionality and cardinality), and foreign keys. It provides a rubric evaluating the ERD design on entities, attributes, and relationships modeled and how correctly they are captured, named, and structured in the ERD.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
93 views
Assignment # 1 - : (Total Marks: 100, Weight: 5%)
The document describes an assignment to design an entity relationship diagram (ERD) reflecting the data in an invoice. It lists the objectives of understanding how to design ERDs and defines the key elements that must be included in the assignment: entities, attributes, unique identifiers, relationships (optionality and cardinality), and foreign keys. It provides a rubric evaluating the ERD design on entities, attributes, and relationships modeled and how correctly they are captured, named, and structured in the ERD.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3
Database Design & SQL CSD 2206
Assignment # 1 - Group Work
(Total Marks: 100, Weight: 5%) Objectives: To understand and be able design entity relationship diagrams Assignment Question: The figure below shows an invoice. Design an ERD reflecting the data contained in this invoice. You will need to define: Entities Attributes Unique identifiers Relationship (optionality and cardinality) Foreign key Database Design & SQL CSD 2206 Database Design & SQL CSD 2206
Rubric:
Excellent (100%) Proficient Needs Not Evident (0-
80%-90% Improvement 20%) (70%) ER-Model 90-100% of the entities 80-89% of the entities 70-79% of the 0-69% of the entities Entities were captured were captured entities were were captured. 90-100% of the 80-89% of the identified captured. 0-69% of the identified entities used entities used correct 70-79% of the identified entities correct naming naming conventions. identified entities used correct naming conventions. There was no confusion used correct naming conventions. There was no confusion between attributes and conventions. There was confusion between attributes and entities There was no between attributes entities. confusion between and entities. attributes and entities. ER-Model 90-100% of the entities 80-89% of the entities 70-79% of the 0-69% of the entities Attributes modeled, contained the modeled contained the entities modeled modeled contained appropriate attributes. appropriate attributes. contained the the appropriate 90-100% of the 80-89% of the attributes appropriate attributes. attributes listed used listed used the correct attributes. 0-69% of the the correct naming naming conventions. 70-79% of the attributes listed used conventions. The Unique Identifier attributes listed used the correct naming The Unique Identifier where indicated was the correct naming conventions. where indicated was clearly labeled. conventions. The Unique Identifier clearly labeled The Unique where indicated was Identifier where not clearly labeled indicated was clearly labeled. ER-Model 90-100% of the 80-89% of the 70-79% of the 0-69% of relationships Relationshi relationships have the relationships have the relationships have the have the appropriate ps appropriate name, appropriate name, appropriate name, name, direction, direction, optionality, and direction, optionality, and direction, optionality, optionality and/or degree/cardinality. degree/cardinality and degree/cardinality. degree/cardinality.