Design discipline which aims to structure the IT system and align it with the enterprise’s strategy and needs
Introduction to the notion
Over the years, the stacking up of software developments has lead to a terribly complicated system, an assembly of functionalities, running on different hardware, answering locally felt needs and which are subject to obsolescence and changes of all kinds.
In order to reduce this complication and to enable the enterprise to take advantage of new technological possibilities, we have to reorganize the system with a more economic architecture. This architecture must take into account the technological possibilities – downstream – but especially – upstream – of the enterprise vision, constraints and objectives. One discipline is there to serve such an ambition: information systems urbanization or IT city planning.
Essentially, the procedures and methods used for IS urbanization are those of mapping applications (for the ‘as is’ situation analysis) and logical architecture (for the design). Today, UML supports this discipline and transforms it from the inside by equipping it with a precise language. This representation technique ensures the continuity between the global representations of the architect and the detailed representations of the designer. This continuity leads to a real revolution in the distribution of roles and the definition of responsibilities.
The founding act of urbanization, in the enterprise, is the publication of an “urbanization target”. It is simply a logical architecture graph that represents the “ideal city”, the system that we would like to build.
Related terms: logical architecture, principle of continuity, target, urbanization trajectory or IT city planning trajectory.