Online Spare Food Collection and Supply

Management System
SOFTWARE

Requirements Specification

Version 1.0

NAME: ASMA AFRAQ

GROUP ID: BC190201751

Supervisor Name: Ghulam Abbas

1
 SEMESTER Spring: 2023
REVISION HISTORY

Date (DD/MM/YYYY): 10-07-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: BC190201751

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

Functional Requirements --------------------------------------------------------- 5

Non-Functional requirements ---------------------------------------------------- 6

Use Case Diagram ----------------------------------------------------------------- 7

Usage Scenarios -------------------------------------------------------------------- 8

Adopted Methodology ------------------------------------------------------------- 11

Work Plan (Work Plan) ----------------------------------------------------------- 13

3
 SRS DOCUMENT
Scope of Project:

Food get’s wasted every year all over the world. Millions do not get the meals they need

to thrive. At time, people may have excess food that may be good but may be wasted due

to lack of organizations catering to needy people. In such times, it is of great help if there

are places that can store these products and distributing them amongst the needy. Our

system works to get food from such donors and help people. Our network moves the food

making sure the donated food and groceries reach where they are needed the most. We

are assuming the donor approaches our organization to make the donations. We register

the donor and accept donations. The donations accepted are then added to the inventory-

by-inventory clerk by updating their expiry date. We are assuming that needy

organizations contact us when they are in need of food, once they approach we register

those organization so as to make them part of our system. The organizations are

categorized on the basis of people they cater. Eg: old people. Once the registered

organization logs onto the system, they will find a product list suitable to their needs.

They can add the product from the list and then logout. To ensure that there is an

optimum efficiency of the food that is delivered to the organization, an algorithm is

implemented that calculates the math and determines if the product will pass its expiry

date within the delivery time frame also food products catering to the specific age group

are displayed to only that age group.

4
Functional Requirements:

This application will perform following operations.

Administrator:

 Admin can manage (Approve, update and delete) Registered Donators Members.
 Admin can manage (Approve, update and delete) Needy Persons.
 Admin can Add, update Food record.
 Admin have only access to delete Food record.
 Admin can view Donated Food Reports.

Registered Donators:

 Donator first create his account and then waiting for admin approval.
 Registered Donator can add the data of spare Food.
 Registered Donator can update or delete the quantity of Food.
 Registered Donator can view the Food Reports.

Needy Persons;

 Needy Persons can create an account.

 A user can check the available food items.

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.

5
o Safety Requirement:

 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

6
Use Case Diagram(s):

7
Usage Scenarios:

Title: Admin View Accounts

Use case ID: OGPM _01
Actor: Admin
Description: All Users(Staff and General 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: BC190201751

Title: Admin / Donator Add Food

Use case ID: OGPM _02
Actor: Admin, Donators
Description: Admin & Donators Add new Food
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login Account
Click on add new Animals
Fill in particulars.
Clicks submit.
Post condition: Task has been completed successfully.
Author: BC190201751

Title: Admin/ Donators Update Food

Use case ID: OGPM _03
Actor: Admin, Donators
Description: Admin and Manager can update Donators
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Login Account
Click on Food you want to update
Update required fields
Clicks update.
Post condition: Task has been completed successfully.

8
Author: BC190201751

Title: Admin delete Donators

Use case ID: OGPM _04
Actor: Admin
Description: Admin have authority to delete any Food
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click on Delete.
Reload page
Post condition: Task has been completed successfully.
Author: BC190201751

Title: Admin Manage Users

Use case ID: OGPM _05
Actor: Admin
Description: Admin Add Tax
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
Click Donators or Needy Peoples.
Fill in particulars.
Clicks submit.
Post condition: Task has been completed successfully.
Author: BC190201751

Title: Admin View Contact Us messages

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

9
Title: Admin/ Generate Reports
Use case ID: OGPM _07
Actor: Admin
Description: Admin create Food 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: BC190201751

Title: Donators view Reports

Use case ID: OGPM _8
Actor: Donators
Description: User view Reports
Pre-condition: Application is running and ready for use.
Task sequence: Open application.
User login
View Reports.
Post condition: Task has been completed successfully.
Author: BC190201751

10
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

11
 phase. Development phase covers the designing, coding and testing and finally the
application is delivered to client for further evaluation
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.

12
WORK PLAN:

# Task Start Duration June Jul Aug sep oct

1 SRS 15-june-23 30Days
2 Design 15-Jul-23
3 Test 14-Sep-23
4 Final 05-Oct-23

13