Auditing the existing code
Structure, hidden faults, risky areas and dependencies are examined.
EA Modification
EA modification and extension
Bug fixing, refactoring, feature development and audit.
- Audit reportBefore a single change
- Documented changesEvery edit traceable
- Regression checklistWithout breaking what works
Scope
What this service actually covers
The scope is settled before work starts; the items below are part of this service.
Targeted repair
The change stays limited to the actual problem, with no gratuitous rewrite.
Protecting what works
Behaviour that is already correct is left untouched.
Post-change control
Regression testing is run across the system's main paths.
The current code is reviewed and change risks identified before any modification, then fixes are applied and documented.
The audit states which parts are reusable and which must be rewritten, and that decision is made before any change begins.
Every change is confirmed by a specific test, and the handover includes a changelog.
Delivery
How this service is delivered
Four stages with defined output; nothing moves on without your approval.
-
Intake and audit
The existing files are reviewed and the problems listed in writing.
Stage output Audit report -
Change scope
What will be fixed and what stays untouched is agreed.
Stage output Approved scope -
Repair and extend
The changes are applied with the logging and comments they need.
Stage output Revised build -
Test and hand over
Regression testing, a before-and-after comparison and a change report.
Stage output Change report
Handover
What you receive
What you receive at the end of the project.
3 items
- Audit report of the existing code
- Documented fixes
- Regression checklist
This list is part of the project scope; each item is handed over at the end of its stage, before final delivery.
Who it is for
Who this service is for
If one of these describes your situation, this is the right service.
Owner of an unfinished or faulty EA
The system mostly runs but shows unwanted behaviour and recurring errors.
A project that lost its developer
You hold the source, but nobody knows it well enough to change it.
Questions
Common questions about this service
Short answers to what clients ask about this specific service.
Do you work on someone else's code?
Answer
Yes, provided compilable source exists. Without source the work becomes a limited rebuild.
The old structure is unmaintainable — what then?
Answer
The audit states whether repair is enough or whether rebuilding part of the system is the more sensible and cheaper route.
Are changes tested?
Answer
Yes. Every change is checked with regression testing across the main paths and a before-and-after comparison.