Quick database project

Problem Statement In a text file, submit a 2 - 3-paragraph problem statement describing the need for the database you are creating. The statement should overview the current environment, what your database will do, and how the environment will be better after they start using your database. Entity Relationship Diagram Submit an Entity Relationship Diagram of your entire database design according to the following guidelines: Your database should include at least 5 tables. Each table should be related to at least one other table. You must identify all primary and foreign keys in all tables. Your design should be in 3NF or higher (if not, you must document why). Your database tables and fields should follow a consistent naming convention. Submit the ERD as an image (PNG preferred). SQL CREATE Statements Submit the SQL Statements necessary to create your database according to the following guidelines: Your SQL statements should exactly mirror your ERD. All primary keys, foreign keys, and relationships should be implemented in your SQL statements. You do not have to include the CREATE DATABASE command, as your instructor will assume the database has already been created and selected. Include DROP TABLE statements before your CREATE TABLE statements so your script can be run multiple times. Submit your SQL CREATE Statements as one text file, with a .sql extension. SQL INSERT Statements Submit SQL INSERT Statements that will populate the database with sample data. You must insert at least 5 records into each table in your database. Submit your SQL INSERT Statements as one text file, with a .sql extension. SQL SELECT Statements Submit SQL SELECT Statements to demonstrate several reports off your database, according to the following guidelines: You must submit at least 5 SELECT Statements. Each statement must select data from more than one table. Each table should be selected from by at least one statement. You must use at least one aggregate function (e.g. sum, count, max, avg, etc.). Each statement should have a WHERE clause. Each statement should have an ORDER BY clause. When selecting data from multiple tables, do not use "old-style joins" with the tables delimited in the FROM clause. Use the JOIN clause instead. Submit your SQL SELECT Statements as one text file, with a .sql extension. Suggestions Here are some suggestions for creating a successful Final Project: You might be stumped trying to come up with what tables and fields to create in your ERD. One suggestion for brainstorming is to make a list of all the questions you might ask of the resulting database. For instance, if you create a course registration system, you might ask the following questions. "How many students are enrolled in each class?" "What students does Professor X have this semester?" "What courses has Johnny taken during his entire career as a student?" Then, once you have a good list of questions, start identifying all the fields that would be necessary to answer the questions. Think about what entities in which those fields might exist, and then think about how the entities would have to relate in order to answer the question. After you create your ERD with DBDesigner, use its built-in function to generate a script that will actually create your database. This is a very helpful tool, and it validates that you have done your ERD correctly. This tool also ensures that your CREATE statements exactly mirror your ERD; it saves a lot of typing as well. Make sure you actually test your SQL statements in your own MySQL environment before submitting them. Significant points will be deducted if the statements do not actually run. Insert actual meaningful data into your tables. Then when you create your SELECT statements, it will be much easier to validate whether or not they are actually giving you correct information.