4 ms·
What you are looking for is called "Program Understanding". If you Google for it you'll find a bunch of research papers on the topic. For some reason, tools r
by diegof79 4y ago
What you are looking for is called "Program Understanding". If you Google for it you'll find a bunch of research papers on the topic.
For some reason, tools related to program understanding are not widely adopted by IDEs.
A while ago I used a tool for Java that was based on the Object-Oriented Metrics[0] book by Michele Lanza. But, that tool was discontinued and it doesn't exist anymore[1].
If you are interested in that topic take a look at Moose[2], a dig a little bit in the research papers. (honestly I tried Moose a few times, but I wasn't very comfortable with it).
For TypeScript projects, the TS compiler API is extremely powerful and easy to use. You can use that to extract information and analyze the code relationships (Graphviz is your friend here :) ).
[0]: https://link.springer.com/book/10.1007/3-540-39538-5 https://link.springer.com/book/10.1007/3-540-39538-5
[1]: https://web.archive.org/web/20150428173717/http://www.intooitus.com/products/infusion https://web.archive.org/web/20150428173717/http://www.intooi...
[2]: https://moosetechnology.org/ https://moosetechnology.org/
- marktangotango 4y agoThere was also a lot of work in this area in the 90s leading up to the y2k (non)event. Mostly back then it revolved around cobol, which was understandable given y2k impact was in many cases related to legacy cobol systems. A lot of architecture visualization and recovering business requirements from code. I did some work on diagramming mainframe JCL files for example.