Write the relational schema and draw the dependency diagram for the 1NF (first normal form) INVOICE table (see below), following the example from the material provided above.

You may use whatever tool you like to create the diagram--draw.io, Word, Excel, etc.

Determine the TWO partial dependencies that you can 'pull out' into two new tables.

Technically there are three partial dependencies, but one of them remains in the original table. As usual, we'll discuss in class.

Write the relational schemas for both the 1NF form (single table) and the 2NF form (three tables).Example relational schema using the Employee table from the slides:

EMPLOYEE (EMP_NUM, EMP_NAME, JOB_CLASS)

The general form is:

TABLE_NAME ( [list of attributes, with PK underlined and FKs italicized] )

As a hint, invoice_id and product_id are both keys--and together they form the composite primary key.

Submit all responses, including the dependency diagram image from draw.io

submit ONE image of your 1NF dependency diagram

write the following in the same document (NOT in the comments):

(a) partial dependency sets -- equivalent to what will become the three 'new' tables (just try this, doesn't have to be correct) and

(b) your relational schemas for BOTH the original 1NF form AS WELL AS the three relational schemas for the 2NF form.