Week 3 Assignment Grading Rubric:
|#8.17||0.6 points||#10.23a||0.2 points|
|#8.26||0.6 points||#10.23b||0.3 points|
|#9.3||0.6 points||#10.23c||0.3 points|
|#9.4||0.6 points||#10.23d||0.3 points|
|#10.22||0.6 points||#10.23e||0.3 points|
Here are the contents of Assignment #3 (however – please use the template attached – don’t copy and paste from here):
CH 8: THE ENHANCED ENTITY-RELATIONSHIP (EER) MODEL
#8.17 – Consider the BANK ER schema of Figure 7.21, and suppose that it is necessary to keep track of different types of ACCOUNTS (SAVINGS_ACCTS, CHECKING_ACCTS, …) and LOANS (CAR_LOANS, HOME_LOANS, …). Suppose that it is also desirable to keep track of each account’s TRANSACTIONs (deposits, withdrawals, checks, …) and each loan’s PAYMENTs; both of these include the amount, date, time, … Modify the BANK schema, using ER and EER concepts of specialization and generalization. State any assumptions you make about the additional requirements. (You may use Visio)
#8.26 – Which of the following EER diagram(s) is/are incorrect and why? State clearly any assumptions you make. (refer to the diagrams in your text – they are not too clear here).
CH 9: RELATIONAL DATABASE DESIGN BY ER- AND EER-TO-RELATIONAL MAPPING
#9.3 – Try to map the relational schema of Figure 6.14 into an ER schema. This is part of a process known as reverse engineering, where a conceptual schema is created for an existing implemented database. State any assumptions you make.
#9.4 – Figure 9.8 shows an ER schema for a database that may be used to keep track of transport ships and their locations for maritime authorities. Map this schema into a relational schema, and specify all primary keys and foreign keys.
CH 10: PRACTICAL DATABASE DESIGN METHODOLOGY AND USE OF UML DIAGRAMS
#10.22 – What are the current relational DBMSs that dominate the market? Pick one that you are familiar with and show how it measures up based on the criteria laid out in Section 10.2.3?
#10.23 – A possible DDL corresponding to Figure 3.1 is shown below:
CREATE TABLE STUDENT (
NAME VARCHAR(30) NOT NULL,
SSN CHAR(9) PRIMARY KEY,
Discuss the following detailed design decisions:
a. The choice of requiring NAME to be NON NULL.
b. Selection of SSN as the PRIMARY KEY.
c. Choice of field sizes and precision.
d. Any modification of the fields defined in this database.
e. Any constraints on individual fields.
#10.24 – What naming conventions can you develop to help identify foreign keys more efficiently?
The post Discuss the following detailed design decisions: appeared first on Homework Handlers.