LOYALITY POINT MANAGEMENT SYSTEM

INTRODUCTION OF LOYALTY POINT MANAGEMENT SYSTEM

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

Every time customer make a purchase from the shop there is trick to regain the customer, so that they come again to the shop to purchase anything ., earlier it was very difficult due to increasing competition in same business,

so it becomes very difficult and must to retain customer . the trick here is instead of taking all give something that they can spend next time .The discount is related to every item according to the season and sell active on the days and given to the customers.

every shop provides it occasionally to increase the sale. it’s always in trends and every shopper follows it. Like here the few part of the total purchase is given out to the customers account automatically.

Next time he can purchase using these points.Payment for the purchase can be done many ways one is using cash as normally we use to of next is an online card which is the hottest trending way of doing the payment.

Other is in this system is the loyalty points which they have in their account and make the payment done. he can use both combinations of payment methods too.

MODULES OF LOYALTY POINT 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.

LOYALTY POINT CALCULATOR:

Every time customer make a purchase from the shop there is trick to regain the customer, so that they come again to the shop to purchase anything ., earlier it was very difficult due to increasing competition in same business,

so it becomes very difficult and must to retain customer . the trick here is instead of taking all give something that they can spend next time . Like here the few part of the total purchase is given out to the customers account automatically.

Next time he can purchase using these points.

DISCOUNT:

The discount is related to every item according to the season and sell active on the days and given to the customers. every shop provides it occasionally to increase the sale. it’s always in trends and every shopper follows it.

PAYMENT:

Payment for the purchase can be done many ways one is using cash as normally we use to of next is an online card which is the hottest trending way of doing the payment.

Other is in this system is the loyalty points which they have in their account and make the payment done. he can use both combinations of payment methods too.

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 REQUIREMENTS OF LOYALTY POINT 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 LOYALTY POINT MANAGEMENT SYSTEM

ENTITY PRODUCT:

PRIMARY KEY PRODUCT_ID:

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

NAME:

the name of the product is here

EXPIRY DATE:

the date of expiry

MANUFACTURING DATE:

the date at which it was made

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

PRICE:

The price of the product

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.

QUANTITY:

the no of products

FOREIGN KEY PAYMENT_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 PURCHASE:

PRIMARY KEY PURCHASE_ID:

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

NO OF PRODUCTS:

the no of product items we have.

FOREIGN KEY GRAND TOTAL:

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.

QUANTITY:

quantity per products.

FOREIGN KEY DISCOUNT:

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 LOYALTY POINT:

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

PRIMARY KEY DISCOUNT_ID:

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

FOREIGN KEY PRODUCT_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 PURCHASE_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 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.

DATE:

the date at which discount is actively given

ACTIVE STATUS:

the status of activeness of discount or not.

ENTITY LOYALTY_POINTS:

PRIMARY KEY LOYALTY_POINTS_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 PURCHASE_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.

POINTS:

The points from the payment are given here by calculating few parameters.

EXPIRY DATE:

The points are valid for few time that will be given here.

ENTITY PAYMENT:

PRIMARY KEY PAYMENT_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 PURCHASE_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 PRODUCT_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.

PRICE:

The price to be paid Is here.

PAYMENT STATUS:

is the amount paid or not.

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 LOYALTY POINT MANAGEMENT SYSTEM

In this system, we have mainly 2 factors one is a user who registers himself on the system and then purchases the products from the system and then he gets the payment done via card and any other mean he gets loyalty points every time he purchases anything to his account it is some part of it total purchase .

discount is also given and users are retained by this mean. they can spend those points to buy new products. In this way, the system is maintained

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF LOYALTY POINT MANAGEMENT SYSTEM

FUNCTIONAL REQUIREMENTS OF LOYALTY POINT 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 LOYALTY POINT 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 LOYALTY POINT 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 loyalty point 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.

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 LOYALTY POINT MANAGEMENT SYSTEM

Finally in loyalty point management system, we have a system where a user who registers himself on the system and then purchase the products from the system and then he gets the payment done via card and any other mean he gets loyalty points every time he purchases anything to his account it is some part of it total purchase.

discount is also given and users are retained by this mean. they can spend those points to buy new products. In this way, the system is maintained