Submit to Canvas on or before midnight on Thursday, October 8.
(Typed, not handwritten. It should be plain text, MS Word, or PDF.)
Before you begin, write a one-paragraph summary
of what your project application domain is. In other words, remind me of
your project and what you promised to do in it. Also, if I gave
you comments, corrections, or suggestions about Part 2 of your project,
address those modifications first, before you proceed with Part 3. (If your
ER diagram required change, you will need to submit the changed ER diagram as part of Part 3.)
To Do: Convert your ER diagram to relations. Do
not normalize yet. (We have not covered database normalization in
class yet.) Follow the procedures taught in class and described in the
textbook. For your solution, submit a list of relation schemas. Write
down the schema as a series of SQL "create table" commands, in
correct syntax, as shown in textbook examples. (See Section 5.3.2, particularly page 159
in the 3rd edition.)
Attach an up-to-date copy of your ER diagram (modified and corrected based on
our comments, if required) to your answer.
Pick suitable data types for each attribute.
Do not forget to specify at least one key for each relation (using the
PRIMARY KEY constraint).
What to turn in: Digital or paper copies of ER diagram and resulting relations.
(Relation definitions typed.)
Including the up-to-date ER diagram is required, so that I can verify that you did the
conversion correctly. Identify your group by your project title and the
team members. As always, note any additional constraints or restrictions
that your domain possesses that are not reflected in your model.
Required but not graded: Include one sentence per group member summarizing
each group member's contribution to Project Part 3. These sentences will be
required in all project parts from here on. They are not for part of any student
grades. They will be used to monitor group dynamics.
Common mistakes:
Unrealistic data type selection:
For those students who consider 20 (or 10, or 30) characters enough to store a human name,
please take a look at
the full name of Pablo Picasso, the famous painter.
When selecting a data type for an address, consider
the names of these places before you decide that 30 characters is enough to store a full address.
There are less than ten billion people on the planet, at present. Eleven decimal
digits would be needed to uniquely identify all presently alive. Very, very few
businesses will have that many customers.
Entities / relationships / tables may be removed from your project
only with written permission from the professor.
Font size must be 10 pt or larger. E-R diagram from Part 2 must be "full size";
do not shrink the diagram down to a tiny size.