Posted by & filed under Architecture, Dependency Management.

In an excellent on-line presentation Juergen Hoeller gives rationale and guidelines for controlling the structure of large, evolving code-bases. Juergen is the chief architect of the Spring framework, which as I have previously pointed out is structurally almost perfect. This didn’t happen by accident.

If you don’t have time go though the 88 minute presentation, here is a nice sysnopsis by Mike Nereson.

One Response to “Code Organization Guidelines for Large Code Bases”

  1. Mike

    Thanks for the mention. If you are into architecture (which I can see that you are) please take a quick look at a library that I wrote to wrap jdepend to assert architecture rules when you run your tests.



Leave a Reply to Mike Cancel reply

Your email address will not be published. Required fields are marked *