Software modernisation
Does every software change take longer, while updates introduce new problems? We help decide what to keep and where to start modernisation. We make changes in stages, with tests of existing features, a migration plan and a way to roll back. Modernisation is planned alongside product development and your users’ daily work.
Discuss a system reviewPlan modernisation alongside the changes your product needs
You evaluate the first stage before deciding on the next. You know which constraint a change addresses, what needs testing and how users will move to the new version. The plan accounts for the data and integrations that must work with it.
What you receive
- A change plan identifying constraints and what is worth keeping
- Tests of important functions to assess the impact of modernisation
- Phased updates or replacement of selected software components
- Transfer of data and knowledge needed for continued development
Where we can help
Changes that put existing features at risk
We organise dependencies and add tests for key features to make errors easier to detect in future changes.
Outdated components
Plan library and runtime upgrades alongside compatibility tests and a transition path.
Migrating data and functionality
Move selected areas in stages, checking data completeness and behaviour before switching users.
Modernisation alongside TimeCamp’s product development
We modernise TimeCamp’s desktop application built with C++ and wxWidgets while continuing to develop its features. Tests of existing workflows help assess changes before the next release.
All projects
TimeCamp: modernisation without replacing the whole application
View project: TimeCampWe appreciate that the Software Logic team brings its own ideas for improving our product. They respond quickly when our needs change and deliver what we agree on. We work with people who care about the quality of the application and take responsibility for their work.
How to start and what you receive
You can commission the first stage separately. You know its scope and cost before work begins and decide on further work based on the results. If you already have an analysis or specification, we will use it when planning the work.
Review and modernisation plan
An assessment of code, data and integrations identifies risks and the order of changes. The first-stage plan includes test scope and, where migration is needed, data transfer steps and conditions for returning to the previous version.
The first software change
We modernise a selected area. Tests of existing features and a rollback plan prepare the change for deployment.
A plan for further work
We assess the first release and update priorities. Further changes are planned alongside product feature development.
View an extract from an example modernisation plan
Illustrative example: a short extract for a fictional scenario. It shows how findings can be presented, rather than results from a client project. We agree on the deliverables before work begins.
First stage: separating reporting
Changes to reports require updating the entire order management system. The team wants to develop reporting independently of day-to-day sales operations.
- Scope of the change
- Move one agreed report to a separate module using data from the current system. Order processing stays in the existing application.
- Acceptance criteria
- Compare the new and existing report using the same data, including amendments and cancelled orders. Explain every difference and check access for each user role.
- Launch and rollback
- Release the report to a selected group. Keep the previous view available as a fallback. Before launch, define who can decide to revert and under what conditions.
- Next decision
- After the first report is accepted, assess the effort needed to move the others. Resolve data discrepancies before expanding the scope.
Frequently asked questions
We compare code condition, business requirements, maintenance cost and migration risk. A complete rewrite is an option, not a starting assumption.
Plan the first stage of modernisation
Tell us which changes you are postponing and what limits the current system. We will define a review to choose the first area to modernise and assess its cost and impact on users.
During our conversation, we will assess how we can help and identify the information needed to define the scope and prepare an estimate.
You can also email us directly: office@softwarelogic.co