UNIVERSITY OF MYSORE

YUVARAJA’S COLLEGE
(A constituent autonomous college)

JLB Road, MYSORE-560005

Department of Computer Science

A PROJECT REPORT

ON

“FOOD NETWORK”
SUBMITTED AS PARTIAL FULFILLMENT OF THE COURSE FOR THE AWARD OF

DEGREE OF BACHELOR OF COMPUTER APPLICATIONS

Submitted By
RAKSHITH R KASHYAP (YBC17153)

SHIVAKUMAR K M (YBC17138)

Under the guidance of

Mr. CHANDRAIAH T Dr. LOKESH GOWDA J
Assistant Professor Assistant Professor
Dept. of computer science Dept. of computer science
Yuvaraja’s college, Mysuru Yuvaraja’s college, Mysuru

Mr.DHANANJAYA KUMAR K Mr. DAYANANDA KJ

Assistant Professor Assistant Professor
Dept. of computer science Dept. of computer science
Yuvaraja’s college, Mysuru Yuvaraja’s college, Mysuru
 YUVARAJA’S COLLEGE
(A constituent autonomous college of the University of Mysore)

JLB Road, MYSORE-560005

Department of Computer Science

DECLARATION
We, the students of VI semester, BCA, at Yuvaraja’s college Mysore,
declare that the project work titled “FOOD-NETWORK” has been
carried out by us and submitted in partial fulfilment of the course
requirements for the award of degree in Bachelor of Computer
Applications of Mysore University, during the academic year 2019-20

RAKSHITH R KASHYAP (YBC17153)

SHIVAKUMAR K M (YBC17138)
 ACKNOWLEDGEMENT
The successful implementation of the system filled us with a great sense of
satisfaction because it is concatenation of diverse needs that we were fulfilled by
various well-wishers it is deep reverence that acknowledge their gesture.

Our heartfelt thanks to Dr. B.N. YASHODHA, Principal, Yuvaraja’s College, Mysore
for giving us the accessory environment to acquire knowledge and skill.

We are thankful to Mrs. ANNAPURNA H, Head of the department, Computer

Science, for his valuable support during the project. We express high regards to our
esteemed college Yuvaraja’s College, Mysore for grooming us all these years. The
support given to us by the Department of Computer Science is highly memorable.

Our sincere thanks to Mr. CHANDRAIAH T, Assistant Professor, Department of

Computer Science, Dr. LOKESH GOWDA J, Assistant professor, Department of
Computer Science, Mr. DHANANJAYA KUMAR K, Assistant professor, Department
of Computer Science, Mr. DAYANANDA K J, Assistant professor, Department of
Computer Science, Department of Computer Science , for the kind support for our
project. We are deeply grateful to our faculty members of Computer Science
Department for their guidance. Without their help the project would not have seen the
light of success.

Finally, a sincere sense of gratitude to our parents who supported throughout the
project and lastly, we thank all our friends.

Thanking you,

RAKSHITH R KASHYAP (YBC17153)

SHIVAKUMAR K M (YBC17138)
 YUVARAJA’S COLLEGE
(A constituent autonomous college of the University of Mysore)

JLB Road, Mysore-560005

Department of Computer Science

C ERTIFICATE

This is to certify that the project entitled “FOOD-NETWORK” is the benefice

project work carried out by Rakshith R Kashyap Register No. YBC17153
student of BCA, Yuvaraja’s college. A constituent autonomous college of the
University of Mysore, during the year 2019-20. In partial fulfilment of the
requirements for the award of Degree of Bachelor of Computer
Applications.

SIGNATURE OF THE GUIDES

1: ....................................................

2: ....................................................

SIGNATURE OF EXAMINER

1: .....................................................

2: ............................................. SIGNATURE OF HOD

 YUVARAJA’S COLLEGE
(A constituent autonomous college of the University of Mysore)

JLB Road, Mysore-560005

Department of Computer Science

C ERTIFICATE

This is to certify that the project entitled “FOOD-NETWORK” is the benefice

project work carried out by SHIVAKUMAR K M Register No. YBC17138
student of BCA, Yuvaraja’s college. A constituent autonomous college of the
University of Mysore, during the year 2019-20. In partial fulfilment of the
requirements for the award of Degree of Bachelor of Computer
Applications.

SIGNATURE OF THE GUIDES

1: ....................................................

2: ....................................................

SIGNATURE OF EXAMINER

1: .....................................................

2: ............................................. SIGNATURE OF HOD

 CONTENTS
SL. NO. NAME OF THE TITLE PAGE NO.

1 INTRODUCTION................................................................................ [1-2]

1.1 Motivation for the project

1.2 Objective of the project

2 LITERATURE SURVEY............................................................... [3-4]

2.1 Overview

2.2 Literature Survey

3 FEASIBILITY STUDY................................................................... [5-7]

3.1 Introduction

3.2 Types of Feasibility

4 USER APPLICATION ENVIRONMENT................................... [8-18]

4.1 Tools and Technologies used

5 SYSTEM ANALYSIS.................................................................... [19-20]

5.1 Existing System

5.2 Proposed System

6 SYSTEM REQUIREMENT AND SPECIFICATION................ [21-24]

6.1 Introduction

6.2 Functional Requirements

6.3 Non-Functional Requirements

6.4 System Requirements

7 SYSTEM DESIGN............................................................................ [25-42]

7.1 Introduction

7.2 System Architecture Diagram

 7.3 Detailed Design

7.3.1 Data Flow Diagram

7.3.2 Use case diagram

7.3.3 Sequence Diagram

7.3.4 Activity Diagrams

7.3.5 Entity-Relationship Diagram

8 SYSTEM IMPLEMENTATION................................................... [43-47]

8.1 Introduction

8.2 Pseudo Codes

8.3 Code

9 SYSTEM TESTING...................................................................... [48-54]

9.1 Introduction

9.2 Types of Testing

10 SYTEM SCREENSHOTS............................................................ [55-57]

11 CONCLUSION AND FUTURE ENHANCEMENT.................. [58-58]

11.1 Future Enhancements

12 REFERENCES AND BIBLIOGRAPHY.................................... [59-60]

12.1 References

12.2 Bibliography
FIG.NO
NAME OF THE DIAGRAM PAGE NO.
4.1.1
The .NET Framework Overview 10
4.1.3
Visual Studio 2015 13
4.1.7
4.1.7 SQL server 18
7.1
Three-tier Architecture 26
7.2
System Architecture 27
7.3.1 a)
Level 0 DFD 29
7.3.1 b)
Admin Level 1 DFD 30
7.3.1 c)
Receiver Level 1 DFD 31
7.3.1 d)
Donor Level 1 DFD 31
7.3.2 a)
Admin Use case diagram 32
7.3.2 b)
Receiver & Donor Use case diagrams 33
7.3.3 a)
Admin Sequence Diagram 34
7.3.3 b)
Donor Sequence Diagram 35
7.3.3 c)
Receiver Sequence Diagram 36
7.3.4 a)
Admin Activity Diagram 38
7.3.4 b)
Donor Activity Diagram 39
7.3.4 c)
Receiver Activity Diagram 40
7.3.5
Entity Relationship Diagram 42
9.1
The Testing process 49
TABLE OF DIAGRAMS
 CHAPTER 1

INTRODUCTION
 CHAPTER 1

INTRODUCTION
137crore people call India as their home, which is about 17.7% of total world population. India
is the second most populated country in the world, as the population increases the biggest challenge is
to feed the huge population. India is currently number one in the list of most undernourished people in
a country; there are nearly 20crore people who are undernourished due to lack of food, proteins and
minerals. The sharp increase in the amount of wastage in terms of food makes the need for charity in
terms of donation. In the current scenario food is being wasted daily on a large basis in different
restaurants, weddings, social functions, college canteens and many other social events. People donate
food manually by visiting each organization number of times, in order to reduce the problems of food
wastage where as there are websites that have taken efforts to help people donate food .The proposed
system presents, a new internet-based application that provides a platform for donating leftover food to
all needy people/organizations.

The system is shown to be an effective means of donating things to organizations, etc. over the
internet. It shows the potential for avoiding the wastage of food. It provides information and the
motivation to donate food and reduce food wastage, thereby describing existing donation system and
how the product works for betterment of the society. This system will create a common collaboration
portal for hotels/restaurants and charities, charity can directly contact restaurants who have food
remaining and report generation which will show how much food is donated by which restaurant.

In this system Food Donor, Food receiver, Transporter, admin are the main modules where
Food Donor can be any organization/Person who wants to donate food, he can create a new food
donation request and Food receiver can be any charity firm seeking for food. A new food donation
request will be created on the portal and once the request is accepted, a notification is sent to
Transporter who is responsible for moving food from food donor to food receiver.
1.1 Motivation for the Project
In highly populated countries like India, food wastage is a disturbing issue. The streets,
garbage bins and landfills have ample proof to prove it. Marriages, canteens, restaurants, social and
family get-togethers and functions expel out so much food. Food wastage is not only an indication
of hunger or pollution, but also of many economic problems. The high standard of living has
resulted in the wastage of food, clothes, etc. because of quick changes in habits and lifestyle.
Instead of wasting these things we can put them in use by donating them to various organizations
such as orphanages, old age homes, etc. This system aims to establish a link between donors and
the charity homes/needy households to enable excess food donation.

1.2 Objective of the project

The application's main motto is "Minimum wastage & Maximum consumption" of food.

➣ The automated system provides different types of users to support the cause by actively
involving themselves in various functions of the system.
➣ This system tracks the most possible locations where large amount of food is being wasted
and a database of the donations and organizations are maintained.
➣ Instead of wasting food, the Food-Network helps to feed orphans, homeless,
undernourished etc. by real time analysis and communication.
 CHAPTER 2

LITERATURE SURVEY
 CHAPTER 2

LITERATURE SURVEY

2.1 OVERVIEW

A literature review can be just a simple summary of the sources, but it usually has an
organizational pattern and combines both summary and synthesis. A summary is a recap of the
important information of the source, but a synthesis is a re-organization, or a reshuffling, of that
information. The relevant literature on food wastage management has been reviewed in this section.

Managing fresh food supply chains is very complex with the recently increased concern of
public health, food safety, food quality, demand and price variability, and the limited lifetime of
these products. Due to the short shelf life and product perishability, inventory management. Hence
the below surveys were analysed to build the system.

2.2 Literature survey

Paper: Food donation portal [1]

Published in 2015 summaries in brief the evolution of food donation activities and offers a
medium that connects donors with NGOs. An idea for a food donation network is presented and
impact on society through this medium is mentioned. The disadvantage in this paper is that there is
no GPS service available. That means the system does not allow the organization or charity to find
the nearest donor available in the area and they have to manually find the donors.

Paper: Helping Hands [2]

Published in 2016, a new internet-based application that provides a platform for donating
old stuff and leftover food to all needy people/organizations. It provides information about the
motivation to come up with such an application, thereby describing the existing donation system
and how the proposed product works for the betterment of society. The disadvantage of this project
is that there is no dashboard available that is, at the end of the month the system didn’t get all the
records that how much is donated or received by the receiver.
Paper: Beyond food sharing: Supporting food waste reduction With ICTs [3]

Published in 2016, guaranteeing food security is the key in improving the quality of life of
citizens at all levels of society The recent economic crisis has increased the number of people
living in conditions of food poverty, especially in developed regions. This paper describes the use
of ICT tools to recover food surplus at different stages of the supply chain and also describes the
way forward for an integrated set of ICT tools to reduce waste from producers to households.

Paper: Food donations using a forecasting-simulation model [4]

Published in 2016, presents a methodology to estimate donations for non-profit hunger

relief organizations. These organizations are committed to alleviating hunger around the world and
depend mainly on the benevolence of donors to achieve their goals. However, the quantity and
frequency of donations they receive varies considerably over time which presents a challenge in
their fight to end hunger. A simulation model is developed to determine the expected quantity of
food donations received per month in a multi-warehouse distribution network. The simulation
model is based on a state-space model for exponential smoothing. A numerical study is performed
using data from a non-profit hunger relief organization. The results show that good estimation
accuracies can be achieved with this approach. Furthermore, non-profit hunger relief organizations
can use the approach discussed in this paper to predict donations for proactive planning.
 CHAPTER 3

FEASIBILITY STUDY
 CHAPTER 3

FEASIBILITY STUDY
3.1 INTRODUCTION
Feasibility is defined as the practical extent to which a project can be performed
successfully. To evaluate feasibility, a feasibility study is performed, which determines whether the
solution considered to accomplish the requirements is practical and workable in the software.
Information such as resource availability, cost estimation for software development, benefits of the
software to the organization after it is developed and cost to be incurred on its maintenance are
considered during the feasibility study. The objective of the feasibility study is to establish the
reasons for developing the software that is acceptable to users

3.2 TYPES OF FEASIBLITY

 Economical Feasibility
 Technical Feasibility
 Operational Feasibility
 Legal Feasibility
 Cultural & social Feasibility

Economic Feasibility:-
 The system is economically feasible as the proposed system is a nonprofit based
integrated platform promoting less wastage and maximum consumption of food.
 Investment needed is less than cost of any other way of communication.
 The software cost at the beginning of the project will be 1000/- Rupees or less the
project also requires some additional equipment at the end which may cost less with the
funding of government.
 The total life of the software and the equipments is 2 years or more with frequent
updates.
 The only purchases required by the users are the Data connection, Cost charged for
installation of browser, Operating system and other necessary computer peripherals.
Technical Feasibility:-
 The traditional way doesn’t use any technical components other than a telephone
contact which is highly unreliable.
 Proposed system only requires a web browser and any third party application or
even the basic email service for the smooth and effective operation of the system.
 The proposed system can be built based on existing technology and mix of current
technology.
 As the existing system is analogue, we can use current technology to implement the
operations of the old system in the new one.
 Further updates after the initial application can support new technology and addition
of new services.
 The proposed system can be technically enhanced as the need grows or changes in
future.

Operational Feasibility:-
 The management will provide support and training to use the proposed system after the
implementation and testing.
 The user environment will not be effected once the operation of system is started as the
updates are easy and user understandable.
 Proposed system makes sure that the computer resources and network architecture of
user system are workable.
 The size of the application is minimal and consumes less memory consumption and
CPU usage.

Legal Feasibility:-
 There are no patents or software licensed based on the current technology hence the
system is legally feasible.
 Our country’s law allows the use of automated documenting and tracking services, our
system will abide by any and all the rules imposed by the government.
 The system further will be a open source project downloadable and installable by
anyone under fair usage policy with terms and conditions applied.
Cultural & social Feasibility:-
 The system will be a web application which may be managed by the government or
nonprofit organizations hence the system is ensured to uphold social values
 Main objective of this system is to provide a facility for different users to socially
communicate and serve people in need.
 As per the main motto of the system “minimum wastage and maximum usage of food “
this will be delivered after the installation of the system into the society
 India is rich in culture and social values , similarly the system ensures balance in
cultural and ethnic diversity
 Usage of different utensils, tagging and storage of vegan and non-vegan food
separately ensure the religious views and food habits of the receiver or user is not
disturbed
 CHAPTER 4

USER APPLICATION
ENVIRONMENT
 CHAPTER 4

USER APPLICATION ENVIRONMENT

4.1 Tools and Technologies used

4.1.1 NET

The .NET Framework is a computing platform that simplifies application development in

the highly distributed environment. The .NET Framework introduces a completely new model for
the programming and deployment of applications.

.NET is Microsoft's vision of "software as a service", a development environment in which

we can build, create and deploy our applications and the next generation of components, the ability
to use the Web rather than our own computer for various services.

The .NET Framework is not a single application, it’s actually a collection of different
technologies bundled into one marketing term. The .NET Framework includes new languages like
C# and VB.NET, an engine for hosting programmable web pages and web services (ASP.NET), a
new model for interacting with databases (ADO.NET) and a class library stocked with tools for
everything from sending email to encrypting a password. The .NET technology facilitates to learn
about component based programming, structured error handling and how to access the files, XML
and relational databases.

.NET is a cluster of different technologies which includes:

 The .NET language : These include C# and Visual Basic .NET, the object-oriented and
modernized successor to Visual Basic 6.0, as well as Jscript.NET ( a server side version of
Java Script), J# ( a Java Clone), and C++ with manage extensions.
 ASP.NET: This is the engine that includes both web applications and web services, with
almost any feature from the .NET class library. ASP.NET also includes a set of web
specific services.
  Windows Form: This is the engine that is used to develop Windows based applications
which is also known as standalone applications. Like ASP this also has various controls and
tools which can be used to design the user interface. Windows forms are best suited for the
applications of installation type
 Visual Studio .NET: This optional development tool contains a rich set of productivity and
debugging features.

The framework is designed to fulfil the following objectives:

 To provide a consistent object-oriented programming environment whether object code is

stored and executed locally, executed locally but internet distributed or executed remotely.
 To provide a code execution environment that minimizes software deployment and
versioning conflicts.
 To provide a code-execution environment that guarantees safe execution of code, including
code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance problems of
scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of applications
such as Windows based and Web based applications.
 To build all communications on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.

The code written in .NET is not compiled directly to the execution; instead .NET uses two steps
to compile the code. First, the code is compiled to an Intermediate Language called
Microsoft Intermediate Language (MSIL). Second, the compiled code will be recompiled with the
Common Language Runtime (CLR), which converts the code to the machine code. The basic idea
of these two stages was to make the code language independence.

Microsoft introduced great technologies like COM, DCOM, COM+ etc. to enable reuse of
Software. Although these technologies are very powerful to reuse Software, they required a huge
learning curve. According to this aspect, Microsoft realized that its time to come up with a new
technology, a better one, an easier one, a new Framework, within which each programming task is
easy accomplished.
The major components of the .NET framework are shown in the below diagram:

Fig. 4.1.1 The .NET Framework Overview

Features Of .NET

 Interoperability - Because so many COM libraries have already been created, the .NET
Framework provides methods for allowing interoperability between new code and existing
libraries.
 Common Runtime Engine - Programming languages on the .NET Framework compile
into an intermediate language known as the Common Intermediate Language or CIL.
Microsoft's implementation of CIL is known as Microsoft Intermediate Language or MSIL.
In Microsoft's implementation, this intermediate language is not interpreted but rather
compiled in a manner known as just-in-time compilation (JIT) into native code. The
combination of these concepts is called the Common Language Infrastructure (CLI), a
specification; Microsoft's implementation of the CLI is known as the Common Language
Runtime (CLR).
 Language Independence - The .NET Framework introduces a Common Type System or
CTS. The CTS specification defines all possible data types and programming constructs
supported by the CLR and how they may or may not interact with each other. Because of
 this feature, the .NET Framework supports development in multiple programming
languages.
 Base Class Library - The Base Class Library, sometimes referred to as the Framework
Class Library, is a library of types available to all languages using the .NET Framework.
The BCL provides classes which encapsulate a number of common functions such as file
reading and writing, graphic rendering, database interaction, XML document manipulation,
and so forth.
 Simplified Deployment - Installation and deployment of Windows applications has been
the base of many developers' existence. Registry settings, file distribution and DLL hell
have been nearly completely eliminated by new deployment mechanisms in the .NET
Framework.
 Security - .NET allows for code to be run with different trust levels without the use of a
separate sandbox.

The design of the .NET framework is such that it supports platform independence. That is, a
program written to use the framework should run without change on any platform for which the
framework is implemented. At present, Microsoft has implemented the full framework only on the
Windows operating system. Microsoft and others have implemented portions of the framework on
non-Windows platforms, but to date those implementations are not widely used.

4.1.2 ASP.NET:

 ASP.NET is a web development platform, which provides a programming model, a

comprehensive software infrastructure and various services required to build up robust
web applications for PC, as well as mobile devices.
 ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and policies
to set a browser-to-server bilateral communication and cooperation.
 ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are compiled codes,
written using the extensible and reusable components or objects present in .Net framework.
These codes can use the entire hierarchy of classes in .Net framework.

The ASP.NET application codes can be written in any of the following languages:

 C#

 Visual Basic.Net
  Jscript

 J#

 ASP.NET is used to produce interactive, data-driven web applications over the internet. It
consists of a large number of controls such as text boxes, buttons, and labels for
assembling, configuring, and manipulating code to create HTML pages.

ASP.NET Web Forms Features

ASP.NET is full of features and provides an awesome platform to create and develop web
application. Here, we are discussing these features of Web Forms.

o Server Controls

o Master Pages

o Working with data

o Membership

o Client Script and Client Frameworks

o Routing

o State Management

o Security

o Performance

o Error Handling

4.1.3 Visual Studio 2015

Visual Studio includes a code editor supporting IntelliSense (the code completion component) as
well as code refactoring. The integrated debugger works both as a source-level debugger and a
machine-level debugger. Other built-in tools include a forms designer for building GUI
applications, web designer, class designer, and database schema designer. It accepts plug-ins that
enhance the functionality at almost every level—including adding support for source-control
systems (like Subversion) and adding new toolsets like editors and visual designers for domain-
specific languages or toolsets for other aspects of the software development lifecycle (like the
Team Foundation Server client: Team Explorer).

Visual Studio supports different programming languages and allows the code editor and
debugger to support (to varying degrees) nearly any programming language, provided a language-
specific service exists. Built-in languages include C, C++ and C++/CLI (via Visual C++), VB.NET
(via Visual Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2015). Support for other
languages such as M, Python, and Ruby among others is available via language services installed
separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Java (and J#) were
supported in the past.

Microsoft provides "Express" editions of its Visual Studio at no cost. Commercial versions of
Visual Studio along with select past versions are available for free to users via Microsoft's Dream
Spark program

Fig 4.1.3 Visual Studio 2015

4.1.4 HTML5

HTML stands for Hyper Text Mark-up Language. It is used to design web pages using mark-up
language. HTML is the combination of Hypertext and Mark-up language. Hypertext defines the
link between the web pages. Mark-up language is used to define the text document within tag
which defines the structure of web pages. HTML 5 is the fifth and current version of HTML. It has
improved the mark-up available for documents and has introduced application programming
interfaces (API) and Document Object Model (DOM).
Features:
 It has introduced new multimedia features which supports audio and video controls by using
<audio> and <video> tags.
 There are new graphics elements including vector graphics and tags.
 Enrich semantic content by including <header><footer>, <article>, <section> and <figure>
are added.
 Drag and Drop- The user can grab an object and drag it further dropping it on a new
location.
 Geo-location services- It helps to locate the geographical location of a client.
 Web storage facility which provides web application methods to store data on web browser.
 Uses SQL database to store data offline.
 Allows to draw various shapes like triangle, rectangle, circle, etc.
 Capable of handling incorrect syntax.
 Easy DOCTYPE declaration i.e. <!doctype html>
 Easy character encoding i.e. <meta charset=”UTF-8″>

4. 1. 5 CSS3

CSS stands for Cascading Style Sheets. CSS is a standard style sheet language used for describing
the presentation (i.e. the layout and formatting) of the web pages. Prior to CSS, nearly all of the
presentational attributes of HTML documents were contained within the HTML mark-up
(specifically inside the HTML tags); all the font colors, background styles, element alignments,
borders and sizes had to be explicitly described within the HTML.

As a result, development of the large websites became a long and expensive process, since the style
information were repeatedly added to every single page of the website.

To solve this problem CSS was introduced in 1996 by the World Wide Web Consortium (W3C),
which also maintains its standard. CSS was designed to enable the separation of presentation and
content. Now web designers can move the formatting information of the web pages to a separate
style sheet which results in considerably simpler HTML mark-up, and better maintainability.

CSS3 is the latest version of the CSS specification. CSS3 adds several new styling features and
improvements to enhance the web presentation capabilities.

Advantages of Using CSS

The biggest advantage of CSS is that it allows the separation of style and layout from the content of
the document. Here are some more advantages, why one should start using CSS?

 CSS Save Lots of Time — CSS gives lots of flexibility to set the style properties of an
element. You can write CSS once; and then the same code can be applied to the groups of
HTML elements, and can also be reused in multiple HTML pages.

 Easy Maintenance — CSS provides an easy means to update the formatting of the
documents, and to maintain the consistency across multiple documents. Because the
content of the entire set of web pages can be easily controlled using one or more style
sheets.

 Pages Load Faster — CSS enables multiple pages to share the formatting information,
which reduces complexity and repetition in the structural contents of the documents. It
significantly reduces the file transfer size, which results in a faster page loading.

 Superior Styles to HTML — CSS has much wider presentation capabilities than HTML
and provide much better control over the layout of your web pages. So you can give far
better look to your web pages in comparison to the HTML presentational elements and
attributes.

 Multiple Device Compatibility — CSS also allows web pages to be optimized for more
than one type of device or media. Using CSS the same HTML document can be presented
in different viewing styles for different rendering devices such as desktop, cell phones, etc.

4.1.6. JavaScript

JavaScript is a very powerful client-side scripting language. JavaScript is used mainly for

enhancing the interaction of a user with the webpage. In other words, you can make your
 webpage more lively and interactive, with the help of JavaScript. JavaScript is also being
used widely in game development and mobile application development.

Features

 Universal support

All popular modern Web browsers support JavaScript with built-in execution environments.

 Imperative and structured

JavaScript supports much of the structured programming syntax from C(e.g. if statements, while
loops, switch statement, do while loops etc.).One partial exception is scoping: JavaScript originally

had only function scoping with  var.

 Weakly typed

JavaScript is weakly typed, which means certain types are implicitly cast depending on the
operation used. JavaScript has received criticism for the way it implements these conversions as
well as the inconsistency between them

4.1.7 MSSQL

Microsoft SQL Server is a relational database management system developed by Microsoft. As a

database, it is a software product whose primary function is to store and retrieve data as requested
by other software applications, be it those on the same computer or those running on another
computer across a network (including the Internet). There are at least a dozen different editions of
Microsoft SQL Server aimed at different audiences and for workloads ranging from small single-
machine applications to large Internet-facing applications with many concurrent users. Its
primary query languages are T-SQL and ANSI SQL.

Features of MSSQL
  Always on availability groups -- This feature takes database mirroring to a whole new
level.
 Column store Indexes -- This a cool new feature that is completely unique to SQL Server.
They are special type of read-only index designed to be use with Data Warehouse queries.
Basically, data is grouped and stored in a flat, compressed column index, greatly reducing
I/O and memory utilization on large queries.
 User-Defined Server Roles -- DBAs have always had the ability to create custom database
role, but never server wide.
 Enhanced Auditing Features -- Audit is now available in all editions of SQL Server. New
filtering features give greater flexibility in choosing which events to write to the log.
 BI Semantic Model -- This is replacing the Analysis Services Unified Dimensional Model
(or cubes most people referred to them). It's a hybrid model that allows one data model will
support all BI experiences in SQL Server.
 Sequence Objects -- A sequence is just an object that is a counter -- a good example of it's
use would be to increment values in a table, based a trigger. SQL has always had similar
functionality with identity columns, but now this is a discrete object.
 Enhanced Power Shell Support -- Windows and SQL Server admins should definitely
start brushing up on their Power Shell scripting skills.
 Distributed Replay -- Distributed replay allows you to capture a workload on a production
server, and replay it on another machine. This way changes in underlying schemas, support
packs, or hardware changes can be tested under production conditions.
 Power View -- You may have heard of this under the name "Project Crescent" it is a fairly
powerful self-service BI toolkit that allows users to create mash ups of BI reports from all
over the Enterprise.
 
Relational Database System: Like almost all other database systems on the market, MSSQL is a
relational database system.

Client/Server Architecture: MSSQL is a client/server system. There is a database server

(MSSQL) and arbitrarily many clients (application programs), which communicate with the server;
that is, they query data, save changes, etc. The clients can run on the same computer as the server
or on another computer (communication via a local network or the Internet).
SQL compatibility: MSSQL supports as its database language -- as its name suggests – SQL
(Structured Query Language). SQL is a standardized language for querying and updating data and
for the administration of a database. There are several SQL dialects (about as many as there are
database systems). MSSQL adheres to the current SQL standard , although with significant
restrictions and a large number of extensions.

Fig.4.1.7 SQL server

 CHAPTER 5

SYSTEM ANALYSIS
 CHAPTER 5

SYSTEM ANALYSIS

5.1 EXISTING SYSTEM

Similar system exists in a non automated format .NGOs and Government/private charity services
runs this system. In the existing system the donor has to directly contact the trust for pickup and
delivery of the excess food. The trust then contacts a transporter who may or may not be available
at that time.

5.1.1 Disadvantages of existing system

1. Requires manual effort for registering each entry from the donor.
2. Donors has to manually manage contacts of trust and trust also has to manage details of
handlers, recipients etc.
3. Quality and quantity of the food may get compromised due to negligence or middlemen.
4. Real-time tracking of supply and demand is not available.
5. Inefficient supply chain and connectivity causes the wastage or delay in the processing of
food products.
6. Collection of data in manual way is a hard work and requires time to analyze it later on or to
sort the obtained data.

5.2 PROPOSED SYSTEM

This application will be a web application which can run on any web browser which meets
the minimum requirements .This system automates the processes which were manual in the
existing systems through this automation it also helps us in overcoming the problems that we face
in the conventional method. In this system Food Donor, Food receiver, Transporter, admin are the
main modules where Food Donor can be any organization/Person who wants to donate food, he can
create a new food donation request and Food receiver can be any charity firm seeking for food. A
new food donation request will be created on the portal and once the request is accepted, a
notification is sent to Transporter who is responsible for moving food from food donor to food
receiver.

5.2.1 Advantages of proposed system

1. Automated logging of the data helps to track and minimize food wastage.
2. Data of donors, receivers, trusts, NGOs, Transporters, inspectors etc are digitally stored and
available across the system.
3. Tracking of resources enables transparency and ensures the proper usage of system.
4. Digital ID for food products for different type ensures the food is safe by recording the shelf
life of food and this ID is used to assign the food's delivery location.
5. Saves time and money.
6. Avoids wastage of food.
7. Provides 24 x 7 support.
8. Fights against hunger, malnutrition, poverty and economic instability.
9. Builds a nation by feeding its needy citizens efficiently and boosts strength, status and Self
confidence of the same.
10. Promotes the Idea of giving to the society and accounts for sustainable development.
 CHAPTER 6
SYSTEM REQUIREMENTS
AND
SPECIFICATION
 CHAPTER 6

SYSTEM REQUIREMENT AND SPECIFICATION

6.1 INTRODUCTION

Software requirements specification (SRS) is a description of a software system to be

developed, laying out functional and non-functional requirements, and may include a set of use
cases that describe interactions the users will have with the software.

Software requirements specification establishes the basis for an agreement between

customers and contractors or suppliers (in market-driven projects, these roles may be played by the
marketing and development divisions) on what the software product is to do as well as what it is
not expected to do. Software requirements specification permits a rigorous assessment of
requirements before design can begin and reduces later redesign. It should also provide a realistic
basis for estimating product costs, risks, and schedules.

The software requirements specification document enlists enough and necessary requirements that
are required for the project development. To derive the requirements we need to have clear and
thorough understanding of the products to be developed or being developed. This is achieved and
refined with detailed and continuous communications with the project team and customer till the
completion of the software.

6.2 FUNCTIONAL REQUIREMENTS

 A functional requirement document defines the functionality of a system or

one of its subsystems. It also depends upon the type of software, expected
users and the type of system where the software is used.
 Functional user requirements may be high-level statements of what the system
should do but functional system requirements should also describe clearly
about the system services in detail.
  The main purpose of functional requirements within the requirement specification
Document is to define all the activities or operations that take place in the system.
 A function is nothing but inputs, its behaviour, and outputs. It can be a calculation, data
manipulation, business process, user interaction etc. These are derived through
interactions with the users of the system. Since the Requirements Specification is a
comprehensive document & contains a lot of data.

Functional requirements capture the intended behaviour of the system. This behaviour may be
expressed as services, tasks or functions the system is required to perform.

6.2.1 User module

• Registration

The user will enter the details like Name, Username, Password, Email, and Phone etc. to
store the data into the server, which will be used by the user to enter into application.

• Login

The user will specify his credentials like Username and Password to enter into the application
for using the application.

6.2.2 Admin module

 User Management

In this module, the registered users will be managed by the admin. The admin can view or
delete the registered users based on the requirement.

 Food Management

In this module, the registered user Donates Food will be managed by the admin. The admin can
view or delete.

6.3 Non-functional requirements

The Non-functional attributes of the project are as follows:

1. Security
 2. Usability
3. Maintainability
4. Extensibility

1. Security:

The application provides complete security for where the users of this application having
unique username and password to access this facility which provides complete security through
user authentication.

2. Usability:

The proposed system find extended application in all the sectors where teachers and users
interact together using computers linked to a network such as the Internet. Which allows a users to
attend a class from anywhere in the world and aims to provides a learning experience that is similar
to a real classroom.

3. Maintainability:

Since we are using the .net software to support our application no maintenance is very easy
and economical also. Through virtual class we can greatly reducing the travel, time, and expense of
on-site teaching/training programs.

4. Extensibility:

This application has various other features like Interaction between the admin, donor ,
receiver and the transporter , this will happen via e-mail, phone, forums etc.

6.4 SYSTEM REQUIREMENTS

Most software defines two sets of system requirements: minimum and recommended. With
increasing demand for higher processing power and resources in newer versions of software,
system requirements tend to increase over time. Industry analysts suggest that this trend plays a
bigger part in driving upgrades to existing computer systems than technological advancements. A
second meaning of the term of System requirements is a generalization of this first definition,
giving the requirements to be met in the design of a system or sub-system. Typically an
organization starts with a set of Business requirements and then derives the System requirements
from there.

6.4.1 Hardware Requirements

• Processor : Intel i3 2 .4GHz

• Hard Disk : 40GB

• Ram : 4 GB or above

6.4.2 Software Requirements

• Operating system : Windows 7 and above

• Front End : ASP.NET (HTML5, CSS3, JavaScript)

• Coding Language : C#.Net

• Database : MSSql Server 2014

• IDE : Visual Studio 2015

 CHAPTER 7

SYSTEM DESIGN
 CHAPTER 7
SYSTEM DESIGN
System design is the phase that bridges the gap between problem domain and the existing
system in a manageable way. This phase focuses on the solution domain, i.e. “how to implement?”

 It is the phase where the SRS document is converted into a format that can be implemented
and decides how the system will operate.

 In this phase, the complex activity of system development is divided into several smaller
sub-activities, which coordinate with each other to achieve the main objective of system
development.

7.1 Introduction

Three-tier architecture

Three-tier (layer) is a client-server architecture in which the user interface, business process
(business rules) and data storage and data access are developed and maintained as independent
modules or most often on separate platforms.

The Architecture of Application is based on three-tier architecture. The three logical tiers are

 Presentation tier - Web forms, Images.

 Middle tier – C#
 Data tier- MSSQL Database
The main reason for considering three-tier architecture for the Application is as follows:

Flexibility:

 Management of data is independent from the physical storage support,

  Maintenance of the business logic is easier,
 Migration to new graphical environments is faster.
 If there is a minor change in the business logic, we don’t have to install the entire system in
individual user’s PCs.

Reusability:

 Reusability of business logic is greater for the presentation layer. As this component is
developed and tested, we can use it in any other project and would be helpful for future use.

Security:

 More secured architecture since the client cannot access the database directly.

Fig.7.1 Three-tier Architecture

Presentation tier

The presentation tier for the application System is Web Forms with Pages. The presentation tier
takes care of the user interaction and the visual part of the website. The various Web forms used by
clients are listed below.
Middle Tier

The Middle Tier or Business Logic layer consists of Admin, Users pages that includes in an
application.

Data Tier

The Data Tier layer consists of database such as MSSQL which helps to store data. The data tier
mainly concentrated on manipulating the data using a database management system. Here we
implement the data tier using MS Access. Different varieties of data base are Oracle, SQL

7.2 System Architecture Diagram

Fig.7.2 System Architecture

7.3 Detailed Design

Detailed design starts after the system design phase is completed and the system design has
been certified through the review. The goal of this phase is to develop the internal logic of each of
the modules identified during system design.
In the system design, the focus is on identifying the modules, whereas during detailed design the
focus is on designing the logic for the modules. In other words in system design attention is on
what components are needed, while in detailed design how the components can be implemented in
the software is the issue.

The design activity is often divided into two separate phase system design and detailed design. In
the second level the internal design of the modules or how the specifications of the module can be
satisfied is decided. This design level is often called detailed design or logic design.

7.3.1 Data Flow Diagram

DFD graphically representing the functions, or processes, which capture, manipulate, store,
and distribute data between a system and its environment and between components of a system.
The visual representation makes it a good communication tool between User and System
designer. Structure of DFD allows starting from a broad overview and expands it to a hierarchy
of detailed diagrams. DFD has often been used due to the following reasons:
 Logical information flow of the system
 Determination of physical system construction requirements
 Simplicity of notation
 Establishment of manual and automated systems requirements

Basic Notations
Process: Any process that changes the data, producing an output. It might perform computations,
or sort data based on logic, or direct the data flow based on business rules. A short label is used to
describe the process, such as “Submit payment.”

Data store: files or repositories that hold information for later use, such as a database table or a
membership form. Each data store receives a simple label, such as “Orders.”

External entity: an outside system that sends or receives data, communicating with the system
being diagrammed. They are the sources and destinations of information entering or leaving the
system. They might be an outside organization or person, a computer system or a business system.
They are also known as terminators, sources and sinks or actors. They are typically drawn on the
edges of the diagram

Data flow: the route that data takes between the external entities, processes and data stores. It
portrays the interface between the other components and is shown with arrows, typically labelled
with a short data name, like “Billing details.
Data Flow Diagram

View Recievers
Food
Specification

Feed India

Get
Donate food
acknowledgement

Send
Acknowledgment View Donation

Fig.7.3.1 a) Level 0 DFD

 View
Reciever

Manage Reciever
Admin
Reciever data

Delete
Reciever

Login

View Donor

Manage
Donor
Donor data

Delete Donor

View
Donation

Manage
Donation
Donation
data

Delete
Donation

Fig.7.3.1 b) Admin Level 1 DFD

 Reciever

View
Doantion Data
Donation
Register

Reciever
Login Fetch Donor Donor Data
data

Send
Acknowledgement

Fig.7.3.1 c) Receiver Level 1 DFD

Donor

Food
Specification
Register

Donor data Login Donate food Donation Data

Get
Acknowledgement
View Reciever

Reciever Data

Fig.7.3.1 d) Donor Level 1 DFD

7.3.2 Use case diagram

Use case diagram is a graph of actors, a set of use cases enclosed by a system boundary,
communication associations between the actor and the use case. The use case diagram describes how a
system interacts with outside actors; each use case represents a piece of functionality that a system provides
to its users. A use case is known as an ellipse containing the name of the use case and an actor is shown as a
stick figure with the name of the actor below the figure.

The use cases are used during the analysis phase of a project to identify and partition system functionality.
They separate the system into actors and use case. Actors represent roles that are played by user of the
system. Those users can be humans, other computers, pieces of hardware, or even other software systems.

Use case diagrams

Feed India

Login

Manage donor

Manage Reciever

Admin Manage donation

Logout

Fig.7.3.2 a)Admin Use case diagram

 Feed India

Register

Login

View Donation

Receiver View Receiver

Send
Acknowledgement

Logout

Feed India

Register

Login

Food Specification

Donate food

Get
Donor
Acknowledgement

View Receiver

Logout

Fig.7.3.2 b) Receiver& Donor Use case diagrams

7.3.3 Sequence Diagram

A sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario. Sequence diagrams are sometimes
called event diagrams, event scenarios.

UML sequence diagrams are used to represent or model the flow of messages, events and
actions between the objects or components of a system. Time is represented in the vertical direction
showing the sequence of interactions of the header elements, which are displayed horizontally at
the top of the diagram Sequence Diagrams are used primarily to design, document and validate the
architecture, interfaces and logic of the system by describing the sequence of actions that need to be
performed to complete a task or scenario. UML sequence diagrams are useful design tools because
they provide a dynamic view of the system behaviour.

Admin: Server: Database:

Validate
Login
credentials

Credentials
Admin Homepage rendered Validated

View/Delete
Fetch info
Donors

Display/Remove Send Data

View/Delete
Receiver Fetch info

Display/Remove Send data

View/Delete
Fetch Info
donation

Display/Remove Send data

Logout

Logout

Fig.7.3.3 a) Admin Sequence Diagram

Donor: Server: Database:
Validate
Register
credentials

Registered Credentials
successfully Validated

Login validate

Login
successfully

Food
Store
Specification

Stored Send message

store donation
Donate food
details

stored succefully Send message

View Receiver Fetch info

Display Send data

Logout

Logout

Fig.7.3.3 b) Donor Sequence Diagram

Receiver: Server: Database:
Validate
Register
credentials

Registered Credentials
successfully Validated

Login validate

Login
successfully

View Donation Fetch data

Display Send Data

Search Donor Fetch

Display Send Data

Send Acknoledgment Store

Sent message
Send Message
displayed

Logout

Logout

Fig.7.3.3 c) Receiver Sequence Diagram

7.3.4 Activity Diagrams
Activity diagrams represent the business and operational workflows of a system. An
Activity diagram is a dynamic diagram that shows the activity and the event that causes the object
to be in the particular state. It is a simple and intuitive illustration of what happens in a workflow,
what activities can be done in parallel, and whether there are alternative paths through the
workflow.

Basic Notations

Initial Activity

*This shows the starting point or first activity of the flow. It is denoted by a solid circle.

Final Activity

*The end of the Activity diagram is shown by a bull's eye symbol, also called as a final activity.

Activity

*Represented by a rectangle with rounded (almost oval) edges

Decisions

*A logic where a decision is to be made is depicted by a diamond.

Workflow

Workflow is depicted with an arrow. It shows the direction of the workflow in the activity diagram.
 Admin login to
Application

False
Valid

True

Manage Manage Manage

Donors Receivers Donation

Delete Delete
View Donors Delete Donors View Receivers View Donation
Receivers Donation

Fig.7.3.4 a) Admin Activity Diagram

 Register

Donor login to
Application

False
Valid

True

Food
Donate food View Donation
Specification

Get
View Receiver
Acknoledgment

Fig.7.3.4 b) Donor Activity Diagram

 Register

Receiver login to
Application

False

Valid

True

Send
View Doantion Fetch Donor
Acknoledgment

Fig.7.3.4 c) Receiver Activity Diagram

7.3.5 Entity-Relationship Diagram

Entity Relationship Diagram depicts the various relationships among entities, considering
each objective as entity. Entity relationships are described by their dependence on each other, as
well as the extent of the relationship between the data stores. It depicts the relationship between
data objects. The ER diagram is a notation that is used to conduct the data modelling activity.

The Symbols used in this E-R Diagram are-

SI.NO NAME SYMBOL DESCRIPTION

1 Entity Entity is a “thing” in the real world with an

independent existence. It is an elementary basic
building block of storing information about
business process.

2 Relationships A relationship is a named connection or

association between entities or used to relate to
two or more entities with some common attributes
or meaningful interaction between the objects.

3 Attributes Attributes are the properties of the entities and the

relationships are the description of the entity.
Attributes are elementary pieces of information
attached to an entity.

4 Key attributes An entity type usually has an attribute whose

values are distinct for each individual entity in the
collection. Such an attribute is called key attribute.

Table 7.3.5: Symbols used in ER-diagram

 Admin_name
pass_word
Admin_id

1
1
Admin Manage
Manages

1
password

Donor_name Donor 1 password

*
Manage
Donor_id Receiver_name Receiver

Make
*
Receiver_id

Event_id

* *

Donation View
*

Discription
userName
Get Amount

Send

Acknowledgement

ReciverName
Ack_id
DonorName

Fig.7.3.5 Entity Relationship Diagram

 CHAPTER 8

SYSTEM IMPLEMENTATION
 Chapter 8

System Implementation

8.1 Introduction

The term implementation has different meanings ranging from the conversation of a basic
application to a complete replacement of a computer system. The procedures however, are virtually
the same. Implementation includes all those activities that take place to convert from old systems to
new the new system may be totally new replacing and existing manually or automated system or it
may be major modification to an existing system

8.2 Pseudo Codes

Generalised algorithms can be written as pseudo codes which are easy to understand and
explain.

8.2.1 Pseudo Codes for Admin

Step 1: The admin login by entering admin name and password

Step 2: Admin view the list of users verify them and give approval

Step 3: Admin give the users register and also delete based on the requirement

Step 4: Admin view the list of Food added by the user and manages it

Step 5: Logout

8.2.2 Pseudo codes for Users

Step 1: The user get register by entering the credentials

Step 2: Login with the user name and password

Step 3: Input the food list/request list

Step 4: View the history

Step 6: Logout
8.3 Code

Here is a sample code from Page Donations!

8.3.1 CODE TO DESIGN FRONT END

<- HTML CODES ->

<head runat="server">

<meta charset="utf-8"/>

<meta http-equiv="x-ua-compatible" content="ie=edge"/>

<title>MANAGE DONATIONS</title>

<meta name="description" content=""/>

<meta name="viewport" content="width=device-width,

initial-scale=1"/>

<!-- <link rel="manifest" href="site.webmanifest"> -->

<link rel="shortcut icon" type="image/x-icon"

href="img/favicon.png"/>

<!-- Place favicon.ico in the root directory -->

<!-- CSS CODES -->

<link rel="stylesheet" href="css/bootstrap.min.css"/>

<link rel="stylesheet" href="css/owl.carousel.min.css"/>

<link rel="stylesheet" href="css/magnific-popup.css"/>

<link rel="stylesheet" href="css/font-awesome.min.css"/>

<link rel="stylesheet" href="css/themify-icons.css"/>

 <link rel="stylesheet" href="css/nice-select.css"/>

<link rel="stylesheet" href="css/flaticon.css"/>

<link rel="stylesheet" href="css/gijgo.css"/>

<link rel="stylesheet" href="css/animate.css"/>

<link rel="stylesheet" href="css/slicknav.css"/>

<link rel="stylesheet" href="css/style.css"/>

<!-- <link rel="stylesheet" href="css/responsive.css"> -->

</head>

<body>

<!--[if lte IE 9]>

<p class="browserupgrade">You are using an

<strong>outdated</strong> browser. Please <a
href="https://browsehappy.com/">upgrade your browser</a> to
improve your experience and security.</p>

<![endif]-->

<!-- header-start -->

<header>

<div class="header-area ">

<div id="sticky-header" class="main-header-area">

<div class="container">

<div class="row align-items-center">

<div class="col-xl-3 col-lg-3">

<div class="logo-img">
 <a>

<img src="images/v3.gif" alt=""

width="289px" height="100px;"/>

</a>

</div>

</div>

<div class="col-xl-9 col-lg-9">

<div class="menu_wrap d-none d-lg-block">

<div class="menu_wrap_inner d-flex

8.3.2 BACK-END CODE

protected void GridView1_RowCommand(object sender, GridViewCommandEventArgs e)

{
if (e.CommandName == "Delete")
{
int x = Convert.ToInt32(e.CommandArgument);
GridViewRow row = GridView1.Rows[x];
SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["ConStr"]);
try
{
con.Open();
string query = "Update Itemslist set Stat='Disposed' where Did='" + row.Cells[0].Text +
"'";
SqlCommand cmd = new SqlCommand(query, con);
cmd.ExecuteNonQuery();

}
catch
{
}
finally
 {
con.Close();
Response.Redirect("donations.aspx");
}
}

if (e.CommandName == "View")
{
int x = Convert.ToInt32(e.CommandArgument);
GridViewRow row = GridView1.Rows[x];
Response.Redirect("managefood.aspx?Did=" + row.Cells[0].Text);
}
}

8.3.1 LINKING DATABASE

public partial class donations : System.Web.UI.Page
{

SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["Constr"]);

public void BindData()
{
con.Open();
//string uname = Session["UserName"].ToString();
string query = "SELECT * FROM Donation where Did in (select distinct Did from Itemslist
where Stat='Pending')";
SqlCommand cmd = new SqlCommand(query, con);
SqlDataAdapter sda = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
sda.Fill(dt);
GridView1.DataSource = dt;
GridView1.DataBind();
con.Close();

}
 CHAPTER 9
SYSTEM TESTING
 CHAPTER 9
SYSTEM TESTING
9.1 Introduction
Testing is the major process involved in software quality assurance (QA). It is iterative process.
Here test data is prepared and is used to test the modules individually. System testing makes sure
that all components of the system function properly as a unit by actually forcing the system to fail.
• The test cases should be planned before testing begins. Then as the testing progresses,
testing shifts focus in an attempt to find errors in integrated clusters of modules and in the
entire system. The philosophy behind testing is to find errors. Actually testing is the estate
of implementation that is aimed at ensuring that the system works actually and efficiently
before implementation.
• Testing is done for each module. After testing all the modules, the modules are integrated
and testing of the final system is done with the test data, specially designed to show that the
system will operate successfully in all its aspects conditions. The procedure level testing is
made first. By giving improper inputs, the errors occurred are noted and eliminated. Thus
the system testing is a confirmation that all is correct and an opportunity to show the user
that the system works.
• The final step involves Validation testing, which determines whether the software function
as the user expected. The end-user rather than the system developer conduct this test most
software developers as a process called “Alpha and Beta test” to uncover that only the end
user seems able to find.
• This is the final step in system life cycle. Here we implement the tested error-free system
into real-life environment and make necessary changes, which runs in an online fashion.
Here system maintenance is done every months or year based on company policies, and is
checked for errors like runtime errors, long run errors and other maintenances like table
verification and reports.
• During the requirement analysis and design, the output is a document that is usually textual
and non-executable. After the coding phase, computer programs are available that can be
executed for testing purpose. This implies that testing not only has to uncover errors
introduced during coding, but also errors introduced during the previous phases.
WHITE BOX TESTING

White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is purpose. It
is used to test areas that cannot be reached from a black box level.

BLACK BOX TESTING

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box .you cannot “see” into it. The test provides inputs and
responds to outputs without considering how the software works.

Fig. 9.1 The Testing process

9.2 Types of Testing

The various types of testing done on the system are:

 Unit Testing
 Integration Testing
 Regression Testing
 Security Testing
 Functional Testing
 Performance Testing
 System Testing

9.2.1 Unit Testing

Unit testing verification efforts on the smallest unit of software design, module. This is
known as “Module Testing”. The modules are tested separately. This testing is carried out during
programming stage itself. In these testing steps, each module is found to be working satisfactorily
as regard to the expected output from the module.

9.2.2 Integration Testing

Integration testing is a systematic technique for constructing tests to uncover error

associated within the interface. In the project, all the modules are combined and then the entire
programme is tested as a whole. In the integration-testing step, all the error uncovered is corrected
for the next testing steps.

9.2.3 Regression Testing

Regression testing is defined as a type of software testing to confirm that a recent program

or code change has not adversely affected existing features. Regression Testing is nothing but a full
or partial selection of already executed test cases which are re-executed to ensure existing
functionalities work fine.

9.2.4 Security Testing

Security Testing is a type of Software Testing that uncovers vulnerabilities of the system

and determines that the data and resources of the system are protected from possible intruders. It
ensures that the software system and application are free from any threats or risks that can cause a
loss.

9.2.5 Functional Testing

Functional testing is a type of software testing whereby the system is tested against

the functional requirements/specifications. Functions (or features) are tested by feeding them input
and examining the output. Functional testing ensures that the requirements are properly satisfied by
the application.

9.2.6 Performance Testing

Performance testing is the process of determining the speed, responsiveness and stability of
a computer, network, software program or device under a workload. Performance testing can
involve quantitative tests done in a lab, or occur in the production environment in limited scenario

9.2.7 Acceptance testing

When the system has no measure problem with its accuracy, the system passes through a final
acceptance test. This test confirms that the system needs the original goal, Objective and
requirements established during analysis. If the system fulfils all the requirements, it is finally
acceptable and ready for operation.

9.2.8 System Testing

Once individual module testing completed, modules are assembled to perform as a system. Then
the top down testing, which begins from upper level to lower level module testing, has to be done
to check whether the entire system is performing satisfactorily.
After unit and integration testing are over then the system as whole is tested. There are two general
strategies for system testing.
They are:
 Code Testing
 Specification Testing
9.2.8 a) Code Testing

This strategy examines the logic of the program. A path is a specific combination of conditions
handled by the program. Using this strategy, every path through the program is tested.

9.2.8 b) Specification Testing

This strategy examines the specifications stating what the program should do and how it should
perform under various conditions. The test cases are developed for each condition of developed
system and processed. It is found that the system developed perform according to its specified
requirements. The system is used experimentally to ensure that the software will run according to
tits specification and in the way user expect.
Specification Testing is done successfully by entering various types of end data. It is checked for
both valid and invalid data and found System is working properly as per requirement

9.2.9 Test Plan

A software project test plan is a document that describes the objectives, scope approach and
focus of a software testing effort. This process of preparing a test plan is a useful way to think
through the efforts needed to validate the acceptability of a software product. The completed
document will help the people outside the test group understand ‘Why and How’ of production
validation. Different test plans are used at different levels of testing.

9.2.9.1 Test Plans used in Unit Testing

Each module is tested for correctness whether it is meeting all the expected results. Condition loops
in the code are properly terminated so that they don’t enter into an infinite loop. Proper validations
are done so as to avoid any errors related to data entry from user.
9.2.10 Test Cases

Test Case
Expected result
Number Testing Scenario Result

Registration Testing

TC – 01 Clicking submit without entering details Alert "Please fill all details" Pass

TC – 02 Clicking submit without entering Username Alert "Please fill Username" Pass

TC – 03 Clicking submit without entering password Alert "Please fill Password" Pass

TC – 04 Clicking submit without entering email id Alert "Please fill email id" Pass

Clicking submit without entering phone Alert "Please fill contact

TC – 05 number number" Pass

Clicking submit entering confirm password

Alert "Password and Confirm
data which is not matching with password
Password do not match"
TC – 06 data Pass

Login Testing

Clicking submit without entering login Alert "Please enter the

TC – 07 details username and password" Pass

Alert "Please enter the

TC – 08 Clicking submit without entering password password" Pass

Alert "Please enter the

TC – 09 Clicking submit without entering Username Username" Pass

Alert "Invalid User"

TC – 10 Clicking submit entering wrong Username Pass

TC – 11 Clicking submit entering wrong password Alert "Invalid User" Pass

Clicking submit entering wrong Username

Alert "Invalid User"
TC – 12 and password Pass
Table.9.2.10 test cases
 CHAPTER 10

SYTEM SCREENSHOTS
HOME PAGE : HEADER

HOME PAGE : FOOTER

CONTACT US PAGE
ABOUT US PAGE
 DONATION PAGE

ADMIN- MANAGE DONATIONS PAGE

 CHAPTER 11

CONCLUSION AND FUTURE

ENHANCEMENT

CHAPTER 11

CONCLUSION AND FUTURE ENHANCEMENT

 The development of this product surely prompts many new areas of investigation. This
product has wide scope of implementation by making it live. Moreover this product creates many
benefits for the organisations and the community. By taking it online it will help many people
throughout the city by donating food daily.

Hundreds of thousands of tons of food are either lost or wasted while millions of people
suffer from malnutrition. A plausible initiative is the food donation portal in which large retail
chains and potentially other organizations can donate food. This food is collected and delivered by
Third Party vendor to NGO in need. Food donation portal will help thousands of people that suffer
from starvation and also consume food that are wasted with no reason.. As consequence, research
and actions are needed to improve the efficiency of food donation portal.

The application development is and will be purely intend on non profit works, Government,
NGOs , Organisations, places of interest and people will surely benefit from the system and the
receiver will get good food and a bright future where there is no place for hunger and malnutrition.

“Minimum wastage: maximum consumption of food”

That’s the motto and will be carried out in our further enhancements.

11.1 FUTURE ENHANCEMENTS

In future, we can enhance the developed module of our project in such a way that it
improves the efficiency of the system. Addition of new features like volunteers based transport,
adding new listings of storage places , more efficient and robust application based on the change in
trends and technology.
 CHAPTER 12

REFERENCES

&

BIBLIOGRAPHY

CHAPTER 12

REFERENCES AND BIBLIOGRAPHY

12.1 REFERENCES
 1.W3 schools - https://www.w3schools.com/

2. Tutorials Point - https://www.Tutorialspoint.com/

3. Stack Overflow- https://www.stackoverflow.com/

4. Github- https://github.com/

5. Visual Studios Guide – https://code.visualstudios.com/

6. HTML , CSS , JS guide at - https://html-css-js.com/css/editor/

7. https://softwaretestinghelp.com/

8. C# guide at – https://codecademy.com

9. Templates courtesy – https://Browsehappy.com

10. Images courtesy- https://Pexels.com , https://Unsplash.com , https://Pixlr.com

12.2 BIBLIOGRAPHY

I. Komal Raut, Nimesh Shah, Akash Thorat, “ Food donation portal” [1]
http://ijarcet.org/wpcontent/uploads/IJARCET-VOL-5-ISSUE-4-906-908.pdf
II. Dhruvi Shah, Adnan Ansari, Ruchi Sharma,“ Helping Hands” [2]
http://ijsrd.com/Article.php?manuscript=IJSRDV4I110485
III. Hitesh Raut, Swapnil Rajput, Danjhan Nalavade, “Smartphone based food supply
chain for Aurangabad city using GIS location based and google web services”
https://ieeexplore.ieee.org/document/7580874/metrics
IV. Issac Nuamah, Lauren Davis, Steven Jiang, “ Predicting donations of forecasting
simulation model” [3] https://dl.acm.org/citation.cfm?id=2888832

V. Aaron Ciaght, “Beyond food sharing: Supporting food wastage reduction “[4]
http://esatjournals.net/ijret/2016v05/i04/IJRET20160504058.pdf
VI. Amir Saxena. Khushi Verma, Aadit Patil, “ Development of a food supply chain by
PHP” https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2610113/
VII. https://www.mecknc.gov/LUESA/SolidWaste/BusinessRecycling/Documents/WO
W_FoodWasteBook_v2.pdf
VIII. http://www.eesc.europa.eu/en/agenda/our-events/events/food-donation-fighting-
food-poverty-and-addressingfood-waste#downloads.