CLOTHES MANAGEMENT SYSTEM

 

INTRODUCTION OF THE CLOTHING STORE ORGANIZER

Are you looking for clothing store organizer for your final year project? We are here to help you. You can contact us

everyone wants to wear the bright, trendy , and diverse clothes of their choice and needs to be taken care of while shopping the clothes it becomes very tedious to select clothes when we do not know the clothes to which area it is according to the choice and many options here we have the system which has the capability of making the clothes of a kind to register on the different places which could be further taken care when needed .

Mainly this system is concerned with the classification of the clothes. However it is shirt then it is taken care that which color it is and which gender it supports and which size it is of and then it like this all clothes like trousers , pants , inner and apart from this all others clothes also managed in the particular area of the shop and administered by the staff of the store then the admin takes it care.

Whenever the user wants according to the choice, he can select the particular clothes and get it.

MODULES OF CLOTHING STORE ORGANIZER

The modules of the clothing store organizer are 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.

CLASSIFY CLOTHES:

This is the interface of the system in which one can put all the different kind of clothes in various racks according to the type, price, colour and few more attributes of it.

Admin takes care of it. It is like a shopkeeper is managing the clothes of types at different places and here he is giving it to the system about the information of it.

Now They keep the shirts in a different area, trousers at another place the ladies clothes at a different location. Clothes of kids are different and put in a different rack. Every track has unique numbering and staff is assigned to it to take care of it.

CHOICE :

As he gives the preference of the user, the parameter from which he will choose is shown in this interface. The user selects the clothes by colour, size, when to wear kind of situation clothes type and many more things are considered here.

This choice interface is necessary to choose the clothes and to estimate the pricing of it making a bill out of it according to the quantity and pricing.

STAFF:

This interface is for staff in this interface admin assigns the teams on particular rack area from where the choices need to be taken care of. Now the assignment is based on his quality and needs to be taken care he can do the job or not.

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. Or 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 THE CLOTHING STORE ORGANIZER

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 THE CLOTHING STORE ORGANIZER

ENTITY CHOICE:

PRIMARY KEY CHOICE_ID:

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

CATEGORY:

To which category it belongs is written over here.

CLOTHES TYPE:

The kind of the clothing used in that item is also considered.

DESCRIPTION:

Anything special about the clothes is written in it to make the clothes data more valuable.

CLOTHE_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. 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 CLOTHES:

PRIMARY KEY CLOTHES_ID:

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

TYPE:

which kind of clothing is it for party wear, casual or anything else will come here.

FOREIGN KEY SHIRT_ID:

This is reference key from the other entity to link the data of that table.Reference to shirt table is done through this attribute.

FOREIGN KEY TROUSER_ID:

This is reference key from the other entity to link the data of that table.Reference to trouser table is done through this attribute.

FOREIGN KEY SUIT_ID:

This is reference key from the other entity to link the data of that table.Reference to suit table is done through this attribute.

FOREIGN KEY INNER ID:

This is reference key from the other entity to link the data of that table.Reference to the Inner table is done through this attribute.

FOREIGN KEY OTHERS_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.Reference to Others table is done through this attribute.

ENTITY STAFF:

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

STARTING RACK:

From where he is assigned to give duty.

FINISHING RACK:

The last frame to which he is assigned to provide his services.

ENTITY SHIRTS:

PRIMARY KEY SHIRTS_ID:

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

TYPE:

The kind of the clothes is used in it is fed here.

COLOR:

Color is important to choose the clothes.

BRAND:

To which brand it belongs is also the matter of concern.

PRICE:

Per unit price is mentioned here.

RACK NO.

The Rack no . is given to which it should be kept to classify and retrieve fast.

SIZE:

The size of which it will come fit. Like xl, x ll, l their many sizes should be mentioned in it.

GENDER:

For Which gender the clothing is for.

ENTITY TROUSERS:

PRIMARY KEY TROUSERS_ID:

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

TYPE:

The kind of the clothes is used in it is fed here.

COLOR:

Color is important to choose the clothes.

BRAND:

To which brand it belongs is also the matter of concern.

PRICE:

Per unit price is mentioned here.

RACK NO.

The Rack no . is given to which it should be kept to classify and retrieve fast.

SIZE:

The size of which it will come fit. Like xl, x ll, l their many sizes should be mentioned in it.

GENDER:

For Which gender the clothing is for.

ENTITY SUIT:

PRIMARY KEY SUITS_ID:

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

TYPE:

The kind of the clothes is used in it is fed here.

COLOR:

Color is important to choose the clothes.

BRAND:

To which brand it belongs is also the matter of concern.

PRICE:

Per unit price is mentioned here.

RACK NO.

The Rack no . is given to which it should be kept to classify and retrieve fast.

SIZE:

The size of which it will come fit. Like xl, x ll, l their many sizes should be mentioned in it.

GENDER:

For Which gender the clothing is for.

ENTITY OTHERS:

PRIMARY KEY OTHERS_ID:

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

TYPE:

The kind of the clothes is used in it is fed here.

COLOR:

Color is important to choose the clothes.

BRAND:

To which brand it belongs is also the matter of concern.

PRICE:

Per unit price is mentioned here.

RACK NO.

The Rack no . is given to which it should be kept to classify and retrieve fast.

SIZE:

The size of which it will come fit. Like xl, x ll, l their many sizes should be mentioned in it.

GENDER:

For Which gender the clothing is for.

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.

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 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 statement is attributed in this.

Here we have 3 actors mainly in the system .User chooses the clothes staff picks the cloth and admin take them calculated, and the choice of clothes is provided to him.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF THE CLOTHING STORE ORGANIZER

FUNCTIONAL REQUIREMENTS OF THE CLOTHING STORE ORGANIZER:-

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 CLOTHING STORE ORGANIZER:-

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 CLOTHING STORE ORGANIZER-

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 the clothing store organizer 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 clothing store organizer ultimately builds interface easy to use for a lengthy time. In distinction to ancient vogue wherever the goal is to make the difficulty or application physically enticing, the purpose of interface trend is to create the user’s interaction expertise as straightforward and intuitive as double – what’s typically mentioned as user-centred vogue.

Where smart graphic/industrial fashion is daring and eye-catching, intelligent interface trend 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 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 a clean program.

CLOTHING STORE MANAGEMENT SYSTEM PROJECT

CONCLUSION OF THE CLOTHING STORE ORGANIZER

Finally, in this clothing store organizer, we have a system in. The user chooses the clothes staff picks the cloth and admin take them calculated, and the choice of clothes is provided to him.Hence the system is working fine and giving the clothes working a smooth and classified edge.