Automation for the people: Asserting architectural soundness
Take charge of your architecture by using a proactive build process
In the seventh installment of his "Automation for the people" series, Stelligent CTO, Paul Duvall,
demonstrates how you can discover architectural deviations by writing tests using JUnit, JDepend, and Ant to discover problems proactively instead of long after the fact.
Published by the popular IBM developerWorks, the article, "Asserting architectural soundness", covers techniques that enable you to proactively analyze a software architecture through build automation so you and your team can discover when source code violates an established architecture early in the development life cycle.
Be sure to check out the related podcast in which Paul expands on this concept.
The "Automation for the people" series is dedicated to exploring the practical uses of automating software development processes and teaching you when and how to apply automation successfully. Also, check out developerWorks' "Improve Your Java Code Quality" discussion forum for topics addressing best practices for ensuring your code is the best it can be.
|
