Hi Is it enough for sequence diagrams to show interacting components or do individual classes have to be shown. The number of classes used will make the component diagram cramped.
Thanks for joining JavaRanch. Unfortunately your name violates our naming policy. Please take a quick look at the rules and edit your profile accordingly. Thank you!
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
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
Ajith Kallambella
Sheriff
Posts: 5782
posted 14 years ago
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).
sriram ramanathan
Greenhorn
Posts: 12
posted 14 years ago
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.
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database