Definition of IT landscape mapping
A map does not reproduce a territory: it keeps what helps you find your way in it. IT landscape mapping applies this principle to the information system. In common usage, it refers to the organised representation of its elements and of the links between them: processes, functions, applications, data, flows, infrastructure.
The term covers the work of description and its result, a set of diagrams and inventories. The links count as much as the objects: which application serves which process, with which data, on which infrastructure.
The views: business, functional, application, technical
A breakdown used in IT urbanisation layers four views.
- The business view: the organisation’s processes.
- The functional view: the expected functions, without reference to tools.
- The application view: the applications and the flows that link them.
- The technical view: the infrastructure that supports them.
The titles and number of views are set in each organisation: a data view or a flow view may be added.
The decisions a map informs
- The impact of a project: which applications and which flows does replacing a piece of software affect?
- Redundancies and weak points: several applications for the same function, a critical process carried by a component that is no longer maintained.
- The baseline from which an IT master plan and a target architecture start.
- Preparing a redesign: our application modernisation page lists the information to record on the scope concerned, including business value and coupling.
ANSSI, the French national agency for information systems security, has published on cyber.gouv.fr a guide entitled “Cartographie du système d’information” (information system mapping).
Keeping the map up to date
An information system changes with every go-live. A map that does not keep up describes a past state, without saying so. Several measures can help.
- A named owner. The French State job profile (choisirleservicepublic.gouv.fr, read on 12 November 2026) entrusts the information systems urbanist with designing and updating the map, and asks this person to guarantee its integrity in line with the IT master plan.
- An update tied to the events that change the system: a go-live, the retirement of an application, a new flow.
- A date shown on each view.
- A level of detail limited to what is consulted, since every object described is an object to maintain.
IT landscape mapping, IT urbanisation, enterprise architecture, C4 model: not to be confused
IT urbanisation is an approach, which decides on a breakdown and on exchange rules. The map serves it as an instrument: it describes the existing state, then the target.
Enterprise architecture is a discipline, which starts from the organisation’s objectives. The map is one of its outputs, along with principles and the roadmap.
The C4 model represents the architecture of a software system, by zoom levels. IT landscape mapping sits at the level above: all the systems and their exchanges.
Finally, an inventory lists objects, applications or servers, without saying what links them. It feeds the map without taking its place.
A logistics provider’s warehouse software, read view by view
Take a logistics provider that operates several warehouses and wants to replace its warehouse management software. The business view recalls the processes concerned: receiving, storage, picking, shipping. The functional view shows that parcel labelling is handled twice, by the software to be replaced and by a tool specific to one site. The application view reveals that the customer portal reads the warehouse software’s database directly. The technical view points to picking terminals tied to the current version.
The replacement thus affects three objects that the project had not identified: the labelling tool, the portal and the terminals. The map showed where to look before costing.
Which scope should you map, and in how much detail? The answer depends on the decisions to be informed, the principle from which the approach described on the IT architecture page starts.