You do not need to provide any SQL code for this assignment. Your job is to create the logical database layout for the requirements and specifications above.t is all about logical database design. In this assignment, you will take the following business requirements and turn them into a logical database design using appropriate entity relationship diagrams. You can sketch these out or use any design tool of your choice and use any notations or comments in your design document. The final product needs to be readable and understandable to a database design audience.

Task:

You are designing a database system that keeps track of invoices for a veterinary clinic. At a minimum the invoicing system needs to capture:

$1.$ Important details about the pet,

$2.$ The pet owner$($s$)$ and their relevant details,

$3.$ The procedure$($s$)$ including any medication$($s$)$ and all the relevant details surrounding the procedure,

$4.$ The cost of the procedures $($individually$)$ and the total cost of the visit.

Important factors to consider in your design:

$1.$ Owners may have many different pets and different pets may have more than one owner. I.e$.,$ think of a married couple $($two people$)$ owning three different dogs and two cats. They use the same veterinary clinic that has two different veterinarians.

$2.$ What data might need to be calculated versus stored as a column? Pay close attention to the need to sum up medications and procedures into a single invoice.

$3.$ The final solution should be in $3$rd normal form: no redundancy $+$ no duplication. Entity classes and attributes should be easy to follow.

$4.$ All foreign and primary keys need to be identified.

$5.$ All cardinality issues must be addressed. Many to many tables$/$relationships$/$classes are not allowed. You will need to use at least one resolution table.

Your design document needs to explain:

$1.$ How you arrived at your keys,

$2.$ How you thought about determinants,

$3.$ What you did to resolve any many$-$to$-$many relationships.

$4.$ Total number of entity classes and attributes with all descriptions of the relationships between the table.