Contact at mumbai.academics@gmail.com or 8097636691
Responsive Ads Here

Friday, 5 January 2018

WELDING MANAGEMENT SYSTEM

WELDING MANAGEMENT SYSTEM

INTRODUCTION OF WELDING INFORMATION MANAGEMENT SYSTEM

Are you looking for a Welding information management system for your final year project? We are here to help you. You can contact us
Our house has many many items which are made up of many iron pieces. like window case, gate, coats etc. Apart from this its vehicles which have a lot of joints, and many heavy machines too.
Here we come a system where users register themselves with some sort of attributes. The user uses the system to give the dimensions of the item he wants.
He can give the length, width, shape, material used and many their attributes with diagram pic of the piece if he wants it completed customized or the part where he wants the welding done.
Here he has one option after registering in the system either we will bring his item which needs to be weld to the shop or request to be transported by the vendor transport system.
Another option is to customize from scratch in this transport can be opted in the end . and then it will be delivered to the premise of the user.In this system completes its task.

MODULES OF WELDING INFORMATION 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.

CUSTOMIZED ITEM :

The customized item is the interface that we can say is the soul of this system as every user want their own kind of item so one needs to understand what piece actually is and its dimensions to know the amount of material we will get to use to make it.
What will be the time used and approval? So here we have the option of the picture that how the item looks like and diagram pic can also be uploaded. This kind of minute details helps in making the system more feasible and smooth to accomplish using particular machine and number of rods and other materials.

ORDER:

The order for the making of the item an user wants is done through this system as one can choose many attributes from here like how your piece should look like through the customized item section.
When he wants the order and at what address. The cost and others required attributes are mentioned in it.

TRANSPORTER:

Transporter is the person who is responsible for his vehicle to maintain and load the item in it according to the order given by the user and instructed by the admin.
He maintains his vehicle and he is responsible for its well-being like no plate, pollution certificate and any other feature plus the driving of the vehicle to the destination .he can all manage through this interface and track these in this.

FEEDBACK:

Feedback interface also an important part of the system as the user satisfaction and the staffs working quality and any kind disregard or complaint or if any problem in the system the first information to come up with that is taken from here.

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 WELDING INFORMATION 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 WELDING INFORMATION MANAGEMENT SYSTEM

E-R DIAGRAM OF WELDING INFORMATION MANAGEMENT SYSTEM

E-R DIAGRAM OF WELDING INFORMATION MANAGEMENT SYSTEM

ENTITY MACHINE :

The attributes of the machine are written in this entity.

NAME:

The name of the machine is written on it as of identity.

BRAND:

The manufacturer name is the brand of the machine.

POWER:

The consumption of the power in particular span of time is written here.

PRICE:

The price of the machine which it costs is here.

CATEGORY:

The category to which it belongs.

SIZE:

The small, medium or large machine cost the users more that’s why need to be known due to its benefits, usability.

TYPE:

Gas or normal welding depends

NO. OF RODS:

The number of rods that one customized piece requires.

ENTITY CUSTOMIZED ITEM:

PRIMARY KEY CUSTOMIZED ITEM_ID:

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

NAME:

The unique name given to the item is fed over here.

BRAND:

The brand to which they loyal can be seen over here.

PRICE:

The price per unit will be fixed over here.

CATEGORY:

It depends upon the Material used that is lustrous and week for mild usage, hard but strong for heavy usage.

HEIGHT:

The height of the item in the foot can be seen here.

WIDTH:

The width of the item in the foot can be seen here.

COLOR:

The colour of the item can be seen over here.

SHAPE:

Shape of item is directly written as estimation to which it references

REFERENCE PIC:

The picture of the item that they want or rough diagrams clicks work for it.

TIME TO COMPLETE:

The deadline to which the order is required by the user and they need to a complete that order at time

ENTITY ORDER:

PRIMARY KEY ORDER_ID:

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

FOREIGN KEY CS_ID:

Reference to the Customized item id

FOREIGN KEY USER_ID:

Reference to the user’s id

FOREIGN KEY TRANSPORTER_ID:

References to the transporter id

TIME OF DELIVERY:

The time at which he wants the delivery.

PLACE OF DELIVERING:

a place where he wants the delivery, that is address

COST:

The cost of the Item can be shown over here.

ENTITY TRANSPORTER:

PRIMARY KEY TRANSPORTER_ID:

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

PLACE OF DELIVERY:

where to deliver.

STARTING TIME:

The time to start from source.

REACHING TIME:

The time at which the delivery reaches.

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

ENTITY VEHICLE:

PRIMARY KEY VEHICLE_ID:

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

NAME :

The brand name of the vehicle

SIZE:

The size of the vehicle which it is.

ENTITY FEEDBACK:

PRIMARY KEY FEEDBACK_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. 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 TRANSPORTER_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.

DESCRIPTION:

The issue related all the information is given here, one can mention the time venue and person with whom he has a complaint and any other information if he wants. This will be read by higher official and necessary actions will be taken. This will make scenario easy to understand.

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:

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.

FOREIGN KEY : –

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.

USE CASE DIAGRAM OF THE WELDING INFORMATION MANAGEMENT SYSTEM

USE CASE DIAGRAM OF THE WELDING INFORMATION MANAGEMENT SYSTEM

Here user orders the customized item with giving its all the attributes then it will be assigned to machine and rods to accomplish the order. Depending on the task they do the transporting to home and do the necessary welding on it.
Transporter does the transport works for machine and material.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF WELDING INFORMATION MANAGEMENT SYSTEM

FUNCTIONAL REQUIREMENTS OF WELDING INFORMATION 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 WELDING INFORMATION 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 WELDING INFORMATION 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 the welding information 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 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.

WELDING QUALITY MANAGEMENT PROJECT

CONCLUSION OF WELDING INFORMATION MANAGEMENT SYSTEM

Finally, we have a system where the Here user orders the customized item with giving its all the attributes then it will be assigned to machine and rods to accomplish the order.
Depending on the task they do the transporting to home and do the necessary welding on it. transporter does the transport works for machine and material.hence this system accomplishes the task of welding smoothly.

No comments:

Post a Comment