The goal of the Term Project Proposal and the Term Project is to work through key steps in the design of a very basic relational database. Keep the topic “simple”, only 2 entities are needed to a

The goal of the Term Project Proposal and the Term Project is to work through key steps in the design of a very basic relational database. Keep the topic “simple”, only 2 entities are needed to apply the concepts covered in the course.

For this assignment, we select a topic, and entities. We will also describe the entities and the relationship between them (include only 2 entities, avoid additional entities, they add to the complexity). The topic must be based on a one-to-many or a many-to-many relationship.

The database design will be completed in the Term Project exercise. By examining the functional dependencies and working through the normalization process we will finalize the tables needed. A separate bonus assignment will allow you to earn points (2%) by creating an Access DB that matches your design.

The exercise feedback will include an “approved” (sometimes with conditions) or “not approved” statement. If your topic is not approved, you will be given an opportunity to adapt your topic or chose a new topic. Your term project topic must be approved – if you submit a Term Project without approval, the Term Project assignment grade will be materially impacted.

Follow the outline below (you must include the outline as section labels in your submission, the proposal must be 700+ words in length). 1) Project Name. (5%) Name of the project2) Purpose. (10%) Explain the purpose of the database.3) Entities.  (20%) 

3.1 Describe the entities that will be the focus of the project (You only need 2 entities – be careful – limit your topic – contact the instructor if you are having difficulty). 

3.2 Discuss the type of information to be stored in each entity, and what a row in each entity represents. You are strongly urged to limit this to 2 entities. IF you include more than 2 entities – explain why. 

3.3  Define each entity using the phrase "EntityName is a ....." and complete the defitnion.  For example a"A Student is a person who is enrolled in the university."

3.3 For each entity you need to list the attributes and the primary key. Also designate the foreign key field(s). Use the following format:

Department(DeptID, DeptName, Location) The primary key is DeptID.  

Employee(EmpID, FirstName, LastName, Street, City, Zip, Phone, DeptID)  The primary key id EmpID.  DeptID serves as a foreign key.

4) Questions. (10%) What question would you like the database to be able to process – the question should require content from both proposed entities.5)  Users and Administrators. (10%) Users and administrators – explain who will use and who administer the database.6) Recording and Used Without Database. (10%) Explain how this information would be recorded and used without a database7) Relationship. (15%)

7.1  Explain the relationship between the entities. 

7.2  You must have a one-to-many or a many-to-many relationship between the proposed entities – explain how you expect each row in one entity (table) will relate to a row or rows in the other table (entity).  

7.3 Note that if you have a many-to-many (N:M) relationship you must create a new entity type (named like Entity1NameEntity2Name for example) whose primary key will be the composite primary key of the two two entities.  The attributes in this composite PK will also be foreign keys.

7.4  Include statements reflecting the relationships and multiplicity constraints in both directions.  For example consider the following:

Each Department may have many Employee(s) assigned.

Each Employee may be assigned to a Department.

Note that  the above example accommodates the business rules:

1)  An employee may not be assigned to a Department (the president for example).  

2)  A Department may not have any Employee assigned to it as well (like when it is first set up).  

These business rules may not apply to all organizations.

8) (20%) Submission organization, clarity of content, grammar, writing style, APA guidelines.Restrict your use of direct quotes (copy and paste) to less than 15% of the submission (the grade will be impacted if you exceed this limit).

Here is a list of topics that will be rejected: projects that track statistics, keeping track of movies or DVDs, Recipes, Students and Classes, modifications to examples in our text, or examples in other textbooks (Premier Products, Henry Books, Marina Group, Orders and Parts, Customer and Orders, or Customers and Products), Cars and Owners, Owners and Rental locations, Products or Parts / Suppliers, IT asset tracking, Books and Authors, Physical fitness tracking, Flight and Tail-numbers, and Game based topics.

Submit a Word compatible document. Name your document Last Name_ProjectProposal (i.e. Smith_ProjectProposal).

And

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) Abstract.  (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) Users and Administrators. (5%) Who will use, and who will administrator the database.3) Design Method. (10%) Explain the design method / approach you followed – refer to design methods in our text.4) Entities.  (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) Functional Dependency Analysis. (15%) Using the functional notation shown on pages 410-413 Examples14.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 NOTE16) Relationships.  (10%) 

6.1 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

 6.2  Include statements reflecting the relationships and multiplicity constraints in both directions.  For example consider the following:

Each Department may have many Employee(s) assigned.

Each Employee may be assigned to a Department.

Note that  the above example accommodates the business rules:

1)  An employee may not be assigned to a Department (the president for example).  

2)  A Department may not have any Employee assigned to it as well (like when it is first set up).  

These business rules may not apply to all organizations

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.  Identify any PKs or FKs.  PKs are underlined and FKs are designated in italics.  You cans also state them in sentences to be safe. 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.  Identify any PKs or FKs.  PKs are underlined and FKs are designated in italics.  You cans also state them in sentences to be safe.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. Identify any PKs or FKs.  PKs are underlined and FKs are designated in italics.  You cans also state them in sentences to be safe.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 -> Field2Field1 -> Field2, Field3Field4, 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)