Scribd
Upload
24 views6 pages

System Analysis and Design

The document outlines the process for developing a restaurant billing system for "The Chowk" restaurant. Stakeholders including managers, waitstaff, kitchen staff, and customers provided input on their needs. The scope of the project is to streamline operations and enhance the customer experience through features like order management, menu customization, reservations, and payments. The system will be designed based on an analysis of the restaurant's requirements and processes.

Uploaded by

gopelaw218
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
24 views6 pages

System Analysis and Design

The document outlines the process for developing a restaurant billing system for "The Chowk" restaurant. Stakeholders including managers, waitstaff, kitchen staff, and customers provided input on their needs. The scope of the project is to streamline operations and enhance the customer experience through features like order management, menu customization, reservations, and payments. The system will be designed based on an analysis of the restaurant's requirements and processes.

Uploaded by

gopelaw218
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Report on Restaurant Billing

System Management for


“The Chowk”

Introduction

Purpose
This report outlines the system analysis and design process for
the implementation of a Restaurant Billing System at "The
Chowk”, a vibrant and popular restaurant located in the heart
of the city.

Scope
The scope of this project encompasses the development of a
comprehensive Restaurant Billing System to streamline
restaurant operations and enhance the dining experience for
both our customers and staff. It will include features such as
order management, menu customization, table reservations,
and payment processing.

Methodology
To ensure the success of this project, we adopted a thorough
and collaborative approach, involving the entire team at "The
Chowk”. We conducted interviews and gathered valuable
insights from various stakeholders, including managers,
waitstaff, kitchen staff, and customer-facing roles.

Restaurant Billing System 1


Determining System Requirements

Interview Findings

Managers: Managers expressed the need for real-time data


on restaurant performance, including sales trends, popular
menu items, and staff productivity. They also emphasized the
importance of a user-friendly interface for menu customization.

Waitstaff: Waitstaff requested a user-friendly order


management system that would simplify the process of taking
orders and enable them to handle multiple orders
simultaneously, especially during peak hours.

Kitchen Staff: Kitchen staff emphasized the importance of


clear and timely communication of orders, including special
requests or dietary restrictions. They also highlighted the need
for accurate preparation time estimates.

Customers: Customer feedback highlighted the desire for a


seamless dining experience, including the ability to make
reservations online and split bills with ease. They also
expressed interest in receiving personalized promotions based
on their dining history.

Restaurant Billing System 2


General System Requirements
• What do you want the system to do?
• Who will use the system (e.g., staff and customers)?
• What problems do you want the system to solve?
• Do you want the system to work on computers, tablets, or
phones?

Menu and Orders


• What items will be on the menu?
• How should customers order their food (e.g., at the table,
online)?
• Should customers be able to customize their orders (e.g.,
extra cheese)?
• Do you need a way to track special requests or dietary
restrictions?

Reservations
• How should customers make reservations (e.g., online,
phone)?
• What information should be collected for reservations (e.g.,
date, time, number of guests)?
• Should customers receive confirmation emails for
reservations?

Customer Information
• What customer details do you want to collect (e.g., name,
email, phone)?
• Do you want to offer a loyalty program or customer
accounts?

Restaurant Billing System 3


Payments
• How should customers pay (e.g., cash, credit card)?
• Do you need to split bills for groups?
• What type of receipts should be generated?

Kitchen Communication
• How should orders be communicated to the kitchen staff?
• Is there a need for order priority?
• Do you want the kitchen to confirm when an order is ready?

Data Storage
• What data do you need to store (e.g., order history, customer
information)?
• How long should data be kept, and do you need to back it
up?

Security
• How do you plan to keep customer data and payments
secure?
• Do you need user accounts with passwords for staff?
• What happens if there's a system outage or data loss?

Budget and Timeline


Budget:
What is the expected budget for the development and deployment
of the Restaurant Billing System?

Timeline:
What is the projected timeline for system development and
deployment?

Restaurant Billing System 4


Structuring System Process Requirements
Process Modeling

Order Processing:
We will model the order-taking process, including order entry, ticket
generation, and order delivery to tables or for takeout. This will ensure
efficient communication between waitstaff and kitchen staff.

Condition 1 Condition 2 Condition 3


(Order Entry (Table (Takeout Action (Order-Taking
Method) Availability) Request) Process)
Manual Entry Table No Takeout Take Order, Generate
(Waitstaff) Available Ticket, Serve at Table

Manual Entry Table Takeout Take Order, Generate


(Waitstaff) Available Requested Ticket, Prepare for
Takeout
Manual Entry Table N/A Inform Customer,
(Waitstaff) Unavailable Offer Alternative
Mobile App N/A N/A Receive Order,
Order Generate Ticket,
Prepare for Takeout
Online Order N/A N/A Receive Order,
Generate Ticket,
Prepare for Takeout

Fig: Decision Table for Order Processing

Condition 1 (Customer Condition 2 (Order Action (Order


Type) Type) Priority)
Regular Customer Dine-In Normal Priority
Regular Customer Takeout High Priority
VIP Customer Dine-In High Priority
VIP Customer Takeout Highest Priority

Fig: Decision Table for Order Priority

Restaurant Billing System 5


Payment Handling:
Visualizing payment processing, including the ability to split bills,
accept multiple payment methods, and generate digital receipts for
customers.

Condition 1 Condition 2 Condition 3 Action


(Payment (Credit Card (Mobile Wallet (Payment
Method) Validity) Balance) Processing)
Credit Card Valid N/A Process
Payment
Credit Card Invalid N/A Reject Payment

Cash N/A N/A Accept Cash


Payment
Mobile Payment N/A Sufficient Deduct
Payment from
Wallet
Mobile Payment N/A Insufficient Ask for
Alternative
Method

Fig: Decision Table for payment processing

Condition 1 Condition 3
(Number of Condition 2 (Bill (Payment Action
Guests) Splitting Request) Method) (Processing)
Greater than 1 Requested (Yes) Credit Card Split Bill and
Charge
Greater than 1 Requested (Yes) Cash Reject Split
Request
Greater than 1 Requested (Yes) Mobile Split Bill and
Payment Deduct
Greater than 1 Not Requested Credit Card Charge Total
(No) Amount
Greater than 1 Not Requested Cash Accept Cash
(No) Payment
Greater than 1 Not Requested Mobile Deduct Total
(No) Payment Amount

Fig: Decision Table for splitting bills

Restaurant Billing System 6

You might also like