I'm studying the Cade's book for an example of the class diagram. In Cade's book, the class diagram seems to be based upon the business model alone. Just wondering if this level of detail is appropriate. Don't we need to show DAO classes, Service Locator, Session Facades ..etc in the class diagram? And also do we need to show the detailed attributes and accessor methods?
Joined: Apr 25, 2003
There are 2 ways of thinking about class diagrams
1. Class diagrams should show only business classes and no implementation specific classes 2. Class diagrams should show all classesin the system i.e implementation speciifc classes as well.
I personally think that option 1 is good as there are other UML diagrams like package diagrams and component diagram where we can show implementation details.
Joined: Jul 15, 2003
Thanks. So I guess any approach would be fine. Can anybody who passed part2 like to share their experience?
Joined: Oct 27, 2003
Class diagrams are supposed to be implementation independent ie whether you use a j2ee system or vb, they will not change. For the architecture exam, however, you can add some stateless beans(like customermanager, transactionprocessor etc) to strengthen a j2ee solution. All specific j2ee components will be in component diagram ONLY.