Step 7 - Support & Maintenance

Support

EPRI Customer Assistance Center (CAC) provides first-line support, answering questions on logistics, delivery, installation, and overall software operation.

Maintenance (Bug Fix) Release Process

1. EPRI Project Manager must notify SSAS that a bug fix release will be submitted
2. Developer fixes the bug and in the application and documentation:
   • Increments the release version number (i.e., Version 1.0 to Version 1.01 or Version 1.1)
   • Updates the EPRI Product ID #
   • Updates the copyright year
3. Developer writes a developer's statement describing:
   • Specific changes that were made
   • Development testing performed (including regression testing done) to check that the changes worked
   • How SSAS can test the changes
4. EPRI Project Manager submits the bug fix release package to SSAS for testing. The package consists of the following items:
   1. Bug Fix Release with developer's statement
   2. Software Source Code with Source Code Build Instructions
   3. Software Acceptance Form (SAF) (119 KB)
   4. Certificate of Conformance (C of C)
5. SSAS tests and approves the bug fix for distribution
6. EPSC distributes bug fix software to an EPRI Project Manager designated bug fix tester to test using real world data
7. After acceptance by the designated bug fix tester, the software is distributed to EPRI customers
8. EPRI customers who received the previous release are automatically notified by the EPSC of the bug fix release

For software documentation (e.g., User Manual) changes only, the EPRI Project Manager may work with SSAS and the EPSC to replace the existing documentation or insert addendum sheets. Any replacement documentation needs to be clearly labeled with the current date, so that users can easily identify what documentation release they have.

Track the process and tasks of Step 7 using the Software Development Process Spreadsheet (40 KB).

Process Steps: <<< Step 6 | Step 1 >>>