INTRODUCTION OF RESTAURANT DEPOT LOCATIONS

Are you looking for Restaurant depot locations for your final year project? We are here to help you. You can contact us

It’s very difficult to find the desired kind of restaurant on the go, when we need particular type food to eat at any time, we need to go street by street and search for that which is itself a very tiring task , we need a kind of system where we can find the restaurant as we want ,

we have a system in which we can search the restaurant according to the taste food type and availability and also price we consider too. We can filter the many choices out of the pool and refine to a specific item.

The detail of the restaurant is updated by the vendor of the system they get to register as the user and have the privilege to add new items in the system and change the details of existing which is finally feed to be shown in the system.

The user can see that and filter out the items and make choice of particular restaurant accordingly.Here the user can upload the pictures of the items and restaurant itself as to give more clarity to the user so that they can easily identify the premise and make the things easily available .the size of the pic, length width and other qualities are considered for the sake of more clearance.

MODULES OF RESTAURANT DEPOT LOCATIONS

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.

Locate Restaurant:

It’s very difficult to find the desired kind of restaurant on the go, when we need particular type food to eat at any time, we need to go street by street and search for that which is itself a very tiring task , we need a kind of system where we can find the restaurant as we want ,

we have a system in which we can search the restaurant according to the taste food type and availability and also price we consider too. We can filter the many choices out of the pool and refine to a specific item.

Details updated:

The detail of the restaurant is updated by the vendor of the system they get to register as the user and have the privilege to add new items in the system and change the details of existing which is finally feed to be shown in the system.

The user can see that and filter out the items and make choice of particular restaurant accordingly.

Pic Upload:

Here the user can upload the pictures of the items and restaurant itself as to give more clarity to the user so that they can easily identify the premise and make the things easily available .the size of the pic, length width and other qualities are considered for the sake of more clearance.

Registration:

Users information have to be compelled to be registered within the system thus on establish every of them unambiguously and do the-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 REQUIREMENTS OF RESTAURANT DEPOT LOCATIONS

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 RESTAURANT DEPOT LOCATIONS

SYSTEM DESIGN OF RESTAURANT DEPOT LOCATIONS

Entity Restaurant:

Primary Key Restaurant_id:

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

Name:

The name of the owner is fed here.

Email:

the email to contact the premise.

Owner name:

the name of the owner who is responsible for the restaurant working and any grievances.

Item_id:

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

Address:

Address of the restaurant where it is located is must for the entity and cannot be null.

Opening time:

The at which it opens is written over here

Closing time:

the time at which it closes is written over here.

Entity item:

Primary Key item_id:

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

Name:

The name of the item.

Foreign key User_id:

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

Price:

The price of the item.

Quantity:

the quantity at which they are available.

Type:

the type of the item that is beverage or food or anything else.

Foreign key pic_id:

This is reference key from the other entity to link the data of that table.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 pic:

Primary Key pic_id:

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

Name:

name of the pic

Size:

size of the pic in m b will be shown here.

Length:

The length of the pic.

Width:

The width of the pic is here.

The click of date:

the date of the clicking pic will be here.

Foreign Key Item_id:

This is reference key from the other entity to link the data of that table.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 filter:

Primary Key filter_id:

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

Opening time:

The at which it opens is written over here

Closing time:

the time at which it closes is written over here.

Color:

the colour of the food item they search of availability

Price:

the price at it marked will be given to this.

Rating:

the rating out of 10 will be provided here. one can give a rating between zero to ten.

Address:

Address of the restaurant where it is located and need to find is must for the entity and cannot be null.

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.

Entity locator:

Primary Key locator_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.

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 restaurant_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.

Address:

the address where it is located can be found here and reflected on the interface.

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 Key User_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:

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 RESTAURANT DEPOT LOCATIONS

USE CASE DIAGRAM OF RESTAURANT DEPOT LOCATIONS

In this system mainly we have three actors one is a user who searches the required restaurant according to the different filter given to him, the price colour and other things.

The Vendor here is available to update the details of the restaurants.Admin manages the other users and lets them do their task smoothly.

FUNCTIONAL AND NON-FUNCTION AL REQUIREMENTS OF RESTAURANT DEPOT LOCATIONS

Functional requirements of restaurant depot locations:-

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 restaurant depot locations:-

These requirements needs unit among the style of “system shall be “, associate an 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 restaurant depot locations 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 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 doable – 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.

CONCLUSION OF RESTAURANT DEPOT LOCATIONS

Finally, in Restaurant depot locations, we have a system where a user who searches the required restaurant according to the different filter given to him, the price colour and other things.

The Vendor here is available to update the details of the restaurants.Admin manages the other users and lets them do their task smoothly.