Application Architecture Review
Legacy mainframe interface archaeology
Documentation archaeology for COBOL-era interfaces ahead of a financial services merger in Seoul.
Scope narrative
We interviewed retirees-on-contract, mapped dormant batch jobs, and correlated job names to modern API gateways. The output prioritized retirement candidates versus must-migrate paths.
What we examine
- Batch job inventory cross-checked with ops logs
- API gateway mapping to legacy endpoints
- Knowledge-capture interviews with retirees-on-contract
- Retirement candidate scoring model
- Regulatory reporting dependency tracing
Transaction outcomes we highlight
- Merger filing included a credible interface retirement wave
- TSO avoided paying for three dormant jobs rediscovered in week two
- Engineering hiring plan adjusted for niche skills
Engagement FAQ
No. We document behavior and risks; remediation planning is separate.
Field notes from prior sponsors
“Mainframe archaeology sounded theatrical until the team surfaced four silent dependencies on a pension calc job. Worth the slower calendar.”