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

[milochen]

I study UML by myself in the book
The Unified Modeling Language User Guide
written by Grady Booch, James Rumbaugh and Ivar Jacobson.

From study this book,

I understand that use case diagram is for static view, but
suddenly is for dynamic.

Since the book say
"the static aspects of this (use case)view are captureed in use case
diagrams."
^^^^^^^
and also say
"use case diagram is one of the additional diagram
to view the dynamic parts of a system use case diagram"
^^^^^^^^^^

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.
Thank you very much.




PS:The full context about my problem is describing as the following...
==========================================

In page 32, it say that
The use case view of a system encompasses the use cases that describe
the
behavior of the system as seen by its end users, analysts,and testers.
This view
doesn't really specify the organization of software system. Rather it
exists to
specify the forces that shape the system's architecture. With the UML,
the
static aspects of this view are captured in use case diagrams; the
dynamic
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
aspects of this view are captured in interaction diagrams, statechart
diagrams,
and activity diagram.

In page 94, it say that
You'll often use five additional diagrams to view the dynamic parts of
a
system.
^^^^^^^^^^^^^^^^^^^^^^^^^^

1. Use case diagram
^^^^^^^^^^^^^^^^^^^^^
2. Sequence diagram
3. Collaboration diagram
4. Statechart diagram
5. Activity diagram

[mAsterdam]

Post by milochen
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.

[milochen]

So the author of this book was just give us a suggestion,
but not the absolute way.
Because the suggestion is not always definitly true.

How to choice a good diagram fit you to describe into clear
is better than
choice the diagram that author suggest you to choice.
Right?

Post by mAsterdam

Post by milochen
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.

[H. S. Lahman]

Responding to Milochen...

Post by milochen
I study UML by myself in the book
The Unified Modeling Language User Guide
written by Grady Booch, James Rumbaugh and Ivar Jacobson.

From study this book,

I understand that use case diagram is for static view, but
suddenly is for dynamic.
Since the book say
"the static aspects of this (use case)view are captureed in use case
diagrams."
^^^^^^^

This just means that a Use Case Diagram just captures the static
structural relationships among use cases, actors, etc. The diagram does
not capture the dynamic /content/ of the use cases.

Post by milochen
and also say
"use case diagram is one of the additional diagram
to view the dynamic parts of a system use case diagram"
^^^^^^^^^^
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.
Thank you very much.

I think you are correct. The Use Case Diagram only describes static
structure, not the dynamics of individual use case content. However,
one can establish links to other UML diagrams (Sequence Diagrams,
Statecharts, Activity Diagrams) that do describe the behavior within use
cases.

In my edition Use Case Diagrams are grouped under Behavioral Diagrams,
which makes no sense to me. The justification in the text is that they
"organize the behaviors". While that is true in the sense that each use
case defines a different set of actor activities, I think that is a
major stretch of the imagination. The diagram itself makes provides no
representation of behavior. Any such inference depends on knowing what
the content of the use cases is.

Since Use Cases are really just an alternative expression of
requirements that conveniently organizes them around user activities, I
can only assume that the authors saw that organization of requirements
as the primary aspect of Use Cases when they decided how to categorize
the Use Case Diagram.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
***@pathfindermda.com
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH