IST 210: Organization of Data

 	                  Fall 2008

                 Proj #2 (DUE: Oct. 30, 9:45AM)

           Last Updated: Mon Oct  7 09:12:28 EDT 2008


NOTE: Team Assignment (also available in ANGEL)

Proj #2 has FOUR parts:

1. Fix-up

Fix up all errors that were pointed out in your proj #1. Revise your
ER design and associated assumptions, etc.  NOTE that if any parts
from Proj #2 still contain errors because you fail to fix them up, you
will lose points again. If you do not understand my comments, talk to
me. I will help you.

2. ER to Relational Model

Show relational schema that are to be generated from your ER
design. In particular, for each table, you need to determine:

- Attribute: name, data type, and nullable or not

- Primary Key (PK) -- note that primary key attribute can't be null
Pay extra attention to those "Relationship" -- depending on whether
they are unary/binary/ternary or cardinality/modality, the resultant
table schema may vary.

- Foreign Key (FK) and Referential integrity (RI) constraint (ie,
delete-cascade, delete-restrict, or delete-null policy).

3. Data Population

For each table, populate at least ** FIVE ** bogus tuples. Since you
may need to modify your schema later, do not waste your effort on
populating a lot of tuples. In Proj #3, you will need to populate more
number of tuples per table.

Using your tables and data, show three exampls SQL queries (see Chap
5) that demonstrate: SELECT, PROJECT, and JOIN.

4. Normalization

Show that ALL of your generated tables are in 3rd Normal Form.


Part 2: Turn-In of Proj #2 Report

Your report should consist of at least the following:

- On the cover page, list project team name (e.g., Team-A), and all
  member names

- FIXED ER and assumptions, and description as to why your ER can
answer 10 scenarios

- Relational schema of all tables -- for each table, mention attribute
name and type, then primary and foreign keys. Also, mention what
referential integrity policy is used on what pair of attributes.

- Show that all of your tables are in 3NF.

- A screen-shot of all tables (using Query Design Editor in SQL
Server). Note that all tables must be linked via foreign keys
correctly. If any table is isolated, then your schema population is
not correct.

- A screenshot of three example queries (ie, SELECT, PROJECT, and
JOIN) and their results returned

- Short description of WHO did WHAT role in your team (all members
  must participate in the project)

Then, do ** BOTH **:

1. Drop one copy of report to ANGEL (otherwise, 70 points deduction)
2. Turn in one hard-copy of the report (otherwise, 10 points deduction)

If your project team has some problems (eg, some members don't
come to project meetings), you need to inform me early so that I
can intervene. Otherwise, all team members share the identical
scores for the projects.