Functional requirements

Order Placement:

The system should allow customers to place orders for food items from the menu.

Customers should be able to modify or cancel their orders before they are processed by the kitchen staff.

Order Processing:

The system should receive and process orders in real$-$time.

It should ensure accurate transmission of orders to the kitchen staff.

Orders should be processed efficiently, minimizing waiting times for customers.

Notification:

The system should notify customers when their orders are received and ready for pickup or delivery.

Notifications should be sent via preferred communication channels $($e$.$g$.,$ SMS$,$ email$).$

Kitchen Integration:

The system should integrate seamlessly with the kitchen operations, enabling kitchen staff to receive and prepare orders efficiently.

It should provide clear instructions to kitchen staff regarding order details and preparation steps.

Menu Management:

The system should support dynamic updating of the menu, allowing Braum's to add, remove, or modify food items as needed.

Changes to the menu should reflect immediately on the ordering interface for customers.

Non$-$Functional Requirements:

Performance:

The system should be capable of handling peak ordering loads during busy hours without significant degradation in performance.

Response times for order processing and notification should be minimal to ensure a smooth customer experience.

Reliability:

The system should be highly reliable, ensuring that orders are accurately received, processed, and delivered to customers.

It should have built$-$in mechanisms for error handling and recovery in case of system failures or disruptions.

Security:

The system should implement robust security measures to protect customer data, including personal information and payment details.

Access to sensitive information should be restricted to authorized personnel only.

Scalability:

The system should be designed to scale horizontally to accommodate growing demand and an increasing number of users.

It should support the addition of new restaurant locations without significant architectural changes.

Usability:

The ordering interface should be intuitive and user$-$friendly, catering to customers of all ages and technical proficiency levels.

It should provide clear instructions and feedback to guide users through the ordering process effectively.

Compatibility:

The system should be compatible with devices present in the store.

Current processes, Workflows, Data flows

Current processes

Customer arrives at Drive$-$Thru: customers drive up to the Braums Drive$-$Thru and approach the automated order system.

System greets customers: the system displays a welcome message and prompts the customer to begin their order.

Customer selects items: the customer selects items from the displayed menu using voice over.

Customization and special requests: customers have the option to customize their orders by specifying preferences.

System recommends condiments: the system recommends extra condiments in order to upsell.

Order review: the system presents a summary of the customer$$s order for review so the customers can review their selected items, quantities, and any customizations before proceeding.

Payment: after finalizing the order, the system prompts the customer to select a payment method $($cash$,$ or credit$/$debit cards$)\backslash$

Confirmation: upon successful payment, the system confirms the order and provides an order number or receipt to the customer.

End of transaction: the order payment process is complete, and the customer proceeds to the next stage of the drive$-$thru experience.

Give me a sequence diagram and a activity diagram