I need help with this project picture and how to do it. I do not know how to complete this at all.

ITCS 3330 Applied Database Management

Database Design Project Due: 1 March 23 (option to turn in earlier for feedback)

Purposes: To give you experience with developing a database to model a real domain

Requirements

This project is deliberately made quite open-ended. It consists of the following four parts.

1. Choose a domain with which you are familiar. Identify a set of requirements for a system that is appropriate for this domain. (If you wish, you may choose an appropriate subset of a larger domain.)

2. Develop an E-R diagram for a database that models this domain (or the chosen subset).

3. Turn your E-R diagram into a database design for the (subset of the) domain - i.e. a set of tables, each with appropriate attributes, a primary key, and appropriate foreign keys. The database should be based on the E-R diagram.

a. Populate your database with sample data to allow testing of the schema and the various transactions.

b. Create (SQL as example) select/insert/update/delete statements that correspond to your initial requirements.

c. Thoroughly test your queries and your constraints using your sample data. Be sure to test using both good and bad data.

d. During the last class before finals, 15 October, you will present your work orally to your classmates in 2-3 PowerPoint slides.

Specific Project Output Expectations:

Part I - Requirements

A description of the problem domain, written using terminology that a user of the system would use, not technical database terminology.

A statement of requirements. This may take the form of an overall use case diagram.

Part II - E-R Diagram

An ER diagram for your database, including attributes for entities and relationships.

Part III - Database Design, Implementation, and Sample Data

A printout containing your (SQL as an example) statements that create the database or subset of a database.

Screenshots of the database in operation

Documentation of testing. You must turn in printouts of the results of these tests indicating that statements for your requirements worked correctly and that your constraints correctly allowed good data and caught bad data.

Your printouts may include comments (handwritten or entered as comments in a test file) that indicate what each test is testing - i.e. a specific requirement (if "good" data) or a specific problem you were catching (if testing a constraint on "bad" data).

Part IV - Presentation

To facilitate oral presentation and discussion, you will need to prepare approximately two (2) or three (3) PowerPoint slides. Assume the audience is your company Vice President with only limited knowledge of databases. Include your description of the problem, a diagram, the output or a component to demonstrate the database. These slides need to be turned in as part of the project on or by 14 October.