STREET FOOD DELIVERY MANAGEMENT SYSTEM

 

INTRODUCTION OF ONLINE STREET FOOD DELIVERY MANAGEMENT SYSTEM

Are you looking for an Online street food delivery management system for your final year project? We are here to help you. You can contact us

Food is an important part of life or precisely the tasty food. now when we compare the food available in the hotels and food items that are available around the streets we can not deny that street foods are best in taste.

Everyone like to have these as there is taste and in the end quantity plus quality. But if one wants to eat that food at their home they need to go there and have that, which is a bit of problem for persons who are buy in some tasks at their places.

So we decided to come up with some of the kinda system which can make it easy to order the street food easily from the particular stall. For this we need the shops to be registered on the system then the whole item list that stall is feed in the system which is made available to all the people or users of the system.

Now users come to the system online and search their desired through different filter given to him according to the shop and taste of food he wants. He can select the food and give orders according to the quantity.

Here we have the option of the delivery boy which the vendors work in collaboration the orders are passed to him with proper order detail he delivers the order at a time then make it clear. The user gets the orders and enjoys it at their places no need to go anywhere.

Hence they also can appreciate the order through feedbacks.

MODULES OF ONLINE STREET FOOD DELIVERY 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.

STREET SHOP:

All shops which are available on the roadsides, if they desired they can be enrolled in the system.

While enrolling them we take care of few attributes related to that shop few of them are the name of the shop, area, famous for, and other contact details like things this is punched in the system through this interface by Vendor of the shops.

Here one can upload the menu items for the users to look at and few other details about the product.

VENDOR:

The detail of the vendor who is the owner of the shop is saved into the system through this interface he registers himself in this system.

He needs few of the details like name, address, the shops in, contact detail and few other detail then they can make their shop live in the interface.

DELIVERY BOY:

This interface is for the person who is responsible for the delivery of the food item to the place of users. They also register them self with He needs few of the details like name, address, the shops in, contact detail and few other detail.

He works in collaboration with the vendors. And make this system feasible.

ORDERS:

Orders are done through this interface and users can see the products in this interface and select from these . they have many filters to select a particular item they need.

There they will see the products price and timing of orders and address where they need the orders according to their wish.

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 the particular type of inputs.

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

SYSTEM REQUIREMENTS OF ONLINE STREET FOOD DELIVERY 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 ONLINE STREET FOOD DELIVERY MANAGEMENT SYSTEM

ENTITY ITEM:

PRIMARY KEY ITEM_ID:

This is the unique key generated by the system to distinctly identify, find, and track this anywhere in the system.

NAME:

Name of the item is given in this field.

CATEGORY:

To which category the food belongs that is continental, fast food, or any other category is given here.

PRICE:

The price per unit.

QUANTITY:

A number of items I . e no of items as of price is given here.

AVAILABILITY:

Sometimes the items are not available so that these will be seen by the users but the item may not be prepared by them so to overcome this problem we give availability attribute to the item.

FOREIGN KEY STREET SHOP ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. It is used to reference that table to any other table or any interface to show the data of it and support other entities.

ENTITY STREET SHOP:

PRIMARY KEY STREET SHOP _ID:

This is the unique key generated by the system to distinctly identify, find, and track this anywhere in the system.

NAME:

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

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 food they provide is given here

SIZE:

How much big the shop is given herein area wise in meter square.

ENTITY VENDOR:

The vendors are registered in this entity.

PRIMARY KEY VENDOR_ID:

This is the unique key generated by the system to distinctly identify, find, and track this anywhere in the system.

FOREIGN KEY STREET SHOP _ID:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. It is used to reference that table to any other table or any interface to show the data of it and support other entities.

AGE:

The age till the date is given here.

GENDER:

To which gender they belong.

NUMBER:

The contact number of the vendor to ask any query.

ENTITY ORDER:

The order details will go to this entity.

PRIMARY KEY ORDER_ID:

This is the unique key generated by the system to distinctly identify, find, and track this anywhere in the system.

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. It is used to reference that table to any other table or any interface to show the data of it and support other entities.

FOREIGN KEY STREET SHOP ID:

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

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

FOREIGN KEY VENDOR_ID:

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

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

NO. OF ITEMS:

The number of items one user orders.

TOTAL WEIGHT :

The total weight of the item is given here.

COST:

The cost of the items is calculated over here.

ADDRESS:

Where the item needs to be delivered is given here.

TIME OF DELIVERY:

At what time the order needs to be delivered.

ENTITY DELIVERY BOY:

PRIMARY KEY DELIVERY BOY:

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

NAME:

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

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 USER:-

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:

User 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 a new event 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 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.

It grants 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.

USE CASE DIAGRAM OF ONLINE STREET FOOD DELIVERY MANAGEMENT SYSTEM

Our system has mainly four factors the first is the user who register with the system with his details and then login he gets the menu to order from many stalls. he chooses and orders, the order will be passed to the delivery boy to deliver at the given place of the user in time as mentioned in the order. He delivers an order completes.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF ONLINE STREET FOOD DELIVERY MANAGEMENT SYSTEM

FUNCTIONAL REQUIREMENTS OF ONLINE STREET FOOD DELIVERY 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 ONLINE STREET FOOD DELIVERY MANAGEMENT SYSTEM:-

These requirements needs unit among the style of “system shall be “, 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 ONLINE STREET FOOD DELIVERY 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 online street food delivery 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 not 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 the clean program.

CONCLUSION OF ONLINE STREET FOOD DELIVERY MANAGEMENT SYSTEM

Finally in online street food delivery management system, we have a system where a user who registers with the system with his details and then login he gets the menu to order from many stalls. he chooses and orders, the order will be passed to the delivery boy to deliver at the given place of the user in time as mentioned in the order. He delivers an order completes.