User Tools

Site Tools


v070:modeling

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:modeling [2018/10/08 21:58]
djnemeth [Associations]
v070:modeling [2018/10/08 23:08] (current)
djnemeth [External elements]
Line 341: Line 341:
 === Ports === === Ports ===
  
-Ports of a class are defined inside the class. Ports can be characterized by two interfaces: The //​provided//​ interface defines which signals can be sent to that port by the environment of the class. The //​required//​ interface tells which signals can be sent from the port to the environment.+Ports of a class are defined inside the class. Ports can be characterized by two interfaces: The //​provided//​ interface defines which signals can be sent to that port by the environment of the class. The //​required//​ interface tells which signals can be sent from the port to the environment. This might feel counter-intuitive,​ but the reasoning behind is that in this context, signals represent //​requests//​.
  
 <​code>​ <​code>​
Line 821: Line 821:
 <code java> <code java>
 // JtxtUML: // JtxtUML:
-Action.connect(CA.e.class, ​aObj.port(A.P.class),​ +Action.connect(CAB.e.class, ​instanceOfA.port(A.P.class),​ 
-               CB.f.class, ​bObj.port(B.Q.class));​+               CAB.f.class, ​instanceOfB.port(B.Q.class));​
  
 // In case of the following connector definition: // In case of the following connector definition:
Line 891: Line 891:
 To keep txtUML models compliant to the UML standard, several limitations have to be considered during modeling. ​ In some cases, however, it is not desired or even possible to define a functionality using the tools of UML exclusively. To address this problem, we offer the concept of //​externals//​. To keep txtUML models compliant to the UML standard, several limitations have to be considered during modeling. ​ In some cases, however, it is not desired or even possible to define a functionality using the tools of UML exclusively. To address this problem, we offer the concept of //​externals//​.
  
-A model element marked as external is invisible ​for the rest of the model. You can use any Java features inside, but that part of the model can't be referenced internally, validated, exported, visualized or translated to other languages. Currently, attributes, operations, operation bodies (both in XtxtUML and JtxtUML), types and super declarations (JtxtUML only) can be marked as external.+A model element marked as external is invisible ​to the rest of the model. You can use any Java features inside, but that part of the model can't be referenced internally, validated, exported, visualized or translated to other languages. Currently, attributes, operations, operation bodies (both in XtxtUML and JtxtUML), types and super declarations (JtxtUML only) can be marked as external.
  
 <​code>​ <​code>​
v070/modeling.1539028725.txt.gz · Last modified: 2018/10/08 21:58 by djnemeth