User Tools

Site Tools


v070:layout

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
v070:layout [2018/10/05 22:10]
djnemeth [Diagram Language Description for version 0.7.0]
v070:layout [2018/10/08 09:08] (current)
djnemeth [Execution]
Line 195: Line 195:
  
 ==== General structure ==== ==== General structure ====
-A sequence diagram description is a Java class inheriting from class ''​SequenceDiagram''​+A sequence diagram description is a Java class inheriting from class [[http://​txtuml.inf.elte.hu/​releases/​txtuml-v070/​api/​java/​hu/​elte/​txtuml/​api/​model/​seqdiag/​SequenceDiagram.html|SequenceDiagram]]
  
 Lifelines can be defined as class members in a diagram description. To give an ordering between them on the generated diagram, the ''​Position''​ annotation can be used.  Lifelines can be defined as class members in a diagram description. To give an ordering between them on the generated diagram, the ''​Position''​ annotation can be used. 
Line 208: Line 208:
  
   * ''​Sequence.send(from,​ msg, to)'':​ **from** is expected to send a message to **to** which is equal to **msg**.   * ''​Sequence.send(from,​ msg, to)'':​ **from** is expected to send a message to **to** which is equal to **msg**.
-  * ''​Sequence.fromActor(msg,​ to)'':​ **msg** should be sent to **to** by an actor.+  * ''​Sequence.fromActor(msg,​ to)'':​ **msg** should be sent to **to** by an actor. Reaching this call, the sequence diagram executor actually sends the message to the target.
   * ''​Sequence.assertState(obj,​ s)'':​ immediately after the target of the most recent ''​Sequence.send''​ or ''​Sequence.fromActor''​ call has received the message, **obj** is in state **s** (also see [[v070:​layout#​Condition evaluation during execution]]).   * ''​Sequence.assertState(obj,​ s)'':​ immediately after the target of the most recent ''​Sequence.send''​ or ''​Sequence.fromActor''​ call has received the message, **obj** is in state **s** (also see [[v070:​layout#​Condition evaluation during execution]]).
  
Line 240: Line 240:
  
 ==== Execution ==== ==== Execution ====
-The execution of the diagram can be configured by setting the execution mode. For this purpose, the ''​ExecutionMode''​ annotation ​of the ''​run''​ method ​can be used.+The execution of the diagram can be configured by setting the execution mode. For this purpose, the ''​ExecutionMode''​ annotation ​can be used on the ''​run''​ method .
  
-Regardless of the chosen mode, the entire messaging defined in ''​run''​ should ​happen ​in the model during the execution. ''​ExecMode.STRICT''​ does not allow any other communication,​ while ''​ExecMode.LENIENT''​ does.+Regardless of the chosen mode, the entire messaging defined in ''​run''​ should ​occur in the model during the execution. ''​ExecMode.STRICT''​ does not allow any other communication,​ while ''​ExecMode.LENIENT''​ does.
  
 === Condition evaluation during execution === === Condition evaluation during execution ===
v070/layout.1538770238.txt.gz ยท Last modified: 2018/10/05 22:10 by djnemeth