INTRODUCTION OF GROCERY MANAGEMENT SYSTEM

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

Wheat, rice, pulses, oil, cosmetics, etc. are the part of the life such that they can not be seen as different from life. These products are available quickly and frequently at any store, every store has their set of glossary products which need to be managed properly in such a way that as one customer come to take the product the items can be easily removed and collected at a place, then it needs to be set according to the price.

Here what this system does is in this system we can see the items like wheat, rice, pulses, soap and any other product according to the attributes like type, brand, category, price, etc.

So that using system it can be located quickly and give instructions to staff to take out the products and the total of the goods are presented in the order table to total the price. The bill is made on that basis and given to the customers.

The admin maintains the detail of the clients and staff . can be the counter manager or any staff. In this way, this gives a sense of management to the store and brisk the pace of work.

MODULES OF GROCERY MANAGEMENT SYSTEM

The module of the Grocery management 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.

Item Selection:

The user chooses the item from the interface he gets on the basis different choice of filters like price, colour, category and much more he can add as many items he wants he may specify it as he wants and get the selected items done in the interface.

Order:

The things which choose by the user then move to order interface to get ordered by the user as he will see here the details of the final result to order the total and timings. He can remove any item if he wants.

Payment:

They may make payment online through their debit card they use this module to pay as the ticket shows the amount in the account of the owner of the bus.As he makes the payment the card become confirmed and ready to be used.

Staff assignment:

Admin assigns the team on the particular rack to pick the items as fast as they can their task is to pack the item fast and collect it to the central area where packing can be done properly and give the order to customers.

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.

Login:

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 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 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 timetable 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 GROCERY MANAGEMENT SYSTEM

Now, this method is intended in such the way that it takes fewer resources to figure out work correctly. It’s its 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 GROCERY MANAGEMENT SYSTEM

SYSTEM DESIGN OF GROCERY MANAGEMENT SYSTEM

Entity Order:

Primary Key Order_id:

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

Items_id:

Reference to the item id is given here.

No . of items:

Total no of items for order.

Quantity:

Quantity per item

Price per item:

Price of per item is given

Discount:

Any discount if offered will be paid here

Total:

Total of all costs is given here.

Entity item:

Primary Key item_id:

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

Rice_id:

Reference to the Rice id is given here.

Wheat_id:

Reference to the Wheat id is given here.

Others_id:

Reference to the other type of items id is given here.

Soap_id:

Reference to the item id is given here.

Cereals_id:

Reference to the cereals id is given here.

Entity Soap:

Primary Key Soap_id:

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

Name:

name of the soap is here.

Type:

type of the soap for washing clothes or bathing

Size:

The size of the soap small, large medium.

Brand:

The brand of the soap

Price:

The cost of the soap.

Color:

The colour of the soap.

Rack No.

The rack in which it is kept.

Fragrance:

The scent of the soap as it is.

Entity Rice:

Primary Key Rice_id:

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

Type:

The kind of it is mentioned

Size;

The size of the soap small, large medium.

Brand:

The name to which it belongs

Price:

The price of the item.

Color:

Color of the item

Rack No.

To which rack it is put.

Condition of packing;

Is the item packed or not depends

Entity Cereals:

Primary Key cereals_id:

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

Type:

The kind of it is mentioned

Size;

The size of the soap small, large medium.

Brand:

The name to which it belongs

Price:

The price of the item.

Color:

Color of the item

Rack No.

To which rack it is put.

Condition of packing;

Is the item packed or not depends

Entity Others:

Primary Key others_id:

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

Used For:

Where the item is used is given here the purpose.

Type:

The kind of it is mentioned

Size;

The size of the soap small, large medium.

Brand:

The name to which it belongs

Price:

The price of the item.

Color:

Color of the item

Rack No.

To which rack it is put.

Condition of packing;

Is the item packed or not depends

Entity Payment:

Primary Key Payment_id:

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

User_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Ticket_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Status:

Is the payment is done or not is given here.

Entity Staff:

Primary KeyStaff_id:

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

Staff name:

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

Qualification:

The requirement 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 made to make member aware of new offers new events, and for future reference, 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.

Starting rack:

From where his duty starts of racks.

Finishing rack:

Till where he gives responsibility.

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:

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 made to make member aware of new offers new events, and for future reference, 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 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 relevant info. Regarding this account is attributed in this.

USE CASE DIAGRAM OF GROCERY MANAGEMENT SYSTEM

USE CASE DIAGRAM OF GROCERY MANAGEMENT SYSTEM

 

This system has mainly 3 actors. Users order the item according to the wish given by the filters he chooses and specify the no . of it and make the payment; he gets the order as staff picks out the items from the racks and give to the user.

Admin assigns the team to the racks. In he analyzes the profit and gain and booking for the customers.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENT OF GROCERY MANAGEMENT SYSTEM

Functional requirements of Grocery 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 glossary management system:-

These requirements needs unit among the style of “system shall be,” overall associated property of the regime as a full or of an individual 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 grocery management 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 of grocery 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 nonhelpful 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 build the difficulty or application physically enticing, the purpose of interface trend is to build the user’s interaction expertise as straightforward and intuitive as double – what’s typically mentioned as user-centred fashion.

Where smart graphic/industrial fashion is daring and eye-catching, intelligent interface fashion is sometimes delicate and invisible.

Keep things simple and consistent:-

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

Observe use of typography:-

The typography is taken care 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 are taking feedback of forms and rising the system.

Simplified forms:-

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

CONCLUSION OF GROCERY MANAGEMENT SYSTEM

Finally, in grocery management system we have a system where users order the item according to the wish given by the filters he chooses and specify the no . of it and makes the payment; he gets the order as staff picks out the items from the racks and give to the user.

Admin assigns the staff to the racks. In he analyzes the profit and gain and booking for the customers.