Analysing a Visual Foxpro application to derive requirements. Tools/approaches/practices?

Posted by Kabeer on Stack Overflow See other posts from Stack Overflow or by Kabeer
Published on 2010-03-26T10:01:17Z Indexed on 2010/03/26 10:03 UTC
Read the original article Hit count: 473

Hello. In an upcoming project I am supposed to re-engineer a huge application built on Visual Foxpro into a web-application. The target platform is .Net.

The application from the end-users' perspective is very complex (complex forms, reports, navigation, etc). The sorry state is that there are no documents available from which I can derive, business processes, business rules, work-flows, validations, application state, etc. I can gather some requirements from end-users but it cannot be complete from any perspective. Maneuvering through the code would be tedious & time consuming, given the millions of lines of code.

Therefore I am looking for a tool that can help me in code analysis. My googling attempt didn't help me at least for a Visual Foxpro code base. Besides, I will appreciate if someone can share processes/approaches/techniques to establish the requirements as far as possible.

BTW, this link didn't quite help.

© Stack Overflow or respective owner

Related posts about visual-foxpro

Related posts about reverse-engineering