Yeah, I agree with Tomi. Just stick to the core business model, dont show any implementation specific classes (controllers, delegators,facades,daos etc). If you are still inclined to show the entities and session, show them as <<stereotypes>> in your class diagram. eg. Customer can have a <<entity>> stereotype attached to it. The only thing I am very tempted to show are the adapters to the outside system. Am trying to figure out where they would fit in the class diagram, or I might just show them standing alone in some corner of the class diagram
Originally posted by Eduardo Rodrigues: Hi guys My class diagram contains only 10 classes . I�m showing only the core business model classes. None EJB, only the entities and their relationships... Am I wrong or missing something???
Eduardo, I dont think the number of the classes matter. If your model meets the requirements of the system, then you are fine. Keeping the model simple should be your main priority.
Joined: Apr 25, 2003
I was also inclined not to show any EJBs etc on class diagram as I think class diagram should purely represent domain and not the framework (J2ee in our case) we want to use. I was confused because lot of people here discussed putting enity/sessions/managers/controllers etc on the diagram.
Assignment only says about one class diagram in delverables. I would have liked to draw two diagrams really- one purely domain/business view and other design view. Are there any guidelines for this?
Eduardo you need not worry about actual number of classes but make sure you have cpatured all the business model neatly.
Joined: Jul 01, 2003
Thank you so much guys! I will keep my class diagram without 'technology classes'.. Only the business model...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com