a quality assurance model for analysis phase
Quality Assurance should be carried out in each phase of the development life cycle. For high quality software, its requirements document should be a quality product. It should be complete, unambiguous and understandable. If the documents produced in the early life cycle phases are left over with defects then it results in a greater number of defects in the final product. A defect may appear to be a low risk defect in the early stages but it may take a very serious shape in latter phases. If the analysis people provide a quality document the development effort of the software is reduced to nearly 50 percent. This is why the quality assurance activity is more critically needed during the analysis phase. In this paper we have proposed a model for the quality assurance people for the systematic verification and assessment of the analysis phase.
quality assurance requirements software quality quality assurance techniques requirements analysis