• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

POJO's / Value objects in the Sequence Diagrams

 
W. Walden
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have many places in my sequence diagrams where plain value objects are created. For example, when a search is done for flights, one of my DAO classes creates multiple Segments to combine together into a Flight. Both Flight and Segment are just value objects, and their usage in the sequence diagrams boils down to just alot of calls to "create()" (since these classes don't have methods).
So, should these type of classes be in the sequence diagrams at all?.. or could is it safe to assume that a call to a DAO object called "getFlight" will create a Flight object.
My diagrams would be much cleaner without them, but if they are supposed to be there, it would mean many points lost.
What do you guys think? Anyone pass who left them off? Thanks.
 
Bharat Ruparel
Ranch Hand
Posts: 493
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You wrote:

So, should these type of classes be in the sequence diagrams at all?.. or could is it safe to assume that a call to a DAO object called "getFlight" will create a Flight object.

My recommendation will be not to clutter your sequence diagrams with Value Objects (or Transfer Objects). You may want to make a general statement in your assumption document, e.g., it is assumed that the data returned/sent amongst different tiers (presentation/business/integration) will be in the form of Value Objects/Transfer Objects assembled using the composite pattern.
That is what I am doing anyway.
Regards.
Bharat
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic