This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Use case diagrams are static or dynamic diagrams? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Use case diagrams are static or dynamic diagrams?" Watch "Use case diagrams are static or dynamic diagrams?" New topic
Author

Use case diagrams are static or dynamic diagrams?

vijay Mamilla
Ranch Hand

Joined: Dec 29, 2004
Posts: 94
Use case diagrams are Behavior Diagrams
Use case diagrams are static or dynamic diagrams?
Ali Reza Hosseini
Ranch Hand

Joined: Apr 28, 2005
Posts: 33
use case diagramms are structural, because they only demonstrate
WHICH functionalities a system provides and HOW the given
functionalities are structured but not HOW the system
is providing them.
vijay Mamilla
Ranch Hand

Joined: Dec 29, 2004
Posts: 94
Ali,

Is Use case diagram is static diagram?

VJ
Ali Reza Hosseini
Ranch Hand

Joined: Apr 28, 2005
Posts: 33
In my opinion, yes they are static, because they describe
only the structure of a system.
kaiser eblovich
Greenhorn

Joined: May 28, 2005
Posts: 23
no guys, they are not
(for the UC diagrams are describing the behaviour of the system, and the behaviour is inherently dynamic)

Kaiser Eblovich,
Sun Certified Everything
Ali Reza Hosseini
Ranch Hand

Joined: Apr 28, 2005
Posts: 33
they are not dynamic because
dynamic diagramms explain changes in a system's state over time,
this is what behavior is about.

Usecase diagramms don't describe state changes over time, they only
describe how the system functionality is structured ...
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2922
    
    5
According to The Unified Modeling Language Reference Manual 1e (Rumbaugh,Jacobson,Booch) use case diagrams are part of the use case model which itself is focused on the use case view which is part of the dynamic view.


{page 494}
use case diagram: A diagram that shows the relationship and use cases within a system. See actor, use case. Notation A use case diagram is a graph of actors, a set of use cases enclosed by a system boundary (a rectangle), associations between actors and the use cases, relationships among the actors. Use case diagrams show elements from the use case model (use cases,actors).

{page 496}
use case model: A model that describes the functional requirements of a system or other classifier in terms of use cases. See actor, use case. Semantics The use case model represents functionality of a system or other classifier as manifested to external interactors with the system. A use case model is shown on a use case diagram.

use case view: That aspect of the system concerned with specifying behavior in terms of use cases. A use case model is a model focused on this view. A use case view is part of the set of modeling concepts loosely grouped together as the dynamic view.

{page 265}
dynamic view: That aspect of a model dealing with the specification and implementation over time, as distinguished from static structure found in the static view. The dynamic view is a grouping term that includes the use case view, state machine view, activity view, and interaction view.
vijay Mamilla
Ranch Hand

Joined: Dec 29, 2004
Posts: 94
Thanks
Ali Reza Hosseini
Ranch Hand

Joined: Apr 28, 2005
Posts: 33
OK, but I think that the uml specs are wrong at this position ...

.. because ..

as there stays about the definition of dynamic view: " .. That aspect of a model dealing with the specification and implementation over time .."

but usecase diagrams do not include any information about
specification and implementation OVER TIME ...

from a scientific point of view, I vehemently disagree with that !!!



alireza
Meena Anduvan
Greenhorn

Joined: Nov 11, 2005
Posts: 1
There is a BIG difference between a "view" and an actual "diagram".
In UML Use Case diagrams are only the STRUCTURE of the system and are STATIC. They are a STATIC component of a dynamic view - but have no concept of time or of change and are NOT dynamic themselves.

Have a look at this: http://www.developer.com/design/article.php/1553851

The UML diagrams that fall under each of these categories are:
1) Static:
oUse case diagram <=== !!!
oClass diagram
2) Dynamic:
oObject diagram
oState diagram
oActivity diagram
oSequence diagram
oCollaboration diagram
3)Implementation
oComponent diagram
oDeployment diagram
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2922
    
    5
With all due respect to the authors of that article I'm sticking to the Three Amigos in all matters UML. The "Unified Modeling Language User Guide", Chapter 17: Use Case Diagrams

Use case diagrams are one of the five diagrams in the UML for modeling the dynamic aspects of systems (activity diagrams, statechart diagrams, sequence diagrams, and collaboration diagrams are the four other kinds of diagrams in the UML for modeling dynamic aspects of systems).

Their definition of "dynamic" may be simply "not static". Chapter 16: Use Cases

A use case describes a set of sequences, in which each sequence represents the interaction of things outside the system (its actors) with the system itself (and its key abstractions).

A sequence is neither instantaneous, nor permanent. So it takes place over time - not necessarily properly quantified, nor the order of the steps identified.
[ November 11, 2005: Message edited by: Peer Reynders ]
 
GeeCON Prague 2014
 
subject: Use case diagrams are static or dynamic diagrams?