Make certain that your Term Paper follows the below outline (you must include section labels in your submission):

0) Was the Term Project topic approved Yes or No (minimum 15% deduction, if not approved)
0) 10% writing style, organization of submission, clarity. YES it is approved

1) 5% Term Paper Abstract (include purpose and goal, explain one query – question – you expect the database to be able to process – the query MUST require the use of more than one table))
2) 5% Who will use, and who will administrator the database.
3) 10% Explain the design method / approach you followed – refer to design methods in our text.
4) 15% Describe the entities (tables), and attributes (fields). For each field: describe what the contents of each field represents, the type of field, and any constraints that you would like to see applied. Identify the primary key for each table. You may need to revisit this item at the end of the exercise, ensure all 3NF tables are explained and the fields in each.

SUGGESTION: Review the User Discussion of Multiplicity, Functional Dependencies, Related Normalization Terms and the Parts and Suppliers examples in Terms and Concepts Forum.

HINT: carefully review your entity (table) selections – for this exercise, 2 tables should not have the same primary key “and” keep in mind that tables will need to be linked together (to satisfy the one-to-many or many-to-many relationship requirement), if you start with an unnormalized or 1NF table – the normalization process helps to ensure the needed links are included – often we start with 2NF tables, and while that is OK – we still need to consider the links (sometimes foreign keys, sometimes additional tables are needed)

5) 15% Include one complete functional dependency analysis, ensure all fields in the database are included (at least once) – use the functional notation shown on page 413 Example 14.5. (Field1 à Field2) Also, explain at least one row of the submitted functional dependencies in plain English (stating field B depends on field A would not be sufficient – demonstrate that you understand functional dependencies), you may incorporate values for the determinant and functionally dependent field(s) to make the explanation easier.

6) Design (note – any table that uses an auto-number field for the primary key must be accompanied by significant explanation as to why that is the only approach to determining a primary key for that table)
a) (15%) Submit a complete set of 2NF tables, include the second normal form definition from the Connolly text, or the Terms and Techniques Forum as a basis to explain why the tablesare in 2NF. Additionally, include some plain English – possibly using some fields in one of your tables – to explain this in your own words. You need to demonstrate an understanding of the definition and how it applies to this exercise. (If your 2NF tables are the same as your 3NF tables – include them in 6a and again in 6b, with the appropriate explanations.

You must use the shorthand representation shown near the bottom of page 423 “Table-name (field, field1, field2…)”, look at page 111 which uses the notation to describe the tables on page 112 of the Connolly text (there is also a set of table notations on pg. 149 that describes the same tables), ensure you underline the primary key fields. DO NOT INCLUDE SPREADSHEET LIKE FIGURES.

b) (15%) Submit a complete set of 3NF tables, include the third normal form definition from the Connolly text, or the Terms and Techniques Forum as a basis to explain why the tables are in 3NF. Additionally, include some plain English – possibly using some fields in one of your tables – to explain this in your own words. Again, use standard notation to describe the tables. The same tables may be in 2NF and 3NF, which means the same tables might appear in 6a and 6b – but with different rationale.

c) (10%) Using table and field names, explain the one-to-many or the many-to-many relationship included in your design.

Submit a Word compatible document. Name your document Last Name_TermProject (i.e. Smith_TermProject). (500 word minimum)

Database Management Systems school INFO321