New & Updated Software Requirements, Policies, & Forms

1. July 1, 2008: New Preproduction Distribution Process: A new Preproduction (e.g., Alpha, Beta, Prescreen, Prototype) distribution process is in place, which started on July 1, 2008. All preproduction software are now distributed through the EPRI Apollo System, not by the EPRI Project Manager or software developer. The new process introduces two new items to the Software Deliverable Requirements Form (SDRF). In addition, a preproduction splash screen is required for all preproduction software.
   
   
2. Security Vulnerabilities Usability Testing: A web application may contain many security vulnerabilities that can be exploited. Information can be read and databases corrupted if the vulnerabilities are not addressed. Click here to see examples of testing EPRI SET will perform.
   
   
3. Use of Open Source Software: Before software coding begins, the project managers must have agreement from Legal to utilize Open Source software which includes review and approval of the open source license. SET must be made aware of any potential use of third party tools which includes open source software as soon as the subject is being considered for incorporation into a software. EPRI software should use few third-party tools. All third party tools must be licensed to EPRI, have a non-restrictive license, and be maintained and supported by their developer/owner.

   As a general rule, EPRI will not permit incorporation of any software code licensed under "Restrictive License" in software developed either inside EPRI or under contract to EPRI. Requests to use code subject to open source licenses must be approved by EPRI Legal. Please see the open source policy ("Inbound Software Policy and Requirements for Use of Open Source Software Code") on insideEPRI (for EPRI Internal Use Only).
   
   

4. Windows Vista in addition to Windows XP and Windows 2000 are EPRI required platforms for all software deliverables due in 2008.
   
   
5. In 2008, a Certificate of Conformance is required from all developers (including internal developers). Internal developers as well as contactors must follow the EPRI requirements as noted on the Software Development Requirements website on epri.com. There are now two CofC templates: one for contractors and one for internal software developers.
   
   
6. In 2008, Mary McKenna is the point of contact for any R&D Group web application related questions. Paul Durdle will work with Mary on access control and scalability issues. Please review the web application requirements Guidelines for SWS and APPs.doc and fill out the web application request form at http://inside.epri.com/epri_com/webapplicationchecklistform.htm. Your application will be reviewed and any exceptions to EPRI standards and guidelines will require a justification statement to be reviewed by Mary McKenna before proceeding.
   
   
7. For software tracking purposes in Apollo, beta software will not be accepted for beta testing without an Apollo Product ID number. Before submitting your beta software, be sure to obtain an Apollo ID number. In addition, please review the beta submittal deadline in the 2008 Schedule section of the SET Newsletter.
   
   

1. Software Deliverable Requirements Form (SDRF) (SET will only accept the current revision -- currently dated 07/01/2008)



2. Software Description Template (SET will only accept the current revision -- currently dated 07/01/2008)



3. Software Acceptance Form (SAF) (SET will only accept the current revision -- currently dated 07/01/2008)