The final assignment for this course is an eight to ten page Final Project according to APA style. The purpose of the Final Project is for you to culminate the learning achieved in the course by describing your understanding and application of knowledge in the field of database management systems through the creation of a proposed database system to meet the data needs of a business or individual personal needs.  This is a cumulative assignment where you will complete most sections of the Final Assignment during your weekly course activities.

Include the following major points in your paper:

• Introduction
• Background:
  • Describe the proposed new database system- NEW DATA BASE FOR BOOKS
  • What business requirements or personal requirements will be satisfied by your proposed database system?
  • Who will be the users of the database system?
  • What specific functionalities will your completed database system provide?
• Structure (Conceptual):
  • What are data items that should be in your database?
  • Entities become tables in a database.  List all entities for your database.  List a minimum of 5 entities.
• Structure (Logical)
  • Attributes become fields in a table.  Attributes describe entities (For example, a Customer entity could have attributes such as: name, address, and telephone number).  List a minimum of 5 attributes for each entity.
• Relationships and Constraints (Logical):
  • Define constraints/restrictions for at least two attributes in each entity. (e.g., Number of digits in student ID, range of values for Age attribute, an employee’s salary must be between 6,000 and 350,000 …)  If some attribute should not be NULL, use NOT NULL to specify this aspect. Also provide DEFAULT values wherever applicable.
  • Define relationships between entities in your database. A relationship describes an association among entities [one-to-many ex. a Painter can have many Paintings, many-to-many e.g., An employee may learn many job skills, and each job skill may be learned by many employees, or one-to-one e.g. a store is managed by a single employee and an employee manages only a single store.
•  Entity Model:
  • Create Entity-Relation (ER) model of your database.
• Keys (Physical):
  • Specify Primary Keys on your Entity Relationship Diagram.
  • In a foreign key reference, a link is created between two tables when the column or columns that hold the primary key value for one table are referenced by the column or columns in another table. This column becomes a foreign key in the second table.
  • Identify and discuss at least two foreign keys in your table relationships.
  • Keys are one way to categorize attributes. A primary key is an attribute or combination of attributes that uniquely identifies one and only one instance of an entity. The primary key becomes a foreign key in any entity type to which it’s related through a one-to-one or one-to-many relationship.
• SQL (Physical):
  • Use the Week3 Understanding Core Database Concepts Exercise 1 instructions to execute your CREATE Table statement for one of your proposed tables.
  • Take a screen shot of your query results.  Copy your query statement and add the screenshot of your query results to a MS Word document or PDF for upload.
  • Use the Week3 Understanding Core Database Concepts Exercise 1 instructions to execute your INSERT statement.
  • Take a screen shot of your query results.  Copy your query statement and add the screenshot of your query results to a MS Word document or PDF for upload.
  • Provide the SQL CREATE TABLE commands for the five tables in your proposed database.  Include PRIMARY KEY and NOT NULL commands.
  • Provide the SQL INSERT commands to insert five rows of data into your five tables.
• Views:
  • Use the Week3 Working with Views instructions to execute your CREATE VIEW statements.
    • Take a screen shot of your query results.
    • Copy your query statement and add the screenshot of your query results to a MS Word document or PDF for upload.
  • Provide the CREATE VIEW commands to create two views for your database.
• Normalization:
  • Analyze your five tables and confirm if normalization is needed to avoid data redundancy and ensure the efficient and reliable management of data.  Justify your position.
• Security and Impact of Globalization Diversity:
  • Protecting data security, privacy, and integrity as well as managing impacts of diversity are important database functions.  Identify key activities that are required in the DBA’s managerial role of enforcing those functions in your proposed database?
• Distributed or Centralized
  • Justify whether your proposed database has to be distributed or centralized?
• Summary

The Final Project – My Database System

• Must be eight to ten double-spaced pages in length (not including title and references pages) and formatted according to APA style as outlined in the UAGC Writing Center.
  • Must include a separate title page with the following:
  • Title of paper
  • Student’s name
  • Course name and number
  • Instructor’s name
  • Date submitted
• Must use at least three scholarly sources in addition to the course text.
  • The Scholarly, Peer Reviewed, and Other Credible Sources  Download Scholarly, Peer Reviewed, and Other Credible Sourcestable offers additional guidance on appropriate source types. If you have questions about whether a specific source is appropriate for this assignment, please contact your instructor. Your instructor has the final say about the appropriateness of a specific source for a particular assignment.
• Must document all sources in APA style as outlined in the UAGC Writing Center.
• Must include a separate references page that is formatted according to APA style as outlined in the UAGC Writing Center.

After reviewing the work to date, I think it would be most helpful, for you and for me, to include a “data dictionary” in the FINAL PROJECT submission. It will look much like the example below but it should contain a description of each attribute (b/c there are many attributes with characters, which is good),  constraints, PK, FK. I’m providing a link to images of a data dictionary you can refer to, data dictionary  . The data dictionary does not have to be complicated, but it definitely outlines the entities, attributes, PK, Constraints.

We’re nearly to the end! Week 5 is upon us so it is time to review our Week 1 thru Week 4 assignments to reflect on the work completed thus far. YES, this is the FINAL PROJECT Week, and I look forward to reading some excellent database proposals! As you begin your final project write-up, I would like you to use side headings to organize each area to be covered on the rubric: Introduction, Background, etc. 

With that said, this is my recommendation moving forward with this project:

• As you finalize your work on the “final project” this weekend, ensure that you’ve covered these bullet points:
  • Review the background information that you submitted in Week 1. Review and write a clear description of the database and how this database will satisfy business requirements or personal requirements.
  • Identify the users — that means all stakeholders who might interact with this system.
  • What exactly will the database do (functionalities). In the end we want our databases to create reports for management in order to enhance decision making, inventory control, etc. What other business areas will be impacted? (Accounting, finance, etc.)
  • Conceptual and Logical Structure — I strongly recommend using a format like this for each table in your database. This is what we call a “data dictionary”. You can use the Insert tab in Word — Create table, Identify column headings and then provide row content.

ENTITY NAME

Attribute (Field) Name

Data Type

Sample Data

Constraints

*Use asterisk to identify Primary Key

Be sure to define relationships between tables as identified on page 36 of our course guide.

• Create an ER Diagram (you have done this but you may need to review it).
• Write the SQL statements (page 37) of our course guide. You have some of this done but will need to review and possibly revise.
• Normalization; follow instructions
• Describe how you plan to secure database functions (this impacts privacy, integrity and the diversity of the database). Week 4 content
• Distributed or Centralized — “justify” your position
• Summary — provide an interesting conclusion which may include the process for developing this database. We have used a week to week migration to the final project but you do need to review and revise as necessary.

Finally, this week’s discussions will facilitate your understanding of the legal, ethical and globalization challenges of database administration. Please post your initial response to both discussion questions by Thursday of Week 5; you have until Monday to post responses to your classmates. Please maximize your points by responding to classmates.

All have done an excellent job thus far; the Final Project is a BIG DEAL — worth 30 points! Please work diligently on this.