1、ANSI/ANS-10.4-2008verification and validation of non-safety-relatedscientific and engineering computer programsfor the nuclear industryANSI/ANS-10.4-2008ANSI/ANS-10.4-2008American National StandardVerification and Validation of Non-Safety-RelatedScientific and Engineering Computer Programsfor the Nu
2、clear IndustrySecretariatAmerican Nuclear SocietyPrepared by theAmerican Nuclear SocietyStandards CommitteeWorking Group ANS-10.4Published by theAmerican Nuclear Society555 North Kensington AvenueLa Grange Park, Illinois 60526 USAApproved October 28, 2008by theAmerican National Standards Institute,
3、Inc.AmericanNationalStandardDesignation of this document as an American National Standard attests thatthe principles of openness and due process have been followed in the approvalprocedure and that a consensus of those directly and materially affected bythe standard has been achieved.This standard w
4、as developed under procedures of the Standards Committee ofthe American Nuclear Society; these procedures are accredited by the Amer-ican National Standards Institute, Inc., as meeting the criteria for AmericanNational Standards. The consensus committee that approved the standardwas balanced to ensu
5、re that competent, concerned, and varied interests havehad an opportunity to participate.An American National Standard is intended to aid industry, consumers, gov-ernmental agencies, and general interest groups. Its use is entirely voluntary.The existence of an American National Standard, in and of
6、itself, does notpreclude anyone from manufacturing, marketing, purchasing, or using prod-ucts, processes, or procedures not conforming to the standard.By publication of this standard, the American Nuclear Society does not insureanyone utilizing the standard against liability allegedly arising from o
7、r afterits use. The content of this standard reflects acceptable practice at the time ofits approval and publication. Changes, if any, occurring through developmentsin the state of the art, may be considered at the time that the standard issubjected to periodic review. It may be reaffirmed, revised,
8、 or withdrawn atany time in accordance with established procedures. Users of this standardare cautioned to determine the validity of copies in their possession and toestablish that they are of the latest issue.The American Nuclear Society accepts no responsibility for interpretations ofthis standard
9、 made by any individual or by any ad hoc group of individuals.Requests for interpretation should be sent to the Standards Department atSociety Headquarters. Action will be taken to provide appropriate response inaccordance with established procedures that ensure consensus on theinterpretation.Commen
10、ts on this standard are encouraged and should be sent to SocietyHeadquarters.Published byAmerican Nuclear Society555 North Kensington AvenueLa Grange Park, Illinois 60526 USACopyright 2008 by American Nuclear Society. All rights reserved.Any part of this standard may be quoted. Credit lines should r
11、ead “Extracted fromAmerican National Standard ANSI0ANS-10.4-2008 with permission of the publisher,the American Nuclear Society.” Reproduction prohibited under copyright conventionunless written permission is granted by the American Nuclear Society.Printed in the United States of AmericaForewordThis
12、Foreword is not a part of American National Standard “Verification and Validationof Non-Safety-Related Scientific and Engineering Computer Programs for the NuclearIndustry,” ANSI0ANS-10.4-2008.!The purpose of this standard is to provide guidelines for the verification andvalidation VANSI0ANS-10.5-20
13、06, “Accommodating User Needs in Scientific and Engineer-ing Computer Software Development”;ANSI0ANS-10.2-2000, “Portability of Scientific and Engineering Software.”In addition, an effort has been made to maintain consistency in terminology andconcepts with various software standards being developed
14、 under the sponsorshipof the Institute of Electrical and Electronics Engineers, Inc., and to identifyareas of disagreement.Compliance with this standard does not substitute for compliance with regula-tory requirements. For example, any analysis that requires a 10 CFR Part 50Appendix B quality assura
15、nce program would still require one whether or not itconforms with this standard.Charles R. Martin was the working group chair for much of the development ofthis standard. His contributions are gratefully acknowledged.This standard has been written by Working Group ANS-10.4 of the AmericanNuclear So
16、cietys Standards Committee. The membership of this group duringthe preparation of the final drafts consisted of the following:A. O. Smetana Chair!, Savannah River National LaboratoryB. L. Kirk, Oak Ridge National LaboratoryJ. B. Manneschmidt, Oak Ridge National LaboratoryK. A. Morrell, Savannah Rive
17、r Nuclear Solutions, LLCC. R. Martin, U.S. Defense Nuclear Facilities Safety BoardSubstantial contributions toward the development of the earlier drafts of thisstandard have also been received from the following:H. Hunter, Oak Ridge National LaboratoryT. M. Lloyd, BNG Fuel SolutionsY. Orechwa, U.S.
18、Nuclear Regulatory CommissionD. Peercy, Sandia National LaboratoriesH. S. Hopkins, Lawrence Livermore National LaboratoryK. OKula, Westinghouse Safety Management SolutionsC. A. Sparrow, Mississippi State UniversityR. G. Quirk, U.S. Defense Nuclear Facilities Safety BoardR. C. Singleterry, Jr., NASA
19、Langley Research CenterJ. Pardo, Savannah River Nuclear Solutions, LLCD. Sparkman, U.S. Department of EnergyT. Austin, Bechtel NationalD. D. Brayton, Safer ServicesG. Danielson, U.S. Department of EnergyiJ. R. Shultz, U.S. Department of EnergyS. S. Seth, U.S. Department of EnergyR. C. Schrotke, Jr.,
20、 Battelle Northwest National LaboratoryR. W. Stevens, Jr., U.S. Department of EnergySubcommittee ANS-10, Mathematics and Computation, had the following mem-bership at the time of its approval of this standard:A. O. Smetana Chair!, Savannah River National LaboratoryB. R. Frank, Westinghouse Electric
21、Company, LLCJ. B. Manneschmidt, Oak Ridge National LaboratoryB. L. Kirk, Oak Ridge National LaboratoryR. C. Singleterry, Jr., NASA Langley Research CenterC. R. Martin, U.S. Defense Nuclear Facilities Safety BoardP. P. H. Wilson, University of Wisconsin-MadisonY. Orechwa, U.S. Nuclear Regulatory Comm
22、issionC. A. Sparrow, Mississippi State UniversityE. L. Quinn, Longenecker and AssociatesThe American National Standards Committee N17, Research Reactors, ReactorPhysics, and Radiation Shielding, had the following membership at the time itreviewed and approved this standard:T. M. Raby Chair!, Nationa
23、l Institute of Standards and TechnologyA. Weitzberg Vice Chair!, IndividualS. Anderson, Westinghouse Electric Company, LLCW. H. Bell, American Institute of Chemical EngineersAlt. R. D. Zimmerman, American Institute of Chemical Engineers!R. R. Brey, Health Physics SocietyR. E. Carter, IndividualD. M.
24、 Cokinos, Brookhaven National LaboratoryM. L. Corradini, National Council on Radiation Protection and MeasurementsE. Ehrlich, General ElectricB. K. Grimes, IndividualN. E. Hertel, Georgia Institute of TechnologyC. Heysel, McMaster UniversityW. A. Holt, IndividualW. C. Hopkins, IndividualM. A. Hutmak
25、er, Jr., U.S. Department of EnergyA. C. Kadak, Massachusetts Institute of TechnologyL. I. Kopp, IndividualP. M. Madden, U.S. Nuclear Regulatory CommissionAlt. A. Adams, Jr., U.S. Nuclear Regulatory Commission!J. F. Miller, Institute of Electrical and Electronics EngineersJ. E. Olhoeft, IndividualR.
26、E. Pevey, University of Tennessee-KnoxvilleW. J. Richards, National Institute of Standards and TechnologyC. T. Rombough, CTR Technical Services, Inc.T. R. Schmidt, Sandia National LaboratoriesS. H. Shepherd, IndividualA. O. Smetana, Savannah River National LaboratoryR. R. Tsukimura, Aerotest Operati
27、onsA. R. Veca, General AtomicsS. H. Weiss, National Institute of Standards and TechnologyAlt. T. J. Myers, National Institute of Standards and Technology)iiContentsSection Page1 Scope and objective . 11.1 Scope . 11.2 Objective 11.3 Guidance for applying this standard 12 Definitions . 13 Introductio
28、n and overview 24 Overview of V complexity;regulatory requirements; and American Na-tional Standards Institute0American NuclearSocietyANSI0ANS-10.5-2006, “AccommodatingUser Needs in Scientific and Engineering Com-puter Software Development,” intended use ofthe program.Application of this standard is
29、 expected to pro-vide material for use in a quality assuranceprogram. This standard does not recommend aparticular approach toward quality assurance.Questions about frequency of reviews or au-dits, resolution of discrepancies, or responsibil-ity for configuration control are not within thescope of t
30、his standard.2 DefinitionsIn the context of this standard, the followingdefinitions apply.non-safety-related: Software whose failurewould not create a hazard to a facility, worker,or member of the general public.validation: a! The process of testing a com-puter program and evaluating the results toe
31、nsure compliance with specified require-ments. b! The demonstration that the verifiedcomputer programand by inference the math-ematical model! are an adequate representa-tion of the physical phenomena.verification: The process of evaluating theproducts of a software development activity toprovide as
32、surance that they meet the require-ments defined for them.Verification and validation is abbreviatedthroughout the standard as Vmanagement plan;requirements specification;design specification;program documentationusers manual, tech-nical manual, etc.!;source code;integrated program;installation pack
33、age;test plan;VV the design specification isverified against the requirements specifica-tion; and the source code is examined to ensureconsistency with the design specification.The criteria presented in this document de-pend upon the availability of a document stat-ing the requirements that a comput
34、er programmust satisfy. Because of the research basis ofmost scientific program development, how-ever, it is often not possible to provide a prioria complete requirements specification. Whatconstitutes a valid answer or appropriate algo-rithm is often not known until after differentapproaches have b
35、een tried and their resultsevaluated. In such cases an iterative approachis recommended that allows the requirementsto be refined or respecified as results fromdifferent activities of program development be-come available. The final program documenta-tion and the final Vrequirements definition;desig
36、n;coding;integration and testing;installation;operation and maintenance.Table 1 provides a summary of Vthe general Vthe level of effort applied to each activity;the assignment of testing responsibilities;the procedures for incorporating V description of inputs in the ap-plication shall be provided t
37、o allow for testplanning.The VVschedule of VVVsummary of Vdevelopment materials evaluated;Vtools and techniques used;Vsecurity and control procedures followed;deviations from the VAmerican National Standard ANSI0ANS-10.4-20085Vanalyst who detected the discrepancy;description of the discrepancy;sever
38、ity rating high,medium,orlow!;impact of the discrepancy;recommended resolution.5.2 Verification of requirementsThe requirements specification forms the foun-dation for program development. It identifiesthe functions to be performed; the inputs, out-puts, and interfaces required; the accuracy andtimi
39、ng that must be achieved; the models tobe used; and the acceptance criteria for theprogram.The requirements specification also forms thefoundation for V2! Testing is performed by the software de-veloper. In addition, testing is performed byanother developer without reference to theoriginal developer
40、s test plan, test database,or test results;3! Testing is performed by the software de-veloper. In addition, an organizationally in-dependent Vapproach to conducting tests and evaluat-ing test resultsH18537 requirements to be tested,H18537 acceptance criteria for each requirement,H18537 methods to be
41、 used for conducting thetests,H18537 methods to be used to evaluate test re-sults and determine compliance with eachrequirement;American National Standard ANSI0ANS-10.4-20086test problem descriptions;test case specifications test cases are sim-plified test problems set up in order to dem-onstrate a
42、specific capability of the program!H18537 description of each test caseH18537H18537 unique identification,H18537H18537 objectives of the test case features tobe tested!,H18537H18537 input data,H18537H18537 expected results,H18537H18537 evaluation criteria,H18537H18537 relation to other tests,H18537H
43、18537 rationale for test setup,H18537H18537 hardware and software environmentin which tests will be run;plan for test databaseH18537 building,H18537 updating,H18537 maintaining,H18537 recording test output in the test database;test proceduresH18537 step-by-step instructions for execution oftest case
44、s, evaluation of test results, anddisposition of test output;planned reporting formats and proceduresH18537 discrepancy reports,H18537 test case log,H18537test report.Note that much of the information specified inthe test plan is developed later during programdevelopment. The test plan is updated as
45、 infor-mation becomes available.5.4 Verification of preliminary testplansTest plans prepared during program definitiondescribe the tests to be used to validate thesoftware product. A preliminary test plan de-fines the scope, objectives, and testing ap-proach; provides an initial description of thete
46、st problems, test cases, and test proceduresthat will be used; and describes the plannedreporting formats and procedures.Verification of a preliminary test plan is per-formed to ensure the following:1! The testing approach is consistent withthe scope and objectives stated in the plan;2! The tests be
47、ing considered will be ade-quate and sufficient for demonstrating thatthe program conforms with the requirementsspecification;3! The reporting formats and procedures areconsistent with the Vdetailed descriptions of each test case, in-cluding, as applicableH18537 identification of any programs that w
48、illsupply test case inputs,H18537 results of measurements, experimentaldata, analytical results, and other infor-mation to be used to evaluate the resultsof program calculations;methods for building, updating, and main-taining the test database;draft test procedures;additional information on reporti
49、ng for-mats and procedures, if applicable.6.4 Verification of updated test plansWhen a test plan is updated, it should be ver-ified to ensure the following:1! The tests being considered will be ade-quate and sufficient for demonstrating theprogram conforms with the requirementsspecification;2! The updated test plan is consistent withthe design specification and the preliminaryprogram documentation.Verification of a test plan is given in Checklist2 in Appendix A. Verification during designshould focus on those items identified in Sec. 6.3.The results of the test
