SRS Fast Food

Online Fast Food Management System
SOFTWARE REQUIRNMENTS SPECIFICATION DOCUMENT
[Category]
i Software Requirements Specification

Revision History
Date Description Author Comments
Version 1 First Revision
Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:
Signature Printed Name Title Date
Supervisor , CSIT-21306
ii Software Requirements Specification

Table of Contents
1. Introduction 1
1.1 Purpose 1
1.2 Scope 1
1.3 Definitions, Acronyms, and Abbreviations. 2
1.4 References 3
1.5 Overview 4
2. The Overall Description 5
2.1 Product Perspective 5

2.1.1 Operations 5
2.1.2 Site Adaptation Requirements 5
2.ProductFunctions 5
User Characteristics 6
2.4 General Constraints 7
2.5 Assumptions and Dependencies 8
3. Specific Requirements 9
3.1 External Interface Requirements 9

3.1.1 System Interfaces 9
3.1.2 Interfaces 10
3.1.3 Hardware Interfaces 10
3.1.4 Software Interfaces 11
3.1.5 Communications Interfaces 11
3.2 Functional Requirements 12
iii Software Requirements Specification

3.2.1 <Functional Requirement or Feature #1> 13
3.2.2 <Functional Requirement or Feature #2> 14
3.3 Use Cases 15

3.3.1 Use Case #1 16
3.3.2 Use Case #2 17
3.4 Classes / Objects 39

3.4.1 <Class / Object #1> 40
3.4.2 <Class / Object #2> 40
3.5 Non-Functional Requirements 41

3.5.1 Performance 41
3.5.2 Reliability 41
3.5.3 Availability 42
3.5.4 Security s42
3.5.5 Maintainability 42
3.5.6 Portability 42
3.6 Logical Database Requirements 43
3.7 Design Constraints 45
4. Analysis Models 46
4.1 Sequence Diagrams 47
4.2 Data Flow Diagrams (DFD) 48
4.3 State-Transition Diagrams (STD) 49
5. Supporting Information 56
Appendix A – Background Research on: 57

Appendix B – Data Dictionary 65
iv Software Requirements Specification

1. Introduction
The fast food restaurant management system can provided a lot of things which can be
easily access and can be good in taste. And the food that can be provided in the restaurant
can be good. And in our SRS we should define the whole management system of the
restaurant. We should define the how many workers works to run our project and how
many customers will be entered in the restaurant to order their place. And we should make
sure that everyone can be worked properly and every customer should be deal properly and
no one can complain to us. We should make sure that the software we should be used must
be easy and can be easily understandable to everyone no complex software will be made
that we can face difficult to manage our software. And whole record of the system should
be used and store in computer that whenever we want to use we can easily access them by
the manager and by the employee that works in the restaurant.
1.1: Purpose:
The purpose of the system should be described in this section. The SRS will allow to
complete understand the system of management. The clear understanding of the system
and its functional will allow for the correct software to be developed for the end users and
will be used for the development of the whole project. By reading the SRS we should be
able to design the complete software and the project that can be implemented and testing
as a whole.
The SRS can be used by the system development team which can be manage by the
manager and the end users of the system that works in making the whole project.
1.2 Scope
In this undertaking fast food site will be planned named Fast Food Restaurant and a site
will be made.
1 Software Requirements Specification

In this venture, a fast food organization is planned and as a contextual investigation to
empower clients request for sustenance and get it conveyed in like manner furthermore to
lessen the long lines of clients at the counter requesting for nourishment and to diminish
the work master on the representatives. The accompanying things are in addition to other
things that are talked about and what the product would handle:
 About the fast food organization.
 The fast food and the administrations offered there.
 Online buy.
 Type of nourishment gave.
 In this venture a database will be made which contain record of the clients .the
undertaking contain the name, address portable number of the clients.
 The undertaking will contain the record of menu.
 Menu cost will be kept up.
 Will contain the record of workers.
 A site will be made.
1.3 Acronyms, and Abbreviations Definitions,
 SDLC:
System development life cycle
 OFFRMS:
Online Fast Food Restaurant Management System.
 CUSTOMER
Who will use the services.
 SQL:
Structured query language
 HTML:
Hypertext markup language
1.4 References
 http://www.siteground.com/tutorials/php-mysql/mysql_database_user.htm
 http://www.siteground.com/tutorials/php-mysql/connect-mysql/
 http://www.siteground.com/tutorials/php-mysql/php_mysql_connection.htm
 http://www.siteground.com/tutorials/php-mysql/database_connection.htm
 http://www.siteground.com/tutorials/php-mysql/execute_server_commands.htm
 http://www.siteground.com/tutorials/php-mysql/display_table_data.htm
 http://www.siteground.com/tutorials/php-mysql/individual_records.htm
1.5 Overview:
The Fast food Menu and Ordering System is a product bundle to encourage requesting
inside of a conventional eatery. The client can see the menu, place orders, call the server,
and compose the last bill through the surface PC interface incorporated with their table.
Servers can instate a table for clients, control table capacities remotely to help clients,
affirm orders, send requests to sustenance readiness staff and conclude the client's bill – all
through their remote tablet PC. The nourishment staff, with their touch-show interfaces to
the framework, can see arranges sent to the kitchen by servers. Amid arrangement, they
can tell the server the status of everything, and can send warnings when things are finished,
again through the touch-show. The framework contains full responsibility and logging
frameworks, and backings chief activities to represent remarkable circumstances, for
example, a supper being discounted or left. Clients are given an appealing and simple to-
use surface PC GUI with a move and customize "object" similitude in their menus. Servers
can perform all activities that the table framework ordinarily handles through their tablet
PCs, so in the case of a client being notable work the surface PC, the server can deal with

requests generally while utilizing holding the responsibility and logging elements of the
framework, and holding the same channel of correspondence with sustenance staff.
2. The Overall Description
2.1 Product Perspective
It is necessary user name and password to login in this system.User will enter user name
and password to login.In this project we will provide the tools sql server apache server and
php. The software described in this SRS is the software for a complete RMOS system. The
system merges various hardware and software elements and further interfaces with external
systems. Thus, while the software covers the majority of the system's functionality, it relies
on a number of external interfaces for persistence and unhandled tasks, as well as
physically interfacing with humans.
2.2 Product Functions
We will make a database in which we will contain the record the clients who will utilize
our administrations, for example, their name address, the information about recipes
likewise be contained, price of the administrations contained, service suppliers information
will be contained, for example, directors ,businesses ,and information about the wages of
the employers. The data about bosses will be contained, for example, their name address
and wages that will be given to them as per their work, for example, low wages employees
as indicated by their work that they will do and high wages employees as indicated by their
work.
• Allows for writing in client data
• When a client looks at the sum owed is shown
• Records installment
Following and Selling Food System
• Tracks all dinners bought

2.3 User Characterizes:
The clients of the surface PCs are stroll in clients and ought to subsequently be expected
to have no pertinent earlier aptitudes or training other than essential capacities to work a
robotized framework; not any more unpredictable than a stopping meter or candy machine.
The clients of the tablets and presentations are servers and gourmet specialists separately
and they ought to have the capacity to utilize the framework and further have the capacity
to prepare others with negligible preparing themselves. They should have the capacity to
clarify all components of the client interfaces with the exception of the server. Bosses
likewise fall into the same classification, however they will need to learn different
segments of the framework (discounts and so forth); these ought not be of remarkably more
prominent multifaceted nature than the standard capacities. This class of client would be
relied upon to have a middle school testament instruction or equal
2.4 General Constraints
The RMOS ought to be composed in an item situated dialect with solid GUI joins and a
straightforward, available system API. The essential applicant device chains are
Java/Swing, C++/Qt and Python/Qt. The framework must give an ability to parallel
operation and framework outline ought not acquaint adaptability issues with respect with
the quantity of surface PCs, tablets or showcases associated at any one time. The end
framework ought to likewise take into consideration consistent recuperation, without
information misfortune, from individual gadget disappointment. There must be a solid
review chain with all framework activities logged. While interfaces are secured in Section
2.1, it is significant that this framework is prone to fit in with what is accessible. In view
of that, the most versatile and convenient advancements ought to be utilized for the usage.
The framework has criticality seeing that it is a live framework. On the off chance that the
framework is down, then clients must not notice, or notice that the framework recoups
rapidly (seconds). The framework must be sufficiently dependable to run accident and
glitch free pretty much inconclusively, or encourage mistake recuperation sufficiently solid
such that glitches are never uncovered to its end-clients.

2.5 Assumptions and Dependencies
The SRS expect that none of the constituent framework segments will be executed as
inserted applications. The suggestion is that the objective equipment will give an ability to
standalone program/application organization and not require altered installed firmware to
be composed. It is further accepted that tablet PCs of adequate handling ability and battery
life will be used. The surface PCs utilized by the framework ought to encourage being
used/left on for amplified periods (adequate for day by day use) and that they are
programmable in the same manner as x86 engineering PCs. At long last, it is further
accepted that the sending environment is equipped for supporting an IEEE 802.11 remote
system for framework correspondence.
3. Specific Requirement:
In this section we will fulfill the requirement of the customer. The customer that wants to
eat we will try to provide them. In our restaurant we will provide each and every thing to
the customer that fulfill the customer need and which will customer easily get this thing
that we will provide to them. In this section the necessary things that we must need should
be used before we making our project like ram and hard disk and others important things.
And we also need to maintain the backup of important data that we must be store in
computer. We can do all these things because in every computer we must used our data
and in every pc we should easily do all things in this section we must inform all these
important things that we must used in our project making and which database we must b
used to make our project and which languages we must be used.
3.1. External Interface Requirement:
3.1.1. System Interface:

In this step we require the best system for designing our database that must be used further.
We should must used best and easy way to handle our necessary things that must be used
in this project. Like we used that computer which easily handle window 8 and of 4 GB ram
and hard disk that can easily store our necessary information.
Tools & platform:
DBMS: MYSQL server
Language: PHP
Phonetic Keyboard Layout
Reporting: Crystal Reports
Documentation: MS Word, MS Visio, UML Diagram
Technical:
Hardware Cost:
To implement the system they require four computers.
Assumption of cost:
Server Cost Rs. 1500
Cost of 4 PC’s 2*15, 000=30, 000
LAN Cost 5, 000
Software Cost:
Assumption of Cost:
PHP Free
MYSQL Free
3.1.2. Interface:
 The restaurant ordering system screen display confirm to the process impact.

 The system should provide the help link for each displayed html to explain how to
use the page.
 The web pages will permit complete navigation and food item selection in addition
to using the keyboard and mouse.
3.1.3. Hardware Interface:
In this section the project that we made how much memory should be consume and how
many memory we should required for our project. In this section we define how many
memory used be consume by the users to store our important data in the computer. In this
section we should store the following information like:
 Item code
 Item list
 Item details
 Quantity
 Billing system
 Online ordering
3.1.4. Software Interface:
In this section we should define which software we must be used to making our project
and which languages we should be used to making our important data. We should used
http language and PHP language and we make database by using this software. In this
section we must record the following things like:
 Displaying total bills

 Displaying item detail
3.1.5. Communication Interface:

When a specific reservation reserved at same time email information will be sent to the
both staff members email account and guest account. Guest will be notified in check out
date. To achieve the information we must check the proper connection of the internet.
Mostly the client side connection will provide the efficient services.
3.2: Functional Requirement:
Function 1 Make reservation
Input Code, no of guest, no of people in

restaurant
Output Data base record
Processing Record the information to the database
Function 2 Add staff members
Input Code , employee name, employee salary,

employee id, age, email address
Processing Record the information to the data base
Function 3 Search rooms
Input Period, check in, check out, guest
Output Display a message with available room details
Processing Check the room detail at the given time period

Function 4 Add payments
Input Total bill, pay time, credits card details
Processing Store the result in data base system
Function 5 Issue bills
Input Billing no, quantity price, taxes, details,

services
Output Printed version of the bill
Processing Validate the record according to the billing

price.
Function 6 Set rates
Input Check in, check out day, no of guest, no of

order
Processing Validate our data base record according to

data base
Function 7 Take backup
Input Location to save the backup file

Output Showing a result of successfully created
our backup
Processing Save the backup file to the specific location
3.3. Use Case:
Actor
Represent role, external to system interact with the system.
Use Cases
Represent interaction between system and actor.
Scenario
The session of actual input and expected output.
Use Case Diagram
Represent use the services and functionality by the system by the users.
There are three actors that are used in my diagram:
 Administrator
 Registered User
 Visitor

Actors Description
 Administrator:
This is the operation manager of the Company that can create reports add/modify
user, Product record designation (designation type), expense (expense type) after
login.
 Registered User:
This is the type of user which can view and also order the product after login process

 Visitor : This is the type of user which can view the product but no purchase
the product
Actors Use Case:

2 Administrator User Case:

1.2.1.3 Registered User Use Case:
1.2.1.4 Visitor Use Case:
USAGE SCENARIOS

NAME USE CASE ADUSER
PRIORITY: A0-01
ACTOR: Administrator, registered user, visitor
SUMMARY: Save information of new user in the database
PRE-CONDITION: Database file should be attached properly
to system and User form is open.
POST-CONDITION Add NEW RECORD
USES OR INCLUDE: LOGIN
EXTENDS: -------
NORMAL COURSE OF  Start

ACTION:  Enter data into form
 All fields should be filling properly
 Record transaction if error notes that
message and work according to message.
ALTERNATIVE PATH: Exit
EXCEPTION: All fields should be fill properly according to

requirement.
ASSUMPTION  Record new transaction

Update User
NAME USE CASE: UPUSER
PRIORITY: A0-02
ACTOR: Administrator, Registered user, Visitor
SUMMARY Update information of existing user in the

database
PRE-CONDITION: Database file should be attached properly to

system and Employee form is open.
USES OR INCLUDE: LOGIN,UPUSER(search user)
EXTENDS: -------
NORMAL COURSE OF  Search the record

ACTION:  Update the previous records in the fields.
All fields should be filling properly
 Save the Update.
ALTERNATIVE PATH: Exit Action
EXCEPTION: Record is not in the table
 Filled data in text boxes should be right

according to the constraint
ASSUMPTION Record is updated according to the constraint.

Add Category

NAME USE CASE: ADCAT
PRIORITY: B0-01
SUMMARY: Save information of new category in the

database
system and category form is open.

 Record transaction if error notes that
message and work according to message.

requirement.
 Exit Action perform

Update Category
NAME USE CASE: UPCAT
PRIORITY: B0-02
SUMMARY: Update information of existing Category in the

NAME USE CASE: DECAT
database
PRIORITY:
PRE-CONDITION: B0-04 file should be attached properly to
Database
system and Employee form is open.
ACTOR: Administrator, Registered User, Visitor
SUMMARY: Information searched and Click on Delete then record
USES OR INCLUDE: delete from table and
LOGIN,UPCAT(search system So that it is not longer
category)
the part of database of system.
EXTENDS: -------
PRE-CONDITION:  Information in table
NORMAL COURSE OF  Search the record
 And table is attached to system
ACTION:  Update the previous records in the fields. All
 Search the record if exit.
fields should be filling properly
POST-CONDITION Message box if yes then, Record Transaction no
longer the part of System.
USES OR INCLUDE: LOGIN, DECAT(search CAT)
EXCEPTION:  Record is not in the table
EXTENDS:  YES,NO
Filled data in text boxes should be right
NORMAL COURSE OF ACTION:  Start
ASSUMPTION Record is updated according to the constraint.
 Search record
 Press delete button
 Then Click on yes

 Record is deleted
 Alternate path No, exit
ALTERNATIVE PATH:  No action
 Exit Action
EXCEPTION: Record is not found.
ASSUMPTION  After deleting the record

 Record should no longer part of system.
Add Product
NAME USE CASE: ADPRO
PRIORITY: C0-01
SUMMARY: Save information of new Product in the database

system and Product form is open.
EXTENDS: -------

 Enter data into form
 Record transaction if error notes that message
and work according to message.

requirement.

Update Product
UUU
NAME USE CASE: UPPRO
PRIORITY: C0-02
SUMMARY: Update information of existing Product in the database
PRE-CONDITION: Database file should be attached properly to system

and Sale form is open.
USES OR INCLUDE: LOGIN,UPPRO(search product)
EXTENDS: -------

NORMAL COURSE OF ACTION:  Search the record
 Update the previous records in the fields. All fields
should be filling properly

 Filled data in text boxes should be right according
to the constraint
ASSUMPTION Record is updated according to the constraint
Delete Product
NAME USE CASE: DEPRO
PRIORITY: C0-03
SUMMARY: Information searched and Click on Delete then record

delete from table and system So that it is not longer
the part of database of system.

POST-CONDITION Message box if yes then, Record Transaction no longer
the part of System.
USES OR INCLUDE: LOGIN, DEPRO(search PRO)

EXTENDS: YES,NO

 Search record
 Exit Action

Add News
NAME USE CASE: ADNEWS
PRIORITY: B0-01
SUMMARY: Save information of new News in the database

and News form is open.
EXTENDS: -------

 Enter data into form
 Record transaction if error notes that message and
work according to message.

requirement.

Update News
NAME USE CASE: UPNEWS
PRIORITY: B0-02
SUMMARY: Update information of existing Product in the

database

and Sale form is open.
USES OR INCLUDE: LOGIN,UPNEWS(search news)
EXTENDS: -------

 You should be on Sale form and data base must
be attached to the system.

 Message on top left corner of form if record not
found

Delete News
NAME USE CASE: DENEWS
PRIORITY: B0-03
SUMMARY: Information searched and Click on Delete then

record delete from table and system So that it is not
longer the part of database of system.

USES OR INCLUDE: LOGIN, DENEWS(search NEWS)
EXTENDS: YES,NO

ACTION:  Search record
 Exit Action

Add Subscribe
NAME USE CASE: ADSUBS
PRIORITY: C0-01
SUMMARY: Save information of new subscribe in the database

and Subscribe form is open.
EXTENDS: -------


 Record transaction if error notes that message
and work according to message.

requirement.

Update Subscribe
NAME USE CASE: UPSUBS
PRIORITY: C0-02
SUMMARY: Update information of existing Product in the

database

system and Sale form is open.
USES OR INCLUDE: LOGIN,UPSUBS(search subscribe)
EXTENDS: -------

ACTION:  You should be on Sale form and data base must
be attached to the system.

 Message on top left corner of form if record not
found

Delete Subscribe
NAME USE CASE: DESUBS
PRIORITY: C0-03
SUMMARY: Information searched and Click on Delete then

record delete from table and system So that it is
not longer the part of database of system.

USES OR INCLUDE: LOGIN, DESUBS(search SUBS)
EXTENDS: YES,NO

ACTION:  Search record
 Exit Action


3.4. Classes and Object:
I. Class name: food

Attribute: add item, delete item, taste
Function: preparing food item
II. Class name : customer

Attribute: cut id, name, age, email, address,
Function: order food to waiter
III. Class name : account

Attribute: id, email, and person
Function: add payment to account
IV. Class name : employee

Attribute: employee name, id, address, email, age
Function: checks the bills

V. Class name : waiter
Attribute: name, id, address, email
Function: serving order to customer
VI. Class name : manager

Attribute: name.id, email, add payment
Function: checks all the email and account
3.5. Non Functional Requirements:
Because of designing the online ordering system are much standard for the web based
application. The non functional requirement of the system is straight forward. The server
hardware can be capable of both running the web and data base on to the system. For a
restaurant not much of the data can be used so we required only personal computer can b
require to run our data base. As our requirement are must suitable for personal computer
so no more long transactions can be used by the server we can easily manage through this
server.
3.4.1: performance:
In these section we made the project must be work properly in the computer. And their
performances must be suitable for the computer that we must be used. The database we
must be made should be work properly we should make sure that this data base can be run
on each and every computer of different types.
That must be run on the computer of other restaurant. We should be able to write each and
everything in the data base that we should be clearly understand by the server computer
that can check our whole data base.

3.4.2: Reliability:
The system that we should be made must be reliable that when we used we can face no
many problems. We should make sure that the system we should be made must be accurate
and must work properly in the system. We should make our system in such a way that the
server side can easily understand our requirement that we should be provided to them and
can easily be understandable.
3.4.3: Availability:
In this we should define that the system we should be made must be available to every site
that everyone can easily give their order to the employee. Because we should also provide
the facility of online ordering system. And the customer can easily give their order to
employee and they face no problem to give their order. So we should be making sure that
the system we should be design must be available easily to the customer.
3.4.4: Security:
We should make sure that the data base we must be design can be secure for the
unauthorized users. Our data can be access only by the employee that work here and by the
manger. We should must be sure that the data base that can be design must be secure and
cannot be access by the other users that not need the data. We should make our data secure
and easy to access by the manger of the restaurant.
3.4.5: Maintainability:
The system we should be design must be maintain able when any problem can be occurred
in our system. We should design in such a way that we can easily design and easily accurate
our system when they create any problem in the system. We should make our system less
complex that everyone can easily understand the problem of the system and can be easily
accurate the system. We should design our system in much easier way that can be easily
understand by the server and by the manager.

3.6: Logical Database Requirements:
Logical database design is the process of transferring the conceptual data model (such as
ER diagram) into a logical data model (such as relation). The conceptual data model a
statement of the data requirements for an organization that is independent of the target
database management system. In this system the logical database design should be used
that our computer can easily be understand and easily be managed by the users.
Logical Data Models:

These are for major logical data model that are use today.
 Hierarchical Model
 Network Model
 Relational Model
 Object Oriented Model
Selecting an appropriate data model is an important decision in data modeling process.
From above mentioned Logical Data Models the data model I have chosen for this
application is the Relational Data Model. The selection is done on the behalf of three major
reasons.
 First, the relational database model is most commonly used data model in
contemporary database application.
 Second, both hierarchal Models and network Models are old model and are mostly
used for legacy systems i.e. main frames.

 The relational data model is most appropriate for tabular data with relatively
 simple relationships (such as accounting data), on the other hand the object oriented
model is more appropriate for complex data (such as images and maps).

ER diagram:

3.7: Design Constrain:
In this section we should design the database that we should make in our project. The
design must show how the requirement of the users should be full filled by the customer
and how should handle with these requirement of the customer.
We should build it in an easy way that it can be easily understand by the user r the manger
that can handle the whole requirement and whole system.
Add payment
Cust_id
Paid
Employee
Waiter
Emp_id
Waiter-id
Emp_name
Waiter-name
Emp_age
Manager
Mang_Id
Mang _Name
Mang _address
Age
Customer Bills
Cust_id Payment
Cust-name Credit card
Cust-email Cashier

4. Analysis model:
4.1: Sequence diagram:
The sequence diagram consist of object represented in the usual way (as named rectangles
with the name underline).message represented an solid line arrow. The objects are laid out
near the top of the diagram from left to right. They are arranged in any order that simplifies
the diagram. A message goes from one object to another by arrows.
Add Comments
:User :Interface :System :Database
1. Add (Click)
2. Add clic k event call
3. All fiel ds are empty
4. Enter Rec ord 5. Verification of Data

6. Incorrect format
7. Re Enter Record
8. Verified Input
9. Store
Record
10. R esponse s end
12. Msg Record inserted 11. Yes/NO
13. Error mess age

Edit Comments

Delete Comment
1. Add (Click)
3. All fiel ds are empt y

6. I ncorrect format
7. Re Ent er Record
8. Verified I nput
9. Store
Record
10. R esponse s end
12. Msg Record insert ed 11. Yes/NO
13. Error mess age

Edit Subscribe
Delete Subscribe

1. Delete (Click)
2. I nput Rec ord
3. Verification of Data
4. I nput data in c orrect for mat
5. Enter Again
6. Verified I nput
7. Search
8. Res pons e send Record
9. Rec ord Shown 10. Yes/NO

11. MSG (No Rec ord Found)
12. D elete Record
13. R ecord Set to D eletion
14. C ommand
15. R ecord
16. R esponse s end Deleted
18. MSG (Delet ed)
17. Yes/NO
19. MSG (error)
Add Feedback
1. Add (Click)
3. All fiel ds are empt y

6. I ncorrect format
7. Re Ent er Record
8. Verified I nput
9. Store
Record
10. R esponse s end
12. Msg Record insert ed 11. Yes/NO
13. Error mess age
Edit Feedback
4.2: Data flow diagram:

The section shows the context Data Flow Diagram that is drawn for a Food Ordering
System. It contains a process (shape) that represents the system to model, in this case, the
"Food Ordering System". It also shows the participants who will interact with the system,
called the external entities. In this example, Supplier, Kitchen, Manager and Customer are
the entities who will interact with the system. In between the process and the external
entities, there are data flow (connectors) that indicate the existence of information
exchange between the entities and the system.
Level 1:

4.3: State Transaction diagram:

5: Supporting information:
 Appendix A:
Abbreviations: It is the full form of the word.
Acronyms: It describes a word that is written with their initial letters.
Assumptions: something that you accept as true without question or proof.
Availability: Characteristic of an asset that is committable, operable, or usable upon

interest to perform it's assigned or required
Communications Interfaces: an electronic circuit usually designed to a specific standard

that enables one machine to telecommunicate with another machine.
Class: A set, collection, group, or configuration containing members regarded as having

certain attributes in common; a kind or category.
D
Definition: an explanation of the meaning of a word, phrase, etc. an announcement that

characterizes a word, expression, and so on. a statement that describes what something is.
 a clear or perfect example of a person or thing.
Dependencies: Relationship between conditions, events, or tasks such that one cannot
begin or be-completed until one or more other conditions.
Design Constraints: The idea of requirements in outline can be characterized as the act of
constraining client activities on a framework.
Data Flow Diagrams (DFD): An information stream outline (DFD) is a graphical

representation of the "stream" of information through a data framework, displaying its
procedure perspectives.
External Interface Requirements To distinguish and archive the interfaces to different

frameworks and outer substances inside of the task scope. These sorts of interfaces are
classed as subsystem interfaces
Functional Requirements: Functional requirement define specific functionality

that define what a system is supposed to accomplish.
General Constraints: That cannot be expressed by the predefined constructs.
Hardware Interfaces: Architecture used to interconnect two devices together. It includes

the design of the plug and socket.

Interfaces: A system that is used for operating a computer.
Inverse Requirements: Requirements state what the system will not do.
Logical database requirements: A logical database must be able to access and identify all
files within the storage system to operate correctly.
Maintainability: The probability that a system or system element can be repaired in

a defined environment within a specified period of time.
Non-Functional Requirements: Requirement that specifies criteria that can be used to

judge the operation of a system, rather than specific behaviors.
Overview: The executive summary, the low-level documents the technical specifications.
Purpose: The reason for which something exists or is done, made, used, etc
Product Perspective: Product perspective has something to do with looking. Way we see
something.
Product Functions: the technical relationship between product output and the input of
factors of production
Performance: How well a person, machine, etc. does a piece of work or an activity.
Portability: the ability to be easily carried
References: The act of referring to something. Significance for a specified matter, relation
or relationship.
Reliability: The ability of an apparatus, machine, or system to consistently perform its
intended or required function or mission.
Scope: The opportunity or possibility to function or be active.
System Interfaces: An interface is a mutual limit crosswise over which two separate
segments of a PC framework trade data. The trade can be between programming, PC
equipment, fringe gadgets, people and blends of these.
Software Interfaces: An operating system may interface with pieces of hardware.

Applications or programs running on the operating system.
Security: The condition of being shielded or safe from mischief.

Gauges Compliance: the consistence of a site or web program with the web principles of
the World Wide Web Consortium (W3C). To guarantee interoperability a gauges
consistent site does not utilize restrictive programming strategies or components of a
program.
Sequence Diagrams: Sequence diagram models the colllaboration of objects based on time
sequence. It shows how the object interect with others in a particular scenario of a use case.
state-Transition Diagrams (STD): A state diagram is a type of diagram used in computer

science and related fields to describe the behavior of systems. State diagrams require that
the system described is composed of a finite number of states.
User Characteristics: Helps guide your team’s decision about the functionality, design and
content to include on your site. They will use the system as a means of laying out the
design of an as yet unimplemented system.
Use Cases: An utilization case is a strategy utilized as a part of framework examination to

recognize, clear up, and compose framework prerequisites. The utilization case is
comprised of an arrangement of conceivable groupings of connections in the middle of
frameworks and clients in a specific domain and identified with a specific objective.

 Appendix B:
Data dictionary:
 SDLC:
System development life cycle
 OFFRMS:
Online Fast Food Restaurant Management System.
 CUSTOMER
Who will use the services.
 SQL:
Structured query language
 HTML:
Hypertext markup language
 Appendix c:
Abstract
The purpose of study is to determine the feasibility of opening an fast food restaurant
in our city. It is a type of food that can be quickly served and quickly prepared. First of
all as we know fast food is the part of our life and every one like this. In my fast food
restaurant I provide each and every thing which people want to eat and I will also make
sure that the things I provide must be neat and clean that no one can create issue on my
restaurant. I want to know what it makes epidemic so popular in our society. The
section that I will include in my blog is the popularity of fast food, the most important
thing of fast food and their negative effects that can over came the consumer can
contact with us. We should provide different variety of fast food in our restaurant. The
things that I should provide in my restaurant are burger, pizza, hot-dogs, cold drinks
and salad and all these things should easily be provided. And I also provided Chinese

fast food which includes assortment of noodles, rice, crispy fried nuggets. Many fast
food restaurants provide the same thing as usual but in my restaurant I provide a variety
of things.
1. Introduction
Fast food is food that can be prepared very easily and quickly and in a short time. It is
also less expensive that everyone can get it easily. The concept of fast food can be given
in 1920. Ancient Rome cities had streets stand that sold bread and wine. Many fast food
restaurants come in competition with each of us like pizza hut, hot chicks, subway. I
introduce many fast foods in my restaurant that everyone can like. I will provide the
environment of user friendly that no one can complain against our staff. I will also
provide the facility of credit card. Others fast food restaurants not provide this facility.
I wanted to know why eat fast food if nutritional choices have an effect on people
mental and physically health. This is important to me because I have learn through
experience how food choices can affect the life. Fast food restaurants like hot chicks
and subway provide expensive things but I should provide in much more reasonable
price that everyone can get it easily. Usually young generation of our society like fast
food like pizza burger and nuggets. The lists of item that I should provide in my
restaurant.
 Burger
 Pizza
 Sandwich
 Fries
 Fried rice
 Nuggets
 Different kinds of salad
 Chicken pieces
The online ordering facilities are one of the latest services most fast food restaurant
provides. And I will also provide these facilities of online ordering to delivered order

to the customer. This is made so easy to pay online. Customer will provide their
payment by their credits card. So the system that I will design will enable the customer
go online and place their order for their food.
2. Literature Review
An ordering system refers to s set of detail method that is being used in handling the
ordering system. Food ordering can be computerized and can be done regularly. Those
help the customer to order their food themselves which is known as customer self
ordering system. The customer self ordering system can be explain and can be
computerized that is being used by the customer to place their orders. As we know that
fast food provides a huge variety of things.
As I will b discussed I should provide the facility of online ordering to the customer
that the customer can easily place their order. And I should also provide the facility of
credit card that customer can pay their bills. And I will also try to provide friendly
environment to the customers.
3. Problem Statement
The trend of fast food started in Western countries but in Pakistan people addicted also.
Now we see that fast food restaurant are found in every area of every city. People
especially young generation wanted fast food daily instead of having cooked meal at
home. Due to their increasing demand of fast food habits, many health issues have been
reported. According to medical research eating to much fast food can create depression.
In short we avoid all these problems we should eat healthy food and if we eat fast food
make sure it must b neat and clean. One of the main problems is that customer make a
long queue which can create the difficulty to place their order. And all the customer
cannot easily place their order which can create problem.
3.1 proposal Questions
o The system has to be easy for non-technical people to use.

o Are the Requirements fully understood?

o Have users been involved fully in the definition of requirements?
o Is project scope stable?
o How do we handle the database crashing?
o Is system fulfilling all the requirements of users?
o Is system having some security clashes?
o Is system cost equals to the project budget?
o What platform does the systems supports?
3.2 Proposal Objectives
The proposed system is developed to manage ordering activities in fast food

restaurants. It helps to record customer submitted orders. The following function
should support the following order.
 What criteria are important to consumers with respect to patronizing a fast food
establishment.
 In which area fast food restaurant could be most successful.
 To review the current situation for fast food restaurant in our area.
 To allow the customer to make order view order and change order before submitting
their order and allow them to make payment through debit card
Or credit card.
 To provide interface that allow promotion and menus.
Tools that generate reports that can be used for decision making
4. Proposed Methodology
The nature of research determines the both primary and secondary research should
be conduct to collect information for feasibility study. The following steps in
proposed methodology are:
 Data base
 Spiral model

 PHP
 SQL
 HTML
5. References
http://www.theguardian.com/commentisfree/2013/apr/10/america-fast-food-
industry-quick-buck
http ://www.restaurant.org
http://www.studymode.com

SRS Fast Food

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SRS Fast Food

Caricato da

Copyright:

Formati disponibili

Online Fast Food Management System

SOFTWARE REQUIRNMENTS SPECIFICATION DOCUMENT

i Software Requirements Specification

Date Description Author Comments

Version 1 First Revision

Signature Printed Name Title Date

ii Software Requirements Specification

1.3 Definitions, Acronyms, and Abbreviations. 2

2. The Overall Description 5

2.1 Product Perspective 5

2.4 General Constraints 7

2.5 Assumptions and Dependencies 8

3.1 External Interface Requirements 9

3.2 Functional Requirements 12

iii Software Requirements Specification

3.3 Use Cases 15

3.4 Classes / Objects 39

3.5 Non-Functional Requirements 41

3.6 Logical Database Requirements 43

3.7 Design Constraints 45

4.1 Sequence Diagrams 47

4.2 Data Flow Diagrams (DFD) 48

4.3 State-Transition Diagrams (STD) 49

Appendix A – Background Research on: 57

iv Software Requirements Specification

1 Software Requirements Specification

 About the fast food organization.

 The fast food and the administrations offered there.

 Type of nourishment gave.

 The undertaking will contain the record of menu.

 Menu cost will be kept up.

 Will contain the record of workers.

 A site will be made.

1.3 Acronyms, and Abbreviations Definitions,

System development life cycle

Online Fast Food Restaurant Management System.

Who will use the services.

Hypertext markup language

3 Software Requirements Specification

2. The Overall Description

2.1 Product Perspective

2.2 Product Functions

• Allows for writing in client data

• When a client looks at the sum owed is shown

Following and Selling Food System

• Tracks all dinners bought

4 Software Requirements Specification

2.4 General Constraints

5 Software Requirements Specification

3.1. External Interface Requirement:

3.1.1. System Interface:

6 Software Requirements Specification

Tools & platform:

DBMS: MYSQL server

Phonetic Keyboard Layout

Reporting: Crystal Reports

Documentation: MS Word, MS Visio, UML Diagram

To implement the system they require four computers.

Server Cost Rs. 1500

Cost of 4 PC’s 2*15, 000=30, 000

LAN Cost 5, 000

7 Software Requirements Specification

3.1.3. Hardware Interface:

3.1.4. Software Interface: