Phase I Software Needs Analysis and Selection
Needs Analysis – The first step in the software procurement process is to state the software needs. This is a somewhat iterative process, with more detailed needs and applications being defined as the analytical methodologies are being developed and mature with time, in order to guide corresponding revisions to the Software Requirements Specifications (SRS).
Software Evaluation and Selection – A software evaluation team formed of end users and code developers is created. This team evaluates the needs, time frames for development, and investigates. The process of commercially dedicating an item requires an in-depth understanding and knowledge of purpose and function of the item to be dedicated.
Phase II Technical Evaluation
A technical evaluation of the software, the source code, and the procedures/vendor that developed the software is performed at an in depth technical level. The review is focused on credibility of the organization and the quality of the software itself. The detailed technical review investigates the physical characteristics for the code (source code, platform); software performance characteristics (code models, features, correlations); and dependability characteristics (quality procures used in software development, user community base, personnel qualification and training, software testing and update processes, quality of the documentation). Once the software is confirmed to meet the commercial grade definition criteria the team determine how the critical characteristics are to be verified and tested in Phase III.
Phase III Code Testing, Assessment and Acceptance
Phase III focuses on the assessment and testing to commercially dedicate the software. In Phase III four activities are performed: Commercial Grade Survey; Receipt Inspection; Software Inspection; Software Acceptance Testing. Phase III starts with a receipt inspection where the as provided software is logged in the versioning control system. Followed by the software inspection which is performed to verify the quality of software products, including the computer code and associated documentation, against functional, quality, and regulatory requirements. The software test plan is developed following Software Verification and Testing Procedures which identified the test cases used for verification, figures of merit and acceptance criteria. Then the software acceptance testing is performed and documented in the acceptance text matrix for CGD.
FPoliSolutions commercial grade dedication process was created using US Regulations and nuclear industry guidance for our CGD process:
- U.S. Regulations
- 10 CFR 50, Appendix B, Criterion III, Design Control, and Criterion VII, Control of Purchased Products and Services
- 10 CFR 21, requires that a commercial-grade item be “dedicated” – a point-in-time when the item is subject to reporting requirements
- RG 1.203, “Transient and Accident Analysis”
- DG-1305, “Acceptance Of Commercial-grade Design And Analysis Computer Programs For Nuclear Power Plants”
- Nuclear Industry Guidance
- ASME NQA-1
- EPRI NP-5652, “Guideline for the Acceptance of Commercial-Grade Items in Nuclear Safety-Related Applications”
- EPRI 1025243, “Guideline for the Acceptance of Commercial-Grade Design and Analysis Computer Programs Used in Nuclear Safety-Related Applications”