06. We design IT architecture supporting the business sector
Why we design target IT architecture
To achieve maximum modularity and enable us to alter only small parts of the architecture instead of large units, which are expensive and time-consuming to replace.
Our activities at this stage
- Combining results from the design and all value streams (components, front-ends, back-ends, etc.) into one place of the conceptual image of IT architecture. A view of the unique and shared parts is not omitted. The Framework of Modern Architecture forms the foundation.
- Checking the interconnectedness in the overall design from chains to IT architecture. If numerous dependencies are found, especially in business functions, which can change frequently, both design patterns and clear rules of design and implementation are described. The primary owner is also determined.
- Designing a vision of an ideal target architecture, using technologies and principles that enable modularization, such as microservices, containerization, cloud solutions, etc.
- Deciding on the coexistence of legacy software with new systems.
- Analysing and describing the current state of architecture.
- Designing transition architecture in stages, for example, after six months, and the main initiatives leading to implementation.
- Target IT architecture
- A design for interim architecture in time
- A plan of initiatives for introducing target architecture
- Do not forget to adapt the company management, which requires a different form of management communication, focusing mainly on the benefits of the architecture, including aspects of these benefits parts.
- You do not need to switch off legacy applications immediately. But retain the simplicity of the portfolio. If they have the functions of the new application, you can shut down the old applications.
- A framework for modern architecture
- TOGAF ADM