Databases - Entity Relationship Diagram (ERD) & Data Dictionary

Improve on existing ERD from Case Study 1, full details attached. Only have to complete part 1 and 2 from Case Study 2.

Part 1

a) Create and submit the ERD for this database that you are going to use as the basis of your implementation.

b) Include a one or two paragraph explanation as to the changes you have made to the ERD on the basis of your feedback from the ERD done in Case Study 1 and/or as a result of having to support the new functionality and views described.

c) Show the relational schema in 3NF that will be the basis of your implemented design. Show your relations using the following convention: RELATION_NAME (PrimaryKey, Attribute, Attribute, … ForeignKey)

Part 2: Data Dictionary

Create a data dictionary for your database. This should include:

a) For each table: a definition of each column (attribute), consisting of the column name, brief description of what it represents, its data type and size, domain (allowable values), any default value, whether it is required, whether unique, and any constraints (primary key, foreign key).

Use the data types available in Oracle.

b) For each of the columns that is a foreign key, give the appropriate referential integrity rules (i.e. the “on delete…. ; on update“ etc actions that should apply when the corresponding primary key is altered). The appropriate action should be included whether or not there is a statement in Oracle to implement it.

c) Any business rules (enterprise constraints) that should apply to the database that haven’t already been covered by cardinality or participation constraints.

Note that your data dictionary must be consistent with your ERD and schema.

Adatbázis-fejlesztés Adatbázis-programozás Adatbázisfelügyelet Oracle UML-tervezés

Projektazonosító: #20419637

A projektről