Document: NRC Regulatory Guide
Document ID: aa450282-f5b0-4dd2-b41a-917a7491deb2
Document Type: regulatory_guide
Title: Preparing Probabilistic Fracture Mechanics (Rev. 0)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML2133/ML21334A158.pdf
Revision Date: 2023-05
Chapter: 
Section ID: RG-1.245
CFR Part: 
CFR Title: 

Content:
ting. 2.2.2 Probabilistic Fracture Mechanics Software Quality Assurance and Verification and Validation Documents The applicant should ensure that the SQA and V&V documentation for the PFM software is available for NRC review through in-person or virtual audits, if requested by the NRC. 2.3. Quantities of Interest and Acceptance Criteria The quantities of interest (QoIs) to be compared to the acceptance criteria should be clearly defined and include the following: • the units of measurement and time period, • the relationship to the outputs of the PFM software, • the acceptance criteria, and • if the QoI is a probability in the extreme tails of the distribution, a description of how this affected the analysis choices. The use of previously approved acceptance criteria (if already in existence for the specific application at hand) is encouraged but should be appropriately justified and explained. Specifically, the applicant should ensure that inherent assumptions and requirements of the source activity are respected, and that any apparent differences are reconciled. If there is no precedent for an acceptance criterion, the applicant should derive probabilistic acceptance criteria based on risk-informed decision-making principles in accordance with RG 1.200 and RG 1.174, if applicable, and describe the bases for the chosen acceptance criteria. If the PFM submittal includes more than one QoI, the applicant should document the above steps and information for each QoI. 2.4. Software Quality Assurance and Verification and Validation In general, PFM software to be used in regulatory applications should be developed under the framework of an SQA plan and undergo V&V activities. The SQA and V&V activities should depend on the safety significance, complexity, past experience (previous use in regulatory applications), and status RG 1.245 Revision 0, Page 12 of previous approval for the PFM software. The applicant should follow its SQA program and V&V procedures with