INTRODUCTION OF STATIONARY SHOP MANAGEMENT SYSTEM

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

Pen, pencil, notebooks, books are u n differential part of the life. Not particularly part of the student’s life but it is part of the every person’s life as it is helpful in every where like in offices, parking, malls, even in temples and were not.

So this much important thing of life must be very easily accessible and easily provided to the customer . here if we talk about getting it online we have a system which can maintain the whole objects of stationary in very classified manner and make it easy to take out the products fast.

here every user gets registered to the system with their own set of attributes. then they inquire the shop for the material with the set of filters and then they have the option to order the material with specifying the number item and address or they can pick their self.

the order will be registered with the system and then shop vendor will collect items from the racks of shops according to the order. this made ready and it is taken by the user and then the user gets his order.

further, he can use his items as they want. This system helping it to manage the things in a particular item to be put in a particular area like in particular rack. So that it becomes easy to put and take out the item fast.

MODULES OF STATIONARY SHOP 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.

Stock:

The stock interface is the main module of this system here admin manages the stationaries available in the shop. He manages them according to the name of the item.

He includes the book according to the name and author of the book and publisher in the racks. The frequent item which needs to be given is in the nearest of the racks.

Apart from books, we have pens, pencils, notebooks and many other in the racks according to the attributes . its all taken care by the admin. As the things get cleared the updating will be done automatically.

Order:

Order from the shop by the users is stored in this entity and as the no of items and category of the item. As the racks are also mentioned in that the update of main stock is done automatically.The order will be passed and items provided will be given to him.

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.

Log in:

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 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 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 time table 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 REQUIREMENT OF STATIONARY SHOP 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 STATIONARY SHOP MANAGEMENT SYSTEM

E-R DIAGRAM OF STATIONARY SHOP MANAGEMENT SYSTEM:-

E-R DIAGRAM OF STATIONARY SHOP MANAGEMENT SYSTEM

Entity Stock:

Stock is maintained by the Admin and analyzed when to refill

Primary Key Stock_id:

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

Foreign Key Books_id:

This is the attribute which is referenced from the other table. this is to maintain the referential integrity of the data . as here only that data will come which are available in parent entity.

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.

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

This is the attribute which is referenced from the other table. this is to maintain the referential integrity of the data . as here only that data will come which are available in parent entity.

Foreign Key Pencils_id

This is the attribute which is referenced from the other table. this is to maintain the referential integrity of the data . as here only that data will come which are available in parent entity.

Foreign Key Others_id:

This is the attribute which is referenced from the other table. this is to maintain the referential integrity of the data . as here only that data will come which are available in parent entity.

Entity Books:

Primary Key Books _id:

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

Name:

The name is given here to uniquely identify the item. Easy to search wherever needed.

Publisher:

The publisher is important as it determines the quality of the product and people preference for the brand.

Author:

who writes the book is fed here as to uniquely identify the book of choice.

Price:

Price is mentioned here for a unit. which used to calculate the large no . of items.

Edition:

Edition of the book is also mentioned as to know the latest version of the book.

Entity pens:

Primary Key pens_id:

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

Name:

The name is given here to uniquely identify the item. Easy to search wherever needed.

Manufacturer:

The manufacturer is important as it determines the quality of the product and people preference for the brand.

Price:

Price is mentioned here for a unit. which used to calculate the large no . of items.

Entity pencil:

Primary Key pencils_id:

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

Name:

The name is given here to uniquely identify the item. Easy to search wherever needed.

Manufacturer:

The manufacturer is important as it determines the quality of the product and people preference for the brand.

Price:

Price is mentioned here for a unit. which used to calculate the large no . of items.

Entity others:

Primary Key others_id:

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

Name:

The name is given here to uniquely identify the item. Easy to search wherever needed.

Manufacturer:

The manufacturer is important as it determines the quality of the product and people preference for the brand.

Price:

Price is mentioned here for a unit. which used to calculate the large no . of items.important as to give a filter to the user.

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.

User name:

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 new events and for future references, 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. I grant 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 STATIONARY SHOP MANAGEMENT SYSTEM:

USE CASE DIAGRAM OF STATIONARY SHOP MANAGEMENT SYSTEM

We have mainly two actors in the system who interact with the system.

first is the admin who maintains the stocks, he punches the data of the items one by one with the attributes of category and price in racks. once done he manages them he generates the bill as well.

second is a user, the user firstly registers with the system then choose the items he needs to buy as he finishes with choosing he confirms and get the order in hand.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF STATIONARY SHOP MANAGEMENT SYSTEM

Functional requirements of stationary shop 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-

stocks can be punched in it and doing and tells the need of refill

automatic update of racks.

Non-Functional requirements of stationary shop 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 stationary shop management system needs –

unit of measurement usually divided into 2 main categories:

Execution qualities, like security and quality, that unit evident at the run time.

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 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 a clean program.

CONCLUSION OF STATIONARY SHOP MANAGEMENT SYSTEM

So finally here we are with a system which is capable of managing the shops stationary in a very classified manner gives a flair edge of cleanliness and smoothness of access to products and tracking the products for profit and also used to check which product needs to be refilled. In this system gives a good performance.