|
Click here to open a Printer-friendly version of Process Table.
Click here to download a Microsoft Word version of Process Table.
Return to top of the page 
The EPRI project manager is responsible for driving the software development process, following the
general timeline as filled in by the project manager, and ensuring software quality. Project steps are completed in the order shown, starting at the top of the
Process Table, and ending at the bottom. Assign dates for your project to each process step and task.
The software developer, who may be either within EPRI or an outside contractor to EPRI, is responsible
for creating the software application and is responsible for software quality. All developers need to complete the steps shown in the Process Table above.
EPRI Corporate Software Quality is responsible for the development process quality checkpoints and for
software acceptance testing. The required EPRI Corporate Software Quality reviews and documents for your project
are listed on your Software Deliverables Requirements Form.
The users are defined as anyone (e.g., end-users such as clients, approvers such as the CEO or CFO, and system administrators such as IT Departments) who will use the completed software. Involving users as shown in the Process
Table above helps to make sure the software will meet their needs when it is released.
The Process Table steps above apply both to new software and to upgrades of existing software. All EPRI software
development, including web applications, is expected to follow these steps.
The items in this section may be required at the discretion of the EPRI project manager or EPRI management. These items represent software development best practices. EPRI strongly recommends that developers implement these in support of EPRI's commitment to deliver commercial quality software.
- Online help: Context-sensitive online help is recommended for both new software and upgrades. A user accessing this type of help reads a brief, focused message providing assistance for the screen being used. Context-sensitive online help is therefore different from simply displaying a relevant section of the User Manual.
- Additional examples showing more of the software's capabilities are recommended for both new software and upgrades. These examples expand upon the three required solved example problems or tutorial described above.
- Program code allows efficient modification.
- Software scales well to larger data files and networks.
- All displayed text is placed in one file: Placing all error messages and other displayed text in one file facilitates software maintenance for developers, and also eases future translation to local languages. Such a text file is used with a message program that manages variables from the application program and text from the file. This approach enables selected text file contents to be tailored as needed, and to display a variety of situation-specific messages to the user.
The links below provide added background on the software development process.
Return to top of the page
|
|
