Uncia
FR / EN Demo

Glossary

IT architecture

IT architecture is the organized description of an organization's information systems: the business activities they serve, the applications that support them, the data they exchange and the infrastructure that hosts them. The term also names the discipline that decides how those parts fit together and where they should go next.

Updated

What is IT architecture?

IT architecture answers two questions: what are our systems made of, and where should they be heading. The word covers a result (models, diagrams, written principles) and a profession, that of the architects who arbitrate between what projects ask for and what keeps the whole coherent.

The scale varies widely. Across the whole organization, the usual name is enterprise architecture: which business capabilities exist, which applications serve them, which duplicates should be retired. For a single project, architecture describes one solution and ends up in an architecture document.

At either scale, architecture is judged by the decisions it informs. Can this application be decommissioned without breaking invoicing? Does this new requirement justify one more product, or does an existing application already cover it? A model that helps settle no question of that kind is a drawing.

IT architecture documentation therefore has a short shelf life unless someone owns it. The models are produced during projects and transformation programs, then consulted long after by people who assume they still describe what is in place.

What are the layers of IT architecture?

Most practices describe an IT estate in layers, from business down to technology.

The business layer describes what the organization does: processes, activities, actors and the information they handle. A functional layer, common in French practice, splits the estate into blocks of functions (manage orders, invoice, maintain the customer master) without saying which software delivers them. It is the layer that reveals when the same function is delivered three times. The application layer lists the actual applications, their components, their data and their exchanges. The technology layer, or infrastructure, describes what hosts the applications: servers, virtual machines, cloud services, network, storage, security.

Layers are only useful once linked. Knowing that a virtual machine hosts a component of an application that serves order entry lets you answer the question every incident raises: what stops if this machine goes down?

Other breakdowns exist and overlap. The mapping guide published by ANSSI, the French national cybersecurity agency, uses three visions that go from business to technology (business, application, infrastructure), split into six views: ecosystem, business, application, administration, logical infrastructure and physical infrastructure. The guide notes that this breakdown, designed for security purposes, is consistent with architecture standards.

Enterprise architecture, solution architecture, technical architecture: what is the difference?

Enterprise architecture works on the whole estate, over several years. The enterprise architect maintains the application portfolio, sets principles (a single source for the customer master, no new database engine outside the approved platform) and builds the roadmap. The audience is senior management, in IT and in the business.

Solution architecture works on one project. The solution architect turns a requirement into a design that fits the existing estate: which components, which interfaces with neighboring applications, which hosting. The solution architect takes the design to the architecture review board.

Technical architecture deals with shared platforms: virtualization, network, storage, cloud, directories, backup. The technical architect, or infrastructure architect, makes sure these platforms meet load and availability requirements, and that each project uses them as intended. Other specialties cut across the three levels, such as the security architect or the data architect.

In a mid-sized company, one or two people hold all of these roles at once. The distinction is still worth keeping, because a roadmap decision, a project design and a platform choice are not made at the same pace or with the same information. When someone introduces themselves as an IT architect, ask which of the three scales they work at.

TOGAF and ArchiMate: what are architecture frameworks for?

Two standards from The Open Group appear in most architect job descriptions, and they do different jobs.

The TOGAF Standard is an enterprise architecture methodology and framework. Now in its 10th Edition, it is divided into the TOGAF Fundamental Content and the TOGAF Series Guides. The Fundamental Content includes the Architecture Development Method (ADM), its techniques, a part on architecture content and a part on enterprise architecture capability and governance. The Series Guides adapt the whole to specific subjects, business capabilities and value streams among them. TOGAF tells you how to run architecture work. It does not impose a notation.

ArchiMate is the modeling language: element types, relationships and symbols to describe an enterprise from business to technology. Its current version, ArchiMate 4, was published on April 27, 2026.

Neither is mandatory. Many IT departments do useful architecture with a house vocabulary and a few written principles. Frameworks bring a shared language, valuable when several teams or suppliers need to understand each other, and a list of questions not to forget. In a mid-sized organization, keep the vocabulary and the steps that serve your decisions.

Which IT architecture tools exist, and how do you choose?

Spreadsheets and drawing tools (Visio, draw.io) are still the most common starting point. They cost nothing to adopt and are enough for a scope a few people know by heart. Their limit is that every diagram is an independent picture. Renaming an application means fixing twenty files, and nothing flags the one you forgot.

Modeling tools fix that: an element exists once and appears in several views. Archi, an open source tool, lets you create ArchiMate models on Windows, macOS and Linux. It is a good entry point for one architect or a small team.

An enterprise architecture tool adds a shared repository, access rights, multi-user work, application portfolio dashboards and roadmap scenarios. This family suits organizations with an established architecture team and a large application portfolio. It requires an implementation project and sustained data entry.

The CMDB describes what is in service, for operations and change management. It is not an architecture tool, but it often holds the link between applications and servers. The last family, mapping generated from sources, rebuilds the as-is from exports and environments.

To choose, start from the question you need to answer and from who will keep the tool current.

How do architecture and mapping relate?

Architecture mostly describes a target: what was designed and approved, or what the organization wants to reach in three years. IT estate mapping describes the as-is: what runs, where, and connected to what.

The two look identical on paper and diverge in practice. The diagram approved by the review board shows three application servers behind a load balancer. Production has had four since a peak in activity, one of them on an operating system version the document never mentioned. Neither description is wrong in itself: one states what was decided, the other what was done.

The gap between them is information in its own right. It exposes decisions that were never applied, changes that were never documented, and principles that teams work around. An architect who only sees models designs the next target on an assumed as-is. An operations team that only sees the inventory does not know what was intended.

Comparing target and as-is on a regular basis, application by application, is easy to describe and slow to do by hand. Most teams only do it for an audit or a migration.

What Uncia brings, and what it does not do

Uncia sits on the as-is side. It reads the sources of your IT estate in read-only mode (connectors to clouds, hypervisors, CMDB, firewalls and scanners; dropped-in files such as an RVTools export, a flow matrix or an architecture document) and reconciles them in a knowledge base. From that base it generates Architecture, Infrastructure and Network maps, from business domain down to firewall rule, where every element has its own record and its sources. The architecture documents you upload are compared with those sources, gap by gap. Details are on the page IT estate mapping generated from your sources.

Uncia complements your enterprise architecture tool and your CMDB; it does not replace them. You do not draw the target in it or arbitrate a roadmap there: that work stays in your tools and your review boards, and the maps travel back to them through ArchiMate or draw.io export. The link between an application and its business domain only appears if one of your sources carries it. The knowledge base is updated at each collection.

Sources

Frequently asked questions

What is the difference between IT architecture and enterprise architecture?

IT architecture is the broad term for describing and designing information systems at any scale. Enterprise architecture is the organization-wide level: it links business capabilities to applications and infrastructure, and plans how the whole should evolve.

Is TOGAF mandatory for enterprise architecture?

No. The TOGAF Standard is a standard of The Open Group, described as an enterprise architecture methodology and framework. Nothing requires an organization to adopt it, and many only keep its vocabulary and a few steps of its method.

What does an IT architect do day to day?

An IT architect works on project designs (architecture document, review board), keeps the description of the estate current for a given scope, and arbitrates between project requests and shared principles. Depending on scale, the title is enterprise architect, solution architect or technical architect.

Does a mid-sized company need an enterprise architecture tool?

Not necessarily. For a small application portfolio, a maintained inventory, a handful of diagrams and written principles are often enough. A dedicated tool pays off when several people edit the models or when the roadmap spans many projects at once.

Are IT architecture and IT mapping the same thing?

No. Architecture describes what was designed or what is targeted. Mapping describes what exists. The ANSSI guide defines mapping as a representation of the information system and its external connections, made of an inventory and a set of views.

Every week, an article to know your IT estate better

Architecture documents, end of support, NIS2, CMDB, migrations: methods you can apply with or without Uncia.

Get a call from our team

Thirty minutes with a member of our team, remote or on site: Uncia on a demonstration instance, then on part of your own estate if you wish. We reply within 48 hours.

Request received

Thank you. A member of our team will reply within 48 hours to set a date.