Background issues
The Quality assurance is an essential activity for any business which produces products to be used through others. Prior to the 20 century quality assurance was the sole responsibility of the craftsperson who establish a product. The 1st formal quality assurance and control function was defined at Bell Labs in year 1916 and spread rapidly by the manufacturing world.
In during of early days of computing the year of 1950s quality was the sole responsibility of the programmer. The Standards for quality assurance for software were introduced in military contract software development during the year of 1970s and have spread rapidly into software development in the commercial world [IEE94] By Extending the definition presented earlier software quality assurance is a systematic and planned pattern of actions [SCH87] which are needed to ensure quality in software present the implication is that many various constituencies in an company have software quality assurance responsibility-software engineers project managers customers salespeople and the individuals who serve within an SQA group.
The SQA group serves as the customer's in-house representative who is the people who perform SQA must look at the software from the customer's point of view does the software adequately meet the quality factors. Have technical disciplines properly performed their roles as part of the SQA group? Has software development been conducted according to pre-established standards? Attempts to answer these and other questions to ensure which software quality are maintained.