Zorba's Caf Website

Redesign

Team:
Aaryamaan Atriwal, Brian Delaney,
Emily Montana*, Caroline Personius

Table of Contents
Problem Description.....................................................................3
Existing Model.............................................................................. 5
Use Case Diagrams.................................................................................5
Class Diagrams......................................................................................7

Proposed Changes........................................................................8
Feasibility Analysis.......................................................................9
Proposed Model..........................................................................10
Class Diagram......................................................................................12
Sequence Diagrams..............................................................................13

Methods..................................................................................... 15
Database ERD.............................................................................17
Control & Checks........................................................................17
Project Documentation................................................................18

Problem Description
1. Online catering order form:
As seen on the company
website, there is no access
to an online order form. The
only information provided is
the catering menu. Not
only are customers not able
to order directly from the
website, but prices are not
listed and the phone
number is listed closer to
the bottom of the menu.

2. Online reservation system:

Similar to the online
catering form, there is no
way for customers to make
reservations through the
company website.

3. Mobile web page control feature:

When accessing the menu on a mobile device,
it appears there are only a few items on the
menu because the scroll bar, though on the
page, is invisible, and not detected by looking
at the screen.

Existing Model
Use Case Diagrams
1. Catering order use-case:

Use Case: Calls Zorbas Cafe

Primary Actor: Customer
Trigger: Customer calls Zorbas
Relationships:
Association: Customer
Include: Read Menu to Customer, Place Order
Normal Flow of Events:
1. Customer calls Zorbas Cafe.
2. Staff reads menu to Customer.
3. Customer places Order.

2. Online reservation use-case:

Use case: Make reservation

Primary Actor: Customer calls
Zorbas staff
Trigger: Customer calls Zorbas
cafe.
Relationships:
Include: Make Reservation,
Confirm Reservation
Normal Flow of Events:
1. Customer calls Zorbas
Cafe.
2. Customer makes
Reservation.
3. Staff confirms Reservation.

3. Mobile web control use-case:

Use case: Mobile menu view
Primary Actor: Customer accesses
Zorbas mobile website

Trigger: Customer clicks menu on

website

Relationships:
Include: View all
menu items
Normal Flow of Events:
1. Customer accesses Zorbas mobile website
2. Customer clicks menu option on website
3. The website does not show or make it
obvious that there are more items on the menu

Class Diagrams

Proposed Changes
Our team is proposing to redesign how the companys website is designed.
The three major problems discussed above will need to be changed in order
to create a more efficient online presence for Zorbas Greek Caf. There are
specific changes that go along with these problems:
1. Online Catering Ordering Form Changes:

There will be a new option for the catering tab on the companys
website. Customers will be able to order food online. This will eliminate a lot
of the discrepancies from staff trying to take orders from a phone call. An
extension from this new feature would include something similar like online
togo orders.
2. Online Reservation Changes:

Similar to the above change, this enhancement will allow users to

reserve tables online. Online reservations will ensure that the restaurant is
not overbooked, ensure the reservation is correct according to the customer,
it will have the option to send reminders to the customers about the
reservation, and will require critical information like the customers phone
number so the staff will have access to let them know the status of the table
(late, early, inquire if the customer will still show).
3. Mobile Web Control Changes:

This will be a simple change to the structure of the website. Since the
mobile site does not make it obvious that the menu tab continues further
than the appetizers, the new structure will extend the menu screen,
including the pillars, past the screens physical edge, and show the scrollbar
so users know the menu continues beyond the initial items shown. Users will
8

also be able to hyperlink from the menu page directly to the ordering form,
and pay online.

Feasibility Analysis
Technical Feasibility:

Familiarity with Functional Area

Analysts: Medium
Users: High
Familiarity with Technology: Medium to High
Project Size: Small
System Compatibility: High
The technical risks are low to medium, and the feasibility medium to
high. Various members of the team have worked with the company before,
and are familiar with the requirements and processes. The team is also
familiar with the web design, and the coding and database skills required to
build the changes to the existing website. Since the project is an update to
the existing system, the project size is relatively small, compared to creating
an entirely new website or database. Since the project uses the web design
that Zorbas already has in place, the compatibility is high.

Organizational Feasibility:

Company Management Support: High

Project Leadership Support: High
User
Employees: High
Customers: Unknown - Estimated Medium
Strategic Alignment: High

Organizational Feasibility is high. Company management and project

leadership are very supportive of these updates to the existing system. It will
save employees time on the phone, streamline the ordering and reservation
processes, and ensure customer orders and reservations that are currently
on paper are not misplaced. Customers are also much more likely to order
when they can do so online, and not have to call in or be placed on hold.
Increasing efficiency through these updates is also aligned with Zorbas
strategy for providing excellent customer service and improving business
processes.

Proposed Model
Use Cases
1. Catering order use-case:

10

Primary Actor: Customer

Relationships: User and system
Association: Customer and Staff
Include: Open order form, Choose menu items, Pay online, Change order
status to complete
1.
2.
3.
4.
5.

Normal Flow of Events:

Customer logs in to order catering items
Access order form
Add menu items
Pay online
Pick up order from restaurant, and staff changes order status to complete
2. Online reservation use-case:

11

Primary Actor: Customer

Relationships: User and system
Association: Customer and system
Include: create new reservation
Normal Flow of Events:
1. Customer logs in to reserve a time and table
2. Reserve time, number of guests, and/or table

3. Mobile Web Control Use-Case:

Primary Actor: Customer

12

Relationships: User and system

Association: Customer and system
Include: scroll to view more items
Normal Flow of Events:
1. Customer logs in to view menu
2. Customer can easily see that they must scroll to see more
3. Customer can Order and Pay online

Class Diagram

13

Sequence Diagrams
1. Catering Order

14

2. Online Reservation

3. Mobile Web Control

15

Methods
1.

calculateTotalCost

Method Name: calculateTotalCost

Associated Use Cases: Catering Order
Description of Responsibilities: Calculates the total cost of a customer order.
Arguments Received: ItemizedCost
Pre-Conditions: Customer Exists, Order Exists, running system
Post-Conditions: Total cost is calculated and returned, or the order is
canceled.
Pseudocode:
Get individual costs from ItemizedCost.
Multiply by the quantity of items.
Return Total Cost.
2.

calculateTax

Method Name: calculateTax

Associated Use Cases: Catering Order
16

Description of Responsibilities: Calculates the tax of the order.

Arguments Received: TotalCost
Pre-Conditions: Customer Exists, Order Exists, TotalCost Exists, running
system.
Post-Conditions: Tax is calculated and returned, or the order is canceled.
Pseudocode:
Get subtotal from TotalCosts.
Multiply TotalCost by the TaxR
Return Tax amount.
3.

confirmCateringOrder

Method Name: confirmCateringOrder

Associated Use Cases: Catering Order
Description of Responsibilities: Confirm that the received catering order is
correct and can be filled.
Arguments Received: OrderID, CustomerID, Payment Type, ItemizedQuantity,
TotalCost.
Pre-Conditions: Customer Exists, Order Exists, TotalCost Exists, running
system.
Post-Conditions: Order is confirmed or rejected.
Pseudocode:
Receive OrderID, CustomerID, PaymentType, ItemizedQuantity, and
TotalCost from Order.
Confirm field values are valid. If valid, confirm order. If invalid, reject
order, notify user, and issue refund.
4.

confirmReservation

Method Name: confirmReservation

Associated Use Cases: Online Reservation
Description of Responsibilities: Confirm that the received reservation is
correct.
Arguments Received: ReservationID, CustomerID, ReservationDate,
ReservationTime, Number of People.
Pre-Conditions: Customer Exists, Reservation Exists, running system.
Post-Conditions: Reservation is confirmed or rejected.
Pseudocode:
Receive ReservationID, CustomerID, ReservationDate,
ReservationTime, Number of People from Reservation.
Confirm fields are valid and Reservation Date/Reservation Time are
available.
17

If Reservation Date and Reservation Time are available, confirm

reservation. If Reservation Date and Reservation Time are unavailable, reject
reservation and notify user.
5.

updateMenu

Method Name: updateMenu

Associated Use Cases: Catering Order
Description of Responsibilities: Update Menu Names and Prices.
Arguments Received: Item Names, Item Price
Pre-Conditions: Menu Exists, Staff Exists, running system.
Post-Conditions: Menu Items and Prices created or updated.
Pseudocode:
Receive current Item Names and Item Prices.
Intake user input.
Alter Item Names and Item Prices.
Update Item Names/Prices.

Database ERD

18

Control & Checks

1. For payment, only accept Mastercard, Visa, Discover, and American Express.
2. For the Customer table, Reservation Form, and Catering Form, all fields are
required, and will not be accepted if left blank.
3. Order will be automatically rejected if payment information is not filled out,
or not valid.
4. All Customer and Address information must be securely encrypted, and
viewable only by a valid Staff ID or the Customer.
5. Menu Items can only be edited using a valid Staff ID.

19

Project Documentation
1. Work Completed by Group Members
a. Aaryamaan: ERD, Existing System Use Case Descriptions, Sequence
Diagrams
b. Caroline: Problem Descriptions, Class Diagrams, Methods, Feasibility Analysis
c. Emily: Use Diagrams, Proposed System Use Cases, Proposed Changes,
d. Brian: No input/work completed.
2. Notes
a. Despite repeated attempts to contact Brian about working on the project and
assigning parts, he did not respond, and did not complete work on the
project submissions or presentation.

20