Sequence diagrams need not exactly match all the methods in your class diagrams. Make it simple and remember you are architecting the application and not programming. Try to show the interactions as simple messages or java method names. Also remember to keep your classes simple
I don't mean to split hairs here, but sequence diagrams normally depict objects and not classes as participants. Therefore, it is a normal practice to represent the senders/receivers of messages in the form objectName:className. You can omit the objectName and only show :className if your intention is to depict any object instance of that class. Cheers,
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
Thanks for the clarification. What I meant was, if I use say a Home object in the sequence diagram to get a reference to an enterprise bean, should that home object be represented as a class in the class diagram or are the details not important in the class diagram.
This looks like a job for .... legal tender! It says so right in this tiny ad:
a bit of art, as a gift, the permaculture playing cards