A scenario is taken and we have explained how to make a Extended Entity-Relationship (EER) Model with the help of the scenario.

2. A Custom Pizza Online Website Was Created For Customers Of A
Pizzeria To Create Their Orders Online. The Pizzeria Has Been
Taking Orders By Phone For A Long Time And They Wanted To
Add The Option For Customers To Create Orders Online.
Existing Webshop Solutions Involves Putting Products In
Categories.
Such A Division Is Not Suitable For Ordering Custom Pizzas.
There Is A Need To Allow Users To Pick Ingredients For A Pizza,
Ability To Configure Multiple Custom Pizzas And The Ability To
Order Other Products Besides Pizzas.
Our Solution Separates The Ordering Of Products In Non Pizza
Products And Custom Pizzas Which Consists Of A Selection Of
Ingredients For Pizzas.
The Website Allows Customers To Create Custom Pizzas, Pick
Non Pizza Products And Enter Delivery Information.

3. •Employees Can Process Accept Or Deny Orders, And Update The
Status As Processing Orders Continues.
•The Customer Will Be Kept Up To Date By Email Notification When
The Order Status Changes.
•The Administrator Can Add And Edit Ingredients, Non Pizza
Products And He Can Also Add Employee Accounts So The
Employees Can Log In To Process The Orders.

4. Three Types Of Users Should Be Able To Use The System:
Customer, Employee And Administrator(As main employee).
Customers Are Users Who Visit The Website And Can Create
Orders By Customizing Pizzas, Selecting Products And Entering
Customer Details.
Employees Are The Group Of Users That Work With The Ordering
System On A Daily Basis.
Employees Will Have Their Own Accounts To Log On To. They Are
The Ones Responsible For Processing Orders.
Since Customer Users Do Not Need A Log In, Employees Who
Process Telephone Orders Can Use The System As A Customer
And Enter The Telephone Order Directly Into The System As They
Take The Order From The Calling Customer.
The Administrator, Or Super User, Has The Ultimate Control Of
The System, He Can Add, Change Or Delete Ingredients And
Products, As Well As Add, Change, Or Delete Employee Accounts.

5. Order
Customer
Employee
Product

6. Order: O_Id, P_Id, Delivery_Date & Time,
Order_Date ,Order_Time, Total_Price.
Customer: C_Id, C_Name, Add(Room No,
Street No, Street Name, City), Pno, Email.
Employee: E_Id, E_Name, Pwd.
Product: P_Id,
Product_Details(Pizza(p_id,Ingredients_Name,
Price1), Non_Pizza(p_id,p_name,Price2),
O_Id, P_Desc.

8. Variable Name Variable Type Variable Width Values/Notes
C_Id Numeric 4 1-9
Email Varchar 30 Abc@Xyz.Com
F_Name Varchar 50 ABCD
L_Name Varchar 50 ABCD
S_Name Varchar 50 ABCD
Room_No Number 4 1-9
Street No Number 4 1-9
Street Name Varchar 20 A-Z,A-Z
City Varchar 10 A-Z,A-Z
Pno Varchar 10 1-9

9. Variable Name Variable Type Variable
Width
Values/Notes
O_Id Numeric 3 001-900
P_Id Numeric 3 1-300
O_Date Date ’2014-03-28’
O_Time Time ’00:00:00’
D_Date & Time Datetime ’2014-03-28’
T_Price Numeric 5 1-9

10. Variable Name Variable Type Variable Width Values/Notes
E_Id Number 2 1-9
F_Name Varchar 50 ABCD
L_Name Varchar 50 ABCD
S_Name Varchar 50 ABCD
Password Varchar 10 A-Z,A-Z,1-9

11. Variable Name Variable Type Variable Width Values/Notes
E_Id Number 3 1-9
O_Id Numeric 3 001-900
P_Id Numeric 3 1-300
C_Id Numeric 4 1-5000

12. Variable Name Variable Type Variable Width Values/Notes
P_Id Numeric 3 1-9
Product Name Varchar 10 A-Z,A-Z
Price Numeric 3 1-9
Variable Name Variable Type Variable Width Values/Notes
P_Id Numeric 3 1-9
Product Name Varchar 10 A-Z,A-Z
Price Numeric 3 1-9