Interview with Digital Creek: Intelligent Software Modernization - Business Flow Suite and Application Understanding from Digital Creek Software Services
In connection with ScaleUp 360° Legacy IT, the Digitalsummit for IT decision makers, heads of IT operations, heads of mainframe and midrange services and leading IT architects and developers from DACH, we.CONECT Global Leaders interviewed Peter Fried, CTO Digital Creek Software Services ybd CEO Legacy Ratio at Digital Creek Software Services, about his presentation at the Summit.
we.CONECT: Migration, update or new development: How do I decide which applications need to be modernized before the transformation and which can be migrated directly?
Transformation, migration and modernization cannot be separated. Our approach is that everything that is necessary for the business must also be transformed. According to our paradigm, modernization also includes transformation.
One can decide for a new development, if the following conditions are given: Is the requirement analysis completed and is there sufficient budget, as well as a necessary development team with the necessary expertise available. Another important factor is time. If even one of these components is missing, a new development is difficult or even impossible.
There are rational and emotional factors that play a role in making the right decision. Rational factors include cost effectiveness and the need to maintain existing functionality. Emotional factors include trust in the selection of the partner.
Your own business is your own domain. No one understands the functionality of your business better than you. Modernization is a different story. Most of the time, unlike your core business, this is not your own domain. Never try to modernize on your own, always involve a competent partner.
we.CONECT: What needs to be considered when modernizing complex software systems?
There must be a modernization method. This method must be able to answer the questions and handle the problems that arise accordingly. The right questions to ask during a modernization or transformation are: what needs to be modernized and what should not be modernized? Only an analysis can give the correct answers to this question.
How should be transformed or modernized? The answer to this question depends on the functionality of the existing system. This means we have to decide whether rebuilding, conversion or a transfer to a standard software is the right way.
The third question is; with whom do I modernize? The basis of this decision is trust! Who is capable of understanding contexts? Who can deliver the adequate transformation technology and who has already carried out numerous modernization projects?
In the case of an automated transformation, the expected result must also be examined. There are numerous properties of an automatically transformed system that speak against using such a technology. If, for example, the transformation is only operable with a so-called runtime, one should refrain from the transformation.
we.CONECT: What are the advantages of software modernization of legacy systems?
The reason why people decide not to modernize is often due to the development team. It happens that developers do not have the necessary technological knowledge in a new, modern environment. If the lack of know-how is associated with a completely redesigned application, one's own development team is overwhelmed.
Modernization gives developers the confidence to find their way around the business processes.
Therefore, modernization is a smooth transition into a completely new world and saves time, resources, costs and reduces risks. From a test management point of view, modernization can be seen as a kind of release change. Existing test strategies and test cases must even be used because of the necessary comparison.
You can find more information at the following link:
we.CONECT: Thank you very much, Peter Fried, for the interview!
Author: Peter Fried - 24.07.2021