Reference no: EM13875276

Database Design - Read all questions and instructions carefully.

On-the-Vine Vineyard

On-the-Vine Vineyard, Inc., is a small, family-owned winery, one of California's largest in Sonoma Valley, specializing in limited production of premium quality wine.

The Employees: On-the-Vine currently employs over 12 full-time employees, with positions ranging from administrative assistant to winemaker. Each employee is assigned a unique identification number. In addition to the employee's name, position, and identification number, the company also records each employee's Social Security number, address, phone number, and emergency contact.

The Vineyards: On-the-Vine owns several vineyards, each in separate locations. Each vineyard is managed by a single employee and represented by unique number, name, address, and size. No employee manages more than one vineyard.

The Wine: Each bottle of wine produced is given a unique identification number in addition to its name. Other information recorded for each wine includes its vintage year, category (e.g., dry red, dessert, etc.), vineyard where the wine is produced, price, and percent alcohol. Also recorded is the winemaker (employee) in charge of making that bottle of wine. A winemaker may be responsible for producing more than one bottle of wine.

The Customers: On-the-Vine sells its wine to individuals via the Internet. All customers are assigned a unique customer identification number, and this number is recorded along with their first name, last name, address, phone number, and date of birth.

The Orders: All customers obtain their products by placing orders directly with On-the-Vine. A customer can purchase more than one bottle of wine at one order. Each order is assigned a unique order number, and the date of order, the date of shipping, and the shipping status are recorded as well.

Q1. Carefully read the above business description and draw an Entity-Relationship Diagram (ERD) for the database that manages information on employees, customers, and so on.

• Your ERD should include all necessary entities, attributes, and relationships.
• You need to specify relationship names and types (1:1, 1:M, or M:N) as well.
• A relationship should have a name with a verb.