28 DOE G 414.1-4
6-17-05
activities include reviews, inspections, assessments,
bservations, and testing. This Guide expands on ASME NQA-1-2000 acceptance testing
n,
n may
upplier assessments are important aspects of V&V. Assessments are covered in Section 5.2.4,
and all test activity deliverables
laced under configuration management.
e
g strategies that may be appropriate
for acceptance testing include equivalence class testing, branch and path testing, statistical-based
e
V&V activities should be performed by competent staff other than those who developed the item
being verified or validated.
42
V&V
o
activities to include more extensive V&V activities of reviews, inspections, assessments, and
observations as described in other consensus standards.
Reviews and inspections of software deliverables requirement specifications, procurement
documents,
43
software design, code modules, test results, training materials, user documentatio
and processes that guide the software development activities should be performed. The software
deliverables may be combined with other software or system documents. Traceability of the
software requirements to the software design should be performed.
44
As mentioned in the
development practice section, inspections can be formally implemented Fagan inspections,
walkthroughs, or desk checks. Verification of the software design, using one of the above
methods, should be completed prior to approval of the software for use.
45
This verificatio
be performed as part of the software development and implementation activity.
S
Procurement and Supplier Management, and Section 6, Assessment and Oversight.
Observations and testing can be performed during the development, factory or site acceptance
testing, installation, and operation (i.e., in-use testing)
46
of the software. Observations and testing
during development is discussed in Section 5.2.6, Software Design and Implementation.
Software testing activities should be planned and documented. Test cases and procedures,
including expected results, should be created. All test activity deliverables should be under
configuration management. Test results should be documented
47
p
Acceptance testing should include functional testing, performance testing, security testing, stress
testing, and load testing. Users’ guides, use cases, and operational profiles are instrumental in
identifying and detailing the positive test cases and procedures. Failure mode analyses can b
used for defining negative test cases and procedures. Testin
and boundary value testing.
Additionally, the system should continually be monitored to estimate its continuing reliability
and safety. Periodic testing of the operational system should be performed to detect any
degradation.
48
If testing is not possible, monitoring using quantitative measurements should b
performed.
42
ASME NQA-1-2000, op. cit., Part I, Requirement 3, Section 801.1, p. 16.
43
ASME NQA-1-2000, op. cit., Part I, Requirement 4, Section 300, p. 18.
44
ASME NQA-1-2000, op. cit, Part II, Subpart 2.7, Section 402.1, p. 106.
45
ASME NQA-1-2000, op. cit., Part II, Subpart 2.7, Section 402.1, p. 106.
0, op. cit., Part I, Requirement 11, Section 400, p. 29.
Requirement 11, Section 200, p. 29.
ction 400, p. 30.
46
ASME NQA-1-200
47
ASME NQA-1-2000, op. cit., Part I,
48
ASME NQA-1-2000, op. cit., Part I, Requirement 11, Se