All software delivered to members needs to be reviewed and accepted by SQA. This includes Production or Preproduction (e.g., Prototype, POC, Beta) software.
- Software Deliverable - Source code and build instructions must be provided prior to performing any approval related steps. Build instructions should be included in the repo which is setup for you by SQA under the appropriate project to your deliverable type, "EPRI-DevSecOps" or "SQA SWS".
- Software Deliverables - Static Application Scan Approval Request (SAST) is required prior to performing an SQA Submittal. If this is your first time performing SAST for your software you may need to perform the Static Application Security Scan Onboarding Request.
- Subscriber Website Deliverables - Upon completion of the SAST Approval a Qualys Scan Request (DAST) ticket will need to be completed.
- Software Deliverables - Once the applicable SAST and/or DAST approvals have been provided you will need to submit the SQA Submittal ticket.
Deliverable Process Notes
- Please be aware the Copyright Notice has been updated, the updated language applies to all 2025 deliverables.
- 2025 Deliverable Preproduction Submittal Deadline: Monday, September 1st
- 2025 Deliverable Production Submittal Deadline: Monday, November 3rd
- The Software Acceptance Form (SAF) as a word document is no longer utilized or accepted, the SQA Submittal ticket has integrated the form into the submittal process.
- EPRI developed software which has not previously been released to EPRI Members is required to be initially submitted to SQA as "Preproduction" unless an exemption is provided. If your software has previously been released, the "Preproduction" submittal is optional for all future releases.
- Computer-Based Training (CBT) Developers must follow the CBT LMS process and submit the files stated under the "Files to Be Provided to EPRI" section found in Step 5 of the CBT Specific Requirements. EPRI's Training Department is available for consultation for all aspects around developing CBTs.
Nuclear Specific
- Nuclear QMP Database Agreement Splash Screen - This splash screen is only required for Nuclear sector SWS that utilize databases
- ECM Supplemented Submittal - Once you have progressed your ECM workflow to the step "Perform SQA Receipt Evaluation and Place Deliverable in SQA Testing Queue", you should submit a ECM Supplemented Submittal ticket. This ticket facilitates the transfer of information from ECM to the Software Development Portal on your behalf so you do not have to, if desired to do it yourself you may open and submit an SQA Submittal ticket.
Submittal Packages Requirements
| 1. Software File(s) | X | X | X | X | X | X | X | |||
| 2. Software Manual | X | X | X | X | X | |||||
| 3. SWS Promotion Checklist | X | |||||||||
| 4. License Keys | X | X | X | |||||||
| 5. Answer Key | X | X | X | |||||||
| 6. Third Party Software (Software required to be installed to utilize your software). | X | X | X | X | X | |||||
| 7. Third Party Software Spreadsheet | X | X | X | X | X | X | X | X | X | X |
Preproduction Testing
- The Preproduction splash screen template can be found in the Copyright Notice document on pages 7-9, an example of what it may look like is additionally shown on the Preproduction Splash Screen page.
- Preproduction testing is important to ensure you have met user expectations before completing the project
- EPRI developed software which has not previously been released to EPRI Members is required to be initially submitted to SQA as "Preproduction" unless an exemption is provided. If your software has previously been released, the "Preproduction" submittal is optional for all future releases.
- Three preproduction testing options available:
- Option 1 – Standard: Standard: The SQA Team thoroughly reviews applicable EPRI product requirements
- Option 2 – Limited: The SQA Team partially reviews applicable EPRI product requirements. Takes shorter time to complete and provide feedback. The EPRI Project Manager accepts the risk that the release may contain anomalies that can later result in a Production Acceptance Test failure.
- Option 3 - Customer-Focused: The SQA Team partially reviews applicable EPRI product requirements and sends software to select group of users to participate in the development process.
- Note: The project manager may release with Option 2 and then request a complete review with Option 1. Option 3 does not replace Option 1.
Production Testing (Final Acceptance)
- Required for all software types, see Software Type Matrix for specific requirements.
- The software is ready to submit for the Production Acceptance test when:
- All preproduction test results have been addressed
- Developer testing has been completed and no further changes will be made
- All known errors are dispositioned
- The test cases run exactly as documented in the software documentation
SQA Team Does Not Perform
- Verification and Validation (V&V) testing
- Tests with or validation with real world data
- Exhaustive testing or "white box" (source code) testing
Who to Call for Help?
- SQA Team