Help coderanch get a
new server
by contributing to the fundraiser
  • 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
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

Detail legel of Sequence Diagrams.

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

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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic