Professional Documents
Culture Documents
Food Wateage Controll App Chapter 1
Food Wateage Controll App Chapter 1
Introduction
Introduction
Motivation.
Objectives.
Problem Statement.
Expected Output.
Motivation
In Pakistan there are some charity organization who are doing volunteering work to
collect wasted food from restaurant and wedding ceremony. Then they distribute them
to hunger people. But they work manually. So this is not much effective way and a
few of wasted food can be served by this process. A digital platform will be helpful
for them to collect more wasted food. We have built an android based mobile
application. It is very easy to establish link between restaurants or individual users
and charity organization through mobile application. In Pakistan, the total number of
Mobile Phone subscriptions has reached 147 million at the end of January 2018 [1].
Most of them are smart phone and runs on android platform. Communication between
restaurants and charity organizations will be very easy through mobile application and
also authorization will be confirmed. So we have chosen android platform to develop
our project and we think our application will be helpful to reduce the wastage of food
though donation.
Objectives
Expected Output
Our application have some special feature which make our application better
than other existing project and solve the problems. Some special features of our
application are:
Product Features:
During different stages of this project we had to face a few challenges. We were
able to successfully overcome those challenges. The challenges we faced were,
We have faced challenge when we want to create a real time database. We have
overcome this challenge by using Google firebase.
Designing and implementing a user friendly and interactive user interface using
XML was also challenging for us.
We also faced challenge to make the project beneficiary for the restaurant. If
the application is not beneficiary for them, they will not be interested to use it.
We have add ‘goodwill’ point system to solve this problem.
Project Scope
Agile methodology
Figure 2:Agile methodology
Major Milestone
Requirement collection
Analysis
After gathering the requirement, we will perform analysis and we will write our
requirements in a specific format.
Designing
Coding
Now it’s time to actually develop what we have suggested before. Our
programmers will convert the class design and domain into an operational website
In this phase, we are going to implement all requirements to development process
process.
Testing
Testing is the fourth step of product creation. It is the most important part of
creating any product. Firstly, we will perform unit testing. In this testing, we will
check individual components like our sub modules is properly working or not. And
after that, we will test the whole website along with its all functionality. Once all
the test cases are passed, our website will be live for assisting users.
After completion of testing phase. Now, it is time to deploy the product in its
working environment. In this phase, the user will check the activity of the product
whether it is giving desired results or not. If there are any flaws then these flaws
will be reported and will be debugged later on.
Maintenance
This phase will come after the deployment phase. After deployment if there are
errors or bugs, then we can maintain these bugs and errors in this phase. This is
the longest phase. If based on the future needs, there exists any additional
requirements then we can make changes in the existing product and implement the
new features.
In this project we use project management method the Critical Path Method (CPM)
for managing the project activities by the complexity of the process.by using CPM we
present the graphical view of the project through which we predict the time required
to complete the project and make decision which activities are critical to maintaining
the schedule and which are not. Specify the individual activities. Determine the
sequence of those activities.
Activity Chart
A Requirement A 20
collection
B Analysis and B 40
design
C Development C 70
D Testing A,B,C 30
E Deployment D 20
F Maintenance E
Network Diagram
Figure 3:Network Diagram
A->b->c->d->->e->f
Gantt chart
4) System failure.
Preventing Technique