Snooty Fashions is an exclusive custom fashion designer business located in City, State. The company is looking a database design to keep track of the following information and relationships:

Snooty Fashions has designers, customers, tailoring technicians, outfits and fashion shows.

The designers are identified by a unique identifier, as well as the designer name.

Each designer, designs many outfits, each outfit has only one designer.

Tailoring technicians tailor outfits. The tailoring technicians are identified by a unique identifier and name. Each outfit is identified by a unique identifier, price and planned date

of completion. Snooty Fashions will keep track of the date when a tailoring technician started working on a particular outfit.

Each tailoring technician must work on at least one outfit but can work on many. Each outfit has at least one tailoring technician working on it but can have many.

Each outfit is sold in advance to exactly one customer. Each customer can buy one or many outfits. Snooty Fashions does not keep track of customers that have not yet purchased an outfit.

The customers are identified by a unique identifier, her/his name and multiple phone numbers.

The company has fashion shows, each show has a unique identifier, date of show and a location.

Each designer can participate in many fashion shows, but does not have to participate in any. Each fashion show can feature one or two Snooty Fashions designers (Snooty Fashions will not keep track of fashion shows that do not feature Snooty Fashions designers).

Logical database design

a. Convert the above ER diagram into relations (tables). Show all attributes in each relation.

b. Decompose the relations into 3NF. Here is an example of a table in 3NF: Faculty (FID, LName, Phone, Salary)