From the readme:
MultiParse helps to simplify the process of breaking a large app into smaller apps for use in a multi-dll solution. Note well that the method used here may not be optimum for you, but it is optimum for the procedures! What I mean by that is that you may want to use the results created by MultiParse and further refine your dlls into an arrangement that is workable for you. MultiParse is only following the procedure dependencies and organizing them into hierarchies that _can_ be used to build a multi-dll solution. It does not "know" which of your procedures are source, utility, browse, and etc. So keep that in mind when viewing the results.