• 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

Service/Manager implementation classes in Class/Sequence Diagrams

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

In my design I decided to go for "design by interface" approach to improve decoupling, reusability and testability. In practice it means that every Service or Manager has an interface and implementation and if any other class uses it, it is references by interface. Classic, right? Especially when using EJB3 or Spring.

I got confused though when presenting such approach on diagrams. It clutters the picture a bit and it doesn't look like giving any value there. On the other hand it's pretty essential part of design so it should be presented somehow (or at least mentioned in assumptions for Class diagram).

What do you think about it? How you present Service/Manager-like classes in Class Diagram?

What about Sequence Diagrams: calls should go to interfaces or implementations?

Thanks a lot for any comments.

Cheers,
Maciek
 
Maciek Falski
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Anyone?
 
reply
    Bookmark Topic Watch Topic
  • New Topic