You are on page 1of 54

PAINT MANAGEMENT SYSTEM

INTRODUCTION OF THE SYSTEM


“PAINT MANAGEMENT SYSTEM”

A) OBJECTIVES:

 This system provides very easy way to take order according to user re-
quirements.
 This software helps in buying products of good quality from their suppliers
and sales to their customer as per customer requirements.
 Update the records regularly month wise.
 Mainly repetitions of data are avoided.
 Reduce the wastage of time.
 Security of data is also maintained from unauthorized access.
 Generation of yearly or monthly purchase/sale reports become easier.
 Day to day transactions is recorded in the master file.
 Fill comfort ability to take order.
 Mathematical calculation becomes easier.

Thus it is a real world existing system that is very helpful to all people.

TEJAS PARMAR Page | 1


PAINT MANAGEMENT SYSTEM

EXISTING SYSTEM

A. The existing system ‘Paint management System’ is based on manual works and
processes are done manually.
B. This software maintains daily records in register and details of the system also
maintenance daily transaction such as purchase and sales of all type of paints.
C. The existing system maintain all details in supplier master file, sales records in
sales file and purchase records in the purchase file.
D. This system is divided into two types of sales: They are:

1. Whole sale
2. Retail sale

So that any kind of paints are affordable to all people.

E. They also maintain the bill book on purchase or sales of any paint.
F. All the works manually according to the requirements of users so that the more
requirements the selling of specific items is more.

TEJAS PARMAR Page | 2


PAINT MANAGEMENT SYSTEM

NEED OF PROPOSED SYSTEM

 Nowadays in this electronic world all the works are maintain with the help of
computers so that day to day transaction even the small are done with it help.
 The initial basic step is firstly to ask for user login name & password to prevent
the project from unauthorized access.
 The manual works for Paint management System is to be computerized as per
order to overcome any type of situation affecting the existing system.
 It takes automatic orders without any samples maintaining the quality of the
product.
 This system is designed for finding appropriate and suitable matches keeping the
desired quality of the concerned party as its mains objectives.
 The point to focus is that this software includes all types of paints and imple-
ments all the processes through computers successfully.
 It holds all the requirements keeping in consideration the purchase sales activity.
 It also maintains the product quality throughout the year as per the requirements.
 Easy to take order i.e. supplier make the order to different companies and ac-
cording to the which product is sold more is recorded and which are in demand
are taken in mind.
 The inbuilt form are also included the paints the bills of all items that are sold.
 The user can easily find the data avoiding the wastage of time by selecting par-
ticular menus used for specific purpose.
 Security of data is major concern so that the user keeps his/her personal
username and passwords so that security of data is maintained at many extents.

TEJAS PARMAR Page | 3


PAINT MANAGEMENT SYSTEM

FEASIBILITY STUDY
 Feasibility study is undertaken to determine the possibility of either improving the
existing system or developing a completely new system.
 It is carried out whenever there is a complex problem of opportunity.
 It helps to obtain an overview of the problem and to get rough assessment of
whether feasible solution exists.
 This is essential to avoid committing large resources to project and then repent
on it later.

NEED OF FEASIBILITY STUDY


 Answer the question whether a new system is to be installed or not?
 Determine the potential of existing system.
 Improve the existing system.
 Know what should be embedded in the system.
 Define the problems and objectives involved in a project.
 Avoid crash implementation of a new system.
 Avoid costly repairs at a later stage when the system the system is imple-
mented.
 Avoid the ‘hardware approach’ i.e. getting a computer first and then deciding
how to use it.

There are three aspects in feasibility study portion of the preliminary investiga-
tion-

1. technical feasibility
2. economic feasibility
3. operational feasibility of the project

TEJAS PARMAR Page | 4


PAINT MANAGEMENT SYSTEM

Let us discuss the above feasibility in details:

TECHNICAL FEASIBILITY

 Technical feasibility determines whether the work for project to be done


with the present equipment, control procedures existing software’s tech-
nology and available personnel.
 If the new technology is needed then what alternates will be need in the
present structure and works methods?
 This will require a close examination of the present system.
 The technical feasibility should ask question related to:

1) Adequacy of available of technology.


2) Requirements of technology.
3) Availability of hardware.
4) Operating time and support facility etc.

This study determines whether the technology needed for the proposed
system is available and how it can be integrated within the Paint man-
agement system and the technical evaluation must be taken in acc.
Whether the existing system can be upgraded to use the new technology
and whether this system has the expertise to use it.

 The technical feasibility deals with the technology use in the system which
also deals with hardware & software use in the system whether they are of
latest technology or not.
 It happens that after the system is prepared a new technology thus it is
important to check the system technical feasible.

TEJAS PARMAR Page | 5


PAINT MANAGEMENT SYSTEM

ECONOMIC FEASIBILITY

 It looks the financial aspects of the project it is concern with the returns
from the investments in the project it determines whether it is worthwhile
to invest the money in the proposed system or not.

OPERATIONAL FEASIBILITY

This study covers mainly two aspects one is the acceptance which is within this
system it determine how the proposed system will be accurate in the current task if any
retaining to the existing system.

TEJAS PARMAR Page | 6


PAINT MANAGEMENT SYSTEM

SYSTEM FEATURES

 On comparison of computer system with computerized system many advantages


of computerized come up.
 A computerized system one person and a computer can do a job done by many
people.
 In manual to system Speed up the job more people should be customer.
 On the other hand, a Computer can do this work with much more speed and Ac-
curacy.
 The show as plus point of computerization over the manual system.
 Even through Installation of a computer and having the require software.
 Involve lot of Money its long time efficiency is inevitable for a Business.
 Reduction of the Day-to-day Expenses bringing great difference in the profit
earning of Business.
 The speed in which computer works is really in comparable with the manual
work.
 The Accuracy and Efficiency of the Machine adds a plus a Point of computeriza-
tion.
 The cost & benefit analysis of computerization can be conclude in a way by sav-
ing that in the computerization of any system will be benefit, code wise otherwise.
So computerization of system is a Wise Decision in all sense.

TEJAS PARMAR Page | 7


PAINT MANAGEMENT SYSTEM

HARDWARE & SOFTWARE


 HARDWARE REQUIREMENT OF THE SYSTEM:

This phase of the software development process deals with a brief study of different
hardware used in the computerized system. There is a list of hardware materials used
during the making and also during the use of proposed system. As the new system to
be made into a computerized functional system, a requirement of a computer is must.
All the hardware needed here are generally the basic configuration of a typical office
computer. A list of the hardware requirement used in the system given below:

Minimum Configuration:

Intel Dual Core Processor

2 GB RAM

10 GB HDD

Mouse

Keyboard

Monitor

TEJAS PARMAR Page | 8


PAINT MANAGEMENT SYSTEM

 SOFTWARE SPECIFICATION:

Operating System Windows 7


Front-End Tool Visual Basic Studio 2008
Back-End Tool SQL Server 2005

Along with the hardware use into eh system it’s require software to make a system as
well as to run the system with the computer hardware where the collection of different
types of hardware into specific type can form a computer but it cannot execute the dif-
ferent process on its own. For efficient and proper working for any system software
must be installed .this software in the form of operating system or application software.
To make the system one also need to use software.

Vb.net

Visual Studio is an integrated development environment from Microsoft .It is used to de-
velop console and graphical user interface application along with windows forms appli-
cation, websites web applications and web service in both native codes together with
managed code for all platforms supported by MS Windows

Features of visual studio


Code editor
Debugger
Designer
Other Tools
Properties Editor
Date Explorer
Text Generation Framework

TEJAS PARMAR Page | 9


PAINT MANAGEMENT SYSTEM

Vb.net is a version of Microsoft Basic that was designed, as part of the company’s .net
product group, to make web services application easier developer.
Vb version on visual basic launched by Microsoft in 2008.The latest version is Visual
Basic 2010, launched second last year.VB2008 is almost similar to visual basic 2005
but it has added many new featured.
Learn VB2008. In fact. If you are similar with visual basic 6, you can learn VB2008 ef-
fortlessly because the syntax and interface are similar.

According to MS VB.net was reengineered rather than released as vb 6 with added fea-
tures , to facilitate making fundamental change to the language .VB.net is the first full
object oriented programming version of visual basic and as abstraction ,inheritance
,polymorphism and aggregation.

SQL Server:

SQL servers released in October 2005.it conclude native support for managing XML da-
ta, in addition to relational data.

SQL server also includes, the many type’s services:

Replication services
Analysis services
Reporting services
Notification services
Integration services

TEJAS PARMAR Page | 10


PAINT MANAGEMENT SYSTEM

Let’s takes a brief look at each:-

SQL server replication services are used by SQL server to replicate and syn-
chronize database objects, either in entirely or a subset of the objects database
across the network.
SQL server analyses add data capabilities for SQL server database. Analysis
services support the XML for analysis standard as underlying communication
protocol.
SQL server reporting services is report generation environment for data gathered
from SQL server database. it is administrated via a web interface.
originally introduced as a post-release for SQL server 20200, notification services
was bundled as a part of the MS SQL server platform for the first and only time
with SQL server 2005.
SQL server integration services are used to integrate data from different data
sources .it is used for the capabilities for SQL server for data warehousing
needs.

MS SQL server is full featured relational database management system (RDBMS)


that offers a verify of administrative tools to easy the burdens of database develop-
ment, maintenance and administrator

It covers six of the more frequently used tools:

TEJAS PARMAR Page | 11


PAINT MANAGEMENT SYSTEM

Enterprise manager
Query analyzer
SQL server Profiler
Service manager
Data transformation services
Books online

Let’s take a brief look at each:


Enter pries manager is the aim administrative console for SQL server installation.
it provides you with a graphical “birds eye” view of all the SQL server installation
on your network .You can perform high-level administrative function that effect
one pr more servers .Schedule common maintenance task pr creates and modi-
fies the structure of database.
Query analyzers offer a quick and method for performing queries against any of
your SQL server databases. it’s a great way to quickly pull information out of a
database in response to user request ,test quires before implementation them in
other application ,create/modify stored procedures and executes administration
tasks.
SQL profiler providers a window into the inner working of your database perfor-
mance in real time. SQL profiler allows you to capture and replay system ”traces”
that log various activities. It’s a great tool for optimizing databases with perfor-
mance issues or troubleshooting particular problems.
Service manager is used to control the MS SQL server, MSDTC (Microsoft Dis-
tributed Transaction Coordinator) and SQL server agent processors. An icon for
this service normally resides in the system tray of machines running SQL server.
You can use service manager to start, stop or pause any one of this service.
with release, Book Online are now even more routes to introduction in books
online .You can find information by:

1. Navigating the table of contents


2. Looking keywords in the index

TEJAS PARMAR Page | 12


PAINT MANAGEMENT SYSTEM

3. Searching on words and phrases in local and online help topics and fil-
tering the search result if desired.
4. Browsing a dynamically generated list of context department topics in
the dynamic help window.
5. Browsing a categorized set links to help with common user tasks.
Data services, The SQL server database engine sets file access permission on
the physical data and log files of each database to specific accounts. The per-
missions prevent the file from being tampered with should they reside in a direc-
tory that has open permission.
File access permission are set during any of the following database opera-
tion:
1. Creating
2. Attaching
3. Detaching
4. Modifying to add new file
5. Backing up
6. Restoring

TEJAS PARMAR Page | 13


PAINT MANAGEMENT SYSTEM

DATA FLOW DIAGRAM

 DFD stand for data flow diagram

 DFD also known as a “Bubble Chart"

 Data flow diagram is graphical tool defining system input, Process and output.

 It represents flow of data through the system.

 DFD are used modern is a graphical methods of system analysis.

 It is used as a structure analysis tool.

 DFDS server two purpose -:

1. Provide graphical tool which can be used by the analyst to explain his under-
standing or them system to the user.

2. They can be reality converted into a structure chart which can be used in de-
sign.

TEJAS PARMAR Page | 14


PAINT MANAGEMENT SYSTEM

Symbol used in DFDS-:


1. Process-: Here flow data is transformed E.g. forms distribution preparing merit,
etc.

2. External Entity-: A source or destination of data, which is external to the system.


E.g. Student, committee, etc

3. A Data flow-: it is packet of data. It may be in the form of fg document

4. Data store-: Any store data but with no reference to the physical Method of stor-
ing.

TEJAS PARMAR Page | 15


PAINT MANAGEMENT SYSTEM

Context Level

Request order Request for product & Info


Customer Admin

Paints Information

Billing
Paint Man- Payment
agement
Payment System Supplying paints

Place & order Suppliers

TEJAS PARMAR Page | 16


PAINT MANAGEMENT SYSTEM

Zero Level DFD


Purchasing
paints
Customer

Customer
Details

Give the
Product 1.0
Sales Record details
Payment Process Sales Records

Sales Details

Check the stock Feed back

Suppliers 2.0 Suppliers


Place an Order Purchase Supplies
Process Purchase Detail
Supplying Paints

Billing
Payment

TEJAS PARMAR Page | 17


PAINT MANAGEMENT SYSTEM

LEVEL-1 FOR PROCESS 1.0(SALES PROCESS)


Purchase Paints
Customer

Billing
1.1
Payment Retail Retail Records Retailing
Sale

Place an Order 1.2


Whole Whole Sale
Billing Sale Details
Payment

Order Wholesale
Details Detailing

1.3
Inventory
Supplying Paints
Management Retails Details
System

TEJAS PARMAR Page | 18


PAINT MANAGEMENT SYSTEM

Place & Order


Billing 2.1
Placing order
& managing Order Details Purchase
Payment Master
Organization
Paints
Feed back Master
2.2
Warehous-
ing
Receiving
Department
Suppliers Information
Suppliers
Of product
Master

2.2
Warehous- Paint details Paints
Supplying paints ing Master
Department

TEJAS PARMAR Page | 19


PAINT MANAGEMENT SYSTEM

Database Layout

 Admin :

Field Name Data Type Constraint Description

first_name varchar(50) Allow Nulls Describes First name Of User


Describes Last name Of User
last_name varchar(50) Allow Nulls
Describes Mobile Number Of
mob_no numeric(10,0) Allow Nulls
User
Describes Address Of User
address varchar(50) Allow Nulls
Describes Email Of User
email varchar(50) Allow Nulls
Describes Gender Of User
gender varchar(20) Allow Nulls
Describes Birthdate Of User
dob datetime Allow Nulls
Primary Key,
username varchar(50) Describes username
Not Null
Describes password of user
password varchar(50) Allow Nulls
Describes Password for verifi-
retype_pass varchar(50) Allow Nulls cation of userid

 This table is used to store User’s Information, who access the system.
 This table stores the data of Admin_Registration Form.
 Here, the username is the primary key.

TEJAS PARMAR Page | 20


PAINT MANAGEMENT SYSTEM

 Customer :

Field Name Data Type Constraint Description

Primary Key,
cid numeric(18,0) Describes Customer ID
Not Null
Describes First name Of
first_name varchar(50) Allow Nulls
Customer
Describes Last Name Of
last_name varchar(50) Allow Nulls
Customer
Describes Mobile No Of
mob_no numeric(10,0) Allow Nulls
Customer
Describes Address Of
address varchar(50) Allow Nulls
Customer
Describes Gender Of
gender varchar(10) Allow Nulls
Customer
Describes Birthdate Of
dob datetime Allow Nulls
Customer
Describes Email Of Customer
email varchar(50) Allow Nulls

 This table stores all the details of customer, who buy the products.
 This table stores the data of Customer_Registration Form.
 Here, the cid is the primary key.

TEJAS PARMAR Page | 21


PAINT MANAGEMENT SYSTEM

 Supplier :

Field Name Data Type Constraint Description

supplier_no int Not Null Describes No of Supplier


Primary Key,
supplier_id int Describes Supplier's ID
Not Null
Describes First name Of
first_name varchar(50) Allow Nulls
Supplier
Describes Last Name Of
last_name varchar(50) Allow Nulls
Supplier
Describes Gender Of
gender varchar(20) Allow Nulls
Supplier
Describes Address Of
address varchar(50) Allow Nulls
Supplier
Describes Mobile Number Of
mob_no numeric(10,0) Allow Nulls
Supplier
Describes Email Of Supplier
email varchar(50) Allow Nulls
Describes State Of Supplier
state varchar(50) Allow Nulls
Describes Supplier's Compa-
company_name varchar(20) Allow Nulls
ny Name

 This table stores all the details of Supplier, who supply the products.
 This table stores the data of Supplier_Registration Form.
 Here, the supplier_id is the primary key.

TEJAS PARMAR Page | 22


PAINT MANAGEMENT SYSTEM

 Stock :

Field Name Data Type Constraint Description

Primary Key,
stock_id int Describes Stock's ID
Not Null
supplier_id int Not Null Describes Supplier ID
Describes Code of item
item_code numeric(18,0) Allow Nulls
Describes Type of item
item_type varchar(50) Allow Nulls
Describes Paint Color Name
paint_color varchar(50) Allow Nulls
Describes Company Name
company_name varchar(50) Allow Nulls
Describes Purchase Date
purchase_date datetime Allow Nulls
Describes Expire Date
expire_date datetime Allow Nulls
Describes Liters
liters varchar(50) Allow Nulls
Describes Quantity
quantity numeric(18,0) Allow Nulls
Describes Price
price numeric(18,0) Allow Nulls
Describes Total Price
total_price numeric(18,0) Allow Nulls

 This table stores all the details of Products/Items.


 This table stores the data of Stock Form.
 Here, the stock_id is the primary key.

TEJAS PARMAR Page | 23


PAINT MANAGEMENT SYSTEM

 Purchase :

Field Name Data Type Constraint Description

Primary Key,
bill_no numeric(18,0) Describes Bill Number
Not Null
supplier_id int Allow Nulls Describes Supplier's ID
Describes Code of item
item_code numeric(18,0) Allow Nulls
Describes Type of item
item_type varchar(50) Allow Nulls
Describes Paint Color Name
paint_color varchar(50) Allow Nulls
Describes Company Name
company_name varchar(50) Allow Nulls
Describes Purchase Date
purchase_date datetime Allow Nulls
Describes Liters
liters varchar(50) Allow Nulls
Describes Quantity
quantity numeric(18,0) Allow Nulls
Describes Price
price numeric(18,0) Allow Nulls
Describes Total Price
total_price numeric(18,0) Allow Nulls

 This table is used to store details of purchased products from Supplier.


 This table stores the data of Purchase Form.
 Here, the bill_no is the primary key.

TEJAS PARMAR Page | 24


PAINT MANAGEMENT SYSTEM

 Sales :

Field Name Data Type Constraint Description

Primary Key,
bill_no numeric(18,0) Describes Bill Number
Not Null
Describes Name Of
customer_name varchar(50) Not Null
Customer
Describes Address Of
address varchar(50) Allow Nulls
Customer
Describes Mobile No Of
mob_no numeric(10,0) Allow Nulls
Customer
Describes Code of item
item_code numeric(18,0) Allow Nulls
Describes Type of item
item_type varchar(50) Allow Nulls
Describes Paint Color Name
paint_color varchar(50) Allow Nulls
Describes Company Name
company_name varchar(50) Allow Nulls
Describes Sales Date
sale_date datetime Allow Nulls
Describes Liters
liters varchar(50) Allow Nulls
Describes Quantity
quantity numeric(18,0) Allow Nulls
Describes Price
price numeric(18,0) Allow Nulls
Describes Discount
discount numeric(18,0) Allow Nulls
Describes Total Price
total_price numeric(18,0) Allow Nulls

 This table is used to store details of our sales products with customer infor-
mation.
 This table stores the information of Sales Form.
 Here, the bill_no is the primary key

TEJAS PARMAR Page | 25


PAINT MANAGEMENT SYSTEM

Design Layout

 Login Form:

 It is a login form
 It contains the login after giving the valid user id & password it will let you access
the system.
 If the user id & password are incorrect then it will not let access this system .

TEJAS PARMAR Page | 26


PAINT MANAGEMENT SYSTEM

TEJAS PARMAR Page | 27


PAINT MANAGEMENT SYSTEM

 MDI Form:

 It is a main screen.
 The first screen is a main screen. In this we can see the whole work of system.

TEJAS PARMAR Page | 28


PAINT MANAGEMENT SYSTEM

 Admin Registration Form:

 This is the Admin Registration form.


 In this form you can add the details of Admin/User.

TEJAS PARMAR Page | 29


PAINT MANAGEMENT SYSTEM

TEJAS PARMAR Page | 30


PAINT MANAGEMENT SYSTEM

 Customer Registration Form:

TEJAS PARMAR Page | 31


PAINT MANAGEMENT SYSTEM

 This is the Customer Registration form.


 In this form you can add the details of customer.

TEJAS PARMAR Page | 32


PAINT MANAGEMENT SYSTEM

 Supplier Registration Form:

 This is the Supplier Registration form.


 In this form you can add the details of customer.

TEJAS PARMAR Page | 33


PAINT MANAGEMENT SYSTEM

TEJAS PARMAR Page | 34


PAINT MANAGEMENT SYSTEM

 Stock Form:

TEJAS PARMAR Page | 35


PAINT MANAGEMENT SYSTEM

 This is the Stock form.


 In this form you can add the details of Products.

TEJAS PARMAR Page | 36


PAINT MANAGEMENT SYSTEM

 Purchase Form:

TEJAS PARMAR Page | 37


PAINT MANAGEMENT SYSTEM

 It is a purchase form.
 In this form you can add the details of purchased stock.

TEJAS PARMAR Page | 38


PAINT MANAGEMENT SYSTEM

 Sale Form:

TEJAS PARMAR Page | 39


PAINT MANAGEMENT SYSTEM

 It is a Sale form.
 In this form you can store details of our sales products.

TEJAS PARMAR Page | 40


PAINT MANAGEMENT SYSTEM

 Stock Report:

TEJAS PARMAR Page | 41


PAINT MANAGEMENT SYSTEM

 Purchase Report:

TEJAS PARMAR Page | 42


PAINT MANAGEMENT SYSTEM

 Sales Report:

TEJAS PARMAR Page | 43


PAINT MANAGEMENT SYSTEM

 Supplier Report:

TEJAS PARMAR Page | 44


PAINT MANAGEMENT SYSTEM

Testing Procedures
Software testing is a critical element of software quality assurance and
represents the ultimate reviews of specification, design and coding. The testing
phase involves the testing of the system using various test data; preparation of
test data plays a vital role in the system testing. After preparing the test data, the
system under study is tested using those test data, and errors found are correct-
ed and corrections are recorded for future references. Thus a series of testing is
performed before the system is ready for implementation.
 Various types of testing carried out on the system are:

 Validation testing
 Output testing
 User Acceptance testing

Validation testing:
Validation and verification is major part of testing
Validation : The process of evaluating software at the end of its development
process to ensure that it is free from failures and complies with its requirements.
Verification : Verification approaches attempt to identify oviducts faults or er-
rors which give rise to failures.

Validation and Verification Techniques:


First, the validation and verification objectives for our project were decided. Dur-
ing this stage, we have to consider various aspects like constraints, complexities
etc. The objectives of validation and verification is to be systematic and technical
evaluation of software and their associated products of development .For this
purpose, at the end of the development process, it is very much required to do
testing to ensure that the software requirements are compete.

 Reviews :
TEJAS PARMAR Page | 45
PAINT MANAGEMENT SYSTEM

It is always very much required to review a project at the end of phase to


determine whether the requirements are establish, design concepts and
specification have been met or not.

For example, if tax rates changes are required, the it should be possible to
do so.

 Inspection or Walkthrough :
An inspection or walkthrough is a detailed examination of the product on a
step-by-step basis. All program codes are subject to review. The purpose
is to find error. The project leader reviews the code to check its functionali-
ty.

 OUTPUT TESTING :
After performing validation test, the next phase is the output test of the system
because no system can be useful if it does not produce the desired output on the
desired format. By considering the format of reports, they are generated or dis-
played, and tested. Here, output format is considered in two ways; one so on the
screen and the other is in the printed form.
 USER ACCEPTANCE TESTING :
User Acceptance test of a system is the factor for the success of the system. The
system under consideration is listed for user acceptance by keeping in constant
touch with the perspective user of the system at the time of design, development
and making changes whenever required. This is done with regards to the follow-
ing points.
 Input screen design
 Output design
 Menu driven system

TEJAS PARMAR Page | 46


PAINT MANAGEMENT SYSTEM

System Implementation

The process of ensuring that the information system is operational and


then allowing users to take over its operation for use and evaluation is called sys-
tem implementation.

Implementation includes all those activities that take place to convert from
the old system to the new. The following are the aspects of implementation.

 Equipment Installation

1. Site Preparation
An appropriate location must be found to provide an operating environment
for the equipment that will meet the vendor’s temperature, humidity and dust
control specifications. The following factors should be taken into consideration
for space planning

- Space occupied by the equipments

- Space occupied by the people

- Movement of equipment and people

2. Equipment Installation
The equipment must be physically installed by the manufacturer, connect-
ed-to the power source and wired to communication lines if required.

3. Equipment checks out


The equipment must be turned on for testing under normal operating con-
ditions. The implementation team should devise and run extensive tests of its
own to ensure that equipments are in proper working condition.

TEJAS PARMAR Page | 47


PAINT MANAGEMENT SYSTEM

 Training Personnel
A system can succeed or fail depending on the way it is operated and used.
Therefore, the quality of training received by the personnel involved with the system
in various capacities helps or hinders the successful implementation of the infor-
mation system. Thus, training becomes a major component of system implementa-
tion. Training is offer imparted through hands-on learning techniques.

 Training System Operators


The system depends on the computer-centre personnel, who are responsible for
keeping the equipment running as well as for providing the necessary support ser-
vices. Their training must ensure that they are able to handle all possible operations,
both routine and extra-ordinary. Operator training just also involves the data entry
personnel. As part of their training, operators should be given both a trouble shoot-
ing list that identifies possible problems and remedies for them.

 Conversion Procedures
Conversion or changeover is the process of changing from the old system to the
new system. The following are the strategies for converting from the old system to the
new one

1. Direct Changeover
Conversion by direct changeover means that on a specified date, the old sys-
tem is dropped and the new system is put into use. Direct changeover can only be
successful if extensive testing is done beforehand. Direct changeover is considered
a risky approach to conversion.

2. Parallel Conversion

TEJAS PARMAR Page | 48


PAINT MANAGEMENT SYSTEM

This refers to running the old system and the new system at the same time, in
parallel. Both systems are run simultaneously for a specified period of time and the
results are examined. When the same results are gained over time, the new system
is put into use and the old one is stopped.

3. Gradual Conversion
Gradual conversion attempts to combine the best features of the earlier two
plans, without incurring the risks. In this plan, the volume of transactions is gradually
increased as the system is phased in. The advantages include allowing users to get
involved with the system gradually and the possibility of detecting and recovering
from the errors without a lot of downtime.

4. Modular Prototype Conversion


This approach to conversion uses the building of modular, operational proto-
types to change from old systems to new in a gradual manner. As each module is
modified and accepted, it is put into use. One advantage is that each module is
thoroughly tested before being used. Another advantage is that users are familiar
with each module as it becomes operational.

5. Distributed Conversion
This refers to a situation in which many installations of the same system are
contemplated, such as in banking or in franchises such as restaurants or clothing stores

TEJAS PARMAR Page | 49


PAINT MANAGEMENT SYSTEM

System Evaluation
System Evaluation is the process of assessing the performance of a complete
system to discover how it likely to perform in live market conditions.
These are several steps to evaluation:

 Defining personal trading goals.


 Risk Resonance.
 Parameter selection.
 Step testing.
 Calibration and final testing.

All of these steps from part of the trader's method and are carried out routinely
for any system rules he wishes to review. System traders spend a proportion of their
trading time trying to improve their existing systems and looking for new and differ-
ent ideas. This is interesting work when you have the essential tools to carry it out.

It is essential that any proposed system or changes is fully evaluated before be-
ing used in live trading. This is one reason why the successful traders do not pur-
chase system rules- How could they evaluate them beforehand to make sure they
were capable of meeting their requirements?

This is not the problem it might appear to be because it is not difficult to create
your own system rules. Furthermore, there are plenty of ideas around that can be
adapted.

System evaluation brings your complete system into play- not just the rules. This
is essential because the rules are only a part of your system and arguably they are
not the most important part. Your money management techniques are likely to have
a much bigger influence on your final results than any other aspect of your system.

TEJAS PARMAR Page | 50


PAINT MANAGEMENT SYSTEM

Proposed Enhancement

 The developed system is a client-server application. It can be ported on the


web in the later stages of development.
 The Paint Management System currently runs on the windows platforms only.
In the future enhancements the system can be ported on the other platforms.
 The system security is done by ORACLE. The security aspect of the system
is not covered in a detailed manner. That can be done in the future in the fu-
ture enhancements.

TEJAS PARMAR Page | 51


PAINT MANAGEMENT SYSTEM

Limitations

 We can use this system in a single computer only. Because this is desktop sys-
tem.
 To use this system, we need to install visual studio 2008.so if any computer hav-
ing less then 2GB ram. It will give worse performance.

TEJAS PARMAR Page | 52


PAINT MANAGEMENT SYSTEM

Conclusion

The data of the customer and also the other Item sales activities will be
kept in a structured manner. The retrieval, updating and the deletion of the data will
be much easier. Retrieval of the old information for the Item use will be much quick-
er. The documentation of the procedures will be well-designed and will-formatted.
The reports generated by the computerized system will be presentable and also un-
derstandable. The security of the important data will be provided in an efficient man-
ner. The change in one particular document will also be reflected to other related
documents. Customer will understand the system. He won’t have doubts about
working of the system. All the report generation will be done by the system.

TEJAS PARMAR Page | 53


PAINT MANAGEMENT SYSTEM

Bibliography

 Software Engineering By pankaj jalote published by pressman


 Steven Holzner; VB.NET Programming Black Book by Dreamtech publication
 Francesco Balena : Programming Microsoft Visual Basic.NET, Microsoft Press
 Bill Evjen, Billy Hollis, Bill Sheldon, Kent Sharkey and Tim McCarthy :
Professional VB 2005 with .NET 3.0

TEJAS PARMAR Page | 54

You might also like