Food Ordering system-SRS

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 14

SYSTEM REQUIRMENT SPECIFICATIONS FOR

Taste Buds – The Food Ordering Solution

PURPOSE OF THE SYSTEM

The main objective of this project is to develop a system for a


Five Star Hotel in which its customers can order online for recipes
from anywhere. The system will help the users in displaying the
list of recipes items available in that restaurant along with the
offers available for those recipes items. The system will also
display the images of the recipes items along with the list of items.
The accessibility to the system in the restaurant will be given to the
Administrator with the user name and password.

Features

 Provides option to the customers to order food online via


intranet
 Users can select items from a wide range of menu
 Items will be added to the cart, which can be reviewed and
finalized at the time of submitting order
 Ordered items can also be deleted
 Option given to customer to pay the bill separately for the
items which he/she orders, with this option this application
can be easily integrated with any existing hotel
administration software.

PROBLEMS IN THE EXISTING SYSTEM

• For ordering food, either user has to go to the restaurant


manually or by making a telephone call
• Hence the existing process is a time consuming process.
• In case if additional ordering has to be done, it’s an
additional overhead again.

SOLUTION OF THESE PROBLEMS

• In order to issues in existing system, the current application is


being developed, which will enhance the activities and
performances of the hotel food ordering thus reduces the time
taken to order the food.
• Besides that, information can be store and retrieve easily
from computer database if everything is computerizing by
this proposed system.

STUDY OF THE SYSTEM

In the flexibility of the uses the interface has been developed a


graphics concept in mind, associated through a browses interface.
The GUI’S at the top level have been categorized as

1. Administrative user interface


2. The operational or generic user interface

The administrative user interface concentrates on the consistent


information that is practically, part of the organizational activities
and which needs proper authentication for the data collection. The
interfaces help the administrations with all the transactional states
like Data insertion, Data deletion and Date updating along with the
extensive data search capabilities.

The operational or generic user interface helps the users upon the
system in transactions through the existing data and required
services. The operational user interface also helps the ordinary
users in managing their own information helps the ordinary users
in managing their own information in a customized manner as per
the assisted flexibilities.

NUMBER OF MODULES

• It Consists of 4 Modules
• Customers
• Recipes
• Order
• Shopping Cart

Customers:
• This module performs registration and maintenance of
customer information.
• This information can be very much useful for delivering the
ordered ones avoiding any confusion related to delivery
address
Recipes:
• It contains
• Recipes
• Details about all recipes which are existing in the Taste-
Buds
• Adding the new recipes and deleting the Recipes.

Order:
• It contains
• Orders List
• Payments information
Paying type
Card
Cash
• Using this, adding new order and deleting a order

Shopping Cart:
• It contains
• Recipes types
• list of items and cost
• Adding new items under recipes

SDLC METHODOLOGY USED


Object Oriented Analysis and Design (OOAD) is the
model, chosen to design and develop the proposed system.

Features of OOAD:
 It users Objects as building blocks of the application rather
functions
 All objects can be represented graphically including the
relation between them.
 All Key Participants in the system will be represented as
actors and the actions done by them will be represented as
use cases.
 A typical use case is nothing bug a systematic flow of
series of events which can be well described using
sequence diagrams and each event can be described
diagrammatically by Activity as well as state chart
diagrams.
 So the entire system can be well described using OOAD
model, hence this model is chosen as SDLC model.

INPUT DESIGN

Input design is a part of overall system design. The main objective


during the input design is as given below:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the
user.
INPUT STAGES:
The main input stages before the information gets stored in
the database media:
 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

OUTPUT DESIGN

Outputs from computer systems are required primarily to


communicate the results of processing to users. They are also used
to provide a permanent copy of the results for later consultation.
The various types of outputs in general are:
 External Outputs, whose destination is outside the
organization.
 Internal Outputs whose destination is with in organization
and they are the
 User’s main interface with the computer.
 Operational outputs whose use is purely with in the computer
department.
 Interface outputs, which involve the user in communicating
directly with

The outputs were needed to be generated as a hard copy and


as well as queries to be viewed on the screen. Keeping in view
these outputs, the format for the output is taken from the outputs,
which are currently being obtained after manual processing. The
standard printer is to be used as output media for hard copies.

ARCHITECTURAL FLOW

The current application is being developed by taking the 3-tier


architecture as a prototype. The 3-tier architecture is the most
common approach used for web applications today. In the typical
example of this model, the web browser acts as the client, IIS
handles the business logic, and a separate tier MS-SQL Server
handles database functions.

Although the 3-tier approach increases scalability and


introduces a separation of business logic from the display and
database layers, it does not truly separate the application into
specialized, functional layers. For prototype or simple web
applications, the 3-tier architecture may be sufficient. However,
with complex demands placed on web applications, a 3-tiered
approach falls short in several key areas, including flexibility and
scalability. These shortcomings occur mainly because the business
logic tier is still too broad- it has too many functions grouped into
one tier that could be separated out into a finer grained model.

The proposed system can be designed perfectly with the three


tier model, as all layers are perfectly getting set as part of the
project. In the future, while expanding the system, in order to
implement integration touch points and to provide enhanced user
interfaces, the n-tier architecture can be used. The following
diagram will represent the typical n-tier architecture.
CONTEXT LEVEL DFD
FEASIBILITY STUDY:

Preliminary investigation examine project feasibility, the


likelihood the system will be useful to the organization. The main
objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules
and debugging old running system. All system is feasible if they
are unlimited resources and infinite time. There are aspects in the
feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Operation Feasibility
 Economical Feasibility

Technical Feasibility
The technical issue usually raised during the feasibility stage of the
investigation includes the following:
 Does the necessary technology exist to do what is suggested?
 Do the proposed equipments have the technical capacity to
hold the data required to use the new system?
 Will the proposed system provide adequate response to
inquiries, regardless of the number or location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of
access and data security?
Earlier no system existed to cater to the needs of ‘Secure
Infrastructure Implementation System’. The current system
developed is technically feasible. It is a web based user interface
for audit workflow at NIC-CSD. Thus it provides an easy access to
the users. The database’s purpose is to create, establish and
maintain a workflow among various entities in order to facilitate
all concerned users in their various capacities or roles. Permission
to the users would be granted based on the roles specified.
Therefore, it provides the technical guarantee of accuracy,
reliability and security. The software and hard requirements for the
development of this project are not many and are already available
in-house at NIC or are available as free as open source. The work
for the project is done with the current equipment and existing
software technology. Necessary bandwidth exists for providing a
fast feedback to the users irrespective of the number of users using
the system.
Operational Feasibility
Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s operating
requirements. Operational feasibility aspects of the project are to
be taken as an important part of the project implementation. Some
of the important issues raised are to test the operational feasibility
of a project includes the following: -
 Is there sufficient support for the management from the users?
 Will the system be used and work properly if it is being
developed and implemented?
 Will there be any resistance from the user that will undermine
the possible application benefits?
This system is targeted to be in accordance with the above-
mentioned issues. Beforehand, the management issues and user
requirements have been taken into consideration. So there is no
question of resistance from the users that can undermine the
possible application benefits.
The well-planned design would ensure the optimal utilization of
the computer resources and would help in the improvement of
performance status.

Economic Feasibility
A system can be developed technically and that will be used if
installed must still be a good investment for the organization. In
the economical feasibility, the development cost in creating the
system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any
addition hardware or software. Since the interface for this system
is developed using the existing resources and technologies
available at NIC, There is nominal expenditure and economical
feasibility for certain.

You might also like