Please log in to watch this conference skillscast.
Software systems often live for many years or even decades, are carefully maintained and patched again and again. But at some point the UI looks dusty, changes take forever and you want to benefit from the possibilities of modern technologies. The decision to modernize the system is made. And then comes the simplest requirement in the world, which we’ve all heard before: ‘But the new system must be able to do the same things as the old one!’ It is not surprising that we hear this requirement so often: it is simple, it can be formulated even if you know the system only superficially, and it seems to be precise. In fact, this requirement is quite nonsensical. In this talk, we will explain why the simplest requirement in the world is nonsense and provide experience, guidance, and best practices for modernization projects where the goal is to design the target state and plan the path of modernization.
YOU MAY ALSO LIKE:
- Map for the Platform Jungle: What Types of Platforms Are There and How to Survive Discussions? (SkillsCast recorded in November 2022)
- Software Architecture in a DevOps World (SkillsCast recorded in February 2022)
- Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)