Re: In book,Use case diagram is static or dynamic view? (for UML)

milochen wrote:
I really can't understand why use case diagram is static diagram, but
sometime be dynamic. I don't know how to understand it correctly.

All these diagram are just graphical syntaxes for
the visualization of some aspect of the software
under scrutiny. You decide which aspect to show,
you choose the diagramming technique. Before
the UML there were literally hundreds of those syntaxes,
all different in some detail, sometimes fundamentally
different.

A use case diagram is just a visualization
of the use of a system. You choose whether you want
to visualize a static or dynamic phenomenon in your diagram.

--
"The person who says it cannot be done
should not interrupt the person doing it."
Chinese Proverb.
.

Relevant Pages

  • Re: Do developers think more textually than graphically?
    ... > a developer to draw a high level diagram of a system, ... Would you believe the developer did NO ... > size - bishops are taller, ... > And some of them rely more on text, others do more visualization. ...
    (comp.object)
  • Re: In book,Use case diagram is static or dynamic view? (for UML)
    ... Because the suggestion is not always definitly true. ... How to choice a good diagram fit you to describe into clear ... All these diagram are just graphical syntaxes for ... A use case diagram is just a visualization ...
    (comp.object)
  • Visualizing Large C Code Projects
    ... Hi I'm currently building a graphical refactoring tool for C and I was ... concepts for visualizing the dependencies in a C project. ... to find plenty of nifty visualization concepts and ideas for OO ... diagram but that's not really in keeping with our requirements. ...
    (comp.graphics.visualization)