You are on page 1of 18

Overall approach

Identify Yearly processes Financial System

Test & Revise Strategy

Identify Resources Supporting Processes

Fin Date End Project Approach


Implement Strategy Identify Impacts Process wise

Strategy to Resolve Impact & Residual Impacts

Strategy to handle module modifications at AMS


Identify potential impact for all applications List all potential modules impacted Simulation test to confirm impact (if needed)

Develop test plan (ITPS and business)

Testing on modification (ITPS and business)

Module modification

Failed User signoff Pass Test result verification

Criteria to identify impact

Area Program Program Program Report Report OPC Application team assessment Vendors Apps Opns Chklist Operations Interfaces Database Mgmt Report Report Business Unit assessment Programs Programs Process Tools External

Assessment required Scan for date fields. Check if hardcoding/parameter of specific month exist. Check if hardcoding/parameter of 12 months exist Scan for accumulation of data. If annual data, ensure that it get resets correctly. Check for Year End, Annual, Cummulative reports. Check for hardcoding of "Year Ending " or others along this theme. Does the application have any year end jobs that are scheduled in OPC? Check with the various vendors if the application is impacted? Any special annual processing that had been planned? Any modifications required for that processing? Any annual stationery order processing that coincided with YE Financial Report printing? Need to re-align re-order dates. Any downstream/upstream jobs that need to be handled differently? Any changes in database management to align with new YE dates (archival, annual backup, etc) Check for Year End, Annual, Cummulative reports. Check for hardcoding of "Year Ending " or others along this theme. Does the business users have any self maintained programs that may be impacted? Does the business users submit any jobs that may be impacted? Does the business have any process that are impacted? Will IT change required to support the change in process? Does the business users have any analysis tools/systems that may be impacted? Are there any external parties that need to be notified of the new dates? Any change in processes?

e as Ph
Analysis Design Build Unit Test Integration Test Now-

Period A

Time Lines Period B

Period C

Subsystem Name Component Name Component Type

Impact Type

Brief Solution Description

Test environment Requirments

External Dependencies

Effort Estimates for Solution Implenation Coding Testing

Comments / Notes

Subsystem Name

Component Name Component Type

Component New/Existing

Design Document Path

Subsystem Name

Component Name Component Type

Component New/Existing

Design Document Path

Subsystem Name

Component Name Component Type

Component New/Existing

Changes Complete Y/N

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Changes Complete Y/N

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Unit Test Complete Y/N

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Unit Test Complete Y/N

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Signoff Obtained from Dependent System

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Signoff Obtained from Dependent System

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Production Move Activities completed

Comments/Observations

Subsystem Name

Component Name Component Type

Component New/Existing

Production Move Activities completed

Comments/Observations

Subsystem Name

Primary Support

Contact Information

Secondary Support

Contact Information

Special Instructions If any

Subsystem Name

Primary Support

Contact Information

Secondary Support

Contact Information

Special Instructions If any

You might also like