Win a copy of Spring Boot in Practice this week in the Spring forum!
  • 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 ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Detail legel of Sequence Diagrams.

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

I am confused, how detailed Sequence Diagrams should be.

For example, we have Sale-SaleLineItem-Product model.

- Should SD show only handling of system events? E.g. interaction of SaleUseCaseFrontController, SaleUseCaseBusinessDelegator, ServiceLocator, SaleUseCaseApplicationController, DAO, �
Like SD for Application Controller in "Core J2EE Patterns" book.

- Or should SD show more details? E.g. interaction of about components + interaction of domain classes: how Sale, SaleLineItem, Product are created. How they are linked.
Like in the "Applying UML and Patterns" Chapter 17.

Thanks a lot.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic