IBM developerWorks recently interviewed me for my latest Automation for the people article called Asserting architectural soundness. Scott Laningham has a very efficient operation as the whole podcast interview process took no more than 10-15 minutes to complete. Asserting architectural soundness describes a technique to build checks into your build scripts so that you discover architectural violations as soon as they are introduced into the code. For instance, let’s say your presentation layer is making a direct call to your data layer and this is a violation to your architectural layering rules. By using the JDepend API, JUnit and Ant, I show how you can find out about this type of error as soon as you build your software. What’s more, if you’re using Continuous Integration, you’ll learn about the violation for any developer that commits code to the repository and in a consistent manner - several times a day.

This entry was posted on Thursday, July 12th, 2007 at 3:45 pm and is filed under /Paul, News, Java, Inspection, Continuous Integration. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.