All geek questions in one place

When to break down on a sequence diagram

In fact, I cannot find a clear answer. Many interactive design tools (such as Web Sequence Diagrams ) have the option to “activate” and “deactivate” a process, while it is a separate action to “kill” a process. When is it used?

If in the diagram I am modeling, I connect to the online stream, when I am done with this, will I deactivate it or destroy it? When I use the application and it is finished, will I deactivate it or destroy it?

+4
source share
2 answers

In UML, destruction in a sequence diagram means "a message view representing a life cycle destruction request for the life line of a target," that is, the message recipient object is logical or physical remote and inaccessible to future interactions. Deactivate means that the message recipient's object will change from an active to an inactive state, with the possibility of reactivation in a later state. therefore, objects are still available in the application space, but can, for example, move to the archive over time.

+1
source

Destruction would make sense if you were specifying an instance instance somewhere in your diagram.

  • For existing resources, such as an online stream, activating / deactivating makes more sense.
  • For things like running a script, creating / destroying would be better.
+1
source

Source: https://habr.com/ru/post/1500060/

More articles:


All Articles