1 / 19

ITMP Java Remediation Kickoff Meeting: <Application>

ITMP Java Remediation Kickoff Meeting: <Application>. July 26, 2016. Agenda. ITMP Background Project Overview Timeline Testing Communications Next Steps. ITMP Background. Infrastructure Technology Modernization Program Tree-trimming program for AEP’s information technology assets

yolandad
Télécharger la présentation

ITMP Java Remediation Kickoff Meeting: <Application>

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITMP Java Remediation Kickoff Meeting:<Application> July 26, 2016

  2. Agenda • ITMP Background • Project Overview • Timeline • Testing • Communications • Next Steps

  3. ITMP Background • Infrastructure Technology Modernization Program • Tree-trimming program for AEP’s information technology assets • Uplifting underlying technologies that support most software applications • Retiring technologies that no longer meet our needs • ITMP will • Create a more modern and secure environment • Position AEP more favorably for future technology implementations Read more at http://itmp

  4. Project Overview • Goal • Remediate <Application> from <V0.0> to <V0.0>. • <Application> Highlights • Used to search for MSDS documents stored in Asset Suite system • Includes only the search function (portal) • Does not include entry or storage of documents • About 17,500 users

  5. Project Overview • Stakeholders • Project Manager: VamsiGoli • Complex Manager: <Name> • Architect: <Name> • SMEs: <Name> • Infrastructure: <Name> • Cybersecurity: <Name> • Testing: <Name> • BU Approver(s): <Name>

  6. Project Overview • Known Risks, Issues, Constraints • DB2 – Uses JDBC drivers – there is a special license file under Weblogic class path that might need to change • No CEP and Tech Profile Documents • No functionality, deployment and testing documents. We assume Material Safety Data Sheets DOES NOT involve any vendor contracts

  7. Project Overview • Accounting Information • Project ID: ITSSV1430 • Capital Work Order: SITCP03801

  8. Project Flow

  9. Project Milestones If you use this AND the next slide, please be sure that the dates align.

  10. Project Timeline Defect fixing Test analysis Build test cases Test execution Fixes

  11. Testing - Consolidated two slides into one - Moved Testing Communicationsinfo to Project Communications slide • Key Steps • Meet with SMEs (IT & BU) to confirm business processes, rank risks • Create test cases where needed; will need SME validation • Perform sanity test on recompiled application with current framework • Perform system & integration test after framework has been upgraded • Engage SME for User Acceptance Testing (UAT) • Documents Needed • Test cases | Requirements • Documentation that covers functionality • User manuals or help documents

  12. Testing Timeline SME involvement will be high during Week 1 and during UAT testing

  13. Project Communications • Daily Standup Meetings: 10 a.m. Tuesdays(?) • Detailed status review of this project • Weekly Java Meetings: 9 a.m. Wednesdays (?) • High-level status review of multiple Java projects • Testing Communications • Initial meeting | defect triage | UAT • Special Meetings • Scheduled as needed

  14. Next Steps Is this needed ? • Application Demo • CEP & Technology Profile Creation • Cybersecurity Design Meeting • Requirements Meeting Schedule • PMP Review and Approval • Project Status Meeting Schedule • SVN Location / Server Details (IP) for Scan • Test Cases

  15. Questions?

  16. Appendix

  17. Definitions

  18. Overall Assumptions • Application training estimates are not included in this estimate. • A 3% warranty time is added currently to the build hours. • Primary Project Managers are located “Onshore” and an “Onshore” • Technical Lead will be assigned to manage the “offshore” team resources • AEP has existing hardware and software licenses to complete; No new costs are anticipated. • Decommissioning of the old application components (i.e., DB environments, OS environments, frameworks etc.) • Achieved after the post remediation. • Part of AEP's infrastructure team…no estimates are added to the currently estimated hours.

  19. Application Assumptions “Completed” work means production testing (warranty) period has begun. This work includes: • Production testing (warranty) period has begun • Requirements and Testing Matrix completed and approved • Transition to Complex for ongoing support • Service Now records updated to reflect change management Custom Applications • Retiring applications will be monitored by the ITMP team to ensure full retirement. • Automated Build Continuous Integration (ABCI/Hudson) repository will be used and ported to Maven for dependency management. • All source code will be put in Subversion repository for custom applications Vendor Applications • The common recommendation and strategy is to upgrade, retire or virtualize the vendor application. • For vendor application’s source code access may be limited

More Related