Originally posted by Ajith Kallambella:
Yes, class diagrams should not only reflect your analysis of the domain model, but also refer to certain implementation choices - session bean, entity bean, POJO, helpers etc. There are two ways you can represent the implementation specific details. You can include J2EE specific classes in your class diagram, or you can use UML stereotypes. The former option tends to clutter the diagram.
Hope that helps,