Modify Database Design

Lab : Modifying a Database Design  

Worth 75 points

This assignment contains two (2) Sections: Modified Diagram and Design Summary. You must submit both sections as separate files in order to complete this assignment. 

If you’re using Visio, see “Appendix A: Designing Databases with Visio Professional 2010: A Tutorial” to help you complete Section 1: Modified Visio Database Design. (Note: This tutorial focuses on the use of Microsoft Visio. Open source applications are not covered in Appendix A. However, using open source applications or even pen and paper within labs is permitted.)

After reviewing your database design from Lab 1: Creating a Database Design, the college has provided more information for the database that they want developed:

  • For each student, the college needs to track the student  ID, student names, addresses, start date, phone numbers and types (such as mobile, home, work), email addresses and types (such as personal, school, work), gender, and birth date.

  • For each course, the college needs to track the course ID, course name, department, quarters offered, sections, and instructor teaching each course.

  • For each instructor, the college needs to track the instructor ID, name, address, phone numbers and types (such as mobile, home, work), email addresses and types (such as personal, school, work), gender, birth date, and the courses that each instructor is qualified to teach.

  • Additionally, the college needs to track the final grades for each student after each course has completed.

Section 1: Modified Diagram (Using Microsoft Visio is optional; you may also use any other application you know or even modify the diagram with pen and paper and take a picture of it for submission.)

  1. Use the application or pen and paper to:

    1. Modify the database diagram from Lab 1 with the entities and attributes that the scenario identified (i.e., a college tracking students, courses, and instructors).  

    2. Create the appropriate relationships between each entity within the diagram.

  2. Submit your modified diagram.

This is the original Diagram

Modify Database Design 1






Section 2: Design Summary (Microsoft Word or equivalent)

3. Write a one to two (1-2) page paper in which you:

  1. Discuss the degree to which you believe your diagram reflects the database design.  

  2. Describe any assumptions that you had to make about the business rules to in order to create the diagram and the associated relationships.

Section 2 of your assignment must follow these formatting requirements:

  • Submit the design summary as a Microsoft Word file.Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.

  • Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page is not included in the required assignment page length.

The specific course learning outcomes associated with this assignment are:

  • Describe the role of databases and database management systems in managing organizational data and information. 

  • Recognize the historical development of database management systems and logical data models. 

  • Compose conceptual data modeling techniques to capture the information requirements.

  • Use technology and information resources to research issues in database systems.

  • Write clearly and concisely about relational database management systems using proper writing mechanics and technical style conventions.

Grading for this assignment will be based on answer quality, logic/organization of the paper, and language and writing skills, using this rubric.

Points: 75

Criteria

 

Fair

70-79% C

 

Proficient

80-89% B

 

Exemplary

90-100% A

1a. Modify the database diagram from Lab 1 with the entities and attributes that the scenario identified (i.e., a college tracking students, courses, and instructors).

Weight: 30%

Partially modified the database diagram from Lab 1 with the entities and attributes that the scenario identified (i.e., a college tracking students, courses, and instructors).

Satisfactorily modified the database diagram from Lab 1 with the entities and attributes that the scenario identified (i.e., a college tracking students, courses, and instructors).

Thoroughly modified the database diagram from Lab 1 with the entities and attributes that the scenario identified (i.e., a college tracking students, courses, and instructors).

1b. Create the appropriate relationships between each entity within the diagram.

Weight: 30%

Partially created the appropriate relationships between each entity within the diagram.

Satisfactorily created the appropriate relationships between each entity within the diagram.

Thoroughly created the appropriate relationships between each entity within the diagram.

2a. Discuss the degree to which you believe the diagram reflects the database design.
Weight: 15%

Partially discussed the degree to which you believe the diagram reflects the database design.

Satisfactorily discussed the degree to which you believe the diagram reflects the database design.

Thoroughly discussed the degree to which you believe the diagram reflects the database design.

2b. Describe any assumptions that you had to make about the business rules to in order to create the diagram and the associated relationships.
Weight: 15%

Partiallydescribed any assumptions that you had to make about the business rules to in order to create the diagram and the associated relationships.

Satisfactorilydescribed any assumptions that you had to make about the business rules to in order to create the diagram and the associated relationships.

Thoroughlydescribed any assumptions that you had to make about the business rules to in order to create the diagram and the associated relationships.

3. Clarity, writing mechanics, and formatting requirements

Weight: 10%

5-6 errors present

3-4 errors present

0-2 errors present