Learning Objectives: Students will be able to

1. Create a UML physical model given a fully specified ER diagram

Instructions:

Using LucidChart (or a modeling tool of your choice) create two UML physical diagrams. One for the first case study and a different one for the second. Be sure to include your name and todays date on the diagrams, so I can keep track once Ive downloaded them

Case Study 1

The image for Case Study 1 is attached on Blackboard as Case_Study_1_ER.pdf The description below should help you determine appropriate data types

Consider a MAIL_ORDER database in which employees take orders for parts from customers. The data requirements are summarized as follows:

quirements are summarized as follows:

The mail order company has employees, each identified by a unique employee number, first and last name, and Zip Code.

Each customer of the company is identified by a unique customer number, first and last name, and Zip Code.

Each part sold by the company is identified by a unique part number, a part name, price, and quantity in stock.

Each order placed by a customer is taken by an employee and is given a unique order number. Each order contains specified quantities of one or more parts. Each order has a date of receipt as well as an expected ship date. The actual ship date is also recorded.

Case Study 2

The image for Case Study 2 is attached on Blackboard as Case_Study_2_ER.pdf The description below should help you determine appropriate data types.

Consider a CONFERENCE_REVIEW database in which researchers submit their research papers for consideration. Reviews by reviewers are recorded for use in the paper selection process. The database system caters primarily to reviewers who record answers to evaluation questions for each paper they review and make recommendations regarding whether to accept or reject the paper. The data requirements are summarized as follows:

Authors of papers are uniquely identified by e-mail id. First and last names are also recorded.

Each paper is assigned a unique identifier by the system and is described by a title, abstract, and the name of the electronic file containing the paper.

A paper may have multiple authors, but one of the authors is designated as the contact author

Reviewers of papers are uniquely identified by e-mail address. Each reviewers first name, last name, phone number, affiliation, and topics of interest are also recorded.

Each paper is assigned between two and four reviewers. A reviewer rates each paper assigned to him or her on a scale of 1 to 10 in four categories: technical merit, readability, originality, and relevance to the conference. Finally, each reviewer provides a 500 word minimum overall recommendation regarding each paper.

Each review contains two types of written comments: one to be seen by the review committee only and the other as feedback to the author(s).

Rubric:

make sure you include which attributes are primary or foreign keys, use understandable naming conventions for attribute and table names, and accurate data types. If you have questions or need clarification about the case studies, just ask.