CUSTOMER REVIEW RECORDING

 

INTRODUCTION OF OPEN SOURCE CUSTOMER REVIEW SYSTEM

Are you looking for an Open source Customer review system for your final year project? We are here to help you. You can contact us

To find the right the thing at the correct location and appropriate conditions and constraints is terrible these days, one needs to suffer a lot for the minor task also. So here we have a system where on e find the every thing of choice on the base of experience by other user and ratings.

The system is made so that one customer who has experienced the taste of the service they got from some of the facility, however, they get right or wrong they would like to share it with everyone so that many searchers who want excellent service and worth of money they can read it and make necessary choices on the basis of that .

So we have the option of choosing the services like restaurant and item of food they want to review. They can give ratings and describe the experience they had. Here they may flag it good or bad according to wish through ratings and words, pricing and any other parameter.

The other use of this system is that one can choose the perfect choice according to the review, so need an interface to read the review and accept it through some link to their premise or contact details.

So they have many filters available which they choose on the basis of choice of cheap price wise and much more. And get the perfect one, and from that, they can get the contact no, and the web address of that system and do the necessary ordering from there.

MODULES OF THE OPEN SOURCE CUSTOMER REVIEW SYSTEM

The Open source Customer review 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 scheme.

REVIEW WRITING:

The main module of the project is this module. The system is made so that one customer who has experienced the taste of the service they got from some of the facility, however, they get right or wrong they would like to share it with everyone so that many searchers who want excellent service and worth of money they can read it and make necessary choices on the basis of that .

So we have the option of choosing the services like restaurant and item of food they want to review. They can give ratings and describe the experience they had.

Here they may flag it good or bad according to wish through rating s and words, pricing and any other parameter.

VIEW REVIEW:

The other use of this system is that one can choose the perfect choice according to the review, so need an interface to read the review and accept it through some link to their premise or contact details.

So they have many filters available which they choose on the basis of choice of cheap price wise and much more and get the perfect one and from that, they can get the contact no and the web address of that system and do the necessary ordering from there.

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 real 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 correctly 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.

LOG IN:

After registration one will register within the system because of the operator of the system either on behalf of the user.

When this he has the different 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 primary 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 log in 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 only to put our registered email Id and hit the enter.

Then one confirmation email will go to the email where he may 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 can manipulate the access of the users to the data.

The primary 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 time table according to the wish we want to create for a particular type of inputs.

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

SYSTEM REQUIREMENT OF THE OPEN SOURCE CUSTOMER REVIEW SYSTEM

Now, this method is intended in such the way that it takes fewer resources to figure out work correctly. 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 correctly, 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 correctly, and if any error is found, then it can be removed easily.

SYSTEM DESIGN OF THE OPEN SOURCE CUSTOMER REVIEW SYSTEM

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.

ENTITY REVIEW:

PRIMARY KEY REVIEW:_ID:

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

NAME:

Some topic name will be given a title.

FOREIGN KEY RESTAURANT_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.

FOREIGN KEY HOME_SERVICE_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.

FOREIGN KEY DELIVERY_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.

RATING:

The score out of 10 will be provided here. One can give a score between zero to ten.

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.

DESCRIPTION:

One can describe the review according to their wish in their words.It’s important as everyone will go to see this one.

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 HOME SERVICES:

PRIMARY KEY HOME_SERVICES_ID:

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

NAME OF SERVICE:

the name of the service given by the premise.

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.

COST:

The price they charge for the visit and service according to the unit work is given here.

TIME OF DUTY:

When the serviceman will come to the premise for the work.

RATING :

The score out of 10 will be provided here. One can give a score between zero to ten.

ADDRESS:

the address where they can be available to book them.

ENTITY DELIVERY:

PRIMARY KEY DELIVERY_ID:

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

NAME:

some topic is given to the delivery.

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.

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.

RATING:

The score out of 10 will be provided here. One can give a score between zero to ten.

TIME OF DELIVERY:

At what time it will be delivered.

AVERAGE TIME TO DELIVER:

The average duration at which they will be reaching the venue.

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 amount at which they are available.

TYPE:

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

FOREIGN KEY RESTAURANT_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 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:

the requirement is made 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 references, it is also relevant.

TYPE:

the kind 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 accessible 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 analyse 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 relevant info. Regarding this account is attributed in this.

USE CASE DIAGRAM OF THE OPEN SOURCE CUSTOMER REVIEW SYSTEM

In this system we have mainly three actors first is the user who is registered with the system after giving the details of him and that user is vendor also for the services and restaurants we can say.

user select the thing he wants to give a review on. He writes a review on it according to the experience and gives ratings also. after that will be saved and any one can see the review of that after searching in the panel.

They can get the details of the premise too so that they can contact them and make the necessary order they want. Admin manages the system for the review and makes necessary changes.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF THE

OPEN SOURCE CUSTOMER REVIEW SYSTEM

FUNCTIONAL REQUIREMENTS OF THE OPEN SOURCE CUSTOMER REVIEW 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 THE OPEN SOURCE CUSTOMER REVIEW SYSTEM:-

These requirements needs unit among the style of “system shall be “, associated overall property of the regime as a full or of a particular aspect and not an individual operates.

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

NON-FUNCTIONAL NEEDS OF THE OPEN SOURCE CUSTOMER REVIEW SYSTEM –

Unit of measurement usually divided into two broad 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 not helpful consequently, and the system is up to mark performance device.Here we’d prefer to need care of few lots of things before heading towards the system.-

KEEP THINGS SIMPLE AND CONSISTENT:-

Straightforward and harmonic means that are making u i is extraordinarily intuitive and needs to followed

OBSERVE USE OF TYPOGRAPHY:-

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

USE COLOUR AND DISTINCTION CORRECTLY:-

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 excellent implies that taking feedback of forms and rising the system.

SIMPLIFIED FORMS:-

The structure is made simple to fill with the clean program.

CONCLUSION OF THE OPEN SOURCE CUSTOMER REVIEW SYSTEM

Finally, in the Open source Customer review system, we have a system where a user who is registered with the system after giving the details of him and that user is vendor also for the services and restaurants we can say.

user select the thing he wants to give a review on. He writes a review on it according to the experience and gives ratings also. after that will be saved and any one can see the review of that after searching in the panel.

They can get the details of the premise too so that they can contact them and make the necessary order they want. Admin manages the system for the review and makes necessary changes.