Verification and Validation of Simulation Models¶
Sargent, R. G. (2013). Verification and Validation of Simulation Models. Journal of Simulation, 7(1), 12-24.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Validation
- The structural insight is portable: a pharmaceutical trial validates efficacy in target patients; a software system validates against real attack vectors and user workflows; a scientific model validates against holdout empirical data; a policy validates through pilot deployment in target populations, a cross-domain transfer that Sargent (2013) systematizes for simulation models.
This sourceCross-domain treatment of the specification → procedure → evidence → judgment validation pattern as it transfers across simulation, engineering, and scientific modeling domains.
- The structural insight is portable: a pharmaceutical trial validates efficacy in target patients; a software system validates against real attack vectors and user workflows; a scientific model validates against holdout empirical data; a policy validates through pilot deployment in target populations, a cross-domain transfer that Sargent (2013) systematizes for simulation models.
Mechanisms¶
- Approximation Validation
- Its strength is that it lets a team keep the fast thing with a documented conscience: it converts "the shortcut is probably fine" into a bounded, checked claim with a stated validity domain, so the approximation can be trusted inside its stamp and refused outside it.
This sourceValidation can bound confidence in an approximation to a documented purpose, accuracy requirement, and domain of applicability.
- Its strength is that it lets a team keep the fast thing with a documented conscience: it converts "the shortcut is probably fine" into a bounded, checked claim with a stated validity domain, so the approximation can be trusted inside its stamp and refused outside it.
- Model Validation Ladder
- It is the natural backbone for validating many layers over time, and it maps cleanly onto the classic distinction between verification (did we build the model right) and validation (did we build the right model), letting each rung target one or the other.
This sourceModel verification checks correct implementation, while validation checks whether the model adequately represents its intended system and use.
- It is the natural backbone for validating many layers over time, and it maps cleanly onto the classic distinction between verification (did we build the model right) and validation (did we build the right model), letting each rung target one or the other.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:18ba379c83a0 · see in the full table