WASTE FOOD MANAGEMENT SYSTEM

INTRODUCTION OF REDUCING WASTAGE MANAGEMENT SYSTEM

Are you looking for Reducing wastage management system for your final year project? We are here to help you. You can contact us

Everyone enjoys the functions with a lot of food and other products and most of them left waste or unused.We all waste food for various reasons. Typically it’s as a result of there has been an amendment of plans and it’s out of our management, however, most of the time we tend to waste identical varieties of food for identical a pair of main reasons:

we’ve got bought or read an excessive amount of, or we’ve got forgotten to use it on time.Regardless of the rationale why you throw out food, you got it and currently, it’s cost accounting you to throw it out.

So, after you square measure throwing out food, or recording the food you’ve got wasted, cash A note the explanations for your scraps and see if there square measure tiny changes that you just will build to cut back this waste and prevent plenty of dollars.

To solve this problem we come up with a system which can take request from the users who want get settle with the waste food ,they can request to donate or sell at cost to our systems managers who comes to them at given time and pick the order and further park that food to needy place where most people are without food according to need status .

Hence our system takes feedbacks and gives it best to settle the need and cleaning the place and more or less doing humanity.

MODULES OF REDUCING WASTAGE MANAGEMENT SYSTEM

The system is made of the combination of modules which work with collaboration with each other and make it beneficial to accomplish the main aim of the system.

REQUEST MAKING :

This is the interface first provided to the users they can put a request to give their waste food to the needy people who don’t have proper food available due to many reasons.

Users enjoy the function at the places and they left with food which they make a request through this interface to fill the details of the area where they are and details of the food remain.

As they confirm some manager will get assigned to them they come to them and take that food to their vehicles and go to give to the needy people.

MANAGE THE DELIVERY:

This interface in for managers, they manage their vehicles to the places and as they get the request in their interface they take their vehicle details and other details punched get to there to pick the food, Then they check the severity from the other interface and pick the neediest one, and delivers to them.

THE SEVERITY OF THE NEED AREA:

The severity of the need is taken care of this system there are more than one places of need are registered for the food, here they have to check where the need is most and delivers the food right there.It can less, more, much severity of the need.

REGISTRATION:

Users information have to be compelled to be registered within the system thus on establish every of them unambiguously and do the required group action as simple potential .like on the name of the bill are issued.

on the far side, this plenty of things require measure there wherever we will reference him. Without registration, there are few options and pages one user can see which are landing on the home page and taking the features read but he won’t be allowed to use those. For use, he will have to register.

One person needs to put his all the details properly and precisely as it will be helpful in identifying them and believing that he is the real person who has booked for the same. It also includes driver license for them who is driving and parameter too.

LOGIN:

After registration one will log within the system because the operator of the system either on the behalf of user. when this he has the opposite helpful interfaces accessible for any actions.

Here either bride or groom both have to log in with their unique identity and passwords. After this, they will be directed to the main user interface from where they have further options.

FORGOT PASSWORD:

This is quite often that people tend to forget the password they keep for the login. So this could be very tedious and hectic to recover the password manually in case if one needs to login in the emergency.

So to overcome this problem we have this module named ass forgot the password and using this module user can recover their password in seconds. So here we need to only put our registered email Id and hit the enter.

than one confirmation email will go to the email where he has the option to reset the password. In seconds one can use this module and get rid of forgetting password problem.

ADMIN:

Admin has the official powers to control the flow of the data from one part of the system to the other. He has the power to manipulate the access of the users to the data.

The main purpose of this account is to make the user data relevant and then giving the inputs to the other interface module and make it work optimistically and get the timetable according to the wish we want to create for a particular type of inputs.

Hence all the data will be reflected with clean and well data in the interfaces.

SYSTEM REQUIREMENT OF REDUCING WASTAGE MANAGEMENT SYSTEM

Now, this method is intended in such the way that it takes fewer resources to figure out work properly. it’s its own type of minimum needs that we’d like to require care of :

The system wants a minimum of two GB of ram to run all the options sleek and unforeseen.

It wants a minimum 1.3 gigahertz processor to run sleek as else which will produce issues.

The system must be operated by some approved person as wrong hands will build it happy-go-lucky.

Rest is all up to the user’s usage can take care of hardware

For security opposing anti-virus is suggested.

The system is made properly and all the testing is done as per the requirements. So, the rest of the things depend on the user and no one can harm the data or the software if the proper care is done.

All the attributes are working perfectly and if any error is found then it can be removed easily.

SYSTEM DESIGN OF REDUCING WASTAGE MANAGEMENT SYSTEM

ENTITY WASTE FOOD:

PRIMARY KEYWASTE FOOD_ID:

This is system generated and unique, which can be referenced in any other entity.

FOOD NAME:

The name of the food is fed here.

QUANTITY:

The quantity that how the food is.

HYGIENE LEVEL:

The level of cleanliness and untouched ness of the food.

COOKED TIME:

When the food was cooked.

EXPIRY TIME EXPECTED:

when it will become waste.

TYPE:

Is it a beverage or proper dinner or any other type given here.

ENTITY FUNCTIONS:

PRIMARY KEY FUNCTIONS_ID:

This is system generated and unique, which can be referenced in any other entity

NAME:

The name of the function is fed here.

ADDRESS:

The address of the function where it is happening.

WASTE_FOOD_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

USER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

FEED AREA_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

ENTITY MANAGER

PRIMARY KEY MANAGER_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

The name is taken from the user and fed into this it is properly validated so that no mistake happens.

QUALIFICATION:

Qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

NUMBER:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

EMAIL:

Email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

The type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

ENTITY VEHICLE:

PRIMARY KEYVEHICLE_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

The name of the vehicle mentioned is given here.

NUMBER:

The number plate given over there will be given there.

SIZE:

The size of the vehicle as to load the material amount.

COLOR:

The colour of the vehicle.

BRAND:

Brand of the vehicle to which it belongs

MODEL NO.

The model no of the vehicle.

FOREIGN KEY MANAGER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

ENTITY REQUEST:

PRIMARY KEYREQUEST_ID:

This is system generated and unique, which can be referenced in any other entity.

FOREIGN KEY USER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

FOREIGN KEY MANGER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

FOREIGN KEY VEHICLE_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

FOREIGN KEY FUNCTION_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

TIME OF ARRIVAL:

The time at which they want the arrival.

TYPE:

The type of request they make depends on the severity of the request.

ENTITY FEED AREA:

PRIMARY KEY FEED AREA_ID:

This is system generated and unique, which can be referenced in any other entity.

NAME:

Area name is given here.

ADDRESS:

The address of the area.

NO OF PEOPLE:

The no of people for which the food will be required

CATEGORY OF PEOPLE:

The age group that is is they are kids or adults or old

NEED STATUS:

The need of the area according to the feed they will get priority to get the food as the demand meets.

FOREIGN KEY USER_ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number.

ENTITYUSER:-

User data have to be saved in this entity and all fields are required for this purpose which taken from the user .proper validation is checked and the attributes are as follows:

PRIMARY KEYUSER_ID:

This is system generated and unique, which can be referenced in any other entity.

USERNAME:

Username is taken from the user and fed into this it is properly validated so that no mistake happens.

QUALIFICATION:

Qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

NUMBER:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

EMAIL:

Email is taken to make member aware of new offers new events and for future reference, it is also relevant.

TYPE:

ADDRESS:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

ENTITY ADMIN:

PRIMARY KEY ADMIN:

This is the main supervisor of all task happening in the system for long. It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities. It has all the power to make changes in the field of other tables. I grant the privileges to other users of the system that what kind of operations they can perform.

LOGS:

The logs are saved here to analyze the system accordingly. The changes occur. For necessary changes.

PASSWORD:

A Strong password is recommended for this account as no one wants to get hacked and lose the sophisticated data.

DESCRIPTION:

Any important info. Regarding this account is attributed in this.

CASE DIAGRAM OF REDUCING WASTAGE MANAGEMENT SYSTEM

Here in this system, we have mainly three actors the first one will put a request to take the waste food or we can say extra food they left within the function they were enjoying. He fills up the details of the food.

The manager will be assigned to pick the order. He takes the vehicle to the place of function and loads the vehicle and take it to the area where the need of the food is much on the base of severity. he leaves the food there.

And completes the system procedure. admin manages the managers and analyzes the system.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF REDUCING WASTAGE MANAGEMENT SYSTEM

FUNCTIONAL REQUIREMENTS OF REDUCING WASTAGE MANAGEMENT SYSTEM:-

The functional requirements are those requirements which are necessary to the eye of the user and the client. Here we try to make the module possible to accomplish the need of the desired function.

few of its functional requirements are as follows-

NON-FUNCTIONAL REQUIREMENTS OF REDUCING WASTAGE MANAGEMENT SYSTEM:-

These requirements of reducing wastage management system need unit among the style of “system shall be “, the associated overall property of the system as a full or of a particular aspect and not a particular operation.

The system’s overall properties remarkably mark the excellence between whether or not the event project has succeeded or unsuccessful.

NON-FUNCTIONAL OF REDUCING WASTAGE MANAGEMENT SYSTEM NEEDS –

unit of measurement usually divided into 2 main categories:

Execution qualities, like security and quality, that unit evident at the runtime.

Evolution qualities, like liabilities, maintainability, flexibility and quantitative, that unit embodied among the static structure of the code.

Non-functional of the reducing wastage management system needs place restrictions on the merchandise being developed, the event technique, and specify external constraints that the merchandise has to be compelled to meet

Our project qualifies all the factors of helpful and non-helpful consequently and the system is up to mark performance device.Here we’d prefer to need the care of few lots of things before heading towards the system.

The many sensible intuitive interfaces are usually created. that ultimately build interface easy to use for a lengthy time. in distinction to ancient vogue wherever the goal is to create the difficulty or application physically enticing, the goal of interface vogue is to create the user’s interaction expertise as simple and intuitive as double – what’s typically mentioned as user-centred vogue.

where smart graphic/industrial vogue is daring and eye-catching, smart interface vogue is sometimes delicate and invisible.

KEEP THINGS SIMPLE AND CONSISTENT:-

Simple and Harmonic means that making u i is extraordinarily intuitive and needs to followed

OBSERVE THE USE OF TYPOGRAPHY:-

The typography is taken care really strictly as the wish of the system.

USE COLOUR AND DISTINCTION PROPERLY:-

Color band of skin and dark is sweet means that stress and done well throughout this method

CONSIDER FEEDBACK MESSAGES:-

feedback sort may well be an excellent means that taking feedback of forms and rising the system.

SIMPLIFIED FORMS:-

The form is made simple to fill with a clean program.