Course: Database Problem Description-to-ER Diagrams To Relational Model:

Design a database for each of the following problems. Draw a neat Entity-Relationship Diagram for each problem. Translate the diagram into a relational model. It is enough to show the table design like this:

TABLE_NAME(ColumnName1, ColumnName2, )

Underline the Primary Key.

Specify all the Foreign keys like this:

ColName FOREIGN KEY REFERENCES ANOTHER_TABLE(OtherColName).

a) An Internet store sends emails to customers and would like to use a database to keep track of which messages are sent to which customers. A message has a message id (mId), a subject, and a body. A customer is identified by the email address (email), and customer's data includes the attributes name, sex, householdSize, and address. When an email is sent, the date (sendDate) is recorded. You can assume any reasonable domains (types) for these attributes. (8 pts)

b) Design an Entity-Relationship schema for a database of research projects. The database should contain the information about: projects: name, manager, budget, duration (in years), funding agency; employees: SSN, name, projects, salary; funding agencies: name, address. Each project is funded by a single agency. Project names are unique within an agency. An employee can be associated with several projects. Managers are employees. You can make any other additional assumptions that make sense in the real world.