How have you approached your class diagram(s), have many of you done more than one, and if so how have you separated them (software tiers or functionality). Did anyone bother to include UI components (Jsp/Servlets/Swing) on the class diagrams? Cade has a very small section on class diagrams, and his example just shows the domain objects and a couple of the EJB services. Again all his other diagrams show JSP's and neglect the Swing components. Do you think its fair to follow the same track, it would be big hassle to reproduce the exact same diagrams showing the Swing UI as well as the Web UI.
First, I would like to inform you that I haven�t received my results yet.
I have made a simple diagram, just an extension of BDM includding other classes and with propper multiplicity. I haven�t included any other components, like: presentation tier elements, Value Objects etc.
I have seen people who passed using this approach. (the KISS principle)