Using UML 2.0
I attended the How to Represent the Architecture of Your Enterprise Application Using UML 2.0 and More session on the last day of JavaOne 2006. According to the speaker UML 2.0 provides “a lot of flexibility which is an euphemism for ambiguity.” A diagram is not enough. The speaker recommended that every diagram have a key. Along with your diagrams with a key add a glossary and acronym list. Record the rationale behind your design decisions including relevant rejected alternatives. It is also useful to gather the requirements and design constraints in these documents. To facilitate design and analysis documents standardize on templates and use them. I myself have written a lot of use case documents and feature specifications and when I use a template I just fill in the gaps in the template.