Abstract

Requirements validation makes sure that the requirements written in software requirements specification (SRS) must be complete and consistent and are according to the customer’s needs. It ensures the validity of user requirements by eliminating ambiguities and inconsistencies from SRS. Several techniques for requirements validation have been discussed in the literature. This paper gives an overview of requirements validation techniques which have been practicing in industry, which includes requirements inspections, requirements prototyping, requirements testing and viewpoint-oriented requirements validation. This paper also highlights pros and cons of these techniques. In requirements testing, special attention is given to TCD inspections.

References

• Kotonya, G, Sommerville, I, Requirements Engineering, John Wiley & Sons, New York, 1998.
• Thayer, R. & Dorfman, M. Software Requirements Engineering 2nd Edition, IEEE Computer Society Press, California, 1997.
• Gary E. Mogyorodi, “What are Requirements- Based Testing”, CROSS TALK The Journal of Defence Software Engineering, March 2003.
• Laitenberger O, “A Survey of Software Inspection Technologies”, Handbook on Software Engineering and Knowledge Engineering, Citeseer, 2002.
• Steven R. R.,Software Verification and Validation for Practitioners and Managers, Artech House Publishers, 2nd edition (August 1, 2001).
• Ackerman, A. F., Buchwald, L. S., and Lewsky, F. H., “Software Inspections: An Effective Verification Process”, IEEE Software, 1989, pp. 31-36.
• Sommerville I, Pete Sawyer, Requirements Engineering, John Wiley & Sons, New York, 1997.
• Siddiqi J, I. Morrey, R. Hibberd, G. Buckberry, “Towards a System for the Construction, Clarification, Discovery and Formalisation of Requirements”, proceedings of first international conference on Requirements Engineering, IEEE, 1994, pp.230-238
• Laitenberger O, Beil T, Schwinn T, "An industrial case study to examine a non-traditional inspection implementation for requirements specifications," presented at Proceedings of the Eighth IEEE Symposium on Software Metrics, Los Alamitos CA, 2002.
• Leite J.C.S.P, Freeman P.A, “Requirements validation through viewpoint resolution”, IEEE Transactions on Software Engineering, Vol 17, 1991, pp.1253-1269
• CMMI-PDT, "Capability Maturity Model Integration (CMMI), Version 1.1," in CMMI for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing Version 1.1 (CMMI- SE/SW/IPPD/SS, V1.1). Pittsburgh, 2002
• ISO/IEC, "Software Process Assessment TR 15504:1998," vol. 2004. http://www.sei.cmu.edu/iso-15504/: ISO/IEC, 1998.
• Gorschek T, Dzamashvili N - Fogelstrom, “Test- case Driven Inspection of Pre-project Requirements-Process Proposal and Industry Experience Report”, in proceedings of the Requirements Engineering Decision Support Workshop held in conjunction with the 13th IEEE International Conference on Requirements Engineering, 2005.
• Briand L.C, Emam K.E, Freimut B.G, Laitenberger O , “A comprehensive evaluation of capture-recapture models for estimating software defect content”, IEEE Transactions on Software Engineering, Vol 26, No 6, 2000, pp. 518-5
• Fagan M.E, "Design and Code Inspection to Reduce Errors in Program Development," IBM Systems Journal, vol. 15, 1976, pp. 182-211.
• Christian W.D, Projects in Computing and Information Systems, Pearson, 2005, ISBN 0321263553.
• Carolyn B. S, “Qualitative Methods in Empirical Studies of Software Engineering”, IEEE transactions on Software Engineering, Vol 25, No 4, July/August 1999