itssujeeth Principal Product Architect · 2017 Delivered
Enterprise Impact-Analysis Scanner
A source-code scanner that found every application affected by an enterprise-wide store-numbering change across a dozen languages, and became the seed of the portfolio rationalization product.
An enterprise store-numbering change at one of the world's largest retailers had to be assessed across an application estate written in shell, Python, C, C++, Java, COBOL, C#, VB.NET, Perl, JavaScript, HTML, and more. Nobody could say with confidence which applications would break.
I built a C#.NET scanner that read complete source code with customizable patterns and reported every impacted application. It gave the program a defensible list instead of a survey.
Delivered: the program got a complete, evidence-based impact list. The scanner was then generalized into the portfolio rationalization product. No security-coverage metric is claimed for this work; an earlier version of this page attached one here that belongs to a later project.
The scanner was a one-off tool with one job: tell a program which applications an enterprise-wide identifier change would touch. The interesting part came after. Once you have a reliable way to read an entire multi-language estate and answer a structural question about it, the same engine answers other questions, such as what depends on what, where the duplication is, and which applications a portfolio could retire. That generalization became the Application Portfolio Rationalization Engine.
An earlier version of this page described the work as vulnerability tooling with a 50% coverage improvement. That figure belongs to the GenAI-assisted vulnerability remediation at a later employer, and it is now stated there with its qualifier.