Scribd
Upload
52 views4 pages

Food Ordering System

The document outlines several non-functional requirements for an e-commerce system including usability, security, performance, maintainability, scalability, social sharing, order and checkout flow, and product attributes. Specifically, it requires the system to have an easy checkout process, protect against attacks, load quickly, support future changes, handle high volumes of products and customers, integrate social media sharing and reviews, manage complex order statuses and types of products.

Uploaded by

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

Food Ordering System

The document outlines several non-functional requirements for an e-commerce system including usability, security, performance, maintainability, scalability, social sharing, order and checkout flow, and product attributes. Specifically, it requires the system to have an easy checkout process, protect against attacks, load quickly, support future changes, handle high volumes of products and customers, integrate social media sharing and reviews, manage complex order statuses and types of products.

Uploaded by

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

 Non-functional Requirement of a System

Usability
 A customer should easily find the right product for them, and make a
purchase without contacting us.
 No multistep checkout: users must reach the “add to cart” button in one
step from PDP.
Security
 Only the system data administrator can assign roles and change access
permissions to the system.
 The website must be resilient to any kind of attacks, including DDoS and
XSS attacks.
Performance
 The website’s homepage should load in less than 4 seconds on iOS 10+,
Safari on 4G.
Maintainability
 Because we are looking to grow, the website shall remove all the back-
end complexities for in-house engineers to make changes to the system in
the future.
Scalability
 Our main goal for the next two years is internationalization, so the
website shall have multiple store views for each country we’re selling to.
 The store shall expand to support 500k+ SKUs on a single server without a
negative impact on the website load speed.
Social Sharing
 Our product info should be shared on Facebook, Instagram, Pinterest, and
LinkedIn.
 User comments from Facebook should appear on the product detail page
in the “Customer Reviews” page.
Order & Checkout Flow

 The website shall show the following order statuses: confirmed,


processing, shipped, returned.
 After the customer is registered on the website, they should receive one
extra year of warranty on the purchased order.
Product Attributes
 The website shall support simple and bundle product types.
 Product Images on the product detail page should have the option to
zoom in.
User Requirements

 Advanced, mobile-first approach (UI and UX): It's necessary to use utilities that
collect user metrics: the duration of the interaction with the app, which screens
the user visited, when, and how the session was completed, which buttons were
pressed, and many more. Moreover, all changes in the interface should be tested
on small focus groups, collecting statistics, and process feedback.
 Quick search by dishes and restaurants: With the ability to access user location
to order any meal from the nearest restaurant in a short time.
 Order status: Get information about the order status in real-time (accepted,
prepared, courier on the way).
 Convenient method of payment: The user should be able to pay for the order
in different ways – cash/credit card – it allows to cover more audience and widen
the target audience.
 First-line support: It's important to don't neglect the value of the support that
handles orders, complaints, delivery problems. 
 Promo code system: The promotion code system is an opportunity to make up
for disputes with unsatisfied customers by offering gifts/promotions.

Tech Requirements

 Reliable project infrastructure: A full-fledged delivery service with logistics


requires much effort invested in the server-side software. If there is a sudden
inflow of users to the service, it will affect everything: the performance of servers
and server software, network equipment, traffic, resource quota reserves, the
ability of the application to handle competitive requests itself, among others.
 Administrative interface and utility usability: Properly developed admin part
can save time and improve the efficiency of the entire service. Imagine a couple
of seconds saved on a frequent operation and multiplied by the number of
operators in the call center. It can play a big part in the outcome for the potential
client.
 Application's behavior: Logging everything that happens in the system:
incoming and outgoing traffic, algorithm arguments, conditions, and received
results. Here can be used a single ID for the series of logs to tie them to the same
long-term operation. All this will help to understand the application's behavior
and diagnose the problems.
 Automated tracking business and technical metrics: Tracking and making
forecasts is essential to troubleshoot, proactively manage problems, and
potentially prevent. As for business – everything, intended for revenue
generation, especially long-playing processes, should be reflected in the
database.
 Code review process: Projects tend to grow, and with them, the team grows,
which leads to more diverse implementation approaches. Code review allows the
exchanging of experience, compiling the approach to solve the problems, as well
as the rotation of knowledge, which increases the so-called bus factor –
concentration of expertise among individual team members.
 Maintain and actualize the documentation: Rules and practices gained in the
process that will be very useful for developers and will help to avoid
inconsistencies.
 Ongoing product development: Always look for ways to promote, enhance,
update the product. It includes gathering data about the user needs and wants,
designing and engineering the service, and testing it on the targeted audience.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy