blob: 881e5a32a51ea8464ea769190fb318b254de6ecc (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
/**
*/
package org.eclipse.papyrus.eastadl.requirements.requirements;
import org.eclipse.emf.common.util.EList;
import org.eclipse.uml2.uml.Dependency;
/**
* <!-- begin-user-doc -->
* A representation of the model object '<em><b>Link</b></em>'.
* <!-- end-user-doc -->
*
* <!-- begin-model-doc -->
* RequirementsLink represents a relation between two or more Requirements. Source and target Requirements of the relation are distinguished, which means that the relation is directed (from source to target). If such a distinction does not make sense, then use a RequirementsGroup instead.
*
* The standard case will be a relation with one source and one target Requirement. However, it is possible to have several source and/or several target Requirements so that general relations can be expressed with instances of this metaclass.
*
* The semantic of a concrete Requirement relation can be provided by the modeler. In particular, three ways are conceivable:
*
* (1) The user attributes of the relation can be used to specify its meaning, for example with a user attribute called "relationType" which is set to values such as "needs" or "excludes".
*
* (2) The UserAttributeElementType can be used. Certain types will be used for certain relation semantics.
*
* (3) RequirementsRelationGroups can be used, i.e. all relations with an "excludes" meaning are put in one relation group and all with a "needs" meaning are put in another.
* <!-- end-model-doc -->
*
* <p>
* The following features are supported:
* <ul>
* <li>{@link org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsLink#isIsBidirectional <em>Is Bidirectional</em>}</li>
* <li>{@link org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsLink#getSource <em>Source</em>}</li>
* <li>{@link org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsLink#getTarget <em>Target</em>}</li>
* <li>{@link org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsLink#getBase_Dependency <em>Base Dependency</em>}</li>
* </ul>
* </p>
*
* @see org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsPackage#getRequirementsLink()
* @model
* @generated
*/
public interface RequirementsLink extends RequirementsRelationship {
/**
* Returns the value of the '<em><b>Is Bidirectional</b></em>' attribute.
* <!-- begin-user-doc -->
* <p>
* If the meaning of the '<em>Is Bidirectional</em>' attribute isn't clear,
* there really should be more of a description here...
* </p>
* <!-- end-user-doc -->
* @return the value of the '<em>Is Bidirectional</em>' attribute.
* @see #setIsBidirectional(boolean)
* @see org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsPackage#getRequirementsLink_IsBidirectional()
* @model unique="false" dataType="org.eclipse.uml2.types.Boolean" required="true" ordered="false"
* @generated
*/
boolean isIsBidirectional();
/**
* Sets the value of the '{@link org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsLink#isIsBidirectional <em>Is Bidirectional</em>}' attribute.
* <!-- begin-user-doc -->
* <!-- end-user-doc -->
* @param value the new value of the '<em>Is Bidirectional</em>' attribute.
* @see #isIsBidirectional()
* @generated
*/
void setIsBidirectional(boolean value);
/**
* Returns the value of the '<em><b>Source</b></em>' reference list.
* The list contents are of type {@link org.eclipse.papyrus.eastadl.requirements.requirements.Requirement}.
* <!-- begin-user-doc -->
* <p>
* If the meaning of the '<em>Source</em>' reference list isn't clear,
* there really should be more of a description here...
* </p>
* <!-- end-user-doc -->
* @return the value of the '<em>Source</em>' reference list.
* @see org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsPackage#getRequirementsLink_Source()
* @model required="true" transient="true" changeable="false" volatile="true" derived="true" ordered="false"
* @generated
*/
EList<Requirement> getSource();
/**
* Returns the value of the '<em><b>Target</b></em>' reference list.
* The list contents are of type {@link org.eclipse.papyrus.eastadl.requirements.requirements.Requirement}.
* <!-- begin-user-doc -->
* <p>
* If the meaning of the '<em>Target</em>' reference list isn't clear,
* there really should be more of a description here...
* </p>
* <!-- end-user-doc -->
* @return the value of the '<em>Target</em>' reference list.
* @see org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsPackage#getRequirementsLink_Target()
* @model required="true" transient="true" changeable="false" volatile="true" derived="true" ordered="false"
* @generated
*/
EList<Requirement> getTarget();
/**
* Returns the value of the '<em><b>Base Dependency</b></em>' reference.
* <!-- begin-user-doc -->
* <p>
* If the meaning of the '<em>Base Dependency</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 Dependency</em>' reference.
* @see #setBase_Dependency(Dependency)
* @see org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsPackage#getRequirementsLink_Base_Dependency()
* @model required="true" ordered="false"
* @generated
*/
Dependency getBase_Dependency();
/**
* Sets the value of the '{@link org.eclipse.papyrus.eastadl.requirements.requirements.RequirementsLink#getBase_Dependency <em>Base Dependency</em>}' reference.
* <!-- begin-user-doc -->
* <!-- end-user-doc -->
* @param value the new value of the '<em>Base Dependency</em>' reference.
* @see #getBase_Dependency()
* @generated
*/
void setBase_Dependency(Dependency value);
} // RequirementsLink
|
