IT 650 Principles of Design and Database

IT 650 Milestone Two Rubric Submit the preliminary design of the database for the final project. Devise a conceptual model that will best address the case study scenario you selected for the final project. Your model should include all necessary entities, relationships, attributes, and business rules. Based on the conceptual model, illustrate a logical model for your DBMS that accurately represents all necessary aspects of the DBMS to address the solution. Create a physical database design that builds on the nonphysical (conceptual and logical) models you crafted. This design includes the conceptual and logical models of the database, as well as the physical design of the database. Specifically, the following critical elements must be addressed:

 Analysis and Design A. Conceptual Model: Based on the business problem or challenge, devise a conceptual model that would best address the problem. Your model

should include all necessary entities, relationships, attributes, and business rules. B. Logical Model: Based on the conceptual model, illustrate a logical model for your DBMS that accurately represents all necessary aspects of the

DBMS to address the solution. C. Physical Design: Create a physical database design that builds on the nonphysical (conceptual and logical) models you crafted.

Guidelines for Submission: Your paper must be submitted as a 6- to 12-page Microsoft Word document using appropriate modeling language and/or diagrams. It should use double spacing, 12-point Times New Roman font, and one-inch margins. It should include at least three sources, which should be cited in APA format.

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

Analysis and Design: Conceptual Model

Meets “Proficient” criteria, and model evidences detailed attention or keen insight into conceptual design needs and skills

Devises a comprehensive conceptual model that would logically address the identified problem

Devises a conceptual model that does not attend to all necessary entities, relationships, attributes, and business rules or would not logically address the identified problem

Does not devise a conceptual model

30

Analysis and Design: Logical Model

Meets “Proficient” criteria and evidences keen insight into representation, communication, or depiction of logical model design needs for business scenarios

Illustrates an accurate logical model that details the necessary aspects of the DBMS needed to address the business needs and identified problem

Illustrates a logical model that lacks accuracy or necessary detail regarding aspects of the DBMS needed to address the business needs and identified problem

Does not illustrate a logical model 30

Analysis and Design: Physical Design

Meets “Proficient” criteria and exemplifies the knowledge and skills necessary to extrapolate a physical design from nonphysical models for solving data challenges

Creates a physical design that precisely builds on the nonphysical models with incorporation of physical aspects

Creates a physical design that builds on the nonphysical models with incorporation of physical aspects, but with a lack of precision

Does not create a physical design that builds on the nonphysical models with incorporation of physical aspects

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%