EPRI Software Types

EPRI Software Requirements Table

Requirements (1)

Software Type

Developer QA Plan and Developer Review (2)

Software Lifecycle Plan

Planning Documents:
Project Plan, Requirements, Functional Specifications (3)

Design Documents
User Interface, Software Design (3)

Test Plan

Manual or Help File

Beta Test by SET and users

Final Acceptance Test by SET

Internationalization

Localization

Certificate of Conformance

TYPE 1: E-Media -  PDF of reports; Office type files such as documents, spreadsheets., or databases with no, or limited, forms, macros, or internal programming; provided as a Deliverable or as a meeting or conference report.  Does not include daily work product.

4

7

TYPE 2: In-House - Any type of software, developed as a project, intended to be used by EPRI personnel only and not to be given to members or other customers.

10

10

10

10

10

10

10

TYPE 3: Prototype - Proof of Concept software (can be any type of software below)

10

10

5

10

X

7

X

TYPE 4: Service - Software created as a service project.  Includes development for hire, or customizations of existing software that will never be provided to other EPRI members or other customers.

10

10

10

9

10

9

10

9

TYPE 5: General Software - Covers Five Sub-Types

A. Software Component - DLLs, Web Services, Plug-ins to EPRI or third-party software.

B. VBA Type - Excel or Access with Non-Trivial VBA, Macros and/or Forms, MathCAD, LabView, etc.

C. Desktop - Basic Desktop Software

D. Client/Server - Desktop Software that communicates with a separate server application, such as a SQL database or other server application.

E.  Intranet - A Web based application that will be installed and hosted by the end user's company.

X

X

10

10

10

X

X

X

7

8

X

TYPE 6: Internet - A web based application hosted by EPRI.

X

X

10

10

10

X

6

6

7

8

X

Notes:

X.

This item is required.

1.

This table only addresses non-nuclear QA projects (i.e., 10 CFR 50 Appendix B).  Nuclear QA projects will have additional requirements per the applicable QA process.

2.

Most Recent QA Plan must be on file at time of Contract.  Developer QA Review Required for new Developers or at Manager SET discretion.

3.

The specific number of documents and total scope may be adjusted based on the overall project scope, but the key features and content must all be addressed. Developers to provide all documentation as a deliverable.

4.

Test may be performed by any independent person or SET (for published Deliverables, SET test is automatic).

5.

Prototypes are not required to have full manuals with tutorials or test cases.  Prototypes must be marked as such clearly in Splash Screens and About Screens and state that no support is provided. It is a proof of concept intended for customers to decide whether

the project will go on to becoming production software. Prototypes are for demonstration purposes only.

6.

Only the UI functionality is required to be tested for hosted Internet applications, not the installation and initial configuration.  Must meet all applicable EPRI Web Requirements.

7.

Internationalization means proper handling of international units, date, time, and number formats.  This requirement may be waived via written exemption by the applicable Sector VP.

8.

Localization means allowing for different languages.  This is only required if identified in the Lifecycle plan.

9.

Items are required unless specifically defined or excluded in contractual documents.

10.

Items are not required but highly recommended. Note that many customers require planning documents, test plans, etc. before they will install the software. Required customer documentation covered by this table shall be sent for SET review/testing during beta/final testing.

Additional Notes:

A.

Contract approval is required by Manager, SET, for software types 3 through 6.

B.

Use of third-party open source software is not permitted in distributed EPRI software without an exception from EPRI Legal and Mike Howard.

C.

Use of encryption in EPRI software must be communcated to the Manager, SET, as soon as it is known.

Acronyms:

CFR (Code of Federal Regulations); DLL (Dynamic Link Library); E-media is electronic media; PDF (Adobe's Portable Document Format); QA (Quality Assurance)

SET (Software Engineering Team); SQL (Structured Query Language); UI (User Interface); VBA (Visual Basic for Applications)