The client had used the same screens for years. The new app had to reproduce them exactly, working from a virtual machine of the old software, while finally sitting on maintainable code.
← Back to work
End-of-studies project · CESI Software Developer
Quoting software
Rewrite a manufacturer's quoting software once nobody is left to maintain the old one, without users having to relearn anything.
3tiers: data, logic, interface
1:1screens rebuilt pixel for pixel
SAGElink with the accounting ERP
2environments: staging then prod
A hard constraint: change nothing on the surface
Architecture and features
WinDev lets you write code straight into windows; I kept a three-tier architecture with one class per module (Quote, PurchaseOrder, DeliveryNote, User…) and strict naming conventions.
- Admin CRUD: items, users, comments
- Quote creation and conversion into purchase orders
- Print reports: quotes, delivery notes, lists
- Migration of existing databases and SAGE integration
Finishing solo
When my teammate left, I took over the whole project: client meetings, requirements, fixes, feedback. I swapped sprints for a Kanban flow, better suited to a solo developer juggling projects, with a weekly on-site review.
That's where I learned that code is only part of the job: presenting, listening, rephrasing and keeping a client informed matter just as much.