The Perl Debugger (perl -d) is your friend. The 'm' command reports on the various methods available to an object; use it just after you have instantiated the beast --

my $obj = Class::new();
  DB<1> m $obj
[download]

'T' gives stack trace information and tells the context the routines are called in. I also use 's' step into method calls and then explore with 'w' and friends to see where I really ended up.

In terms of graphics, I have yet to find something that beats pencil and paper for the fine detail, white-board and Visio diagrams for the over-all structure. And Document Everything! Build POD, ReadMeFirst files, Twiki pages, what ever make you comfortable. Even if you don't have to come this way again, someone else will.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.