Software Lifecycle Management Plan

Software Lifecycle Management Plan

Complete the Software Lifecycle Management Plan to document the expectations for the resulting deliverable’s role in future research.

A software lifecycle management plan has three parts:

  1. An estimate of how long the work product will be maintained by EPRI in its current role?
  2. Identification of the program(s) and/or projects that will provide support to maintain the software to EPRI standards during its time as an EPRI product.
  3. A list of the names of EPRI personnel who will support the project during its time at EPRI and, also, any users.

If these three factors were already included in a previous document submitted to SQA, please reference that during the software submittal. Otherwise, please answer the following questions:

  1. Planned Development Life:
  2. How long (years) is this software in its current version planning to be available to the membership?

Comments:

  1. Are there plans to modify the software in the future? If so, what modifications are planned and what is the timeframe?

Comments:

  1. What are the plans for dispositioning this software (i.e. selling the software to a vendor for further development, licensing use of the software for 3rd parties to develop derivative products, archiving the software following the duration of research, integrating this work into another project, etc.)?

Comments:

  1. While this product is supported and distributed by EPRI, describe the relationship of this product among EPRI, the members and any contractors and licensees.

Comments:

  1. EPRI does reviews of products every 5 years to determine if it can be made available to the public. Does this software qualify to be publically released? In no, why?

Comments:

  1. Maintenance & Support:
  2. How will the ongoing support both technically and financially be handled after publication of this software?

Comments:

  1. If, following this release, a significant error or miscalculation is discovered, please briefly describe the procedure for how the problem would be fixed. What is the plan both from a technical standpoint and a funding standpoint?

Comments:

  1. What other projects will use this software? Are there support, implementation, and/or training efforts related to this software?

Comments:

  1. Usage and Deployment:
  2. Who is the target audience?

Comments:

  1. How many users are expected?

Comments:

  1. What role do 3rd parties have in the deployment of this product?

Comments:

  1. Project Closure:
  2. Planning, archiving etc.?

Comments:

Additional Comments:

EPRI CONFIDENTIAL INFORMATION: Not to be copied or distributed without written authorization from EPRI Revision: February 2015 (2015.1.0) Page 2 of 2

Top View