Think about your proposed database idea, what tasks you want to perform with it$,$ and the

information you will need to perform those tasks.

Next, develop an initial design of your tables, and the fields in each table. Do not use Access

yet!!! We won't be building your database in Access until Part $4$ of the project.

Your database should have around $3-5$ tables $($Entities$)$ with $7-10$ fields $($Attributes$)$ for each

table. No tables should have the same name for each primary key! $($Same name indicates the

tables should be combined$).$ A good rule of thumb is to have a table that tracks something

that changes, such as a process or transaction. Use good consistent naming conventions $($no

characters, symbols, spaces, etc., using consistent keys$).$

Submit the following for Part $1-[$Idea$],$ you need all three parts for complete credit:

A description of your database project $($just a short paragraph with $2$ or $3$ sentences$),$ include

how you selected the project and why $($looking for the personal connection$).$

A representation of the structure of your database $($tables and fields$)$ with the primary key

underlined. Use the JC consulting database representation $($Relational Database Shorthand

section in the Concepts book$)$ as a guideline.

Example: TableName $($keyfield$,$ field$1,$ field$2,$ field$3)$A list of tasks$/$actions you will perform with your database $($i$.$e$.$ what are you going to do with

it$?!)$; these can be ideas for queries and reports which are outputs of a database. Think

summary $($stats$/$aggregates$),$ detailed, and exception type of reports. Think of a list of bullets

approximately $5-7$ items. Examples of action below:

A report to provide details on customers since $2010$

A query showing all the customers from a certain zipcode

A summary count of the top $5$ tools