Target-State Architecture
Definition
A target architecture sets the framework for planning, assigning resources, and streamlining activities to reach a desired future state.
In essence, the target architecture is the blueprint for both enterprise architects and project managers to follow.
HOW?
- Set the Baseline Architecture
- Assess the baseline architecture based on TIME model
- Define Target State Architecture
Conduct meeting with various stakeholders
Understand of the application inventory and baseline architecture
Tolerate
(the application should be left alone and considered for future improvement)
Invest
(the applications worths investing in, yielding even better returns or seeing a further reduction in costs)
Migrate
(for applications that are low quality but provide high value to the business)
Eliminate
(for applications providing no business value, being unused or used minimally, or being based on obsolete software)
Business: provides a certain amount of values
Technical: high quality
Operation: doens't cost a lot to maintain
Business: recognizable values
Technical: stable and well archtiected
Operation: doesn't require much support
Business: high value
Technical: low quality
Approach
Shift users & data to an existing application then discard the instance
Develop a new application in replacement of this one
Plan
Decide
Execute
establishing the overall business objective(s)
ensuring all stakeholders are on board and moving in the same direction
forecast high-level changes to the IT infrastructure and get a fundamental grasp of the impacts that will need to be addressed
visualizing how short-term initiatives align with long-term business objectives
creating a transformation roadmap that takes into account more granular architectural changes
monitor the progress of evolving business objectives while at the same time measuring stages of completion on individual projects
document the IT repository