Updating your technical components
Upgrading software
Do the functions of your software still meet your needs, but do the technical versions used need to be updated? APPelit carries out agreed upgrades to existing applications. In doing so, we adjust the required code and settings and test the functioning of the relevant functions and integrations.
- 01Software upgrades
- 02Adjust code
- 03Testing integrations
- 04Clear roles
Do technical components need to be updated while your existing functions are retained?
Maintenance counts behind the scenes too
Your employees may still be able to log in and enter registrations as usual. Yet behind the scenes, a technical update may be required. Software versions have a support period; once this ends, security updates for that version may stop. This applies, for example, to PHP. You may receive a notification about this from your hosting provider, or a linked service may now require a different technical connection.
Would you like to retain the existing operation and mainly update the technology? Then we make that delineation part of the assignment. An upgrade does not need to involve a new design or additional user functionalities. For the technical execution, insight into the versions used, available source code and involved environments is important. We also record which parts fall within the upgrade and which changes need to be coordinated with other suppliers.

Collaboration
Your course, our craft
You know your organisation, your processes and your users best. That is why you make the functional choices, and we make sure the technology fits them seamlessly. We are happy to think along, while you stay in charge.
Where you set the direction
- Your business strategy and how IT supports it
- Standard software or custom build: what fits best
- Package choices and how your processes map onto them
- The functional requirements for the custom build
- Which data needs to move to the new system
- Rollout and training of your users
Where we deliver the technology
- Technical specification of the custom build
- Software development
- Testing and quality assurance (QA)
- Software security
- Technical execution of the data conversion
- Hosting and monitoring
Clear roles, one shared result
Aligning your upgrade
Technical work with clear boundaries
- 01
Role of APPelit
We handle the technical specification of the required adjustments, software development, testing, quality assurance (QA) and the agreed software security measures. We carry out the agreed version upgrades and associated code changes. If data conversion is part of the assignment, we carry it out according to your conversion specifications. The technical delivery is also defined in advance.
- 02
Client's role
You determine the business strategy and the IT strategy aligned with it. The choice between standard software and custom software, package choices, functional mapping and functional specifications remain with your organisation. You indicate which functionality must be retained and which usage moments are important. In addition, you provide any conversion specifications and arrange the user training and implementation within your organisation.
Updating versions
Adjusting code and dependencies
During a software upgrade, we can update frameworks, libraries used and the environment in which the application runs, among other things. Which activities are needed depends on the current version and the chosen target version. A transition may require changes to code, settings or components that are no longer supported in the same way. The upgrade information for .NET, for example, distinguishes between different transitions and the corresponding technical changes. We therefore record which versions are being updated, which additional code changes are needed and which integrations need to be checked. New features remain a separate topic: for that, you can go to renewing software. If the application largely needs to be redeveloped, it becomes a matter of rebuilding software rather than just an upgrade. This keeps the scope of the technical work clear.
Existing functioning as a starting point
First test
After the technical adjustments, we test the agreed functions in the updated environment. Think of logging in, saving data, processing files and exchanging information with connected systems. Checks on user rights and agreed calculations can also form part of the testing assignment. For the technical delivery, we make arrangements regarding back-ups, the delivery moment and any recovery steps. A usable recovery route partly depends on changes in data and the systems involved; it is therefore not simply assumed. If prior insight into the technical state is lacking, a separate software audit can help to establish the starting situation. At Trooper, for example, APPelit assessed the code and Azure configuration. Such an assessment can provide input for follow-up work, but is separate from actually carrying out an upgrade.

Information security
Secure by design. Demonstrably.
Do you work with personal or healthcare data? Then you want to be sure that your software partner handles information carefully. APPelit is ISO 27001- and NEN 7510-certified.
ISO 27001
The international standard for information security. Risks, access and incidents are recorded in a management system that is periodically assessed.
NEN 7510
The Dutch standard for information security in healthcare. Important when your software works with medical or health data.
- Security requirements included from the very first specification
- Test cases that align with recorded security requirements
- AI functions also fall within the same data agreements
Contact
Discuss your question
Leave your details. Within 24 hours, a specialist will contact you for an introductory meeting.
