Please read question in comment section,.
Page 1 of 2
Course Project Rubric
Criteria Description Level Weight
Format and
Neatness
High
10 Medium
Low
Entity-
Relationship
Diagram
All significant entity types defined with sufficient attribute descriptions;
Primary key for entity types defined where appropriate;
All significant relationship types defined between entity with cardinality and
participation constraints;
Generalization/specialization used where appropriate
High
30
All significant entity types defined with insufficient attribute descriptions;
Some necessary primary keys not defined;
All significant relationship types defined with missing or incorrect cardinality and
participation constraints;
Generalization/specialization opportunities missed
Medium
Some significant entity types missing or many missing attribute descriptions;
Few primary key definitions;
Some significant relationship types missing or few cardinality and participation
constraints defined;
All generalization/specialization opportunities missed
Low
Relational
Schema
All tables generated from entity types and from relationship types as necessary for
many-to-many relationship types
Complex attributes/repeated attributes flattened
Borrowed attributes and foreign key definitions as necessary for relationship
cardinality and participation and strong/weak relationships
Decisions for generalization/specialization are appropriate for the
overlapping/disjoint and mandatory/optional constraints;
All tables are in Third Normal Form
High
25
All tables generated from entity types, but many-to-many relationship types not
represented as table when necessary
Missing or incomplete attribute borrowing or foreign key definition for relationship
cardinality/participation or strong/weak relationships
Decisions for generalization/specialization do not completely consider the
overlapping/disjoint and mandatory/optional constraints;
A few tables are not Third Normal Form
Medium
Some tables needed for entity types are missing or no tables for many-to-many
relationships
Little of the needed attribute borrowing is done and/or few needed foreign key
constraints are defined
Decisions for generalization/specialization ignore the overlapping/disjoint and
mandatory/optional constraints;
Several tables not in Third Normal Form
Low
Relational
Implementation
(SQL DDL)
All tables in relational schema have create table statements
All attributes have correct domains
All necessary primary key, alternate key, and foreign key constraints are defined
Any other column or table constraints required on attribute domains are defined
Any needed view are defined
High
15
All tables in relational schema have create table statements
Some attributes have non-optimal, but permissable domains Medium
Page 2 of 2
A few missing primary key, alternate key, or foreign key constraints
Missing needed column or tables constraints on attribute domains.
Missing view definitions
Missing create table statement(s) for table(s) in relational schedule
Some attribute domains are in-appropriate for the data they must hold.
No or few primary key, alternate key, or foreign key constraints
No or few needed column or table constraints on attribute domains
Low
Table Population
All tables populated with sufficient data values to demonstrate operational integrity
of database
Data in parent (referenced) tables reflected in child (referencing) tables allows
adequate join testing
High
5 Some tables thinly populated
Child (referencing) tables data insufficient for complete join testing Medium
Some tables not populated
Data does not support many need joins Low
Operational
Testing
Ten (or more) queries are submitted
All queries correctly retrieve data requested and only the data requested and in the
form specified
Queries label data reported meaningfully (including columns for aggregate
functions)
Use of join syntax as appropriate rather than cross product syntax
High
15 Ten queries are submitted
All queries correctly retrieve requested data, but with additional information not
requested
Column labels used in query not defined where needed (especially for aggregate
function results)
Some use of cross product syntax rather than join syntax
Medium
Fewer than ten queries
Some queries do not produce the correct results
No use join syntax
Low
Total 100