In designing a relational database, we are going to look at a real problem presented by one of the class members, Norry. He wants to work out a pricing system for his pool company.

This is the basic information that he provided.

Pools - he has multiple sizes of pools (for example 16 x 32 and 20 x 40) and each of these sizes has a specific cost.

The pools can also be done in different shapes - I am unclear whether this is part of the original specifications on sizes of pools or whether this is an additional charge.

The Concrete Deck work comes in a variety of styles and each one has a price. The customer can also opt for no deck work.

There are a variety of options that the customer can choose from related to heaters, lights and cleaners etc.

When the quote is given, the basic price includes some necessary things that are included in the base price of the pool.

The Customer quote is put together by the salesperson and using these tables the goal would be for it to be automated. There are multiple quotes depending on sizes and options chosen. It would be helpful if the customer could also specify a budget to help keep the quotes in line.

When a contract has been signed the information from the quote goes into making the agreed upon purchase. The person doing the installation needs to receive a form that contains all of the information about the pool including the necessary items that were included as part of the base pool price.