International Journal of Computer
Trends and Technology

Research Article | Open Access | Download PDF

Volume 4 | Issue 2 | Year 2013 | Article Id. IJCTT-V4I2P125 | DOI : https://doi.org/10.14445/22312803/IJCTT-V4I2P125

A Overview of Software Verification Validation and Selection Process

Omprakash Deshmukh, Mandakini Kaushik

Citation :

Omprakash Deshmukh, Mandakini Kaushik, "A Overview of Software Verification Validation and Selection Process," International Journal of Computer Trends and Technology (IJCTT), vol. 4, no. 2, pp. 176-182, 2013. Crossref, https://doi.org/10.14445/22312803/IJCTT-V4I2P125

Abstract

In recent years many Software verification and validation techniques are introduced. This curriculum paper provides an overview needed to understand in-depth curriculum modules in the verification and validation area. This paper also addresses planning considerations for V&V processes, including the selection and integration of V&V techniques throughout the software evolution process. Our work identified, along with their possible V&V objectives. The V&V process consists of numerous techniques and tools, often used in combination with one another. Due to the large number of V&V approaches in use, this paper cannot address every technique. Instead, it will analyze five categories of V&V approaches. These are: • Technical reviews, • Software testing, • Proof of correctness (program verification), • Simulation and prototyping, and • Requirements tracing. In the development of a software system, it is important to be able to determine if the system meets specifications and if its outputs are correct. This is the process of verification and validation (V & V) and its planning must start early in the development life cycle. Both aspects are necessary as a system meeting its specifications does not necessary mean it is technically correct and vice versa. There are many different V & V techniques which are applicable at different stages of the development life cycle. Thorough V & V does not prove that the system is safe or dependable, and there is always a limit to how much testing is enough testing. Therefore, extreme care should be taken in the development of software systems to make sure that the right amount of time is spent on V & V [7]. Software quality is achieved through the application of development techniques and the use of verification procedures throughout the development process Careful consideration of specific quality attributes and validation requirements leads to the selection of a balanced collection of review, analysis, and testing techniques for use throughout the life cycle. This paper surveys current verification, validation, and testing approaches and discusses their strengths, weaknesses, and life-cycle usage.

Keywords

verification and validation, system Testing, Module Testing, Regreation Testing, simulation and prototyping, requirement tracing, Proof of correctness.

References

[1] McCabe, T. J. and G. G. Schulmeyer. “System Testing Aided by Structured Analysis: A Practical Experience.” IEEE Trans. Software Eng. SE-11, 9 (Sept. 1985), 917-921.
[2] Petschenik, N. H. “Practical Priorities in System Testing.” IEEE Software 2, 5 (Sept. 1985), 18-23.
[3] Powell, P. B. “Planning for Software Validation Verification, and Testing.” In Software Validation,
[4] Beizer, B. Software System Testing and Quality Assurance. New York: Van Nostrand, 1984.
[5] Software Testing by Cognizant Technology Solution.
[6] Howden, W. E. Functional Program Testing and Analysis. New York: McGraw-Hill, 1987.
[7] Introduction to Software Verification and Validation SEI Curriculum Module SEI-CM-13- 1.1 December 1988.
[8] Paper by Lu Luo available at http://www.cs.cmu.edu/~luluo/Courses/17939Repo rt.pdF
[9] Rombach, H. D. Software Specification: A Framework. Curriculum Module SEI-CM-11-1.0, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa., Oct. 1987.
[10] Budgen, D. Introduction to Software Design. Curriculum Module SEI-CM-2-2.0, Software Engineering Institute, Carnegie Mellon University, burgh, Pa., Nov. 1988.
[11] Beizer, B. Software Testing Techniques. New York: Van Nostrand, 1983.
[12] Brown, B. J. Assurance of Software Quality. Curriculum Module SEI-CM-7-1.1, Software Engineering Institute, Carnegie Mellon University, Pittsburgh,Pa., July 1987.
[13] Petschenik, N. H. “Practical Priorities in System Testing.” IEEE Software 2, 5 (Sept. 1985), 18-23
[14] Morell, L. J. Unit Testing and Analysis. Curriculum Module SEI-CM-9-1.1, Software Engineering Insti- tute, Carnegie Mellon University, Pittsburgh, Pa., Dec. 1988..
[15] Gourlay, J. S. “A Mathematical Framework for the Investigation of Testing.” IEEE Trans. Software Eng. SE-9, 6 (Nov. 1983), 686-709. 16. Powell, P. B. “Software Validation, Verification and Testing Technique and Tool Reference Guide.” In Software Validation, Verification, Testing, and Documentation, S. J. Andriole, ed. Princeton, N. J.:Petrocelli, 1986, 189-310.