Using the attached Spreadsheet, \"BoatInvoice.xlsx\" Develop a Data Dictionary b

Question

Using the attached Spreadsheet, "BoatInvoice.xlsx" Develop a Data Dictionary based on what you may determine to be the necessary fields for the Data Base.

Assign data types: Varchar, integer, float, etc.

Operator Number has been changed to Operation Number (typo on my part)

Assumptions may be necessary for some portions of the Dictionary but should be labeled as "assumptions".

Attached is a partial version of the Data Dictionary "Partial Data Dictionary Example.xlsx" that you can use as an example.

Explanation / Answer

in the second image they mentioned three relations/tables...

we add the quantity information so take the new relation and describe attributes for that relation..

we require customer number, purchased item id and quantity of that item and amount to be paid for that item...

we add duraion for timely reasons......

Now think about primary key of the out new table....

we assign customer id as primary key we may get duplicates because one customer may buy more than one item... we assign product id as primary key different customers may buy same item this also gives duplicates.....

time will give unique details but how we join two or more tables using time attribute.....

so assign customer id and product id and time as primary key...... if we didn't add time then same customer buy same item after some days will cause duplicate entry......

above is an example to create a table and its attributes....

In the given question mentioned that parts table or mechanics table....

Let's create a parts table:

For uniquely identifying we need part id(integer) and it's name(varchar(15)) as part name.......

part colour varchar(10), supplier id.....(integer) if we use suppliler name it causes multi valued dependency so use supplier id and part id in another new relation called parts_supplier and make supplier id and part id as primary key.... supplier id is a foreign key referencing suplier(suplier id)..... part id is a foreign key referencing parts(part id).....

and we create another table for cost information......

part id and quantity and cost for each quantity of particular part id......

Related Questions

Navigate

• Browse (All)
• Browse U
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.