IT 650 Principles of Database and Design

IT 650 Short Paper Rubric This short paper will allow you to explore database normalization. Database textbooks and tutorials emphasize the need to ensure normalization of the database. While database designers and database administrators will generally ensure that their databases follow best practices relative to normalization, many production databases in use today have ignored normalization. Some people will argue that a denormalized production database reflects poor design, while others will argue that good database architects will knowingly deploy a denormalized database under the right circumstances. After completing the textbook readings and performing some research on the topic of database normalization, discuss your thoughts on the topic of deploying a denormalized database versus a normalized database. Specifically, address the following critical elements:

I. Define, analyze, and compare a denormalized database and a normalized database. II. Define the circumstances under which you consider it reasonable to deploy a denormalized database, or explain why you feel it is not reasonable to do

so. III. Explain the extent to which your final project’s database will be normalized and why.

Guidelines for Submission: Your submission should be one to two pages in length (not including the title page and references). The document should use double spacing, 12-point Times New Roman font, and one-inch margins. Citations should follow APA format.

Critical Elements Exemplary (100%) Proficient (90%) Needs Improvement (70%) Not Evident (0%) Value

Define, Analyze, and Compare

Meets “Proficient” criteria and supports explanation with clear and relevant examples using scholarly research when appropriate

Defines, analyzes, and compares a denormalized database and a normalized database, using database vocabulary and terminology

Defines denormalized and normalized databases but does not compare the two, and/or analysis is insufficient

Does not define, analyze, or compare the database types

30

Define the Circumstances

Meets “Proficient” criteria and supports explanation with clear and relevant examples using scholarly research when appropriate

Clearly defines the circumstances under which it is reasonable to deploy a denormalized database (or explains why it is not reasonable to do so), using basic database vocabulary and terminology

Defines the circumstances under which it is reasonable to deploy a denormalized database (or explains why it is not reasonable to do so) but lacks basic database vocabulary and terminology and/or ideas are not clear

Does not define the circumstances under which it is reasonable to deploy a denormalized database (or does not explain why it is unreasonable to do so)

30

Explain Relation to Final Project

Meets “Proficient” criteria and supports explanation with clear and relevant examples using scholarly research when appropriate

Explains the extent to which the final project’s database will be normalized and why, utilizing database vocabulary, terminology, and specific details

Explains the extent to which the final project’s database will be normalized but lacks basic database vocabulary and terminology, and/or ideas are not clear

Does not explain the extent to which the final project’s database will be normalized and why

30

Articulation of Response

Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy to read format

Submission has no major errors related to citations, grammar, spelling, syntax, or organization

Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas

Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas

10

Total: 100%