Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Engineering

IT architecture: enterprise architecture, IS urbanisation and integration

A useful architecture can be recognised by the decisions it makes simpler. Our consultants help your teams give the information system a target, a roadmap and integration rules that projects apply because they save them time.

Our principles

  • Mapping limited to what serves a decision
  • Few integration rules, and enforceable ones
  • Governance that responds quickly to projects
In brief

IT architecture describes how an organisation's processes, applications, data and infrastructure fit together, and sets the rules governing their evolution. Management Square consultants strengthen your architects on mapping and the target, principles for API and event-driven integration, architecture documents and a governance that helps projects decide.

Scope

How we contribute

  1. Mapping the information system

    Business, functional, application and technical views of the scope concerned, with flows and reference data. The level of detail is set by the decisions to be informed.

  2. Target architecture and roadmap

    A target for a defined horizon and intermediate stages, each of which leaves the information system in an operable state, even if the next one is postponed.

  3. Integration architecture

    Choice of exchange modes (APIs, events, files), interface design rules, ownership of reference data and the place of the integration platform.

  4. Project architecture documents

    Writing or reviewing architecture documents: requirements, options studied, decision, consequences and risks, for projects that commit the information system.

  5. Architecture governance

    Principles, decision-making body, project gate criteria and management of exemptions, sized to respond within project timelines.

  6. Support for architects in post

    Working in pairs with your enterprise and solution architects on current topics, with transfer of models and practices.

Page contents

Absent or in an ivory tower: the two pitfalls of IT architecture

IT architecture suffers from two opposite pitfalls. In some organisations, it is absent: each project chooses its technologies, creates its own interfaces and duplicates the data it needs. The information system grows through successive additions, point-to-point flows multiply, and nobody can say any longer which application is authoritative for a customer, a contract or a piece of equipment.

In others, it exists but remains at a distance. A team of architects produces comprehensive maps, out of date before they are finished, and a target that projects discover when they go before the committee. Architecture is then experienced as a toll: a late approval, which can only delay or rubber-stamp.

In both cases, the flaw is the same. Decisions that commit the information system for a long time are taken without an overall view, or with an overall view that arrives after them. Our involvement aims to bring architecture back to the moment when it is useful: before spending is committed, in contact with projects.

Enterprise architecture, urbanisation, solution architecture: the concepts

Three terms are in circulation, and they do not sit at the same scale.

Enterprise architecture considers the whole organisation. It links strategy and processes to applications, data and infrastructure, and describes the roadmap for moving from the existing situation to a target. Frameworks such as TOGAF, published by The Open Group, offer a method for carrying out this approach, and languages such as ArchiMate a notation for representing it.

IS urbanisation applies the reasoning of a town plan to the information system. It divides it into zones, districts and blocks with distinct responsibilities, and lays down traffic rules between them: a piece of data has a single responsible block, and one block does not directly access another block’s data.

Solution architecture sits at the scale of a project. It describes how an application or a set of applications meets a need while respecting the common framework.

These approaches read the information system through superimposed views. Urbanisation distinguishes four: business (the processes), functional (the functions to be provided, independently of the tools), application (the applications and their exchanges) and technical (the infrastructure). The value of this breakdown is practical. It makes it possible to observe, for example, that three applications cover the same function, or that a critical process relies on an unsupported component.

Integration: choosing between APIs, events and files

Integration is the area where the absence of rules becomes costly the fastest. Three exchange modes coexist in many information systems, and none replaces the other two.

Mode Principle Suitable when Point of caution
Synchronous API One application queries the other and waits for the response An immediate response is needed to continue The caller depends on the availability of the called system, versions must be managed
Events One application publishes a business fact, subscribers react to it Several consumers, deferred processing acceptable Consistency achieved with a delay, message ordering and duplicates, schema governance
Files and batches Data is transmitted in bulk at a fixed time Large volumes with no freshness requirement Error recovery, processing window, dated data

Beyond the mode, a few rules prevent many drifts. Each interface has a written, versioned contract and an owner. Each piece of reference data has a master application. No application reads another’s database directly. The integration platform routes and secures exchanges, but carries no business rules: these remain in the applications responsible for them.

Flows intended for analysis and performance management obey other constraints of volume and history. They fall within the data platform, with which the integration architecture must be designed consistently.

Our approach: architecture in contact with projects

Our consultants work within your teams; decisions remain yours.

Starting from the decisions to be taken. We do not start by mapping the entire information system. We identify the decisions awaiting an architecture answer (rationalising an application domain, opening data to partners, preparing an application modernisation) and we map what they require, at the useful level of detail.

Defining a target that can be reached in stages. A target without a roadmap guides nobody. We describe intermediate stages that each leave the information system in a consistent and operable state. If the programme is interrupted, what has been done retains its value.

Writing few principles, but enforceable ones. A list of forty principles is rarely applied. We recommend retaining those that settle real disagreements, each with its justification, its consequences for a project and the cases where an exemption can be discussed.

Writing architecture documents that set out a decision. A project document presents the requirements, including non-functional ones (availability, security, volumes), the options actually studied, the one chosen and what is accepted in choosing it. Structuring decisions are recorded in a log, in the form of short notes, so that their rationale remains accessible after their authors have left.

Setting up governance that serves projects. The architecture body intervenes early, on criteria known in advance, and responds within a time frame compatible with project schedules. Exemptions are allowed, tracked and given a deadline for resolution. The most effective route remains making the right choice easy: ready-to-use templates, shared services, preconfigured foundations, in the spirit of platform engineering.

The drifts to avoid

  • Mapping for the sake of mapping. A map that nobody consults to make decisions is not kept up to date, and becomes wrong.
  • Applying a framework in full. Enterprise architecture frameworks are toolboxes. Rolling them out in full keeps architects busy producing documents rather than working on projects.
  • Reducing governance to an end-of-design committee. At that stage, the choices have been made and the budget committed. The body can only approve or block.
  • Concentrating business logic in the integration layer. Business rules lodged in flows become invisible and make every change dependent on a single team.
  • Splitting up on principle. Multiplying independent services when neither the organisation of the teams nor the needs for change justify it adds operational complexity without benefit.

How to measure the contribution of architecture

Architecture is judged by its effects on projects and on the information system, not by the volume of its deliverables. The indicators we suggest tracking fall into three categories.

On the functioning of governance: the share of structuring projects reviewed before the main spending is committed, the response time of the body, the number of open exemptions and how long they have been open.

On the state of the information system: the number of interfaces without a contract or owner, the share of reference data with a master application, redundant applications actually retired, the date of the last update of the maps.

On usage: the number of projects that reuse an existing API or service instead of creating a new one. These measurements also feed the decisions of project portfolio management, where a project’s impact on the architecture becomes one prioritisation criterion among others.

Typical work

What our consultants contribute to

Multi-level mapping

Views of the scope studied, kept in a tool or format that your teams can update.

Architecture target and roadmap

Target state, stages, dependencies between workstreams and assumptions on which the roadmap depends.

Repository of principles and rules

Architecture principles and integration rules, each accompanied by its justification and its exemption cases.

Architecture document and decision log

Project document and log of architecture decisions, with their context and consequences.

See also

Related services

Data platform Warehouse, lake, lakehouse, data mesh: the right choice depends on your uses, your organisation and your constraints, not on the trend of the moment. Our consultants help your teams design a platform they know how to operate and whose cost remains clear. DevOps and platform engineering Asking every team to master everything, from code to infrastructure, ends up slowing everyone down. Our consultants build with your teams the platform and golden paths that make good practice simpler than the workaround. Project portfolio (PPM) A portfolio is not the list of your projects: it is the list of your choices. Our consultants help your leadership establish the criteria, the reading of capacity and the arbitration body that make it possible to start less and finish more. AI agents An agent does not just write, it acts in your applications. Our consultants help your teams design it starting from what it is allowed to do, what must remain validated by a human and what must be traced. Cloud migration A migration is not just a matter of moving servers. We help you decide the fate of each application, prepare the receiving ground and carry out the cutovers without losing control of costs or the possibility of leaving again. Custom software development A custom application is justified when it embodies what sets you apart. Our consultants help your teams frame it as a product, deliver it in increments and build it so that it remains changeable long after go-live. Cyber resilience A recovery plan that has never been run is a hypothesis. Our consultants start from your critical activities and help your teams measure what they actually know how to restore, then reduce the gap, including at your providers. Data quality and MDM Data is not good or bad in the absolute: it is either sufficient for a given use or it is not. Our consultants help your teams measure quality where it matters, control it automatically and address the causes at the source. Project audit When the indicators and the corridors no longer tell the same story, you need facts. We establish the actual state of the project, what put it there and what you can still decide. Sovereign and hybrid cloud Not all your data requires the same level of protection, and no single provider meets all your needs. We help you classify your uses, choose the right environment for each and keep the option of changing it.

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is IT architecture?

IT architecture is the organised description of an information system and of the rules governing its evolution. It links four levels: business processes, functions, applications and technical infrastructure. It is used to decide where to place a new function, how to make two applications communicate and in what order to carry out transformations.

What is the difference between enterprise architecture and IS urbanisation?

Both approaches pursue the same goal: aligning the information system with the business and keeping its evolution under control. Urbanisation divides the information system into zones, districts and blocks by analogy with a city plan. Enterprise architecture is the international term, associated with frameworks such as TOGAF, and covers strategy and organisation more explicitly.

Should you adopt TOGAF to structure your architecture?

TOGAF is an enterprise architecture framework published by The Open Group, which offers a common method and vocabulary. It is designed to be adapted: an organisation can retain only the elements useful for its size and its challenges. Applying it in full without an identified need mainly produces documentation.

APIs or events: how do you choose an integration mode?

A synchronous API is suitable when the caller needs an immediate response to continue its processing. Event-driven exchange is suitable when a business fact is of interest to several applications that can each react to it at their own pace. The choice is made flow by flow, according to the need for freshness, the acceptable coupling and tolerance of the other party's unavailability.

What does an architecture document contain?

An architecture document sets out the context and objectives of the project, the functional and non-functional requirements, the options studied, the solution chosen and its justifications, its impacts on the existing information system and the residual risks. It reads as the explanation of a decision, not as an inventory of components.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.