• 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
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Depicting Design Patterns in Component Diagram

 
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Friends,
As per cade's book we should show design patterns in component diagram. In my case i have SessionFacade, DAO etc in my design. Any idea how to show that these components are implementing a design pattern? Is it using custom stereotypes for the component or using UML notes on the diagram?
 
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Amit, as we know component diagram carries very decent number of points so text description of every single component in HTML tabular format would make more sense to me. I did that. Try to keep your diagram very open and very high level. You could show the things in groups like All JSP related to one module in one groups Component. Your description would say what all the sub components are in the group.
 
Kumar Amit
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Rajan Choudhary wrote:Amit, as we know component diagram carries very decent number of points so text description of every single component in HTML tabular format would make more sense to me. I did that. Try to keep your diagram very open and very high level. You could show the things in groups like All JSP related to one module in one groups Component. Your description would say what all the sub components are in the group.


Hi Rajan,
Thanks for the reply. I have also done the same. However do i need to show design patterns on the diagram itself as well or textual description of the pattern in the document is sufficient?
 
Rajan Choudhary
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Add one group component for DTOs, helpers, patterns etc and then describe actual components in text in a tabular form.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic