CHAPTEER-1

INTRODUCTION

With millions of people going hungry every day, and tons of food being wasted, a waste food
management and donation web application has the potential to make a significant impact.
Such an application would allow donors to connect with charities and other organizations that
can distribute leftover food to those in need. The web application would work by allowing
donors to enter information about the food they have available, including location and contact
details, which would then be shared with charities and NGOs that are able to pick up and
distribute the food to those in need. By doing so, the application would help to reduce food
waste and address the issue of hunger simultaneously. In addition, this web application could
also incorporate features such as expiration date management, food sharing between
neighbors, and discounted pricing for unsold products from grocery stores and restaurants.
Overall, a waste food management and donation web application has huge potential to make
a positive impact on both the environment and society.

As per the knowledge the technology is going advanced and growing day by day. Over main
motto is to help needy people. The idea behind over project can be use by many people who
wish to donate things to needy organizations Also, many organizations like to ask for various
things required by them such as clothes, food grains, books utensils. In this mobile app, we
have tried to reduce food wastage by giving waste food to people or organization who need it.
The needy will add to a request, in case of any leftover food donor have. This request is sent
to the list of donors. The Available Donor then accept the request. We are going to manage
the delivery system by appointing delivery person who will collect the food from the donor
and distribute among the needy people. Second option for delivery system is that volunteers
who wish to help to donate food can join us for distribution in near by areas. For eg: they can
distribute food in government school, government hospital, orphanage, old age homes. And
the third option is the Food Bank if we receive food in odd times we can give it to food bank
where the care of food is taken. Safety and Hygiene are maintained in food banks. So. food
wastage or food spoilage cannot occur.
A drastic increase can be seen in food waste. As per data given by Food and Agriculture
Organization, 1/3rd of food produced for human consumption is wasted globally, which
accounts for almost 1.3 billion tons per year. On the other hand, also as per WHO 20% of the
population face extreme food shortages. Hence there is a need to come up with a solution that
can avoid food waste & can help feed the needy.

This web-based Leftover Food Management system can assist in collecting the leftover food
from hotels & restaurants to distribute among those in need. NGOs that are helping poor
communities to battle against starvation & malnutrition can raise a request for food supply
from restaurants through this application. Once the request is accepted, the NGOs can collect
the food from the restaurants for its distribution. In this way this android-based food waste
management system will help restaurants to reduce food waste and will help in feeding the
poor and needy people.

In this system, we have tried to reduce restaurant food wastage by giving leftover food to
NGOs. NGOs will raise a request, in case of any leftover food restaurants have. This request
is sent to the restaurant manager of that particular restaurant. The NGO Manager then
approves the request and assigns it to one of the NGO employees for takeaway and forwards
the request to the restaurant. The leftover food at the restaurant can be given to NGOs at the
end of the day. The admin can track the history of restaurants and NGOs for the leftover
foods.

Many restaurants and people tend throw the leftover food at the end of the day even though
the food is perfectly fine to be eaten, which means that huge amounts of food is wasted.
While all that food is being wasted, some families can barely afford proper meals with their
limited money. They don’t get enough nutrition due to lack of having three meals in a day.
Therefore, we decided to create our application to link the restaurant and people with the
unfortunate people, so instead of throwing the food, the unfortunate will be able to pick it up
from the restaurant and the people at the end of the day. The application allows the
restaurants and people to log in, and upload an image of the meals they have as leftovers
along with a description of that meal, and the location where to pick it up.

A single restaurant wastes about 1000 pounds of food in a month. Restaurants, caterers,
corporate dining rooms, hotels, and other food establishments promptly distribute perishable
and prepared foods to hungry people in their communities. In this system hotels can provide
food to NGO’s by requesting them. NGO’s can also request hotels when they feel shortage of
food. No food waste is the mission of this system. In this system there are 3 major entity
namely, Admin, Restaurant and NGO. Admin can login and manage restaurants and NGO’s
by adding them and update the list. Restaurant can login and update their profiles. They can
also view the accepted food list which is yet to pick up. Restaurant can add access food
details. They can also accept request from NGO. Restaurant can also view the accepted,
pending and previous todays Access Food list which are accepted by NGO. They will be
getting notifications. NGO can login and update their profile by providing details. They can
view and accept the restaurants request and also food details. They can accept and assign an
employee for food pick up. In the time of food shortage NGO can also raise request to the
restaurants. And after request been accepted by restaurant, they can assign an employee for
delivery purpose. They will get notifications.

Many
restaurants and people tend to
throw the leftover food at the
end of the day even though
the food is perfectly fine to be
eaten, which means that huge
amounts of food is wasted.
While all that food is being
wasted, some families can
barely afford proper meals
with
their limited money. They
don't get enough nutrition due
to the lack of having three
meals
in a day. Therefore, we
decided to create our
application to link the
restaurant and people
with the unfortunate people, so
instead of throwing the food,
the unfortunate will be able
to pick it up from the
restaurant and the people at
the end of the day. The
application
allows the restaurants and
people to log in, and upload an
image of the meals they have
as
leftovers along with a
description of that meal, and
the location where to pick it
up.

SCOPE OF THE CAPSTONE PROJECT

Many people face starving because of food shortage. Food shortages in developing countries
are common. The people most affected are smallholder. There are several ways and means to
help the needy but nothing works better than making a contribution to an organization
dedicated to helping poor communities to battle against poverty. People living in NGO also
faces food shortage issues. This application can help needy people to eat food. With help of
this web application restaurant can serve food to many people. NGO’s can also contact
restaurants for providing food in shortage of food. This can feed many poor and needy
people.

The scope of a capstone project on waste food management and donation web application can
be broad and impactful. The project can aim to develop an efficient and user-friendly web
application that connects donors with charities and organizations that distribute food to the
needy. The application can include features such as location-based services, donation
tracking, and priority allocation to ensure that food reaches those who need it most.
Additionally, the capstone project can explore the implementation of innovative features such
as food sharing between neighbors, expiration date management, and discounted pricing for
unsold products from grocery stores and restaurants. The project can also focus on data
collection and analysis to create graphs and reports on the impact of reducing hunger through
the application. Overall, a capstone project on waste food management and donation web
application has the potential to make a significant impact on both the environment and
society by reducing food waste and addressing the issue of hunger.
CHAPTER-2
CAPSTONE PROJECT PLANNING
 Work breakdown structure(WBS)
Here's a possible work breakdown structure (WBS) for Leftover food management and
contribution web application:

1. Project Management

 Appoint a project manager

 Develop a project plan
 Monitor project progress

2. Requirements Gathering

 Identify user requirements

 Define project scope
 Define deliverables

3. Design

 Develop a user-friendly interface

 Create a database to store information about food donations and charities
 Determine the application architecture

4. Development

 Create the front-end of the application

 Develop the back-end of the application
 Implement location-based services

5. Testing

 Conduct unit testing

 Conduct integration testing
 Conduct system testing

6. Deployment

 Prepare the application for deployment

 Deploy the application
  Conduct user acceptance testing

7. Maintenance

 Provide on going support and maintenance

 Continuously update and improve the application
 Monitor application performance

This WBS is not exhaustive and can be further broken down into smaller tasks. The WBS can
be used as a tool to manage the project and ensure that all tasks are completed on time and
within budget.

A waste food management and donation web application project can include the following
tasks:

1. Project Initiation

 Define project vision, mission, scopes, and objectives

 Identify stakeholders and their roles and responsibilities

2. Project Planning

 Create a project management plan

 Develop project schedule and milestones
 Define project budget and resources
 Create the Work Breakdown Structure (WBS)
 Identify project risks and develop risk management plan

3. Design and Development

 Design user interface

 Develop front-end and back-end functionality
 Implement location-based services and food tracking features
 Incorporate expiration date management, food sharing between neighbors, and
discounted pricing for unsold products from grocery stores and restaurants

4. Testing and Quality Assurance

  Conduct system testing
 Ensure data security and privacy
 Perform quality assurance testing to ensure the application meets user requirements

5. Deployment and Launch

 Deploy the application in a live environment

 Provide user training and support
 Conduct a post-implementation review to evaluate the success of the project and
identify areas for improvement

6. Maintenance and Support

 Provide ongoing maintenance and support for the application

 Monitor user feedback and make necessary adjustments to improve the application's
functionality and user experience

Overall, the WBS for a waste food management and donation web application project should
be comprehensive and cover all aspects of the project lifecycle, from initiation to
maintenance and support.

 Timeline development- schedule

Timeline development schedule for waste food management and contribution web application

Based on the provided Web Search Results, a timeline development schedule for a waste
food management and contribution web application can be developed as follows:

1. Project Initiation

 Define the project scope, goals, and objectives

 Identify project stakeholders and their requirements
 Assemble the project team
 Develop a project charter

2. Requirements Gathering and Analysis

  Conduct research on existing waste food management and contribution web
applications
 Identify user requirements and functional specifications
 Develop use cases and user stories
 Define the project timeline and milestones

3. Design and Development

 Develop wireframes and prototypes

 Create the front-end and back-end of the application
 Implement location-based services and food tracking features
 Incorporate expiration date management, food sharing between neighbors, and
discounted pricing for unsold products from grocery stores and restaurants
 Conduct unit testing and integration testing

4. Testing and Quality Assurance

 Conduct system testing

 Ensure data security and privacy
 Perform quality assurance testing to ensure the application meets user requirements

5. Deployment and Launch

 Deploy the application in a live environment

 Provide user training and support
 Conduct a post-implementation review to evaluate the success of the project and
identify areas for improvement

6. Maintenance and Support

 Provide ongoing maintenance and support for the application

 Monitor user feedback and make necessary adjustments to improve the application's
functionality and user experience

Note that the timeline development schedule is tentative and can vary depending on the
complexity of the project and the resources available.
 Cost Breakdown Structure(CBS)

1. Requirements Gathering (1-2% of total cost)

 Conduct focus groups and surveys to identify user requirements

 Analyze user feedback and refine project scope
 Define deliverables and project timeline

2. Design (10-15% of total cost)

 Develop user interface design and application architecture

 Create database schema and data models
 Determine technology stack and third-party integrations

3. Development (60-70% of total cost)

 Develop front-end and back-end functionality

 Implement location-based services and food tracking features
 Incorporate expiration date management, food sharing between neighbors, and
discounted pricing for unsold products from grocery stores and restaurants

4. Testing and Quality Assurance (10-15% of total cost)

 Conduct unit testing and integration testing

 Ensure data security and privacy
 Perform quality assurance testing to ensure the application meets user requirements

5. Deployment and Launch (5-10% of total cost)

 Deploy the application in a live environment

 Provide user training and support
 Conduct a post-implementation review to evaluate the success of the project and
identify areas for improvement

6. Maintenance and Support (ongoing cost)

 Provide ongoing maintenance and support for the application

  Monitor user feedback and make necessary adjustments to improve the application's
functionality and user experience

 Capstone project Risks assessment

The following are potential risks that could be associated with a waste food management and
donation web application:

1. Contamination risk: There is a risk of contamination from plastic and chemical

contaminants in food waste streams. This risk could be mitigated by ensuring that
proper disposal protocols are in place and that the application is designed to handle
waste food safely.
2. Data security and privacy risks: The application will likely store sensitive user data,
such as location and personal information. There is a risk of data breaches or
unauthorized access to this information. This risk could be mitigated by implementing
strong encryption and security protocols.
3. Technical risks: Developing a web application can be complex, and technical issues
such as bugs or compatibility issues could arise. This risk could be mitigated by
conducting thorough testing and quality assurance throughout the development
process.
4. User adoption risks: If users are not willing or able to use the application, it may not
be successful. This risk could be mitigated by conducting user research and testing to
ensure that the application meets user needs and is user-friendly.
5. Legal and regulatory risks: Depending on the jurisdiction, there may be legal and
regulatory requirements that the application must comply with. This risk could be
mitigated by conducting thorough research and ensuring that the application is
compliant with all relevant laws and regulations.

It is important to note that these risks are not exhaustive and may vary depending on the
specific project requirements and context. Conducting a comprehensive risk assessment and
developing a risk management plan can help mitigate potential risks and ensure project
success.
 Requirements Specifications
 Functional

The functional requirements specification for a waste food management and donation web
application:

1. Introduction

 Purpose and scope of the document

 Overview of the waste food management and donation web application

2. General Description

 Product perspective
 Product functions
 User characteristics
 Constraints
 Assumptions and dependencies

3. Functional Requirements

 User registration and authentication

 Donor interface for food donation
 Organization interface for receiving food donations
 Food tracking and management
 Location-based services
 Expiration date management
 Food sharing between neighbors
 Discounted pricing for unsold products from grocery stores and restaurants
 Reporting and analytics

 Non-Functional Requirements

 Performance
 Usability
 Security
  Compatibility
 Maintainability

1. System Requirements

 Hardware requirements
 Software requirements
 Database requirements

2. User Interface Design

 Design principles and guidelines

 Mock-ups and wireframes

3. Glossary

 Definitions of key terms and concepts

 User input

User input and features that could be included in a waste food management and donation web
application:

1. User registration and authentication to ensure security and prevent misuse of the
application
2. Donor interface for users to post pictures and information about the food they wish to
donate, including quantity, location, and expiration date
3. Organization interface for users to find and connect with non-profits and other
organizations that accept food donations
4. Food tracking and management system to keep track of donated food and ensure that
it is distributed efficiently
5. Location-based services to help users find nearby organizations that accept food
donations
6. Expiration date management system to ensure that donated food is still fresh and safe
to consume
 7. Food sharing between neighbors to encourage local communities to come together
and reduce food waste
8. Discounted pricing for unsold products from grocery stores and restaurants,
encouraging businesses to reduce their waste and sell their excess food at a lower
price
9. Reporting and analytics to track the success of the application in reducing food waste
and helping those in need.

 Technical constraints

Technical constraints that may need to be considered for a waste food management and
donation web application include:

1. Data security and privacy: The application will need to handle sensitive information
such as user data and donation information, so it is important to implement strong
security measures to prevent data breaches and protect user privacy.
2. Scalability: The application should be designed to handle a potentially large amount
of data and traffic, especially as the user-base grows.
3. Compatibility: The application should be compatible with a variety of devices and
platforms, including desktop computers, tablets, and smartphones, and different
operating systems such as iOS and Android.
4. Integration with existing systems: The application may need to integrate with existing
systems, such as food banks, to effectively manage food donations and distribution.
5. Performance: The application should be designed to perform efficiently, with fast load
times and minimal downtime.
6. Reliability: The application should be reliable and have minimal bugs or errors to
ensure that it can be used effectively by users.
7. Accessibility: The application should be designed to be accessible for all users,
including those with disabilities.

It is important to consider these technical constraints during the development process to

ensure that the waste food management and donation web application is effective, efficient,
and user-friendly.

Design Specification
  Chosen System Design
Some key considerations for the system design of a waste food management and donation
web application:

1. User interface design: The user interface should be intuitive and user-friendly, with
clear navigation and easy-to-use features.
2. Scalability: The application should be designed to handle a potentially large amount
of data and traffic, especially as the userbase grows.
3. Compatibility: The application should be compatible with a variety of devices and
platforms, including desktop computers, tablets, and smartphones, and different
operating systems such as iOS and Android.
4. Integration with existing systems: The application may need to integrate with existing
systems, such as food banks, to effectively manage food donations and distribution.
5. Performance: The application should be designed to perform efficiently, with fast load
times and minimal downtime.
6. Reliability: The application should be reliable and have minimal bugs or errors to
ensure that it can be used effectively by users.
7. Accessibility: The application should be designed to be accessible for all users,
including those with disabilities.
8. Security: The application should be designed with security in mind, with measures in
place to protect user data and prevent unauthorized access.
9. Data management: The application should have a robust data management system in
place, with clear processes for storing, organizing, and analyzing data related to food
donations and distribution.
10. Testing and quality assurance: The application should undergo thorough testing and
quality assurance processes to ensure that it meets user needs and functions as
expected.

 Discussion of Alternative Designs

 A meal sharing app that connects users with excess food to those in need, either
through direct donation or selling at a discounted price.
 An app that tracks food expiration dates and sends reminders to users to consume or
donate food before it goes bad.
 A food donation app that connects businesses with surplus food to local charities and
food banks.
 A grocery store app that offers discounted prices on products that are close to their
expiration date, encouraging users to purchase and consume them before they go to
waste.
 An app that incentivizes users to reduce food waste by tracking their food
consumption and providing rewards for wasting less food.

 Detailed Description of Components/Subsystems

 User Interface: The user interface should be designed to be intuitive and user-friendly,
allowing users to easily navigate the application and perform tasks such as finding
organizations to donate food to or tracking donated food.
 Donor Interface: A donor interface should be included to allow users to donate excess
food, including features such as uploading photos and descriptions of the donated
food and specifying pickup or drop-off locations.
 Organization Interface: An organization interface should be included to allow non-
profits and other organizations to receive food donations, including features such as
managing incoming food donations and scheduling pickups or drop-offs.
 Food Tracking and Management: A food tracking and management system should be
included to keep track of donated food and ensure that it is distributed efficiently,
including features such as expiration date management and location-based services.
 Reporting and Analytics: A reporting and analytics system should be included to track
the success of the application in reducing food waste and helping those in need,
including features such as data visualization and reporting tools.
 Security: The application should include robust security measures to protect user data
and prevent unauthorized access.
 Integration with Existing Systems: The application may need to integrate with
existing systems, such as food banks, to effectively manage food donations and
distribution.
 Component 1-n

 User Registration and Authentication: This component would allow users to create
accounts, log in, and authenticate their identity to access features such as food
donation scheduling and food tracking.
 Food Donation Interface: This component would allow users to input information
about the food they wish to donate, including type, quantity, and location, and
schedule a pickup or drop-off time.
 Non-Profit Organization Interface: This component would allow non-profit
organizations to register and connect with users looking to donate food, as well as
manage incoming food donations and schedule pickups or drop-offs.
 Food Tracking and Management: This component would allow users and
organizations to track donated food, manage expiration dates, and ensure that food is
distributed efficiently and effectively.
 Reporting and Analytics: This component would allow users and organizations to
track the success of the application in reducing food waste and helping those in need,
including features such as data visualization and reporting tools.
 Security: This component would include measures such as encryption and secure
authentication to protect user data and prevent unauthorized access.
 Integration with Existing Systems: This component would allow the application to
integrate with existing systems, such as food banks, to effectively manage food
donations and distribution.
 Communication and Notifications: This component would allow users and
organizations to communicate with each other and receive notifications about food
donations, pick-up or drop-off times, and other important information.
 CHAPTER – 3
Approach and Methodology:
Methodology

 Agile methodology could be a suitable approach for developing a waste food

management and donation web application. Agile methodology involves iterative and
incremental development, continuous feedback, and adaptive planning, which could
be helpful for managing the complex and evolving needs of a waste food management
and donation web application.
 Scrum could be a specific framework within Agile methodology that could be used to
manage the development of the application. Scrum involves self-organizing teams
working collaboratively with customers, adaptive planning, and flexible approaches to
problem-solving. The Scrum framework includes specific roles (such as product
owner, scrum master, and development team), events (such as sprint planning, daily
scrum, sprint review, and sprint retrospective), and artifacts (such as product backlog,
sprint backlog, and increment).
 Overall, using Agile methodology and specifically Scrum could be a suitable
approach for developing a waste food management and donation web application.
However, it is important to carefully evaluate the specific needs and goals of the
application and choose the most appropriate development methodology accordingly.

One possible use case for a waste food management and donation web application is a
restaurant or grocery store that has excess food that they want to donate to a food
bank or charity. The application would allow the restaurant or grocery store to post
information about the available food, including quantity, type, and expiration date.
NGOs or food banks registered on the application would receive notifications about
the available food and could then arrange for pickup or delivery. The application
would also provide features for tracking the donated food, managing expiration dates,
and generating reports on the success of the donation program. This use case would
help to reduce food waste while also supporting local communities and those in need.