← Kespa Software case studies

Case study · legacy rewrite

Rebuilding a legacy scientific application for the web

A major Irish university relied on an ageing desktop application for long-range scientific modelling. After winning a public tender, we rebuilt it as a modern web application. A government department now owns it, and retains us to develop and host it.

The situation

The original application did important work, but it was desktop software from another era. It ran on only one operating system, and it kept its parameters and data in a local text file, so users couldn't move between devices or pick up their work elsewhere. There was no update mechanism either, so there was no way to get bug fixes or improvements to the people using it.

Its users needed the same trusted results in something they could use from any device, that would stay up to date.

The hard part: the science

The toughest challenge wasn't the code. It was getting to grips with the underlying science. To rebuild the application faithfully, we had to understand the science behind its models and the terminology its users work in.

We even had to learn about the industry around that field, to understand who the application's users were and what they were trying to achieve with it. Only then could we design something that served them better than the original.

We worked closely with university staff and researchers who knew the underlying science. That did more than improve our understanding of the application and how it was meant to be used. It was invaluable for deciphering the equations in the original code, and it meant we could confidently change how forecast models were calculated when the client asked for changes.

What we did

We won the work through a public tender, then rebuilt the application from the ground up: a React front end and a Python (FastAPI) back end, designed to be maintained for years. Our front-end developer, back-end engineer and product owner worked directly with the university's experts.

After launch we were contracted for further development and for managed hosting, so the same team that built it keeps it running.

Our QA lead, Claudia, verified the new application's results against the original model. The old application didn't lend itself to automation, so this meant painstaking manual simulations, run side by side, until we were sure the output matched.

The result

Users now have a web application they use under their own account, from any device. They can save parameter sets for the simulations they run often, and collaborate on simulations with colleagues in their own organisation.

When ownership moved from the university to a government department, the department kept us on for ongoing development and hosting.

Delivered
Desktop → web
Client
A major Irish university; now a government department
Our role
Tender, design, build, ongoing development and hosting
Status
Ongoing
Practice
Kespa Software

Discretion by default

We never name our clients: not on this site, not in sales conversations, not on social media. Your use of Kespa stays between us unless you choose otherwise. That's why you'll find descriptions here instead of logos.

Talk to us

Have software that's become hard to change?

We reply within one working day, and we'll tell you quickly if we're not the right fit.