File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Showing Design Pattern in Diagrams (Part 2)... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Showing Design Pattern in Diagrams (Part 2)..." Watch "Showing Design Pattern in Diagrams (Part 2)..." New topic

Showing Design Pattern in Diagrams (Part 2)...

Peter Lee

Joined: Jun 25, 2003
Posts: 24
Dear all,
Just want to have a discussion on where will you guys show design pattern for Part 2 diagrams.
My plan is I mainly show the design pattern (i.e. session facade, business delegate, DAO, VO and etc) on comoponent diagram and try to keep less pattern related matters in class diagram and sequence diagrams. It is because if showing design pattern related objects in sequence diagrams, it will make the diagrams quite difficult to read and also it seems the main purpose of sequence diagram is to show the message communication between objects, so I think depicts design pattern objects in component is fair enough.
Any comments?
Dhanush Dharsh
Ranch Hand

Joined: Oct 30, 2000
Posts: 33
Hi Peter,
Putting the design pattern related stuff in component diagram is a favoured approach I too found in many forums. As you mentioned, it would help keep the class & sequence diagrams simpler and get the seq diagram concentrate more on communication flow .
I agree. Here's the link:
subject: Showing Design Pattern in Diagrams (Part 2)...
It's not a secret anymore!