Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Showing both Value Object and its corresponding Domain object in Class diagram

 
Sam Gehouse
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have the examinees shown both Value object and its corresponding domain object in the class diagram?
 
Pham Huy Anh
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I think Business Domain Object is the term that Business Analysist uses to modelize. In Java design, it should be transformed into Value Object/Transfer Object or (entity EJB). I prefer VO/TO 'cause it is more clear, and easy to understand (Object that stores data, that glues layers, components.

How do you think?

In fact, the term VO/TO is defined by Sun. I worked for IBM, they said BusinessObject, DataObject

http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html
 
Ricardo Ferreira
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sam,

When designing your class diagram, I should try to focus on object oriented analysis and design techniques (OOAD). At the analysis level, do not include any architectural patterns in the diagram. They should only define business entities and contraints.

At the design level, you can put some extra classes like TO/VO's. To be honest with you, for the exam pourposes, it do not require those patterns. Try to keep your class diagram technology neutral, regardless the business components like fa´┐Żades or business objects.

Regards,
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic