Erlang - code analysis

Question

I have to analyse some existing Erlang code.

Does anybody knows about a tool able to visually / graphically trace the modules calls ?

The behaviour should be : give a directory containing the source code, and get a gui / picture / file of the calls (module1->module2->module3....).

Something like an UML reverse-engineering, but ala Erlang ?

Thanks.

Answer 1

Gradual Typing of Erlang Programs: A Wrangler Experience

Answer 2

xref in OTP works like this. It gives you data about which dependencies exist between applications and modules and produces call graphs. Here's an overview of xref.