aspose file tools*
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Questions on Sequence Diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Questions on Sequence Diagram" Watch "Questions on Sequence Diagram" New topic
Author

Questions on Sequence Diagram

Peter Lee
Greenhorn

Joined: Jun 25, 2003
Posts: 24
HI,
1. I don't want to include many pattern related objects (e.g. HTMLAction, create event) in the sequence diagram and I read other experiences that it is not necessary too. However, if not include those objects in sequence diagrams but only keep in component diagrams, how come developers know the communication between objects? Is my view point right?
2. Is it required to draw sequence diagrams for user creation and user signon?
Thanks.
Regards,
Peter
Ajith Kallambella
Sheriff

Joined: Mar 17, 2000
Posts: 5782
Originally posted by Peter Lee:

1. I don't want to include many pattern related objects (e.g. HTMLAction, create event) in the sequence diagram and I read other experiences that it is not necessary too. However, if not include those objects in sequence diagrams but only keep in component diagrams, how come developers know the communication between objects? Is my view point right?

One of the advantages of using design patterns is that it promotes a common vocabulary ie,. when you speak of a "controller", everyone in your team( assuming they are all good Java programmers with a good knowledge of design patterns) understand what you are talking about. It is for this reason, as an architect, you can often talk the pattern jargon without having to explain all the collarborations and participants.
You *can* include pattern related entities in your sequence diagram if it makes sense. There is no black and white rule here. For instance, you can show a line going from <<CreateItinerary View>> to <<CreateItinerary Action>> in your sequence diagram and safely assume that the evaluator understands that these two collaborating components implement the MVC pattern. Another way to include pattern-related details in the sequence diagram without cluttering is to name your participants appropriately.
ReservationsSessionFacade, TheFlightSeatMapSingleton, CreditCardSystemAdapter etc are some examples.
Hope that helps,


Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Questions on Sequence Diagram