Software Inspection
Capturing the Benefits of Requirements Engineering
IEEE Software
A framework for the measurement of software quality
Proceedings of the software quality assurance workshop on Functional and performance issues
Repeatable Quality Assurance Techniques for Requirements Negotiations
HICSS '03 Proceedings of the 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track1 - Volume 1
A Quantitative Software Quality Evaluation Model for the Artifacts of Component Based Development
SNPD-SAWN '05 Proceedings of the Sixth International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing and First ACIS International Workshop on Self-Assembling Wireless Networks
Design and code inspections to reduce errors in program development
IBM Systems Journal
| Hi-index | 0.00 |
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.