Quality assurance:
Introduction :
Each product should be assured for quality. If quality is not there, no one could buy a product.
It is also same in software development. Each company is needed to assure its client for expected quality. It depends on the clients expectation, investment and some other common things. If your client expectations are low, then you should aim low. Because they could not create any serious complication when things go wrong.
Why should we aim high:
Whether the company may be big or small, it is the developers duty to assure quality up to the level of their client expectations. Actually, quality depends on the performance of other companies. If a clients previous company had provided excellent quality and in the next time you, in your turn, you have provide moderate quality according to the expectations of the client. Obviously, there could not be a chance of getting one more project from the same client. If is the reason one should always aim for high quality assurance.
Quality assurance should ensure following things:
- Time,Faults and cast spent on development should be minimized through scrutinize.
- Unrelated problems at the time of deployment should be separately enlisted.
What is quality:
Can quality be measurable? May not be perfectly. Generally, quality is decided on the basis of long term performance. When you go to buy a new bike, you may ride once or twice. The bike may give good feeing in these two attempts. But, you can not decide its quality in merely two attempts. When you buy it and uses for long term, then only you come to know actual problems about the bike.
In first attempt, you check for basic parts functioning and its pick up and mileage. If those things are right, you can expect the bike as good quality bike. It is same for web application also. If basic functions are good and smooth, then client assumes its quality as high. Later, in longterm use, if client faces any minor problems we can make it solve with our technical support.