Interview with Digital Creek: Intelligent Software Modernisation – Business Flow Suite and Application Understanding of the Digital Creek Software Service
In connection with ScaleUp 360° Legacy IT, the digital summit 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 modernised before the transformation and which can be migrated directly?
Transformation, migration and modernisation cannot be separated. Our approach is that everything that is necessary for the business must also be transformed. According to our paradigm, modernisation also includes transformation.
You can decide in favour of a new development if the following prerequisites are met: Has the requirement analysis been completed and is there sufficient budget available, as well as a necessary development team with the required expertise. 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. The rational factors include cost-effectiveness and the need to maintain existing functionality. The emotional factors include trust when choosing a partner.
Your own business is your own domain. No one understands the functionality of your business better than you. Modernisation is a different story. Unlike your core business, this is usually not your own domain. Never try to modernise on your own, always involve a competent partner.
we.CONECT: What needs to be considered when modernising complex software systems?
A modernisation method must be available. This method must be able to answer the questions and handle the problems that arise accordingly. The right questions to ask during a modernisation or transformation are: what needs to be modernised and what should not be modernised? Only an analysis can provide the correct answers to this question.
How should be transformed or modernised? The answer to this question depends on the scope of functionality of the existing system. This means we have to decide whether the right approach is to create a new system, convert it or transfer it to standard software.
The third question is; with whom do I modernise? The basis of this decision is trust! Who is able to understand the context? Who can provide the appropriate transformation technology and who has already carried out numerous modernisation projects?
In the case of an automated transformation, the expected result must also be assessed. There are numerous characteristics of an automatically transformed system that speak against the use of such a technology. For example, if the transformation is only operational with a so-called runtime, you should refrain from the transformation.
we.CONECT: What are the advantages of modernising legacy systems?
The reason for deciding against modernisation 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 expertise is linked to a completely redesigned application, the development team is overwhelmed.
Modernisation gives developers the confidence to find their way around the business processes.
Modernisation is therefore a smooth transition into a completely new world and saves time, resources, costs and reduces risks. From a test management perspective, modernisation can be seen as a kind of release change. Existing test strategies and test cases even have to be used because of the necessary comparison.
Further information can be found under the following link:
we.CONECT: Thank you very much, Peter Fried, for the interview!
Autor: Peter Fried – 24.07.2021
