• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Breaking Large Diagrams into Pieces

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have reduced sequence diagrams and component diagrams into smaller pieces for the exam assignment. Is this approach being used for those who has passed the exam?
 
Ranch Hand
Posts: 142
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I haven't completed my certification yet, but this is the approach I am following.
Sridhar-
 
Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
For disjunct diagrams that is probabely an easy way.
But if you for example want to show the interaction from Java-client through BusinessDelegate with ServiceLocator, SessionFacade, workflow SessionBeans, EntityBeans plus DAO to an external system, then I would like to see an example of where to cut the diagram into pieces and how to cut. There are no "black bullets" like in data flow diagrams or "Subsystem" in Package Diagrams.
One good point to cut the diagram might be between a Business Delegate and a Session Facade. This might be true for class, component and interaction diagrams respectively.
Another cutting line might be between Java-client and JSP/Servlet related classes.
I even think that thinking in cuttable subsystems will prepare a well designed component diagram.
For cutting between SessionBeans and Entity Beans I have no idea because there is not a single point that could be cut but a M:N relationship between SessionBeans and EntityBeans.
For class, component and interaction diagrams UML as far as I know does not offer anything like it offers a "Subsystem" for Package Diagrams - am I right?.
Any more ideas?
Thomas.
 
pie. 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