V&A; III: verification and validation without independence: a recipe for failure

Authors:
James D. Arthur;Richard E. Nance
Affiliations:
Virginia Polytechnic Institute and State University, Blacksburg, VA;Virginia Polytechnic Institute and State University, Blacksburg, VA
Venue:
Proceedings of the 32nd conference on Winter simulation
Year:
2000

Citing 3
Cited 3

Independent verification & validation: a life cycle engineering process for quality software

Independent verification & validation: a life cycle engineering process for quality software
Evaluating the Effectiveness of Independent Verification and Validation

Computer
Software Verification and Validation: An Overview

IEEE Software

Improving the model development process: expanding our horizons in verification, validation, and accreditation research and practice

Proceedings of the 34th conference on Winter simulation: exploring new frontiers
Next generation modeling II - applications: improving the development process for eukaryotic cell cycle models with a modeling support environment

Proceedings of the 35th conference on Winter simulation: driving innovation
Building modeling tools that support verification, validation, and testing for the domain expert

WSC '05 Proceedings of the 37th conference on Winter simulation

Quantified Score

Hi-index	0.00

Visualization

Abstract

Verification and validation (V&V) is a prominent technical area within simulation, attested to by the 12 tutorial sessions (including five advanced) included in the past ten Winter Simulation Conferences (WSCs). In recent WSCs the issue of Independent V&V (IV&V) has drawn increased attention, with sessions examining the perceived lack of use and little concern for the technique evinced within the simulation community. The objectives of this paper are four-fold: (1) to examine the current picture in software systems development, (2) to review the rationale, role and expressed need for IV&V, (3) to identify the benefits attendant in the insistence on the "independent" status of the activity, and (4) to respond to the usual criticisms of negative impacts on cost and schedule. While the treatment is couched in the more general software systems context, we contend that simulations represent prime candidates for IV&V application.