The other day I was at TGIF’s, and I started wondering about the database they, and probably every other restaurant, used to keep track of their employees. So I asked my friend, the bartender. He told me that they did keep information on each employee, things like IDs, Names, Addresses, and so forth. It turns out that because TGIF’s has a number of restaurants in the same city (each with their own Restaurant IDs), many employees could work a many of the restaurants. Naturally, each restaurant has many employees. Each employee can have many different titles, which surprised me. For example, an employee can be a waiter, a bartender, a cook, a gopher, and so forth – it all depends on where they are needed. They keep track of things like position name, and title pay rate. It turns out that titles are filled in terms of the skills necessary for that title. A title may require many skills, and, of course, a skill may be used in many titles. For example, the waitress and bartender titles both require interpersonal skills and a good memory, as well as other skills. As it turns out, when an employee is hired, they are given a number of tests to determine their skills. Each employee generally has a number skills (interpersonal skills, cooking skills, cleaning skills), and of course, each skill is shared by a number of employees (this in spite of the fact that I have yet to find a bartender there that can get you a drink in less than 15 minutes; maybe they don’t consider speed a skill).

 

Draw the ERD for this situation. Make sure you show ALL of the primary and foreign keys necessary, the cardinality and cardinality constraints for each of the relationships. If additional fields are necessary, show them, but you need not show ALL of the fields you would add

 (a simple composite field called “Others” will suffice).