Transcript Information system of restaurant

INFORMATION SYSTEM OF
RESTAURANT
OSIS – TERM PROJECT
DESCRIPTION OF THE PROBLEM 1/2
• Small restaurant want to have knowledge about its business
• Information system should be able to:
• Place orders and record orders
• Create reports about income of restaurant
• Have evidence about amount of ingredients in local warehouse
• Order missing supplies, when there is lack of it
DESCRIPTION OF THE PROBLEM 2/2
• Web interface for food delivery
• Evidence of customers ratings
CONTEXT DIAGRAM
SYSTEM DIAGRAM
MINISPECIFICATION – RATE ORDER
READ rating FROM customer.
WRITE rating INTO order_info.
READ ratings FROM order_info, CREATE selected_post FROM ratings, SEND
selected_post TO web_page.
FLOW CHART – SALES CALCULATION
DECISION TABLE – SHIFT RECORD
did employee log in?
did employee log out?
write log in date
write log out date
empty shift warning
no action
Y
Y
Y
N
N
Y
N
N
*
*
*
*
ENTITY RELATIONSHIP DIAGRAM
OOA – USE CASE DIAGRAM
USE CASE SCENARIO 1/3
• Use case specification
• Use case name: create web order
• Use case purpose: This use case provides the ability to order food using our
web interface.
• Actor: Customer
USE CASE SCENARIO 2/3
• Optimistic flow:
•
•
•
•
•
A. Actor request web order.
B. System sends appropriate form.
C. Actor fills form with his name, address, e-mail, phone number and sends it.
D. System creates new record for order in order info.
E. System sends notification about successful order.
USE CASE SCENARIO 3/3
•
•
•
Pragmatic flow:
Conditions triggering alternate flow:
Condition : Incorrectly filled web order form.
•
•
•
•
•
D1. System sends notification about incorrectly filled fields in web order form.
D2. System prompts actor to correct it.
D3. Actor fills form correctly and sends it.
D4. If form is filled correctly, perform step D.
D5. Else, perform step D1.
ACTIVITY DIAGRAM - RATE ORDER
CLASS DIAGRAM
THE END
• Thanks for your attention