For me WordPress is totally unknown. I would like to know what tools and techniques do you use to analyze unknown code of WordPress. If more specifically that for the following tasks:

1. To locate the file (s) html template layout of the output to the browser.
2. Identifying the mechanism of routing on the URL that is both on the basis of the URL, the system determines which content and form in which to display or put in short – a mechanism controller in the pattern of MVC.
3. Identifying the mechanism of the assembly of the main content of the modules, and work with a database that is everything for which usually must meet model in the pattern of MVC.
4. Determination of the mechanism of assembly of the entire html page before. That is, view in the pattern of MVC.

For example, for me, it’s probably become traditional: Xdebug, IDE for PHP (Eclipse). Also a very special service helps to visualize the trace files Xdebug – Recognizer. It is good because it builds a comfortable working sequence diagram of a trace log. Maybe enough for someone to read documentation, view the source code or running in the debugger, but for me chart tracing helps to form in my head for the system and has become a really convenient way of analysis.

What else can you advice?
Encourage effective tools and techniques for quick/easy analysis (reverse engineering)?