Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'extraplugins/eastadl/org.eclipse.papyrus.eastadl/src/org/eclipse/papyrus/eastadl/structure/functionmodeling/FunctionPowerPort.java')
-rw-r--r--extraplugins/eastadl/org.eclipse.papyrus.eastadl/src/org/eclipse/papyrus/eastadl/structure/functionmodeling/FunctionPowerPort.java37
1 files changed, 22 insertions, 15 deletions
diff --git a/extraplugins/eastadl/org.eclipse.papyrus.eastadl/src/org/eclipse/papyrus/eastadl/structure/functionmodeling/FunctionPowerPort.java b/extraplugins/eastadl/org.eclipse.papyrus.eastadl/src/org/eclipse/papyrus/eastadl/structure/functionmodeling/FunctionPowerPort.java
index 4f3681565f1..6118c77680c 100644
--- a/extraplugins/eastadl/org.eclipse.papyrus.eastadl/src/org/eclipse/papyrus/eastadl/structure/functionmodeling/FunctionPowerPort.java
+++ b/extraplugins/eastadl/org.eclipse.papyrus.eastadl/src/org/eclipse/papyrus/eastadl/structure/functionmodeling/FunctionPowerPort.java
@@ -23,47 +23,51 @@ import org.eclipse.uml2.uml.Port;
* <!-- begin-user-doc -->
* A representation of the model object '<em><b>Function Power Port</b></em>'.
* <!-- end-user-doc -->
- *
+ *
* <!-- begin-model-doc -->
* The FunctionPowerPort is a FunctionPort for denoting the physical interactions between environment and sensing/actuation functions.
*
- * Semantics:
+ * Semantics:
* The FunctionPowerPort conserves physical variables in a dynamic process.
*
- * The typing Datatype owns two datatypePrototypes called Across and Through, representing the exchanged physical variables of the FunctionPowerPort. In two or more directly connected function power ports, the Across variables always get the same value and the Through variables always sum up to zero.
+ * The typing Datatype owns two datatypePrototypes called Across and Through, representing the exchanged physical variables of the FunctionPowerPort.
+ * In two or more directly connected function power ports, the Across variables always get the same value and the Through variables always sum up to
+ * zero.
*
* Constraints:
- * [1] The owner of a FunctionPowerPort is either a FunctionalDevice, a HardwareFunctionType, or a FunctionType for environment
+ * [1] The owner of a FunctionPowerPort is either a FunctionalDevice, a HardwareFunctionType, or a FunctionType for environment
*
* [2] Two connected FunctionPowerPort must have the same Datatype.
*
- * [3] The typing Datatype shall have two datatypePrototypes called Across and Through, with Datatypes that are consistent and representing the variables of the PowerPort.
+ * [3] The typing Datatype shall have two datatypePrototypes called Across and Through, with Datatypes that are consistent and representing the
+ * variables of the PowerPort.
*
*
* Extension: UML Port
* <!-- end-model-doc -->
- *
+ *
* <p>
* The following features are supported:
* <ul>
- * <li>{@link org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionPowerPort#getBase_Port <em>Base Port</em>}</li>
- * <li>{@link org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionPowerPort#getType <em>Type</em>}</li>
+ * <li>{@link org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionPowerPort#getBase_Port <em>Base Port</em>}</li>
+ * <li>{@link org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionPowerPort#getType <em>Type</em>}</li>
* </ul>
* </p>
- *
+ *
* @see org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionmodelingPackage#getFunctionPowerPort()
* @model
* @generated
*/
public interface FunctionPowerPort extends FunctionPort {
+
/**
* Returns the value of the '<em><b>Base Port</b></em>' reference.
* <!-- begin-user-doc -->
* <p>
- * If the meaning of the '<em>Base Port</em>' reference isn't clear,
- * there really should be more of a description here...
+ * If the meaning of the '<em>Base Port</em>' reference isn't clear, there really should be more of a description here...
* </p>
* <!-- end-user-doc -->
+ *
* @return the value of the '<em>Base Port</em>' reference.
* @see #setBase_Port(Port)
* @see org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionmodelingPackage#getFunctionPowerPort_Base_Port()
@@ -73,10 +77,13 @@ public interface FunctionPowerPort extends FunctionPort {
Port getBase_Port();
/**
- * Sets the value of the '{@link org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionPowerPort#getBase_Port <em>Base Port</em>}' reference.
+ * Sets the value of the '{@link org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionPowerPort#getBase_Port <em>Base Port</em>}'
+ * reference.
* <!-- begin-user-doc -->
* <!-- end-user-doc -->
- * @param value the new value of the '<em>Base Port</em>' reference.
+ *
+ * @param value
+ * the new value of the '<em>Base Port</em>' reference.
* @see #getBase_Port()
* @generated
*/
@@ -86,10 +93,10 @@ public interface FunctionPowerPort extends FunctionPort {
* Returns the value of the '<em><b>Type</b></em>' reference.
* <!-- begin-user-doc -->
* <p>
- * If the meaning of the '<em>Type</em>' reference isn't clear,
- * there really should be more of a description here...
+ * If the meaning of the '<em>Type</em>' reference isn't clear, there really should be more of a description here...
* </p>
* <!-- end-user-doc -->
+ *
* @return the value of the '<em>Type</em>' reference.
* @see org.eclipse.papyrus.eastadl.structure.functionmodeling.FunctionmodelingPackage#getFunctionPowerPort_Type()
* @model required="true" transient="true" changeable="false" volatile="true" derived="true" ordered="false"

Back to the top