The original developer is no longer available
The application keeps running, but nobody knows it in detail any more. I work my way into the existing system and take over its further development.
Software engineering · Legacy · IoT
Software for legacy systems
I take over existing applications, extend them for new requirements and connect them to instruments, sensors and cloud services – from analysis to day-to-day operation.
Does this sound familiar?
Three situations I am most often asked about.
The application has to meet new requirements
New rules, new interfaces, growing amounts of data. I extend the software you have instead of replacing it from scratch.
Devices and existing software have to be connected
Sensors, instruments or machines need to talk to the software you already run. I build the connection and keep it stable in operation.
Focus areas
Three fields that are rarely cleanly separated in practice – which is exactly why they need to be considered together.
01 — LEGACYEvolving existing applications
Legacy software is rarely replaced – it is needed. I make it understandable, stabilise it and extend it where the business actually requires it.
- Analysis and documentation of existing systems
- Changes and extensions while the system is running
- Interfaces between legacy and new systems
- Modernisation in small, safeguarded steps
02 — MEASUREMENTSoftware for measurement systems
Applications that record, evaluate and present measurement data – close to the hardware and built for continuous operation.
- Acquisition and evaluation of measurement data
- Connecting instruments and sensors
- Evaluation, visualisation and export
- Robust processes without manual intervention
03 — IOTIoT integration projects
Devices, systems and services are connected – from the field level to the cloud, traceable and operable.
- Connecting sensors, machines and cloud services
- Established industrial protocols and interfaces
- Data flow, buffering and resilience
- Operation, monitoring and remote maintenance
How I work
No project starts with code. First it has to be clear what the system does today and what it should do tomorrow.
-
Analysis
Record the current state, understand the processes, name risks and dependencies.
-
Concept
Define approach, effort and sequence – with the running operation in mind.
-
Implementation
Deliver in manageable steps, test, and gather feedback early.
-
Operation
Handover, documentation and – if desired – ongoing support and extension.
A system that is stuck?
Describe your situation briefly – I will get back to you with a first assessment.