Part I. Conceptual Database Design
Read a case study for “A Cross-National Research Database” attached.
1. Develop a (E)ER diagram to model the data requirement of the case study.
In the (E)ER-diagram, (i) properly name entity type, attribute, and relationship types, (ii) denote the key(s) of each entity type and if the entity type is weak, try to find a partial key for the entity, (iii) distinguish attributes with their type (e.g., multivalued/composite/complex/required/derived attribute) using their notations, (iv) denote maximum and minimum cardinalities on each relationship, and lastly (v) if there is an IS-A relationship, denote a disjointness constraint (distinct/overlap) and a completeness constraint (total/partial) on the relationship clearly.
If you used any assumption in developing the conceptual scheme, clearly describe it so that the grader can understand it.
For the (E)ER diagram, use Chen’s notations (class slide notations). You can use any drawing tool or database modeling tool (e.g., ERwin, Rational). For example, MS Visio supports Chen’s notations for data modeling.
2. Develop the corresponding UML class diagram to model the data requirement. Give some getter and setter methods and other methods expected in each class. Denote associations clearly between classes.
Students succeed in their courses by connecting and communicating with an expert until they receive help on their questions
Consult our trusted tutors.