In today's competitive environment,companies are intensely concerned with the quality of their products and services. A successful organization constantly must improve quality in every area,including its information systems. Top management must provide the leadership,encouragement and support need for high quality IT resources. In short quality is needed every where. Both Quality Control and Quality assurance in software relates to 4th stage of system development called Implementation stage. A difference between quality control and assurance is provided below:
Quality Control in Software:
In software, quality control means to develop systems in such a way that they
are manufactured to meet or exceed the customer's requirements.These systems are often developed in combination with other engineering and business disciplines using a cross-functional approach.
Quality assurance in software:
No matter how carefully a system is designed and implemented,problems
can occur,especially in complex system. Rigorous testing catches errors in the implementation stage,but is much less expensive to correct mistakes earlier in the development process. The main purpose of quality assurance is to avoid problems or to detect them as soon as possible. Poor quality can result from inaccurate requirements,design problems,coding errors,faulty documentation and ineffective testing.
Quality Control in Software:
In software, quality control means to develop systems in such a way that they
are manufactured to meet or exceed the customer's requirements.These systems are often developed in combination with other engineering and business disciplines using a cross-functional approach.
Quality assurance in software:
No matter how carefully a system is designed and implemented,problems
can occur,especially in complex system. Rigorous testing catches errors in the implementation stage,but is much less expensive to correct mistakes earlier in the development process. The main purpose of quality assurance is to avoid problems or to detect them as soon as possible. Poor quality can result from inaccurate requirements,design problems,coding errors,faulty documentation and ineffective testing.
