3.11 Finalize Target State Systems Environment
Objective
Perform knowledge transfer of As-is Environment and finalize the Initial Target State Systems Environment that captures all required interfaces, application, security/privacy, and data layers.
View Best PracticesTask Activities
-
Customer
Perform knowledge transfer to provider to gain an understanding of the customer’s As-Is Systems Environment including which interfaces to legacy systems will be required
-
Shared
Review initial Target State Systems Environment and compare against the provider’s standard solution to determine where gaps exist
-
Provider
Develop solutions for technical gaps where enhancements are required to systems and infrastructure and where new interfaces will be required
-
Shared
Assess gap solutions of technical environment based on cost and timeline implications and document impacts to release strategy
-
Shared
Finalize Target State Systems Environment, through technical reviews if necessary, to define the scope of the migration and at each release, if applicable
-
Shared
Report updates in governance meetings and Status Reports/Dashboards
3.11 Best Practices
- Leverage the current systems architecture and specification documents as a starting point
- Document critical interfaces between legacy systems and new systems including detailed data requirements and network requirements
Stakeholders
Customer
- Program Manager
- Business Owner
- Functional Lead
- Technical Lead/Solution Architect
- Interface Lead
- Functional SME
- Technical SME
Provider
- Program Manager
- Business Owner
- Functional Lead
- Technical Lead/Solution Architect
- Interface Lead
- Functional SME
- Technical SME
Inputs
- Vision Statement and Business Case
- Requirements Traceability Matrix (RTM)
- Existing Enterprise Architecture Documents & System Specifications
- Target State Systems Environment
- Customer’s As-Is Systems Environment
Outputs
- Validated and Updated As-Is Systems Environment
- Target State Systems Environment
- Status Reports/Dashboards
