Retro-documentation issues for application management
The issue of retro-documentation is linked to the issue of the long-term viability of your applications and the cost of maintaining them.
Documentation is often obsolete or non-existent, and knowledge is held by only a few key employees. This creates risks that need to be managed.
Retro-documentation of your applications meets a variety of needs, such as:
- Day-to-day operation,
- Protecting your assets,
- Independence from third parties,
- Implementing upgrades,
- Team rotation,
- Migration to another system,
- Urbanization…
These are different objectives with different solutions.
Our Retro-Documentation offer
Our methodology is based on a dual functional and technical approach.
The system is described externally by its functions, services and associated technical components.
Our offer is based on our Karto workbench, which provides detailed IS analysis and code navigation.
We adapt the deliverables to the objective. We will not retro-document an application in the same way depending on whether it is to be migrated or redeveloped.
Our tools
Our Karto workbench provides an exhaustive analysis of your IS. It’s a guarantee of completeness. In addition, it gives you a quick overview of your applications in terms of technical and functional mapping.
Applications
We adapt the depth of functional analysis to meet your objectives:
- Corrective maintenance
- Evolutive maintenance
- Modernization towards a modern architecture by rewriting or regeneration
- Urbanization
- Application disimbrication with a view to replacement by a software package
- AM support
We have strong functional skills in banking, insurance, pensions, provident funds, distribution, HR and human resources. We can therefore address business-specific issues in these sectors..
Focus on IS urbanization
The problem of IS urbanization
IS urbanization or IT urbanization enables a system to be modernized brick by brick, so as to meet user expectations while respecting time and cost constraints.
However, the interlocking nature of the various components of an information system makes it difficult, if not impossible, to change or renovate an application simply and economically, while limiting the impact on the rest of the system. IS urbanization is therefore a complex operation that needs to be approached with the right strategy.
Our offer
IS (Information System) urbanization consists in dividing the IS into functional blocks described by business procedures. All IT components are listed and classified into functional blocks.
A block owns its data, and provides an external view of its properties that lasts over time.
A block must:
- Be interchangeable,
- Be able to change version without impacting the rest of the IS,
- Be technically and functionally documented,
- Not disrupt the rest of the IS in the event of shutdown.
Our IS urbanization tools
Our IS urbanization (or IT urbanization) offer is based on a dual functional and technical approach.
System analysis and IT urbanization are largely automated processes, thanks to our KARTO software workshop, which brings you significant productivity and quality gains.
Move Solutions’ KARTO mapping tool provides instrumentation for perimeter mapping, impact studies, automatic renovation, automatic JCL generation, comparison procedures, and file translators for data migration.
This workshop is supported by language parsers. All your assets are mapped and a knowledge base is built. It contains all cross-references between components, and goes down to the precise use of each piece of data.
During analysis, a set of messages is generated for each point of attention relating to the transformations to be carried out. For example, each COBOL component is visualized according to its call hierarchy, right down to the JAVA display TP programs.
Applications
- Replacing one application with another.
- Decommissioning obsolete applications or components.
- Application engineering.
