Conclusion
In this article, we looked at how we might take a useful concept from UML that has no direct equivalent in Java source and use custom Javadoc style tags to store that higher-level design information. This is exactly the sort of information that rapidly becomes lost or out-of-date in dusty volumes of design specification. Here, it is instead right at our fingertips in the source code. In the next article, we leave class diagrams and take a look at the second most important type of diagram in UML: the interaction diagrams. Until then, I will leave you with a short quote from Peter Coad et al's coloring book4
"Black-and-white conveys basic information.
Color reaches out and grabs you.
Welcome to the world of modeling in color, with archetypes..."