SMART HOME MADE FOOD SHOP

SOFTWARE

Requirements Specification

Version 1.0

SUBMITTED BY: LAIBA SAFDAR

VU-ID: MC220201776

SUPERVISOR NAME: SYED HASSAN ALI SHAH

SEMESTER Spring: 2023

1
 REVISION HISTORY

Date (DD/MM/YYYY): 06-10-2023

Version: 1.0

Description:
SRS document includes Scope of the project, Functional requirements, Use Case
diagram, Usage Scenarios, Adopted Methodology, and Work Plan/Gantt Chart.

Author: MC220201776

2
 Table of Contents
Scope (of the project) ------------------------------------------------------------- 04

Functional Requirements --------------------------------------------------------- 05

Non-Functional requirements ---------------------------------------------------- 06

Use Case Diagram ----------------------------------------------------------------- 07

Usage Scenarios -------------------------------------------------------------------- 08

Adopted Methodology ------------------------------------------------------------- 12

Work Plan (Work Plan) ----------------------------------------------------------- 14

3
 SRS DOCUMENT

SCOPE OF PROJECT:

The proposed system is an automated tool for the development of a "Homemade food
ordering system" that helps customers easily order home-cooked food. It overcomes the
disadvantages of the traditional shift system. This system is a means to order food
through online home cooks and mess service. This system improves the way you receive
orders from customers. Home food ordering system will set up an online menu system
and customers can easily place their order their wishes. The proposed system can
recommend mess and food based on the rating of the given companies customers and
home cooks will be informed of improvements along with quality. The payment can be
made online and after payment, it will be saved in the payment history.
Today, many students, working professionals and many others have to stay away from
their homes, rooms or hostels for study, work or other reasons. Most of these people
always want and prefer to eat only home food instead of outside food for many reasons.
Some of the main reasons are unhealthy, unhygienic, expensive, the use of high
additional flavorings in food and poor quality food available in most food restaurants. On
the other hand, homemade food is very healthy, nutritious and hygienic. Home cooked
food is hand washed in a fresh and clean environment. Most of the restaurant owners are
business oriented and do not care about the cleanliness and health of the customers.
Therefore, many people are always looking for homemade food because it is healthier,
contains better quality and nutritional value than the food served in restaurants.

Functional Requirements:
1. Functionalities of Administrator
 Admin can Add, Edit, Delete and View Home Food shop profile.
 Admin can Approve / disapprove Home Food shop’s registration request.
 Admin can Add, Edit, Delete and View customers.
 Admin can Add, Edit, Delete and View Home Food item categories.
 Admin can Add, Edit, Delete and View Home Food items.
 Admin can Add, Edit, Cancel and View customer orders.

4
  Admin can Add, Edit, Delete and View Home Food shop location on map.
 Admin can Check order status.
 Admin can check the rating given by customers about each Home Food
shop.
 Admin can check average rating of each Home Food shop.
 Admin can check the remarks given by customers about each Home Food
shop.
 Admin can block a Home Food shop account in case of continuous poor
rating.
 Admin can view the customer complaints and take appropriate actions.
 Admin can generate a report on a monthly, weekly basis for the total
number of orders and their successful handling.

2. Functionalities of Unregistered Customer (Guest User)

 Any unregistered customer (guest user) can only Search and view the
registered Home Food shops in the system.
 Any unregistered customer (guest user) can only Search and view any items
according to specific filters (item name, category, price, location and rating
etc.) of any registered Home Food shop.

3. Functionalities of Registered Customer (Registered User)

 Customers can register and login to the system.
 Customers can Add, Edit, Delete and View their profile details.
 Search and view Home Food shops and its food items in a proper layout on
the website.
 Search and view any available items according to specific filters (item
name, category, price, location and rating etc.) of any registered Home Food
shop.
 Order any available Home Food items from any registered Home Food
shop.
 Check order status.

5
  Give feedback or any complain about Home Food shop if any issue caused
during/after placing order.
 Give Rating: Customers can give rating to the concerned Home Food shop
after the completion of order according to his/her satisfaction.
 Pay bill: Upon successful completion of any order, customers can either pay
the amount to the concerned delivery person on the spot or can transfer the
amount to the concerned Home Food shop’s account number available on
the website.

4. Functionalities of Home Food shop Manager

 Managers can register and login to the system.
 Managers can Add, edit, delete and view all items, categories and all
information of their Home Food shop in the system.
 Managers can Add Home Food shop’s menu with specific details such as
Home Food item name, picture, price, delivery time etc.
 Managers can manage orders.
 Managers can cancel orders.
 Managers Update order status.
 Managers can View report of daily, weekly and monthly sale.
 Managers can View any complaints of the customer.
 Managers can check the rating given by the customers.
 Managers can check any remarks (if given) by the customers.

Non-Functional Requirements:

o Performance requirements:
 The system need to be reliable.
 Web pages are loaded within few seconds.
 If unable to process the request appropriate error message.
o Safety Requirement:

6
  Users must be authenticated.

 Details need to be maintained properly.

o Security Requirements:

 Sharing of details.

 The details of user must be safe and secure.

 After entering the password and user id the user can assess his profile.

o Evolution

 Testability.
 Maintainability.
 Extensibility

7
USE CASE DIAGRAM:

8
 USAGE SCENARIOS:

Title: Admin – Users Registration

Use case ID: STEP _01
Actor: Admin
Description: All Users Create his/her Account
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click on register.
Fill in particulars.
Clicks submit.
Admin Approved Accounts
Post condition: Task has been completed successfully.
Author: MC220201776

Title: Admin / Add Home Shops

Use case ID: STEP _02
Actor: Admin
Description: Admin Add new Home Shops
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login Account
Click on add new information
Fill in particulars.
Clicks submit.
Post condition: Task has been completed successfully.
Author: MC220201776

Title: Add Menu/Food Information

Use case ID: STEP _03
Actor: Admin
Description: Admin can Add information
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login Account
Click on Provides you want to update
Update required fields
Clicks update.
Post condition: Task has been completed successfully.
Author: MC220201776

9
Title: Admin edit/delete Menu – home shop info
Use case ID: STEP _04
Actor: Admin
Description: Admin have access to edit delete any info
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click on edit delete.
Reload page
Post condition: Task has been completed successfully.
Author: MC220201776

Title: Admin Manage Users

Use case ID: STEP _05
Actor: Admin
Description: Admin manage NDMA - users
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click user list.
Fill in particulars.
Clicks submit.
Post condition: Task has been completed successfully.
Author: MC220201776

Title: Admin View feedback

Use case ID: STEP _06
Actor: Admin
Description: Admin view user feedback
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login admin
Click on feedback
Click on view
Post condition: Task has been completed successfully.
Author: MC220201776

10
Title: Admin/ Generate Reports
Use case ID: STEP _07
Actor: Admin
Description: Admin create reports.
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login with your account
Click on Reports
Create
Post condition: Task has been completed successfully.
Author: MC220201776

11
Adopted Methodology

Definition:
“Methodology is a framework that is used to structure, plan and control the process
developing an information system”.
VU process model is a combination of the waterfall and spiral model.

Waterfall model:
Waterfall model is the first process model to be introduced. This model is also known as
linear sequential model or classic life cycle model. It consists of five stages.

1. Requirement definition:
In this stage, the systems services, constraints and goals are established by consultation
with system users.
2. System and software design:
In this stage, we conceptualize overall system architecture.

3. Implementation and unit testing:

In this stage the software design is realized as a set of programs or program units.
4. Integration and system testing:
In this stage, the individual program unit or programs are integrated and tested as a
complete system to ensure that the system requirements have been met.
5. Operation and maintenance:
Maintenance means correcting errors which were not discovered in earlier stages.
Spiral model:
It is a form of incremental model. In this model, main emphasis is given on risk analysis.
It is used for large and complicated projects. Generally, the spiral model has four phases:
planning, risk analysis, development, and evaluation. Planning phase covers scope,
requirement and functionality of the system. Second phase risk analysis is most important
phase. Development phase covers the designing, coding and testing and finally the
application is delivered to client for further evaluation
12
 Adopted model: VU process model

In our project we choose VU process model it is the combination of waterfall and spiral
model.VU process model is a hybrid approach. It is depicted in following diagram

Requirements Analysis In each vu model

Each phase
Planning: risk analysis: report back
Software requirement cost effectiveness
Work plan with less work

Client evaluation: development: Design

deliver project designing, coding,
with specific testing
requirement otherwise
recycle for further
evaluation.

Acceptance Testing Coding

Above is the diagram of combination of waterfall and spiral model.

Reason for choosing this methodology:

1. VU process model has the benefits of predictability.
2. Maintenance is easy in this model.
3. Requirements are well understood.
4. It is more concise and advanced model than waterfall model.
5. VU process model is heavily dependent on risk analysis.
6. VU process model allows us to do correction at any stage.

13
WORK PLAN:

14