Table of Contents
Why architecture
For almost all businesses, information and communication technology (ICT or even shorter: IT) is an important resource to accomplish business goals. To utilize IT effectively and efficiently, an organization can choose to “work under architecture”.
What does it entail
To work under architecture, the organization has to implement certain methods. Initially, principles and assumptions will have to be drafted as well as requirements for the information flows. Applications and infrastructure should be rationalized, meaning they should be organized in such a way that they align with the business and information needs in the best possible way, both effectively and efficiently. This could involve adjusting the IT landscape, making new investments or perhaps phasing out or moving applications to the cloud. Whatever best suits the business and information needs. There is actually not a single way to describe working under architecture, these are just baselines of what it usually involves.
Implementing a “work under architecture” approach is no small task. One of the most important success factors is the commitment of the top management of the organization. Additionally, a clear vision for the future needs to be developed. The organization needs to define in which direction it wants to go. When an organization decides to work under architecture, it should define roles and tasks, as well as choose methods for creating architectural models.
The possible benefits
If the organization has the possibility to work under architecture, the benefits can be significant. In the default (anticipating) scenario, architecture can cause synergistic effects with developing and implementing different information systems. It can also lead to shorter project timelines and improved communication among project members who are implementing the changes.
References
- Jumelet, D. (2019). Bringing IT Architecture to Life.
- TOGAF | opengroup.org
- ArchiMate® 3.0 Specification (opengroup.org)