SRS (Food System)
SRS (Food System)
SRS (Food System)
Specification
For
Version 1.0
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.
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.
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.
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. Overall Description
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.
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.
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.
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.
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.
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.
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
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
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
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
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.
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.
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.
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.
Block Diagram: