You can use a profiler, like Devel::DProf or my module Devel::Profiler, to extract a call-tree for a given request. If there are a small enough number of request types you might consider producing a call-tree for each request. This might give you an idea of how complex the application is.

Here's a quick example to get you started. First, run the code under a profiler: 

$ perl -MDevel::Profiler -e 'sub foo { bar(); } sub bar { 1 }; print f
+oo();'
1

[download]

Then use the appropriate tool to generate a call-tree. In this case, dprofpp: 

$ dprofpp -T
main::foo
   main::bar

[download]

-sam

In reply to Re: Programs/Methods for analyzing an existing Perl based system by samtregar
in thread Programs/Methods for analyzing an existing Perl based system by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.