Oryon expertise
Application maintenance and improvements
Keep your software moving: tested fixes, improvements and updates.
Based in Givors · Rhône area and remote support across France · Project discussions in French
Keep what matters working.
How can we take over and improve software already in use?
Application maintenance helps businesses take over existing software, fix faults and evolve features. It starts with reading the code and rebuilding the working environment. Work is prioritised and priced in packages, then delivered with checks, traceability and operations documentation.
What you receive
- A code assessment identifying fragile areas and a stabilisation plan
- Traceable fixes recording the change, cause and verification
- Improvements delivered in packages with documented acceptance testing
- Tested dependency and environment updates
- Operations documentation: installation, deployment and known incidents
What this brings you
- A provider who reads your code before changing it
- An explanation and verification for every fix
- The option to resume development internally in future
When can Oryon help?
- The original provider has left and the software has no documentation
- Bugs accumulate and every fix creates another
- You want a feature but nobody understands the existing code
- Outdated dependencies are starting to cause problems
How the work progresses
- Read the code and reconstruct the working environment
- Write an honest assessment of strengths and fragile areas
- Prioritise the backlog with you: fixes first, improvements next
- Deliver regularly, with each release tested and documented
What we need to plan together
- Where tests are missing, we add them around fragile areas before changing them
- Budgets are agreed per work package rather than for an undefined outcome
Details of the work
Scope and deliverables
A takeover begins by reading the code and reconstructing the working environment. The assessment separates necessary fixes, dependency updates and desired improvements.
Each work package defines the changes and how they will be verified. Delivery includes the agreed fixes or features, associated tests and updated operations documentation.
Integration and migration
Pricing depends on the state of the code, available access and existing tests. Tests are added before changing an uncovered fragile area.
Fixes and new features do not necessarily require the same work. Priorities and budget are agreed per package; new findings are discussed before extending the scope.
Maintenance and ownership
Fixes record their cause and verification. Installation, deployment and known incidents are documented to support future work.
You retain control of the code and documentation. Your team or another provider can continue development using the material supplied.
Technologies used
- The project’s existing stack: TypeScript, Node.js, PHP, Python or another technology
Frequently asked questions
Can you take over software without documentation?
The first step is to read the code and reconstruct its environment. The assessment then establishes what can be retained and what is needed before the first fixes.
What is the difference between corrective and evolutionary maintenance?
Corrective maintenance fixes a fault. Evolutionary maintenance adds or adapts a feature. Both are prioritised with you and delivered in tested packages within the agreed scope.
Does maintaining an application require a rewrite?
A takeover begins with examining the existing system. Recommendations depend on its strengths, fragile areas and the changes you want to make.
Let’s discuss your context
Tell us the main programming language and how much documentation is available.
Based in Givors, in the Rhône area, Oryon supports projects remotely across France. On-site work is considered for each project. Project discussions take place in French.
Complementary services
Continue preparing your project
- Project recovery
Recovering an unfinished web project: where should you start?
Is your website unfinished? Access to recover, diagnosis, quotes by work package, acceptance checks and launch: prepare a recovery with a clear, documented scope.
Read the guide - WordPress
WordPress maintenance for businesses: the checks to plan
Backups, updates, tests and contract scope: questions to ask when organising maintenance for a business WordPress website.
Read the guide