Online Food Ordering System

1.Goal
The main objective of online food ordering system is to automate the existing manual system with the
help of advance computerized software so, that valuable data can be stored for longer period with
easy accessing and manipulation of the same.

2.Architectural Drivers Specification

Use Case Entities
ID E01
Title Admin
Description In Online Food Ordering System Admin can handle the functionalities like
add new food items, edit/delete food items, Enable/Disable the food items
according to season and availability. Admin have authority to view order
details and update the delivery status of food. The payment transaction
and user details are also viewable to admin.
Provides Assumptions The Admin has appropriate permissions and authentication to access the
administrative functionalities. The system has already been set up and
initialized with the food items. User and admin registration processes have
been completed
Requires Assumptions Availability of user and admin registration and authentication. Availability
of food list data for management.
Identified Use Cases UC01: Add Food Items, UC02: View / Edit (Price, Enable/Disable) / Delete
Items, UC03: View Orders, UC05: View Users, UC04: View Transactions

ID E02
Title User
Description The registered user can access the account with valid credentials. User can
surf the food items according to categories, Cart and online payment
options are available to user. User can track their orders with the food
details.
Provides Assumptions The user has access to a device with internet connectivity. The user
interface is user-friendly and provides clear instructions. List foods are
available in the system. Payment gateways are functional.
Requires Assumptions Availability of a user registration and authentication process. Availability of
food listings. Functioning payment gateway for online payments.
Identified Use Cases UC06: Register, UC07: Login, UC08: Menu List, UC09: Item Details, UC10:
View Cart, UC11: View Orders and Status
Operational Use Cases
ID UC01
Title Add Food Items
Description Admin can add food items details like name, Photo, Description/
Ingredients, Price, Category etc.
Entities Involved E01: Admin
Preconditions The Admin is logged into the system. Admin has permission to add food
items
Primary Flow Admin user logs into the system. Admin users under go to add food
section. Admin add food items details like name, Photo, Description/
Ingredients, Price, Category etc. The system validates the input data. If
the data is valid, the new vendor is added to the system. The system
validates the changes
Postconditions If a food item is added, the information of the new food will be stored in
the system.
Alternate Flows Input validation error If an admin user provides invalid data (e.g. missing
required fields) when adding or updating food, the system displays an error
message and does not proceed until Valid data is provided. Cancel
confirmation If the admin user cancels the confirmation prompt when
adding food, the system will not proceed with deletion

ID UC02
Title View / Edit (Price, Enable/Disable) / Delete Items
Description Admin can view, edit the food items details as well as Enable/Disable food
items according to season or availability.
Entities Involved E01: Admin
Preconditions Administrator is logged in to the system Admin can view, edit the food
items details as well as Enable/Disable food items according to season or
availability.
Primary Flow 1. Administrator user logs into the system. 2. Admin users navigate to
View / Edit (Price, Enable/Disable) / Delete Items section. 3. The admin user
selects an option to add a new item, update an existing item's information,
or delete an item. 4. If viewing an item: The administrator user views the
necessary information of the new item (eg name, price). 5. If editing item
information: The admin user selects the item to edit. Admin users make
changes to item information (e.g. edit price, enable/disable). The system
confirms the changes. If the changes are valid, the item's information will
be updated. 6. If deleting an item: The administrator user selects the item
to be deleted. The system prompts the administrator for confirmation. If
confirmed, the Item will be deleted from the system.
Postconditions 1. Information of the newly viewed item will be stored in the system. 2. If
you edit item information, detailed information about the item will be
updated and saved in the system. 3. If you delete an item, that item will be
deleted from the system. Alternate flow
Alternate Flows Alternative procedure 1: Input validation error If an admin user provides
invalid data (for example, missing required fields) when editing an item, the
system displays an error message and does not proceed. until valid data is
 provided. Alternative flow 2: Item not found If an admin user tries to edit
or delete an item that does not exist in the system, the system will provide
a response indicating that the item was not found. Alternative flow 3:
Cancel confirmation If an admin user cancels the confirmation prompt
when deleting an item, the system will not proceed with the deletion

ID UC03
Title View Orders
Description Admin can track Live orders and Status Update for particular food delivery.
Entities Involved E01: Admin
Preconditions Administrator is logged in to the system Admin can track Live orders and
Status Update for particular food delivery.
Primary Flow 1. Administrator user logs into the system. 2. Admin users navigate to the
View Orders section 3. The admin user selects an option for live order
tracking and status updates for specific food deliveries. 4. If tracking orders
directly: Administrator users view order information, location and distance
the order is being delivered. 5. If updating the status for a specific food
delivery: The admin user can update the status for a specific food delivery
based on the order status directly.
Postconditions 1. Order status information will be stored in the system. 2. If the status is
updated, the order will be updated and saved in the system
Alternate Flows Input validation error If an admin user provides invalid data (for example,
missing required fields) when editing an item, the system displays an error
message and does not proceed. until valid data is provided. Order not
found If an admin user tries to update an order that does not exist in the
system, the system will provide a response indicating that the order was
not found.

ID UC04
Title View Transactions
Description View previous transaction by date search and total amount at end.
Entities Involved E01: Admin
Preconditions Administrator is logged in to the system View previous transaction by date
search and total amount at end.
Primary Flow 1. Administrator user logs into the system. 2. Admin users navigate to the
View Transactions section 3. Admin user selects an option to view previous
transactions by search date and final total amount. 4. If viewing previous
transactions by search date: Administrator users go to view transactions
and can search by specific date 5. If viewing final total amount: Admin
user selects the option to view the final amount of the transaction
Postconditions 1. Transaction information will be stored in the system. 2. If you search for
a transaction and see the final amount, it will be updated and saved in the
system.
Alternate Flows Alternative procedure 1: Input validation error If an admin user provides
invalid data (for example, missing required fields) when editing an item, the
system displays an error message and does not proceed. until valid data is
provided. Alternative flow 2: Transaction not found If an administrative
 user tries to search for a transaction that does not exist in the system, the
system provides a response indicating that the transaction was not found.

ID UC05
Title View Users
Description Admin can view the users details which are given during registration.
Entities Involved E01: Admin
Preconditions Administrator is logged in to the system. Admin can view the users details
which are given during registration.
Primary Flow 1. Admin user logs into the system. 2. Admin user navigates to the user
management section. 3. Admin user selects an option to view users. 4.
The system retrieves and displays a list of user profiles, which may include
information such as user ID, username, full name, email, and other relevant
details. 5. Admin user can scroll through and review the user profiles.
Postconditions Registered user information will be stored in the system.
Alternate Flows Alternate Flow 1: No User Profiles Found If there are no user profiles in
the system, the system should display a message to inform the admin user
that there are no users to view. Alternate Flow 2: Search and Filter Options
The system may provide search and filter options to help the admin user
narrow down the list of users. This would be an alternate flow where the
user interacts with search and filter controls to find specific users based on
criteria like username, email, or user role. Alternate Flow 3: Detailed User
Information In the primary flow, the system may display a summary of
user details. An alternate flow could involve the admin user clicking on a
user profile to view more detailed information, including account settings,
permissions, and activity history.

ID UC06
Title Register
Description User have to register with essential details for food ordering system.
Entities Involved E02: User
Preconditions 1. The user has accessed the registration page. 2. The user has a valid
email address, phone number that hasn’t been registered before
Primary Flow 1. The user accesses the registration page on the application or website. 2.
The user is presented with a registration form. 3. The user fills out the
registration form, providing required information, which may include: Full
name Email address or phone number Password Contact information
(optional) Other required details 4. If the provided information is valid, the
system generates a unique login ID and password for the user. 5. The
system sends a confirmation email to the user's provided email address
with instructions on how to complete the registration process. 6. The user
receives the confirmation email and follows the instructions to activate
their account. 7. After confirming the account, the user can log in using the
provided login ID and password.
Postconditions 1. The user has a unique username and password for logging into the
system. 2. The user’s email address is confirmed and associated with their
account.
Alternate Flows Alternate Flow 1 - Email already exists: If the email is already in use by
another account, the system displays the error message "Email already
exists". Users can choose to go back and provide a different email address
or choose another method to recover their account. Alternate Flow 2 -
Invalid password: If the password does not meet the system
requirements (for example, at least 8 characters, contains letters and
numbers), the system displays the error message "Invalid password". The
user can go back and enter another password that complies with the
system requirements. Alternate Flow 3 - Connection error: If the system
encounters an error during account creation (for example, database
connection error), the system displays the error message "Connection
error". Users can try again or contact support to resolve the issue.

ID UC07
Title Login
Description User have to login with their credentials to access food ordering system.
Entities Involved E02: User
Preconditions The user has a valid "User" account ID and password.
Primary Flow Go to the app or web and click log in Enter account and password
The application runs to the home page Postconditions
Postconditions The user is successfully logged into the User account.
Alternate Flows Alternate Flow 1: Forgot Password User clicks on a "Forgot Password"
link. User is prompted to enter their email address or answer security
questions. The system sends a password reset link or resets the password
based on the security questions. Alternate Flow 2: Account Lockout If
the user enters incorrect credentials multiple times, the system may
temporarily lock the account. The user must follow a specific process to
unlock their account, which may involve receiving an email or contacting
customer support. Alternate Flow 3: Account Creation If the user does
not have an existing account, there should be a flow to create a new
account. This typically involves providing necessary information and setting
up a new ID and password. Alternate Flow 4: Wrong password If the user
enters an invalid Admin account ID or password: The system displays an
error message indicating that the login credentials are incorrect. The user
is prompted to re-enter the correct credentials or recover/reset the
password if needed.

ID UC08
Title Menu List
Description Different food items with respective categories viewable to user.
Entities Involved E02: User
Preconditions User logs into the system.Different dishes with corresponding categories
that can be viewed by the user.
Primary Flow 1. User logs into the system. 2. Users navigate to the Menu list section 3.
User selects an option to view a list of dishes 4. Different dishes with
corresponding categories that can be viewed by users
Postconditions 1. Information about the dishes that users view will be stored in the
 system. 2. If the user searches for a dish, it will be updated and saved in the
system.
Alternate Flows

ID UC09
Title Item Details
Description User can view food items details and buy the product by doing online
payment.
Entities Involved E02: User
Preconditions 1. The user is logged into the system. 2. The user has the necessary
permissions to view item details. 3. There are existing user accounts in
the system. 4.User can view food items details and buy the product by
doing online payment.
Primary Flow 1. User logs into the system. 2. User navigates to the Item detail section.
3.User selects an option to view food items details 4. The system retrieves
and displays a list of item detail, which may include information such as
item ID, name item, price, and other relevant details. 5. User can buy the
product by doing online payment
Postconditions 1.The user has viewed the item detail as requested. 2. The item detail
remain unchanged in the system. 3.Users must have a credit card or online
payment application
Alternate Flows Alternate Flow 1: No Item Detail Found If there are no Item Detail in the
system, the system should display a message to inform the user that there
are no Item Detail to view. Alternate Flow 2: Search and Filter Options
The system may provide search and filter options to help the user narrow
down the list of item. Alternate Flow 3: Detailed Item Information In the
primary flow, the system may display a summary of Item Detail.

ID UC10
Title View Cart
Description User can view their cart details, delete food items from cart, update
quantity etc.
Entities Involved E02: User
Preconditions 1. The User is logged into the system. 2. User can view their cart details,
delete food items from cart, update
Primary Flow 1. User logs into the system. 2. User accesses the View Cart section. 3.
Admin user selects an option to view cart details, remove food items from
cart, update quantity. 4. If viewing cart details: Users see necessary
information about their cart (for example: item name, price, quantity). 5. If
updating quantity: User selects the quantity of items to update. User makes
changes to product quantity. The system confirms the changes. If the
changes are valid, the product quantity will be updated. 6. If removing a
product from the cart: User selects the item to delete. The system prompts
the user for confirmation. If confirmed, the item will be removed from the
cart.
Postconditions 1. If you view shopping cart details, item information will be stored in the
system. 2. If you update the product quantity, detailed information about
 the quantity will be updated and saved in the system. 3. If you delete an
item from the shopping cart, that item will be deleted from the system.
Alternate Flows Alternative procedure 1: Input validation error If the user provides invalid
data (for example, missing required fields) when adding or updating a
supplier, the system displays an error message and no Continue until valid
data is provided. Alternative flow 2: Product not found If a user tries to
update or delete a product that does not exist in the system, the system
provides a response indicating that the product was not found. Alternative
flow 3: Cancel confirmation If the user cancels the confirmation prompt
when deleting a product, the system will not proceed with the deletion

ID UC11
Title View Orders and Status
Description User can keep track of their orders with delivery status.
Entities Involved E02: User
Preconditions 1. The user is logged into the system. User can keep track of their orders
with delivery status.
Primary Flow 1. User logs into the system. 2. Users navigate to the View Orders section
3. User can keep track of their orders with delivery status.
Postconditions 1. Order status information will be stored in the system. 2. If the status is
updated, the order will be updated and saved in the system
Alternate Flows Input validation error If an user provides invalid data (for example, missing
required fields) when editing an item, the system displays an error message
and does not proceed. until valid data is provided. Order not found If a
user tries to update an order that does not exist in the system, the system
will provide a response indicating that the order was not found.

Quality Attribute Scenarios

No Quality Attribute Scenarios Available.

Technical Constraints
No Technical Constraints Available.

Business Constraints
No Business Constraints Available.

Dynamic Perspective Diagrams

No views exist for this perspective.

Static Perspective Diagrams

No views exist for this perspective.

Physical Perspective Diagrams

No views exist for this perspective.
Traceability Matrix
Operational Use Cases
UC01: Add Food Items
No assignments exist for this architectural driver
UC02: View / Edit (Price, Enable/Disable) / Delete Items
No assignments exist for this architectural driver
UC03: View Orders
No assignments exist for this architectural driver
UC04: View Transactions
No assignments exist for this architectural driver
UC05: View Users
No assignments exist for this architectural driver
UC06: Register
No assignments exist for this architectural driver
UC07: Login
No assignments exist for this architectural driver
UC08: Menu List
No assignments exist for this architectural driver
UC09: Item Details
No assignments exist for this architectural driver
UC10: View Cart
No assignments exist for this architectural driver
UC11: View Orders and Status
No assignments exist for this architectural driver

Quality Attribute Scenarios

No traceability matrix for quality attribute scenarios exists.

Business Constraints
No traceability matrix for business constraints exists.

Technical Constraints
No traceability matrix for technical constraints exists.
3.System Context Diagram
4.Draw C&C view

4.1 Prose
The online food ordering system is to automate the existing manual system with the help of advance
computerized software so, that valuable data can be stored for longer period with easy accessing and
manipulation of the same.The registered user can access the account with valid credentials. User can
surf the food items according to categories, Cart and online payment options are available to user. User
can track their orders with the food details.
4.2 Roles & Responsibilities
User: User have to login with their credentials to access food ordering system.
Menu List Food:
 Menu Management: Responsible for updating and maintaining the list of available food items
on the platform.
 Categorization: Organizing food items into categories (e.g., appetizers, main courses, desserts)
for easy navigation.
  Pricing: Setting and updating prices for each food item.
 Description: Providing detailed descriptions and images for each item to help customers make
informed choices.
Order:
 Order Placement: Handling the process of customers selecting food items and placing orders.
 Confirmation: Confirming orders and sending notifications to customers and restaurants.
 Order Modification: Allowing customers to modify or cancel orders within specified time
frames.
View Order and Status:
 Order Tracking: Providing a feature for customers to track the status of their orders in real-
time.
 Communication: Communicating order updates to customers via email, SMS, or in-app
notifications.
 Order History: Maintaining a history of past orders for customers to reference.
View Cart:
 Cart Management: Allowing customers to review and modify the items in their shopping cart
before finalizing the order.
 Price Calculation: Calculating the total cost of items in the cart, including taxes and fees.
Payment:
 Payment Processing: Handling payment transactions securely, including credit card processing,
digital wallets, and other payment methods.
 Payment Gateway Integration: Integrating with third-party payment gateways for secure and
reliable transactions.
 Refunds and Disputes: Managing refund requests and customer disputes related to payments.
Security:
 Data Security: Ensuring the security of customer data, including personal information and
payment details.
 Secure Communication: Implementing secure communication protocols (e.g., HTTPS) to protect
data during transmission.
 Authentication and Authorization: Implementing user authentication and authorization
mechanisms to control access to sensitive information and features.

Database:
 Database Management: Managing the database that stores information about users,
restaurants, menu items, orders, and transaction records.
 Data Integrity: Ensuring the accuracy and consistency of data within the database.
 Backup and Recovery: Implementing data backup and recovery procedures to prevent data loss
in case of system failures.
5.Draw Allocation View