CS371 Database Design Executive Summary

Availability: In stock

Regular Price: $25.00

Special Price: $20.00

OR

CS371 Database Design Executive Summary

Double click on above image to view full picture

Zoom Out
Zoom In

More Views

Quick Overview

CS371 Database Design Executive Summary


Write a proposal for the new database design to include:
An executive summary for the database project


Develop main project details
Explain the issues that exist with maintaining the data in its current form.
Explain the process of migrating the data in its current form to a well formed data model by highlighting the following in detail:
Identify required attributes that need to be tracked
Identify functional dependencies
Show the redesign in 1NF, 2NF, and 3NF (similar to figures 7.29, 7.31, 7.33)


Explain the project benefits of the data in its new form.


Create the E-R diagram of your relational tables using MySQL Workbench and include in proposal.


Propose some additional data items, which you believe may be beneficial to the University if tracked in your database (i.e. Descriptions, more info about the instructors and students, departments, etc). Describe the steps required to implement these additions.


Identify project risks


In addition to the proposal, in a separate file submit:
Provide the SQL statement required to create at least one of your tables.
Provide the SQL statement required to delete at least one of your tables.
Provide the SQL statement required to create a view which includes Course #, Course Name, Time, and Days only.
Identify at least one index, which you believe would improve performance. Explain your choice.
If you add a course description attribute to your course table, there may be some performance impacts imposed by the addition of this "text" field.

Regular Price: $25.00

Special Price: $20.00

Details

CS371 Database Design Executive Summary

Write a proposal for the new database design to include:
An executive summary for the database project

Develop main project details
Explain the issues that exist with maintaining the data in its current form.
Explain the process of migrating the data in its current form to a well formed data model by highlighting the following in detail:
Identify required attributes that need to be tracked
Identify functional dependencies
Show the redesign in 1NF, 2NF, and 3NF (similar to figures 7.29, 7.31, 7.33)

Explain the project benefits of the data in its new form.

Create the E-R diagram of your relational tables using MySQL Workbench and include in proposal.

Propose some additional data items, which you believe may be beneficial to the University if tracked in your database (i.e. Descriptions, more info about the instructors and students, departments, etc). Describe the steps required to implement these additions.

Identify project risks

In addition to the proposal, in a separate file submit:
Provide the SQL statement required to create at least one of your tables.
Provide the SQL statement required to delete at least one of your tables.
Provide the SQL statement required to create a view which includes Course #, Course Name, Time, and Days only.
Identify at least one index, which you believe would improve performance. Explain your choice.
If you add a course description attribute to your course table, there may be some performance impacts imposed by the addition of this "text" field.

Product Tags

Use spaces to separate tags. Use single quotes (') for phrases.