Is there a documented approach to constructing a class diagram ? i.e, must one construct it from use cases ? Or would you identify the classes and associations from a sequence diagram ?
How much *detail* is necessary to show on a class diagram ? It would appear to me that there would be a high level class diagram that just showed the top level classes (no J2EE component classes) and then a further detailed class diagram that showed attributes, methods, multiplicity. I have read that a class diagram is correct even if you just show the classes in their rectangles and draw the associations between the classes but Sun must have some idea as to the level of detail required.