• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

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

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
Peter
 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 .
Thanks,
Dhanush
reply
    Bookmark Topic Watch Topic
  • New Topic