Assignment Instructions

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

0) Was the Term Project topic approved Yes or No (minimum 15% deduction, if not approved)

1) (5%) Term Paper Abstract (include the purpose of this “database”, explain one query – you expect the database to be able to process – the query MUST require the use of information from more than one entity)

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 initial entities (tables), and attributes (fields). Include an explanation of what a row represents in each table, and 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 and describe the field you believe could be the primary key for each entity.

5) (15%) Using the functional notation shown on pages 410-413 Examples 14.2, 14.3, 14.4 and 14.5, include a functional dependency analysis, ensure all fields in the database are included (at least once). Define functional dependency and explain one row of the functional notation using plain English, and fields from your project to demonstrate your understanding. SEE NOTE1?6) (10%) Using the table names, and what a row represents from each table, explain the one-to-many or the many-to-many table relationship(s) included in your design. SEE NOTE3??7) Design (it is possible that the same table or set of tables are in 1NF, 2NF, and 3NF; or 2NF and 3NF – in which case you need to repeat the tables for each normal form and explain why they meet that definition)

a) (10%) Using table notation - submit a complete set of 1NF tables (this may be one or more tables), include the first normal form definition from the Connolly text, or the Terms and Techniques Forum as a basis to explain why the tables are in 1NF. Additionally, include a plain English explanation – using fields in your tables – to explain this in your own words. You need to demonstrate an understanding of the definition, and how it applies to your project. Once your tables are in first normal form proceed to the next step. SEE NOTE2 below:

b) (10%) Using table notation - 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 tables are in 2NF. Additionally, include a plain English explanation – using fields in your tables – to explain this in your own words. You need to demonstrate an understanding of the definition, and how it applies to your project.

c) (10%) Using table notation - 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 a plain English explanation – using fields in your tables – to explain this in your own words.8) (10%) writing style, organization of submission, clarity, APA usage

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

Contact the instructor with any questions.

NOTE1: Generic functional notation examples:

Field1 -> Field2

Field1 -> Field2, Field3

Field4, Field5 -> Field6

NOTE2: You can find an example of table notation on page 111 immediately under 4.2.6 label which shows the relational schema for part of the Dream Home database.

The basic table notation structure is: Table-name (field, field1, field2…) underline the primary fields.

DO NOT INCLUDE SPREADSHEET FIGURES

NOTE3: Review the Chapter 12 Study Aid document, Table Relationships, and the Parts and Suppliers examples in the Terms and Concepts Forum – if you need to refresh your knowledge base.

HINT: review your tables – for this exercise, 2 tables should not have the same primary key “and” keep in mind that tables will need to be linked (to satisfy the one-to-many or many-to-many relationship requirement), if we start with a single unnormalized or 1NF table – the normalization process ensures the needed links are included – often we start with more than one table, and while that is OK – we need to ensure tables are properly linked (sometimes using foreign keys, and sometimes using a junction table)

TOPIC

Artists and paintings – create a database to track artists and their paintings.?For each artist we want to record – their first and last name, their country of birth, their date of birth, current city, street name, and street number address, their telephone number, and some general comments. You may want to assign a unique artist ID to each artist. For each painting we want to record, the name of the painting, the style, the date painted, the type of canvas used, and other fields you feel appropriate. I suggest assigning a unique painting ID to each painting – or stating that each painting name must be unique.?

Assume: each artist may paint many paintings; each painting is painted by a single artist.

“Real” data is not required; for the extra credit Access DB – you can make up names for painting, artists, etc.

A desired query (question) – list all artists and their paintings – sorted by artistic.