Can someone help me design my database for a dog service business?

Here is the assignment I am working on:

To be honest, I wasn't really sure where to start, so I just made my potential tables. I am a bit confused on whether I am even on the right track and I was hoping someone could help me or help correct what I have already done.

Here's what I've got so far. I haven't related any of my tables yet (I need some help with this) and I also haven't identified my PK or FK for each (also need help with this). Please help me out if you can?

Diegos Dog Services offers services for dogs such as walking, grooming, boarding and training. Diegos Dog service business has been growing rapidly and his old ways of manually keeping track of everything through Excel is no longer cutting it. He needs a database to help maintain the data of his business more efficiently. He would like to use the database to be able to maintain data about his customers, their dogs, services offered and service representatives.

Please let me know what I should change in my tables and how to relate each one. Thanks!!

Term Project - Part 1 Your term project will consist of two parts: design and implementation. For the first part of your project you are asked to think of a unique application to handle the transactions of a business, organization, .... It is up to you to find the topic. Think of something different from the databases we've been using. Once you determine the application you wish to accomplish, design your database. Design your database keeping in mind you want to minimize redundancy and avoid anomalies Give this enough thought; trying to get fast results may not result in a good design For a Term Project you are expected to come up with an application that would require at least 5 tables. Remember, you'll use this design for the second part of the Term Project, the implementation of it using a DBMS Term Project - Part 1 Specifications 1. Write a few paragraphs to fully describe what the database is supposed to accomplish 2. Express each table in the notation we used in Chapter 6. Below is a screenshot of page 189. Use it as an example to guide you expressing the definition of your tables. Remember, you'll use these definitions to create the actual database 189 Database Design 2: Design Method Orders (OrderNum, OrderDate, Customernum) Customer (CustomerNum, CustomerName, Street, City, State, Postal Code, RepNum) Item (ItemNum, Description) OrderLine (OrderNum, ItemNum, NumOrdered, QuotedPrice) You can represent this collection of tables in DBDL and then merge them into the cumulative design. Again, however, you can look ahead and see that you can merge this Customer table with the existing Customer table and this Item table with the existing Item table. In both cases, you will not need to add anything to the Customer and Item tables already in the cumulative design, so the Customer and Item tables for this user view will not affect the overall design. The DBDL representation for the Orders and OrderLine tables appears in Figure 6-7. Orders (Order Num, OrderDate, Customer Num) FK Customer Num Customer OrderLine (OrderNum, ItemNum, Numordered, QuotedPrice) FK OrderNum Orders FK ItemNum Item FIGURE 6-7 DBDL for Orders and OrderLine tables Dog Customer Key key Key Dog Num Dog Breed DogName Customer Num CustomerName Dog Num RepNum Service Sale Key Key ServiceNum Description Service Type Price CustomerNum Key Key Rep RepNum FirstName LastName Commission Rate Key Key Key RepNum ServiceNum CustomerNum Key Term Project - Part 1 Your term project will consist of two parts: design and implementation. For the first part of your project you are asked to think of a unique application to handle the transactions of a business, organization, .... It is up to you to find the topic. Think of something different from the databases we've been using. Once you determine the application you wish to accomplish, design your database. Design your database keeping in mind you want to minimize redundancy and avoid anomalies Give this enough thought; trying to get fast results may not result in a good design For a Term Project you are expected to come up with an application that would require at least 5 tables. Remember, you'll use this design for the second part of the Term Project, the implementation of it using a DBMS Term Project - Part 1 Specifications 1. Write a few paragraphs to fully describe what the database is supposed to accomplish 2. Express each table in the notation we used in Chapter 6. Below is a screenshot of page 189. Use it as an example to guide you expressing the definition of your tables. Remember, you'll use these definitions to create the actual database 189 Database Design 2: Design Method Orders (OrderNum, OrderDate, Customernum) Customer (CustomerNum, CustomerName, Street, City, State, Postal Code, RepNum) Item (ItemNum, Description) OrderLine (OrderNum, ItemNum, NumOrdered, QuotedPrice) You can represent this collection of tables in DBDL and then merge them into the cumulative design. Again, however, you can look ahead and see that you can merge this Customer table with the existing Customer table and this Item table with the existing Item table. In both cases, you will not need to add anything to the Customer and Item tables already in the cumulative design, so the Customer and Item tables for this user view will not affect the overall design. The DBDL representation for the Orders and OrderLine tables appears in Figure 6-7. Orders (Order Num, OrderDate, Customer Num) FK Customer Num Customer OrderLine (OrderNum, ItemNum, Numordered, QuotedPrice) FK OrderNum Orders FK ItemNum Item FIGURE 6-7 DBDL for Orders and OrderLine tables Dog Customer Key key Key Dog Num Dog Breed DogName Customer Num CustomerName Dog Num RepNum Service Sale Key Key ServiceNum Description Service Type Price CustomerNum Key Key Rep RepNum FirstName LastName Commission Rate Key Key Key RepNum ServiceNum CustomerNum Key