Fast Food Restaurant

sunglowmaizeΚινητά – Ασύρματες Τεχνολογίες

10 Δεκ 2013 (πριν από 3 χρόνια και 10 μήνες)

72 εμφανίσεις


Fast Food Restaurant
Ordering System

System
Requirements Specification

Version: S
RS

1.0



Prepared by

Team #15

Berker SAZAN


Doğan KÜÇÜK


Hakan TAŞAN


Hasan Mert TURGUT


Department Of Software Engineering


Supervisor:


Deepti Mishra

November 2
th
, 2012
Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

2
/
19


Team
#15

System Requirements Specification

Version:
1.0



Preface


In this Software Requirements Specification (SRS) document, all requirements,
roles of people in the scope of the Fast Food Restaurant Ordering System are specified
with constraints and related tools.


The document will be advantageous during p
roject development. The rest of the
project will be completed based on SRS document.


We have generated the SRS document using IEEE
8
3
0
Standards.















Version History

Version

Status*

Date

Responsible

Version Definition

1

Released

02.1
1
.20
12

Dee
pti Mishra

Baseline version of SRS



*: Draft, In Review, Released, Approved, Rejected, In Change

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

3
/
19


Team
#15

System Requirements Specification

Version:
1.0



List of Figures

Figure 1.

Product Functions

................................
................................
................................
..........

11



























Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

4
/
19


Team
#15

System Requirements Specification

Version:
1.0



List of Tables

Table 1.
Definitions

................................
................................
................................
.............................

6

Table
2.
Acronyms

................................
................................
................................
.............................

7

Table
3
.
Fast Food Restaurant Ordering System Home Page data flow

................................
.........

14

Table
4
.
Giving order data flow

................................
................................
................................
........

15

Table
5
.
Payment data flow

................................
................................
................................
..............

16

Table
6
.
Performance flow

................................
................................
................................
...............

17








Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

5
/
19


Team
#15

System Requirements Specification

Version:
1.0



Table of Contents

Preface

................................
................................
................................
................................
...............

2

List of Figures

................................
................................
................................
................................
...

3

List of Tables

................................
................................
................................
................................
....

4

Table of Contents

................................
................................
................................
.............................

5

1.

Introduction

................................
................................
................................
............................

6

1.1.

Purpose

................................
................................
................................
................................

6

1.2.

Scope

................................
................................
................................
................................
...

6

1.3.

Definitions, Acronyms & Abbreviations

................................
................................
................

6

1.4.

References

................................
................................
................................
...........................

8

1.5.

Overview

................................
................................
................................
..............................

8

2.

Overall Description

................................
................................
................................
................

9

2.1.

Product P
erspective

................................
................................
................................
.............

9

2.1.1.

System Interfaces

................................
................................
................................
.........

9

2.1.2.

User Interfaces

................................
................................
................................
.............

9

2.1.3.

Hardware Interfaces

................................
................................
................................
...

10

2.1.4.

Software Interfaces

................................
................................
................................
.....

10

2.1.5.

Communication Interfaces

................................
................................
..........................

10

2.1.6.

Memory

................................
................................
................................
.......................

10

2.2.

Product Functions

................................
................................
................................
..............

11

2.3.

User Characteristics

................................
................................
................................
...........

11

2.4.

Constraints

................................
................................
................................
.........................

12

2.5.

Assumptions and Dependencies

................................
................................
.......................

12

3.

Specific Requirements

................................
................................
................................
........

13

3.1.

External Interfaces

................................
................................
................................
.............

13

3.2.

Functional Requirements

................................
................................
................................
...

14

3.3.

Performance Requirements

................................
................................
...............................

16

3.4.

Logical Database Requirements

................................
................................
........................

17

3.5.

Design Constraints

................................
................................
................................
.............

17

3.6.

Software System Attributes
................................
................................
................................

18

4.

Appendices

................................
................................
................................
..........................

19



Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

6
/
19


Team
#15

System Requirements Specification

Version:
1.0



1.

Introduction

1.1.

Purpose

The aim of the SRS is to guide our project which is
Fast Food
Restaurant Ordering
System, during project development. In the SRS, we documented all requirements,
constraints, interfaces, essential software and hardwa
re tools and related interfaces. The
next steps of the project will be completed based on the SRS document.

1.2.

Scope

The name of the software to be produced is
Fast Food Restaurant Ordering System
mobile appli
cation using Android platform. This project

will

provide that ordering
me
chanism will be very efficient.


When any customer of a restaurant wants to order menu, customer will choose
menu touching screen of a tablet PC placed on the table in the restaurant. This order will be
sent the kitchen in the rest
aurant via internet, and then worker will approve t
hat order if it
is available.


The objective of
this project

is to improve ordering mechanism. Moreover, this
application intends to fa
cilitate ordering mechanism.

1.3.

Definitions, Acronyms & Abbreviations

Tab
le 1. Definitions

Word

Definition

Java

An open source programming language.

Android

A java based operating system for mobile phones.

Operating System

An

operating system

(
OS
) is a collection of software that
manages

computer hardware

resources and provides
Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

7
/
19


Team
#15

System Requirements Specification

Version:
1.0



common

services

for

computer programs
.

Eclipse

Eclipse is a platform that has been designed from the ground
up for building integrated web and application development
tooling.

Cost

The amount of money needed for a business or to do a
particular job.

Order

A request to make, supply or

deliver

food or goods.

Customer

A person who buys foods for our project.

Team

The people who work for the sign language tool project.


Table
2
. Acronyms

Acronym

Word

GUI

Graphical User Interface

TB

T
ablet PC

DB

Database

SRS

Software Requirements Specification

OS

Operating System

IEEE

Institute of Electrical and Electronics
Engineers

PC

Personal Computer

JDK

Java Development Kit


Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

8
/
19


Team
#15

System Requirements Specification

Version:
1.0



1.4.

References



IEEE Std 1058
-
1998, IEEE Standard for Software Project
Management Plans



Pressman, Roger S., Software Engineering, 4th edition, McGraw
-
Hill, 1997



Fairley, R. E., Workbreakdown Structure, Software Engineering Project Management,
IEEE CS Press, 1997

1.5.

Overview


This SRS document has been written to document essenti
al requirements for our
project called ROS. It has been prepared in three main headings which are introduction,
overall description and specific requirements respectively based on IEEE 830 Standards.


In introduction part, purpose, scope and definitions, a
cronyms, abbreviations,
references have been explained.


In overall description part, general factors that affect the product have been
explained in different point of view.


Finally, in the last part, all requirements which include functional requirements
,
performance
requirements

etc
.

have been specified in details.




Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

9
/
19


Team
#15

System Requirements Specification

Version:
1.0



2.

Overall Description

2.1.

Product Perspective

2.1.1.

System Interfaces


Our system is an android based application. There is need an internet and a well
-
defined database for availability of menus’ ing
redients such as foods, drinks, etc.

2.1.2.

User Interfaces



Administrators



Customer

Administrators:

There are three admins in our system. The first administrator responds
to
the whole system requirement
. They can easily detect the requirements, such as the varie
ty
of drinks, foods and etc. then makes changes on the system to need the requirements of the
system. The second administrator responds to interface of the system. It means that,
administrator can make adding, delete or updating ingredients of the menu. In

addition to
this, they can change the g
eneral view of the menu buttons
,

names, images, and the other
things which are

included to interface and also

requirements. The third and the

last
administrator
respond

to budget

of the whole system. They can analyze

the number of fast
-
food companies which are using our android based tablets and determine the income and
outcome of the whole system.

Customer:
In our system, without some important constraints of usage, every customer
can easily use this system. Users ca
n do;



See the general view of ordering system without waitress.

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

10
/
19


Team
#15

System Requirements Specification

Version:
1.0





See the general location of menus and ingredients, availability and the price of the
menus.



By using tablet, they can easily choose, add, edit or delete the order without
waitress.



By using ta
blet and credit card, they can easily pay the bill without waitress.

2.1.3.

Hardware Interfaces

System needs an android base tablet and also network system because of
availability of menus. In addition to this, user’s credit card is need to payment.

2.1.4.

Software Inte
rfaces

System needs a database server because of the all records (payment information,
menu names and price informati
on and availability information
)
.

2.1.5.

Communication Interfaces

The Internet connection is use to communication for custome
r and system. For
av
ailability
and updating process of menus, the
internet has

to connect

to the tablet
.

2.1.6.

Memory

For their own tablet;



4 cores 1.4 GHZ Cortex A9 CPU



1280 x 720 Resolution



4.8 inches OLED touch screen



32 GB Hard Disk

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

11
/
19


Team
#15

System Requirements Specification

Version:
1.0





2 GB Ram



2G,3G,4G LTE and Wi
-
Fi internet conn
ection

2.2.

Product Functions

Figure
1
. Product Fun
c
tions




2.3.

User Characteristics

There are 3 three groups of users.


Firstly, customers

who have not enough knowledge on using an Android
application or tablet PC. They are uninterested in technological device
s so they will need
help.


Secondly, customers who have skills about technological devices. They may be
expert or have enough knowledge. They will not need too much help.

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

12
/
19


Team
#15

System Requirements Specification

Version:
1.0




Lastly, Admin user who has enough knowledge about information
-
systems
technologies.

2.4.

Constraints

There are many critical constraints related to our project.



Users may not have enough knowledge about application



Tablet PC must be usable that it must have enough sensitive touch
-
screen



User can
not use tablet PC other than Menu selection

2.5.

Assu
mptions and Dependencies



Tablet PC has enough charge when the restaurant is open



There will not be any interruption in internet connection



Any ordering will not be at exactly the same time

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

13
/
19


Team
#15

System Requirements Specification

Version:
1.0



3.

Specific Requirements

3.1.

External Interfaces

For this part, mentionin
g about the detailed des
cription of all inputs into and
outputs from the software system.

Name of item:
Fast Food R
estaurant Ordering
System
android based tablet.

Home page
of

this system includes the ‘Welcome To ___ Restaurant’ at the top of the page. At
the
bottom of the page; about us, terms of use, F.A.Q and communication buttons will use.
Between the top and the bottom of the page, ‘Press to See the Menu’ button will use.

Description of purpose:

There are some ordering and waitress cost problems at fas
t food
restaurants.

Our system tries to decrease the cost of food companies and human work.
Thanks to this project, we will try find a solution to ordering without waitress and payment
mistakes at th
e
s
e

places.

Destination of input/output:
Customer can eas
ily give an order using this tablet and their
order reach to the user at a particular time.

Valid range, accuracy and/or tolerance:
Credit card information for payment,
availability of foods, drinks or menus, delaying the ordering time, system availability

and
response time, database availability and response time, battery level of the tablet and start
and finish time of ordering.

Units of measure:
N/A

Timing:
Ready for the user during the execution process.

Relationships to other inputs/outputs:
The inform
ation will be a basis for all the parts of
the developed system.

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

14
/
19


Team
#15

System Requirements Specification

Version:
1.0



Window formats/organization:
N/A

Data formats:
Data format, recording format and file format will attend.

Command formats:
The user will navigate by using own finger to the related buttons.

3.2.

Functional Requirements

Table

3.

Fast Food
Restaurant Ordering
System
Home Page data flow









Use Case Name

Fast Food
Restaurant Ordering
System

Priority

Essential

Trigger

Entrance

Precondition

System should available for user

Basic Path

Touch the
‘Pre
ss to See the Menu’
button

Alternate Path

N/A

Post Condition

N/A

Exception Path

If the tablet is not plug in.

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

15
/
19


Team
#15

System Requirements Specification

Version:
1.0



Table

4.

Giving order
data flow
















Use Case Name

Giving order

Priority

Essential

Trigger

Entrance

Precondition

User should touch t
he
‘Press to See
the Menu’ button.

Basic Path


1.User make decision for the order

2.User touch to related button to
choose the order from menu.

3.User approve the order.

Alternate Path

User cancel the order

Post Condition

User approve
s

the order.


Exce
ption Path

1. User give
s

order but finally do not
touch the ‘approve the menu’ button.

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

16
/
19


Team
#15

System Requirements Specification

Version:
1.0



Table

5.

Payment
data flow


3.3.

Performance Requirements




Use Case Name

Payment

Priority

Essential

Trigger

Entrance

Precondition

User should have a valid credit card






Basic
Path

1. User approve the total order and
price.

2. User read the conditions and
agreement part of the payment and
approved it.

3. User touch to enter some
information about the credit card

4. User synchronize the credit card to
the system.

5. User approv
e the all process.


Alternate Path

User pay the bill cash without using
system.

Post Condition

User approve the credit card
information.


Exception Path

1
-
Credit card is invalid or out of the
time of

expiration date

2
-
User cannot remember the credit
ca
rd information

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

17
/
19


Team
#15

System Requirements Specification

Version:
1.0



Table
6.

Performance flow

Main functions

Overall System Response Time

Sub functions

User Responses

1.Touching response time


2.Total Ordering response
time

3.Total Payment response
time



Administrator Response
s

1.Record,update,delete,add data
from database response time

2.Changing the button location
response time

3.Changing the letter and
general view of interface
response time


Time

1.N/A

2.N/A

3.N/A


1.N/A

2.N/A

3.N/A



3.4.

Logical Database Requirements

3.5.

Design

Constraints

We have specified design constraints below
;



ROS is a mobile application



ROS is only used in Android platform



The application is only developed by Java programming language



Connection is provided with internet

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

18
/
19


Team
#15

System Requirements Specification

Version:
1.0



3.6.

Software System Attributes

Reliabi
lity


ROS will be developed by using Java. If we use Exception Handling in our
program, the system will be reliable. Also testing techniques will be used to increase
system reliability.


Availability


Our system ROS will be available in working hours of an
y restaurant since it is a
restaurant ordering system. It will be available half of a day (12 hours).

Security


Administrator is authenticated to modify Restaurant Ordering System. He/She can
reach with his/her username and password. Customers can only cho
ose menu, cancel their
selection before its order is approved by admin user. Customers and workers in the
restaurant have no privilege to change the structure of the system.

Maintainability


When there is a need to make change in requirements or updates, o
ld state of the
system will be protected
.

Portability


We are going to develop our system in Android platform using Java. Therefore, it
will be used only in Android platform.

Fast Food Restaurant Ordering System


Atılım University

COMPE/SE/ISE 491
-
492

19
/
19


Team
#15

System Requirements Specification

Version:
1.0



4.

Appendices