This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
I have designed/developed several applications before. In the design phase, we need to draw a class diagram for each application.
But I am confused about the content of class diagram a long time.
The questions is :
Does the class diagram only include class and class hierarchy of domain model (eg. Student, Course, Teacher..) or class of domain model, service class (eg. OrderService), dao class (eg. StudentDAO, CourseDAO..) and transfer object (eg. StudentTO, CourseTO)?
Because I find that a class diagram belong to the second mode I metioned above in a book "Sun Certified Enterprise Architect for Java EE Study Guide, Second Edition".
A class diagram can include as many information as you need.
I think that adding additional information (e.g. Entity, Session etc....) is really important but many modelers consider that the PIM could not include PSM information.
This is for me modelers brain masturbation
The current situation I see is that only Omondo has developped Jee, persistance profiles which allow to add stereotypes and get annotation code from your class diagram.
It means that the public adoption is very low and the PIM PAN PUNG is still winning