Software Requirements

Specification
For

Food Ordering System

Version 1.0

Project Code CS-303

Supervisor Ms Rubab Manzar
Project Team Arsalan
Athar Abbas
Abdul Moiz Zaveri

Submission Date 26/03/18

Software Requirements Specification Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 1
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment .................................................................................................................... 3
2.5 Design and Implementation Constraints .......................................................................................... 3
2.6 User Documentation ........................................................................................................................ 3
2.7 Assumptions and Dependencies ...................................................................................................... 3
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ................................................................................................................................. 3
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 4
3.4 Communications Interfaces ............................................................................................................. 4
4. System Features .......................................................................................................................4
5. Other Nonfunctional Requirements .......................................................................................6
5.1 Performance Requirements .............................................................................................................. 6
5.2 Safety Requirements ........................................................................................................................ 6
5.3 Security Requirements ..................................................................................................................... 7
5.4 Software Quality Attributes ............................................................................................................. 7
5.5 Business Rules ................................................................................................................................. 7
6. Other Requirements ................................................................................................................7
Appendix A: Glossary....................................................................................................................8
Appendix B: Analysis Models .......................................................................................................8
Appendix C: To Be Determined List ............................................................................................8

Revision History
Name Date Reason For Changes Version
Software Requirements Specification Page 1

1. Introduction

1.1 Purpose

The purpose of this document is to describe overall system. This document will explain
the purpose and features of the system, the interface of the system, how the system will
work, the limitations and the output of the system.

1.2 Document Conventions

In this document headings and sub headings are numbered to create easiness for the
reader. Important times are marked as bold and italics are used to use specified terms.

1.3 Intended Audience

This document is intended for stakeholders and directors and the judging authorities.
Moreover this document can also make sure of customer satisfaction if this product is
sold to a customer.

1.4 Product Scope

This system will help to manage and run the restaurant business systematically. In this
management system, we will provide an app that can be used by the customers to order
food. This will ultimately lead to hire less waiters and receptionist and create an
opportunity to appoint more chefs and better kitchen place to serve food faster than
normal. This will save customer’s time and effort from standing in lines. Customers can
also make payment through debit or credit cards which will be integrated with the
management software. Customers can see current deals of the restaurant. All the
information about daily expenses and income will be saved in the system and hence it
will enable owner to calculate profit or loss easily. Also, the required information’s about
employees will be saved in the system which can be only accessed by the system admin.
1.5 References
1) https://www.isr.umd.edu/~austin/ense621.d/projects04.d/project-food-ordering.html

2) Armstrong, Hilary. "Inamo Interactive Restaurant London." World News. Web. 28

Apr. 2011. http://wn.com/Inamo__Interactive_Restaurant_London

3) "Interactive Food And Drink Ordering System Invention." Freshpatents.com: Patent

Applications Updated Each Week, RSS, Keyword Monitoring. Web. 28 Apr. 2011.
http://www.freshpatents.com/-dt20100429ptan20100106607.php
4) Inamo Restaurant, Soho, London - Interactive Oriental Fusion Restaurant and Bar.
İNAMO. Web. 28 Apr. 2011. http://www.inamo-restaurant.com/
Software Requirements Specification Page 2

2. Overall Description

2.1 Product Perspective

This product will basically take orders from each individual table, confirm their order,
show the bill and total amount and then tell the serving time accordingly. This system
will help owner to reduce the working staff such as waiters and receptionist. Moreover it
will also help customers as all the things will be handled through this software so to edit
the order or to place an order they do not have to wait for the waiter they can only press
the button and this will enable them to do anything. They do not have to stand in lines for
placing the delivery order all they have to do is place an order through a system.

2.2 Product Functions

Common problems faced by consumers when visiting restaurants which lead to

dissatisfaction:
1) Poor Customer Service
2) Incompetent Staff
3) Great Variation in customer service between peak and off peak timings

Solutions are:
1) A food Ordering System at restaurants would enable customers to no longer wait
in queues when order for dine in or delivery.
2) Benefits to owner would be less cost and time saving and a computerized
environment will also attract customers.

2.3 User Classes and Characteristics

There are three type of user who will use our system.
First is the customer who will just click a button to enter the menu screen he will than
select the food he wants to order. Then he will add those items to bucket and he will
finalize the bucket by pressing a button. Then he will get the total amount and last
confirmation will be done when the payment is successful. He will than receive the
estimated time left in delivery of food.
The second user will be a chef/staff who will prepare the order according to his
expertise. He will receive the order and he will prepare the food and the specified
quantity.
The third user will be the owner/admin of the restaurant who can hire staff and who can
check the status of his restaurant. He can also check the income generated by the
restaurant. He can also view the feedback of the customers.
Software Requirements Specification Page 3

2.4 Operating Environment

This application will work on windows 7 or higher. This will be based totally on GUI.
And will be implemented in JAVA. Thus it will be accessible on mostly every pc.

2.5 Design and Implementation Constraints

Our application can only be implemented on desktop so windows environment limits it.
Moreover a SQL database management application will be needed to access the database
and get information about the data. So it will limit to single software.
Moreover, there is a dependency of desktops while implementing this idea. If the
restaurants have large number of tables than it will need as many desktops as much the
tables so it will limit the restaurants as this is huge onetime cost.

2.6 User Documentation

FAQ’s will be available for the user too fully understands the operation of the
application. The GUI will also be simple which will enable user to easily understand the
system.

2.7 Assumptions and Dependencies

If the restaurant cannot buy more desktops and cannot hire such staff who understands
the functionality of the system or the restaurant experiences such customers who are not
familiar with such technologies than it will be worthless to implement this system over
there.

3. External Interface Requirements

3.1 User Interfaces

The System will be equipped easy-to-use Graphical User Interface. The first page will be
the login page where admin and staff will be asked for the authentication. After
successful authentication the system will transit to the next state and will show the
relative User Interface to the concerned user with valid functions of what that specific
user has a right to perform. User from there can choose the option they want and will be
forwarded to their own separate functions such as admin can add or remove staff; kitchen
staff will proceed the orders and so on.
Software Requirements Specification Page 4

3.2 Hardware Interfaces

Laptop/Desktop PC

1) OS – windows 7//8/8.1/10/10.1
2) Hard disk – 80 GB or More
3) RAM – 1 GB or More
4) Keyboard – Standard QWERTY keyboard for typing interface
5) Mouse – Standard mouse with 2 buttons

3.3 Software Interfaces

1) JDK 1.8 - Java is fast, secure, and reliable. From laptops to datacenters, game
consoles to scientific supercomputers, cell phones to the Internet,
2) Netbeans 8.1 - IDE for Java developing.
3) SQLite server - Database connectivity and management

3.4 Communications Interfaces

Windows can be as a communication interfaces. Since this system allows centralized

database so the connection are only the hardware devices or hosts. There is no need of
separate network for them.

4. System Features
Our system consists of 3 main users and the system features depends on them. The three
users are customers, kitchen staff and the admin of the restaurant. Following are the
confirm features of our system. Other features can also be added in according to the
stakeholder’s requirement

4.1 Login feature

4.1.1 Description and Priority
This feature actually gives access to the authorized user in the system which is very
important for security purposes. The risk of not having feature can affect the system
security overall.

4.2 Guest/Customer feature

4.2.1 Description and Priority
This feature actually gives access to the customer through which the customer is able to
enter in to the select dishes section. This feature is not password protected. Without this
feature the customer would not be able to enter their order.
Software Requirements Specification Page 5

4.3 Select Dishes feature

4.3.1 Description and Priority
This feature actually gives access to customer after he/she has pressed the guest button.
In this feature the customer is able to select the dishes and deselect them if done by error.

4.4 Submit Order feature

4.4.1 Description and Priority
This feature is available after the user is in the select dishes feature. After selecting the
dishes, the customer can click on confirm order to forward the order to the kitchen staff.

4.5 Check Order feature

4.5.1 Description and Priority
This feature is available after the user is has confirm the order. After this the customer
has the option to check its order. The customer would be able to see the staff name who
is preparing the dish but also the counter no he has to collect and the time remaining.

4.6 Confirm Order feature

4.6.1 Description and Priority
This feature is available after the user has received the order. This feature confirms that
the customer has been served with their food. Also the second screen of the system gets
activated asking for the customer feedback.

4.7 Give Feedback feature

4.7.1 Description and Priority
This feature is available after the user has finished its food and is ready to give the
feedback about the system, food and the restaurant overall.

4.8 Order Received feature

4.8.1 Description and Priority
This feature is available to the kitchen staff after they are login in to their systems. This
feature will list the orders that are in queue and the order will be selected by the kitchen
staff which will show order received on the customer screen. In this screen kitchen staff
can also predict the time remaining for the order.
Software Requirements Specification Page 6

4.9 Order Complete feature

4.9.1 Description and Priority
This feature is available to the kitchen staff after they are login in to their systems. This
feature will check the selected order completed and will show a pop up on the customer
screen that their food is complete and they can collect it from the particular counter.

4.10 Payment Received feature

4.10.1 Description and Priority
This feature is available to the staff who will collect the bill during the food is served on
the counter desk. User will provide the payment and the staff will record it in to the
database making that particular customer their payments clear.

4.11 Check Profit feature

4.11.1 Description and Priority
This feature is available to the admin only. This feature will provide the total income of
the restaurant to the admin for the specified date.

4.12 Manage Dishes feature

4.12.1 Description and Priority
This feature is available to the admin who can add dishes to the restaurant which will for
the next time will be shown to the customers. Dishes can also be deleted from the
database in the same manner.

4.13 Manage Staff feature

4.13.1 Description and Priority
This feature is available to the admin who can maintain the staff working in the
restaurant which includes adding, editing or removing them.

4.14 Manage Restaurant Environment feature

4.14.1 Description and Priority
This feature is available to the admin who can easily maintain the environment of the
restaurant which includes number of counters, number or tables and number of hours the
restaurant is open. He can also set targets for the specific days.
Software Requirements Specification Page 7

5. Other Nonfunctional Requirements

5.1 Performance Requirements

1) Response time: The systems will response back within a second after checking the
patient information and other information.
2) Capacity: The system has the ability to 800-1200 records at a time.
3) User interface: User interface screen will response within 3-5 seconds.

5.2 Safety Requirements

In Case of any damage to the System, the System will provide a complete backup of
records present in the database. System will also ask for the conformation of user in
order to avoid any kind of unusual behavior.

5.3 Security Requirements

The proper authentication process will be the part of the system so; no one other than
concerned user can access the system or information stored in the database. In order, to
avoid hacking user must set strong and unique passwords. Since customers will not be
authorized so they are not allowed to visit any secured data location, they will just add
their orders so that security is not compromised.

5.4 Software Quality Attributes

1) AVAILABILITY: The system shall be available all the time.
2) CORRECTNESS: bug free software which fulfills the correct need/requirements of
the client.
3) MAINTAINABILITY: The ability to maintain, modify information and update fix
problems of the system.
4) USABILITY: software can be used again and again without distortion.
5) ACCESSIBILITY: Administrator and many other users can access the system but
the access level is controlled for each user according to their work scope.
6) ACCURACY: The reliability on the information/output. Can depend/be sure of the
outcome.
7) STABILITY: The system outcome/output won’t change time to time. Same output
will be given always for a given input.

5.5 Business Rules

1) Developer is not responsible for misuse of the software.

2) Warranty period of maintaining the software would be one year.
3) Additional payments will be analyzed and charged for further maintenance
4) If any error occur due to a user’s improper use. Warranty will not be allocated to it.
Software Requirements Specification Page 8

5) No money back returns for the software.

6) Trust bond placement should be done before designing and coding. An advance or an
agreement.

6. Other Requirements
All of the requirements are fully described in features and functional requirements none
of the requirements are left. Moreover java and SQL languages will be required to get
ease to access data ad develop an application. We can also get the database centralized so
that multiple users can access it altogether but it increases the chances of inconsistency
but this can be solved and will require some time to get over it.
Software Requirements Specification Page 9

Appendix A: Glossary
UI: User Interface: The interface which will be available for the user to interact with the
system.
User-Friendly: Making user's experience more and more interactive with the system.
Stakeholder: Any person with an interest in the project who is not a developer.
Software Requirements Specification: A document that completely describes all of the
functions of a proposed system and the constraints under which it must operate.

Appendix B: To Be Determined List

1) Main GUI design and database connectivity.
2) Mid Evaluation with report.
3) System Design Specifications.
4) Final Report with System.

Appendix C: Analysis Models

Use Case Diagram:

Software Requirements Specification Page 10

Block Diagram: