Often the question is phrased: What is IT Architecture?
IT Architecture is defined in two ways in the Dragon1 open EA Method:
- IT Architecture is the art and science of designing and building a total IT concept for an enterprise.
- IT Architecture is the total concept of IT of an enterprise; It is the set of concepts and their principles that are implemented or respected by the enterprise/organization to realize its strategy.
This total IT concept, when created correctly, enables strategy execution and digital transformation. It helps organizations manage complexity and deal with continuous change related to IT and its Business. If not created correctly, it will hinder innovation and fail to manage complexity.
IT Architecture (the total concept of enterprises' IT) and enterprise architecture (the total concept of an enterprise) in speech may have a similar meaning, but on paper, they are different.
IT Architecture Metamodel
IT architecture is a coherent whole of domains, functions, capabilities, services, concepts, principles, patterns, elements, components, norms, rules, and guidelines, and other entity classes. The visualization below shows the most important entity classes that comprise the meta-model of IT architecture in Dragon1.
IT Concepts
Every enterprise has IT concepts applied to it. To name a few:
- Automation
- Digitalization
- Client/Server computing
- Cloud Computing
- SaaS (software as a service)
- Webshop Sales
We can go on endlessly with all the IT concepts implemented today in organizations. The challenge is to have all these IT concepts coexist and collaborate so that they don't interfere or counteract, but instead work together and reinforce each other.
That is where IT architecture comes into play. IT architects will ensure that the IT concepts are coherent and consistent.
One of the major benefits of working with IT architecture is increasing the ability to implement new IT concepts quickly and successfully. Various organizations are progressing with their IT architecture to improve awareness and maturity in cybersecurity.
IT Architecture Diagram
IT architecture is a set of concepts. Therefore, an IT architecture diagram will visually represent the IT concepts. Below is an example of such an IT Architecture diagram.
The visualization shows concepts like Single Version of Truth, Loosely Coupling, and Server-Based Computing. The company's strategy or stakeholder requirements may necessitate the implementation of these concepts.
IT Architecture Principles
Read all about IT Architecture Principles here.
Every IT concept has a principle. The concept principle is the enforced way a concept works, producing results.
IT architects select concepts because of their principles. So, an architect can only select concepts they know the principles of.
When an IT concept is made part of an IT architecture (the total concept of IT), then its principle will become an IT architecture principle.
A widespread misunderstanding is that principles are the same thing as rules, norms, premises, or starting points.
Principles can be seen as mechanisms or patterns. Principles are about the way things work, but not what you should or must do. Principles are NOT normative statements.
Principles often get the names of their concept, but that isn't very clear. In the EA method, there is a distinction between the concept (the name) and the principle (the way it works). Just think of the coffee machine (concept) and the car engine (concept), and brewing hot water filter coffee (principle) or exploding gasoline to create power (principle).
Examples of well-known and often-used principles are:
- Loosely coupling - By building applications without using knowledge of how other applications internally work and only using the defined interfaces of other applications, the applications will always run even without the other applications being up and running. This will create a much more stable environment.
- Server-Based Computing - By having clients post computing assignments to the server instead of doing them themselves, the huge idle power and memory of the server are used more optimally. This will reduce the costs of acquiring new clients and servers, making it easier to utilize the investment.
- Single Storage of Data / Single Version of Truth - By storing data only once and preventing the storage and retrieval of copies, it is ensured that outdated or wrong versions of the truth cannot be used. This prevents mistakes in organizations, such as sending invoices to deceased clients.
Example IT Architecture
Suppose an organization has had a history of 40 years of introducing and implementing IT systems. Over the past 40 years, many IT systems have been updated and replaced; however, some old and outdated systems and technologies will likely remain.
Some IT systems may not support the strategy or integrate with other IT systems optimally.
An IT architect, in this case, would collect the requirements of the owner/client and stakeholders, collect the strategy, and get an overview of the current IT architecture and IT landscape.
Next, he would select the IT concepts needed for the future state and design a total IT concept (IT architecture). Next, he would design in detail how the various IT concepts should be applied and will have an impact on every current and new IT system.
Suppose the stakeholders have said they require a paperless office. This means that every piece of data, upon entry and exit, must be digital. This also means that every application within the organization must be able to interface with other applications. An IT architect would select the concept of Enterprise Application Integration and choose standards, like XML, for interfacing. Additionally, since everything is digital and increasingly interdependent, the architect adopted the concept of Loosely Coupling, which means that applications do not rely on each other to be alive or run. So, if one application is down or is replaced, the other application will continue to run.
The IT architecture at the conceptual level for this example may look like this:
The architect needs to detail this architecture at a logical and physical level so we know the actual impact on existing IT systems (applications, databases, networks, etc).
In practice, an IT architecture does not consist of only 3 IT concepts. It typically comprises at least ten domains, 100 functions, 100 services, 100 capabilities, and 100 IT concepts, principles, and patterns. Every concept provides the enterprise with one or more IT capabilities, which are implemented in one or more IT functions and delivered to actors through one or more IT services.
Creating an IT architecture is a Hard Job to do
Creating an IT architecture is not easy. It is a hard job to do. As an IT architect, you need to address numerous stakeholders, concerns, issues, politics, trends, and other matters simultaneously.
The Dragon1 open EA method provides a working process to ensure you approve your IT architecture so IT projects will use it.
To be a successful IT architect requires years of training and practice.