Food Panda PDF

Preview

Summary

Functional and non functional system foodpandA...

Description

1. Introduction 1.1 Purpose The purpose of this SRS is to outline both the functional and nonfunctional requirements of the subject Online Food Ordering System. The document should act as a foundation for efficient and well-managed project completion and further serve as an accurate reference in the future. 1.2 Project Scope Restaurant in today’s age has focused on the speedy delivery and quick preparation of the orders rather than offering the rich dining experience. Until recently, all of these delivery orders were placed over the phone, but there are many disadvantages to this system including the convenience of the customer needing to have a physical copy of the menu, lack of visual confirmation that the order was placed correctly and the necessity for the restaurant to have an employee answering the phone and taking orders. This system simplifies the ordering process for the customer.

2. Overall Description 2.1 Product Perspective The Food Ordering system is a software package to facilitate ordering the food items online. The customer is able to view the menu, place orders, and retrieve the final bill. When the customer visits the ordering webpage, they are presented with an interactive and up-to-date menu, complete with all available options and dynamically adjusting prices based on the selected options. Then, payment can also be done online and by Cash On Delivery(COD) through this system. Database will be created to keep track of customers’ information and requests

2.2 System Features The System consists of the following modules.      

Login Registration Menu Payment Feedback About Us

User Classes and Characteristics User:  The user will find the nearest restaurant based on his location.  The user will then search for the food items from the provided menu and place the required order.  The user will also use the payment module for the paying for the food ordered. Admin:  The admin will add the different branches and offers onto the site.  The admin will maintain and keep updating the menu at regular intervals.  The admin will maintain the database of the customer details.  Payment is also recorded with the admin only Branch manager:  The branch manager will view the different orders and will give the approval of the same accordingly.

Modules and Functionalities Login Module Description: The user can login to the system to place orders for the product.

Functional Requirements Purpose Input Processing Output

To check login process Username and password will be entered. Process will be carried to check whether that user is already registered before. If already present then login.

Registration Module Description: The customer who wants to place orders for the food can register into the system and get it done.

Functional Requirements Purpose Input Processing Output

To keep records of all the registration user in the database. To fill registration details The Details will be filled and after that click on the submit button The customer details will be stored in the

database.

Menu Module Description: To let customers browse through the food items.

Functional Requirements Purpose Input Processing Output

To let user choose from the products Required order will be chosen The process will be carried out. If available then it will be provided to the user.

Payment Module Description: This feature is to let the user pay for the placed order which contains options for online payment as well as Cash on Delivery.

Functional Requirements Purpose Input Processing Output

To let user pay for the placed order Paid order will be confirmed The process will be carried out. The order will be provided to the user.

Feedback Module Description: The user is able to provide their valuable feedback to the organization which runs the system.

Functional Requirements Purpose Input Processing Output

Lets the user to provide their feedback. The required information will be given The required process will be carried out. The system will acknowledge the feedback.

About-Us Module Description: The user gets the information about the organization and the system. Functional Requirements Purpose

Lets the user access the information about the system.

Input Processing Output

The required information will be given The required process will be carried out. If available then it will be provided to the user.

Other Non-functional Requirements Performance Requirements  The performance is measured on the terms of the output provided by the application. Requirement specification plays an important part in the analysis of the system.  It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirement of the user, is of no use.

Safety Requirements  The data handled in the system is very safe. The database system should always be confirmed to run properly and so the process can be performed well and the data should be saved to the database at consecutive intervals.  For safety of the product Firewall is activated and antivirus should be installed. 4.2.3 Security Requirements  The system should be highly secured system as it deals with user details in the database.  Only authorized user can access the respective operations and only authorized user will be permitted to access the admin and the database.

4.2.4 Software Quality Attributes Functionality: The ability of the system to do the work for which it was intended. Usability:

The application is easy to use and the end user can easily

grab the idea of the using the application Scalability: the user.

Availability if the system is not limited and is available to

Testability: The developing software should be tested with the available experimental data. Further various types of the testing can be done to improve the system efficiency.

Non-functional Requirements 1. Consistency The Online Food Ordering System provides consistent user interface design to the end-user. The designs of the screen are standardized and consistent that make the end-user feel comfortable to use it. 2. Convenience The system may give convenience to the end-user to make order via online platform. Customers need not go out or make a phone call to order from the restaurant. 3. Availability The system provides the end-user to login the application to browse or make order on 24 hours. 4. Usability

The Online Food Ordering System is ready to use, the end-user may feel easy to use the system.

5. Security The restaurant system provide the password security access control to avoid unauthorized user to login to the application. The system also authenticates the staff level to access to some of admin part....