2.1. priority requirements. This UOG smart cafe is

2.1. Introduction

2.1.1. Purpose:

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!

order now

document presents an explanation of the features, objectives, application and user
interface of “UOG Smart Cafe”. It will describe that how under which conditions
the system must operate. This SRS describes the software functional and
nonfunctional requirements of the “UOG smart café”. This document is intended
to be used by the members of the project team that will implement and verify
the correct functioning of the system. All requirements specified here are high
priority requirements. This UOG smart cafe
is the system where the students/ workers/ faculty will order their food and receive their orders from
cafeteria without any delay, as they can directly go and collect what they
ordered without waiting any time. The purpose of the system is to develop a
simple Canteen Automation System and implement it by android mobile application
and It will be applicable in the boundaries of UOG under certain

Intended Audience and Reading Suggestions

document is intended for many kinds of readers. These readers are system
developers, system designers, system tester and cafeteria owner. By reading
this document they will get knowledge about the system and learn about what the
project is implemented for. So, if the reader will read this document he will
get the clear idea about the system, what are the functionalities and features of
the system.

2.1.3. Project Scope and
Product Features

The system will run
and manage the cafeteria business systematically. In UOG smart café system, we
will provide a mobile application that can be used by the users to place their
order. So, the owner of the cafeteria can evaluate the system and maintain proper
check and balance. This will lead the owner to hire less no. of waiters and
create an opportunity to provide a better place for customers and appoint more
chefs. The customers can also make payment through their accounts which they opened
in cafeteria. Users can see current deals and offers of the café. All the
information of expenditures and profits of a working day will save in the system.
The information of cafeteria employees saved in the system and cafeteria admin can
access them.

2.1.4. References

The references are as follow:

Writing a Software Requirements
Specification Document


Christine. Process Impact Business
Rules Catalog,


example documents


2.2. Overall Description

2.2.1. Product Perspective

The “UOG Smart
Café” is a new system that replaces the current manual and telephone processes
for ordering and picking up lunches in the cafeteria. The context diagram in
Figure 1 illustrates the external entities and system interfaces. The system is
expected to evolve over several releases, ultimately connecting to the Internet
ordering services for several types of user’s and to credit charges online


2.2.2. Product Functions

The functions of this system will perform in this order.

Placement via application
through account
at Spot for Faculty
and Purchase Reports
for each individual Product

2.2.3. Operating Environment

The Operating
environments are as follow:

OE-1:     Operating System: window 7 or above versions
for admin web application.

OE-2:     Operating System: android jellybean 4.2 or
above versions for users of the system

OE-3:     The
UOG Smart Cafe shall operate with the following Web browsers: Microsoft
Internet Explorer versions 8.0 and above, Google chrome version 50.0 or above,
Firefox 50.0 or above and Safari version 9.0 or above.

OE-4:     3
computers. (One for owner, one for
cashier, one for manager)

OE-5:     The
UOG smart café shall permit user access from the corporate Intranet and, if a
user is authorized for outside access through the corporate firewall, from an
Internet connection.

2.2.4. Design and Implementation Constraints


CO-1:     The
system’s design, code, and maintenance documentation shall conform to the Intranet Development Standard.

CO-2:     The
system shall use the current corporate standard MySQL database.

CO-3:     All
HTML code shall conform to the HTML 5 standard.

CO-4:     All
scripts shall be written in PHP.

2.2.5. User Documentation

UD-1:     The
system shall provide an online hierarchical help system in HTML that describes
and illustrates all system functions.

UD-2:     The
first time a new user accesses the system and on user demand thereafter, the
system shall provide an online tutorial to allow users to practice ordering
meals using a static tutorial menu.

2.2.6. Assumptions and Dependencies

AS-1:      It is
assumed that each user has proper working internet connection in order to user
this system.

AS-1:      The
cafeteria is open for breakfast and lunch from (8:30Am-4:30PM) every university
working day in which users are expected to be on site.

DE-1:     The
operation of the UOG Smart Cafe depends on changes being made in the Cafeteria
Inventory System to update the availability of food items as UOG smart cafe
orders are accepted.

2.3. External Interface Requirements

2.3.1. User

UI-1:      The UOG Smart Café screen displays shall
conform to the Internet Application User
Interface Standard.

UI-2:      The system shall provide a help
link/activity from each HTML page/android activities to explain how to use that

UI-3:      The android application shall permit
complete navigation and food item selection using the touch screen and embedded

2.3.2. Hardware Interfaces

No hardware interfaces have been identified.

2.3.3. Software Interfaces

SI-1:       Cafeteria
Inventory management

SI-1.1:       The COS shall transmit the quantities of
food items ordered to the Cafeteria Inventory System through a programmatic

SI-1.2:       The UOG smart café system shall poll the
Cafeteria Inventory System to determine whether a requested food item is


SI-2:       Accounts management

               The COS shall communicate with
the Payroll System through a programmatic interface for the following

SI-2.1:       To submit a payment request for a
purchased meal.

SI-2.2:       To view previous purchased records.

SI-2.3:       To deduct all or part of paid charges if
a user does not take his/her order.

SI-2.4:       To reverse all or part of a previous
charge because a user rejected a meal or wasn’t satisfied with it, or because
the meal was not delivered per the confirmed delivery instructions.

SI-3:       The system shall communicate with the
content manager to get the product specifications.

2.3.4. Communications Interfaces

CI-1:       The UOG Smart Café system shall send a
notification message to the user to confirm acceptance of an order, order
prepared, price, and delivery instructions.

CI-2:       The UOG Smart Café system shall send a
message to the Patron to report any problems with the meal order or delivery
after the order is accepted.

2.4. System Features

2.4.1. Place
Order via Application

User can order food with the application but
it needs specific internet connection.

2.4.2. Take

The chef will take the order and if it is
available to make then he will confirm the order and start to prepare food.

2.4.3. Serve

When the food is ready to be served then the
chef will alert the waiter/distributer/deliverer. After this waiter will insure
the order is served. 

2.4.4. Payment

The payment is done at the time of order
placement from user account. So, the café staff will prevent from taking fake
order requests.

2.4.5. Available
/ Required Goods

The Chef will add what goods are available
and the admin can see that data and the chef will add what goods are required.

2.4.6. Customer

The user will be get registered and be the
member of special customer.

2.4.7. User

Customer can give overall review about the
food items and services provided by the café.

2.5. Other
Nonfunctional Requirements

2.5.1. Performance

performance requirement for this project are as follow:

PE-1:      The
system shall accommodate 400 users during the peak usage time window of 3:00pm
to 4:30pm local time, with an estimated average session duration of 5-10

PE-3:      Responses
to queries shall take no longer than 9 seconds to load onto the screen after
the user submits the query.

PE-4:      The
system shall display confirmation messages to users within 5 seconds after the
user submits information to the system.

2.5.2. Safety Requirements

No safety
requirements have been identified.

2.5.3. Security Requirements

SE-1:      All
network transactions that involve financial information or personally
identifiable information shall be encrypted per BR-33.

SE-2:      Users
shall be required to log in to the Cafeteria Ordering System for all operations
except viewing a menu.

SE-3:      Patrons
shall log in according to the restricted computer system access policy per

SE-4:      The
system shall permit only cafeteria staff members who are on the list of
authorized Menu Managers to create or edit menus, per BR-24.

SE-5:      Only
users who have been authorized for home access to the corporate Intranet may
use the COS from non-company locations.

SE-6:      The
system shall permit Patrons to view only their own previously placed orders,
not orders placed by other Patrons.

2.5.4. Software Quality Attributes

Availability-1:   The
Cafeteria Ordering System shall be available to users on the corporate Intranet
and to dial-in users 99.9% of the time between 5:00am and midnight local time
and 95% of the time between midnight and 5:00am local time.

Robustness-1:   If
the connection between the user and the system is broken prior to an order
being either confirmed or canceled, the Cafeteria Ordering System shall enable
the user to recover an incomplete order.