This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes New to Part 2: What should be in the class diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "New to Part 2: What should be in the class diagram" Watch "New to Part 2: What should be in the class diagram" New topic
Author

New to Part 2: What should be in the class diagram

david chen
Ranch Hand

Joined: Nov 30, 2001
Posts: 44
Hi,

I'm new to Part 2 of SCEA. I was looking at the BDM. I believe the entities in the BDM would translate to classes in the class diagram. Aside from these entities in BDM, what should still be put in the class diagram, EJB objects, controllers?

Thank you very much.

- David
Francis Amanfo
Ranch Hand

Joined: Nov 02, 2003
Posts: 44
What to put in class diagram?
Some spices, pepper, garlic and not too much salt but don't forget onions. It'll then taste great!
Sorry, trying to be funny but not mean. I would have to say however that your question is too general. Maybe you should read some of the software design books first.

Regards

F
[ January 03, 2006: Message edited by: Francis Amanfo ]
Terry McKee
Ranch Hand

Joined: Sep 29, 2000
Posts: 173
Hey David,

If you browse through the posts here, you will see that people have done it a variety of ways. Most of the posts that I have read indicate that you shouldn't put implementation specific classes into the diagram (like controllers, EJBs, etc.). In fact, many that have done this have had to resubmit their assignment later.

As Francis indicated, reading more about software design (architecture) will help you to make decisions about what is important to put in the class diagrams. People have passed by modifying and people have passed by not modifying the original Business Domain Diagram. The key then is not in so much the decisions you make (although if you make a crazy class model you clearly won't pass), rather, (1) how consistent you are acoss all of your documents and (2) how clearly you justify your decisions in your documentation.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: New to Part 2: What should be in the class diagram