Appendix_C_-_EPLC.pdf

Appendix C - Enterprise Project Life Cycle (EPLC) Requirements

Deliverable Ownership Approach Date

Planning Phase

Project Management Plan (PMP)

Program Project Lead, Contractor

The Program project lead and the contractor will prepare the PMP after discussions with COR and appropriate stakeholders. The plan will also address the scope, budget and schedule.

Within 45 days after task is exercised

Project Work Breakdown Structure (WBS)/Schedule

Contractor The Program Project Lead will develop a contract/project level WBS using Microsoft project software.

Within 45 days after task is exercised

Release WBS/Schedule Contractor The Program Project Lead will develop a schedule and detailed list of tasks for each of the major releases.

Based upon WBS

Project Budget Program Project Lead, Contractor

The contractor will develop a detailed budget prior to the commitment of resources for any development activities.

Within 45 days after task is exercised

Schedule Activity List Contractor The Program Project Lead will develop a detailed list of activities in consultation with the stakeholders.

Once a month

Resource Requirements Log

Contractor The Program Project Lead will develop a detailed software and hardware resource requirements as part of the infrastructure plan.

Based upon project plan

Risk Management Log Program Project Lead, Contractor

The Program Project Lead will log all the major project risks in the risk log/register and communicate it to the stakeholders

Monthly (as well as when new risks are identified)

Training Plan Program Project Lead, Contractor

A training plan will be developed which would provide details, including the training approach, training courses offered, duration of each course, intended audience(s).

Based upon project plan

Requirements Phase

Business Process Definition (BPD)

Contractor

Based upon discussions with the business owners, this document will capture the appropriate business processes. This information will be used to drive additional requirements elaboration activities such as the creation of screen mockups.

Based upon project plan

Business System Requirements (BSR) Document

Contractor A requirements document reflecting the high level capabilities and attributes of the desired solution will be created.

Based upon project plan

Release-Level Requirements /RTM

Contractor

This document will provide of the traceability of project level and release level requirements to the functionality contained within a specific release.

Based upon project plan

Logical Data Model Contractor

The logical data model provides a way to represent the business processes (and depicts the relationship between them). This document will be used to further elaborate the system requirements.

Based upon project plan

Deliverable Ownership Approach Date

Design Phase

Technical Design Document (TDD)

Contractor This document will explain the system design and architecture.

Based upon project plan

Physical Data Model Contractor

The Physical Data Model will take the logical data model information and create the physical data model structures. This will be developed in compliance with all appropriate EHBs naming conventions and standards.

Based upon project plan

Data Dictionary Contractor This document would explain the detailed definitions for all tables and columns.

Based upon project plan

Test Phase

Test Plan Contractor

The test plan would define the overall plan for performing the QA testing activities for the project. It would contain the proposed testing approach, types of testing that will performed, and details about the testing tools that will be used..

Based upon project plan

Test Scripts/Cases Contractor

Describes the detailed test scripts and test cases that will be used to validate that the system functions as expected. The contractor will work with the business owners to ensure that the test cases developed exercise all of the business areas/functions of the system.

Based upon project plan

Testing Defects Resolution Report

Contractor

An export of the issues from the issue tracker will be provided so the stakeholders can get the insight into the issues found during contractor’s internal testing and their latest status.

Based upon project plan

Implementation/

Deployment Plan Contractor

The implementation plan will provide details about how the system will be installed and made operational in the production environment for each of the major releases.

Based upon project plan

Operations & Maintenance Phase

Operational Readiness Review

Program Project Lead, Contractor

The Review will ensure that configuration and testing have been completed, documentation has been written and approved, deployment packages have been written and tested, security testing completed, and all other EPLC requirements have been met.

Based upon project plan

Lessons Learned Program Project Lead, Contractor

A lessons learned document will be created to understand what worked well (and what didn’t) in the last release so that this experience can be used to improve the techniques used to develop future releases/systems.

45 days after production implementation

Patch Release/Deployment Plan

Contractor This plan will provide the details about potential impacts/dependencies, and how to apply the patch in the production environment.

Based upon project plan