CORBA35-265 |
when is a connection a "bi-directional connection"? |
UML 2.0
|
|
|
open |
|
CORBA34-274 |
when is a connection a "bi-directional connection"? |
UML 2.0
|
CORBA 3.4
|
Deferred |
closed |
|
UMLR-54 |
Operation calls on behavior ports |
UML 2.0
|
|
|
open |
|
UMLR-35 |
Disjointness should be independent of generalization |
UML 2.0
|
|
|
open |
|
UML22-1381 |
presentation option for transitions |
UML 2.0
|
UML 2.1.1
|
Resolved |
closed |
|
UML22-1379 |
Figure 109, p162 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1378 |
LinkEndData - Inconsistency with Figure 146 |
UML 2.0
|
UML 2.1
|
Closed; No Change |
closed |
|
UML22-1377 |
UML-2 deployment diagram notation |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1376 |
section on connectors in the component chapter |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML23-151 |
Section: 14.3.20 |
UML 2.0
|
UML 2.3
|
Resolved |
closed |
|
UML23-148 |
UML 2 Super / Components / realizingClassifier |
UML 2.0
|
UML 2.3
|
Resolved |
closed |
|
UML22-1373 |
Section: 12.3.52 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML23-149 |
Section: 8.3.4 |
UML 2.0
|
UML 2.3
|
Resolved |
closed |
|
UML241-46 |
actions |
UML 2.0
|
|
|
open |
|
UML241-41 |
Section: 9.3.12 |
UML 2.0
|
|
|
open |
|
UML241-37 |
Section: 11.3.39 |
UML 2.0
|
|
|
open |
|
UML241-33 |
What is a mapping that is not computable? |
UML 2.0
|
|
|
open |
|
UML241-32 |
Components |
UML 2.0
|
|
|
open |
|
UML241-35 |
DeploymentSpecification - notation for DeploymentSpecification on the insta |
UML 2.0
|
|
|
open |
|
UML22-1365 |
Events |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1364 |
Additional events for Interactions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1363 |
Incorrect constraints on Pin and ObjectFlow On Pin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1362 |
resolution to issue 6093 removed too much constraint |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1361 |
Section: 9.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1360 |
Section: 7.11.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1359 |
Notation for property has gone missing |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1358 |
ReadSelfAction |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1357 |
Attribute scope is of type StructuredActivityNode instead of StructuredActi |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1356 |
Section: 12.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1355 |
What are the "edges" we're talking about? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1354 |
Section: 12.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1353 |
Figure 205, p292: |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1350 |
Figure 51, p106 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1349 |
ExceptionHandler |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1352 |
figure 175 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1351 |
Figure 52, p107: shouldn't the <> relationship be reversed ? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1348 |
Section: 12.3.16 -- Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1347 |
Templates, Classifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1346 |
ProtocolConformance - inconsistency with Figure 356 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1341 |
Can connectors co-operate? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1345 |
ParameterableElement - constraint [2] - error in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1344 |
TemplateableElement - inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1343 |
TemplateSignature - Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1342 |
TemplateSignature - inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1338 |
association "implementingClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1340 |
Removed text in 9.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1339 |
$issue.summary |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1337 |
PrimitiveFunction |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1336 |
MarshallAction and UnmarshallAction |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1335 |
Constraint 2 of AcceptEventAction - typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1334 |
SAN semantics for starting and stopping |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1333 |
Variable pins Extend input and output pins to get and set variables |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1332 |
Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1331 |
p.352, section 12.3.35. The attribute Parameter.isStream is inappropriate |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1330 |
empty sections in activities chapter |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1329 |
p.328, Figure 245, and p.331, Figure 249 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1328 |
Inappropriate to reference RFP documents |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1327 |
attribute Activity.isSingleExecution |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1326 |
Section 9.3.5. (ConnectableElement) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1325 |
Section 9.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1324 |
typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1323 |
typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1322 |
component deployment |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1321 |
signal |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1320 |
association between two Nodes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1319 |
Figure 273 - Arrow direction Figure 273 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1318 |
ParameterSet - Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1317 |
ObjectNode |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1316 |
ActivityEdge - Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1315 |
ActivityEdge - Section Semantics - Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1313 |
formal parameter or a return result |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1314 |
typo p. 149 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1312 |
association "context" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1311 |
behaviors |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1309 |
Page: 589 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1308 |
Section: 12.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1307 |
enumerated type MessageSort |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1310 |
There is no redefinitionContext established |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1306 |
heading of table 19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1305 |
Notation of ExecutionOccurrence |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1304 |
Section: 15.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1303 |
introductory text for Property states |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1301 |
notation for statemachine transitions omitted from spec |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1300 |
behavior packages (Interactions, Statemachines |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1302 |
"Implementation" is ommitted |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1299 |
InformationItem - Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1298 |
ReadLinkObjectEndQualifierAction - errors in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1296 |
StartOwnedBehaviorAction - OCL error in constraint |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1297 |
ReadLinkObjectEndAction - errors in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1294 |
ReplyAction - Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1293 |
ReplyAction - Inconsistency with Figure 150 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1292 |
AcceptCallEvent - inconsistent multiplicity "• trigger |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1295 |
ReadIsClassifiedObjectAction - OCL errors in constraints |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1291 |
AcceptEventAction - inconsistencies in Semantics and typos |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1290 |
AcceptEventAction - inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1289 |
AcceptEventAction - inconsistent multiplicities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1288 |
Message - inconsistency "Messageident equalling ‘*’ |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1287 |
Message - inconsistency (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1286 |
Message - inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1285 |
Figure 77 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1284 |
Interface - Typos in Figure 63 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1282 |
Connector - inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1281 |
Connector - typo and inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1283 |
ConnectorEnd - multipliciy of role |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1280 |
Connector - inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1279 |
Typo in ptc/03-08-02 p. 178 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1278 |
Typo Section: 12.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1275 |
Stereotype - Inconsistency in notation Section "Notation", last sentence |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1274 |
Stereotype - typo in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1277 |
ActivityPartition - inconsistencies |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1276 |
Typo In section "Description" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1271 |
AddVariableValueAction - OCL in constraint [1] not correct |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1273 |
Stereotype |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1272 |
Typo, section "Description", paragraph 1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1270 |
VariableAction - undefined query |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1267 |
ReadLinkAction - Constraints use deprecated UML elements |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1266 |
ReadLinkAction - inconsistency with Figure 147 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1269 |
Variable - Typo in Attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1268 |
DestroyLinkAction - Semantics based on non existing "settability addOnly" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1265 |
MultiplicityElement - section is obsolete |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1264 |
LinkEndData - Additional operation not correct |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1263 |
LinkEndData - Typo in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1262 |
AddStructuralFeatureValueAction - Settability removeOnly does not exist |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1260 |
DestroyObjectAction - inconsistency in constraints |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1259 |
Component - problem with provided interfaces (see also Issue 6875, 6338) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1261 |
Typo - section Description, first sentence |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1258 |
Manifestation - visual representation should be dashed arrow |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1256 |
Deployment - keyword <> not introduced |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1255 |
InteractionOccurrence - Syntax rules for name not clear |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1257 |
DeploymentTarget - Missing OCL expression |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1254 |
Figure 95 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1253 |
Connector - Constraint [3] not necessary ? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1252 |
Connector - Constraint [2] is inprecise |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1251 |
ReadSelfAction - Typos in OCL constraints |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1249 |
Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1248 |
Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1250 |
ReadSelfAction - delete constraint [4] |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1247 |
TestIdentityAction - additional constraint |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1246 |
TestIdentityAction- delete constraint [2] |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1245 |
Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1244 |
DeleteObjectAction - delete constraint [1] |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1241 |
SendSignalAction |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1240 |
Delete the following sentence in section "Notation": |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1243 |
CreateObjectAction - delete constraint [4] |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1242 |
Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1239 |
Sentence not finished in section "Changes from previous UML" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1235 |
Collaboration - inconsistency with Figure 99 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1237 |
Typo in Figure 124 on page 182 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1236 |
StructuredClassifier - Regular expression for namestring too complicated |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1238 |
Typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1233 |
GeneralizationSet - constraints expressed in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1232 |
GeneralizationSet - Incorrect Mulitiplicities of associations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1234 |
GeneralizationSet - example in section "Semantics" is not clear |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1231 |
GeneralizationSet description conf. about meaning of "specific" + "general |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1230 |
GeneralizationSet - outdated description |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1229 |
Region - Additional structural constraints necessary |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1228 |
Constraint [2], p.70 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1227 |
Figure 355 - mulitplicities of redefinitionContext should be 0..1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1226 |
Figure 355 - ownedStateMachine should subset ownedBehavior |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1225 |
Typo p 497 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1221 |
State - Constraints - errors in OCL and inconsistencies |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1223 |
Change Constraint [1] to |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1222 |
Non-existent property isFinal referenced |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1224 |
ownedStateMachine not described correctly |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1220 |
Define containingStateMachine() for Vertex |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1219 |
State - Inconsistency |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1218 |
p.461, first sentence: |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1216 |
AssociationClass - Additional Operation [1] should be deleted |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1215 |
AssociationClass Constraint [1] should be reformulated |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1214 |
Association - endType should be of type Classifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1217 |
Constraints of ConnectionPointReference - OCL not correct |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1213 |
Stereotype «buildComponent» defined twice, description not clear |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1212 |
Typo p 589 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1210 |
ExtensionPoint should be a specialization of Feature (from Kernel) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1211 |
Typo p 587 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1209 |
Multiplicity of extensionLocation should be 1..1 instead of 1..* |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1207 |
Constraint not precise enough |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1206 |
Unnecessary sentence p 339 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1208 |
Imprecise sentence p 334 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1205 |
"Joining of tokens" not clear |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1204 |
Typo p 339 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1203 |
Typo - Missing colon p 302 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1201 |
Constraint not precise enough |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1200 |
Typo p 320 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1202 |
No Activity Edges from with equal source and target |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1197 |
Typo p 161 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1196 |
Another Inconsistency with Figure 100 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1199 |
Multiple activity edges between a given pair of activity nodes possible ? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1198 |
Inconsistency between constraint of ControlNode and Semantics of JoinNode |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1195 |
Inconsistency with Figure 100 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1194 |
Figure 103 at the wrong place |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1193 |
Connector - default value für "kind" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1192 |
Typo p 137 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1191 |
Missing multiplicities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1190 |
Typo p. 595, Table 25, row 6, column 3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1189 |
Additional Operations specification of NamedElement::allNamespaces() |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1186 |
Second row of table 22, column "Notation", labels switched |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1185 |
UseCase - Inconsistencies with Figure 401 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1188 |
typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1187 |
Typo in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1184 |
UseCase - Extend is not a Namespace |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1183 |
Inconsistent multiplicity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1182 |
Inconsistency betw. Figure 328 and associations listed in s. Associations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1180 |
Wrong association name |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1179 |
Constraint [2] - Missing parenthesis in OCL |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1181 |
type p 419 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1178 |
Inconsistency between section "Associations" and Figure 327 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1177 |
typo p 340 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1176 |
object edges" should be replaced by "object flows |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1172 |
graphic nodes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1171 |
typo p 421 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1175 |
object edges" sould be replaced by "object flows |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1174 |
typo p 356 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1173 |
typo p 240 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1170 |
typo p 420 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1169 |
typo p 403 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1168 |
Inconsistencies between Figure 43 and the detailled description of Package |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1165 |
The section "Associations (BasicActivities)" is not complete |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1164 |
The query 'hostElement' has some errors |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1167 |
Inconsistencies between Figure 3 and the detailled description of package |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1166 |
• /context : Classifier [0..1] |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1163 |
See CommonBehavior for a description of Event specifications |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1162 |
page 95 diagram |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1161 |
On templateableElment - additonal features |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1160 |
Figure 346 needs updating |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1157 |
Incorrect mentioning of General Order On p 412 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1159 |
Omission of non-terminal ‘arguments’ (p. 424) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1158 |
Remove occurrences of “TBD” |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1153 |
Message notation. Incorrect notation in Figure 333 p.414 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1155 |
Message End association to Interaction should be removed |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1154 |
Strict ordering in Inline Part Decomposition |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1156 |
EventOccurrence, multiplicities incorrect in metamodel diagram |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1152 |
On page 140, the title for Parameter is "Parameter (Collaboration, as speci |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1151 |
The title of the Property description on page 144 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1150 |
labels for ExecutionOccurrence |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1149 |
duration observation" vs DurationObservationAction etc |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1148 |
Missing sections for for enumeration MessageKind or MessageSor |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1147 |
figure 8-137 and 8-139 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1146 |
CommonBehaviors describes "Operation (from Communications, as specialized) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1144 |
inconsistency between figure 5.1 on page 179 and figure 7-122 on page 337. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1143 |
OpaqueExpression in CommonBehaviors |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1145 |
CommonBehaviors |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML25-603 |
CollaborationOccurence |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-609 |
Deployment (from ComponentDeployments, Nodes) |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-608 |
Dependency associations |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-628 |
Notation of enumeration literals |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-624 |
Associations section of InteractionUse |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-627 |
Figure 307 and Figure 308 are exactly the same |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-562 |
Section: 9.3.3 |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-561 |
At «implementation Class», what does "a child of instance" mean?! |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-559 |
three possibilities for aggregation kind at 7.11.2, but only two notations |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-558 |
Section: 7.11.2 |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-560 |
It is not clear what 'related to' means |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-567 |
Concept of 'port side' not to be found in metamodel |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-565 |
Description text for CollaborationOccurrence unclear |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-564 |
Editrial error in Section: 9.3.4 ? |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-563 |
Association collaborationRole |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-576 |
There is no "precise mapping |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-575 |
Semantics section of StructuralFeature |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-592 |
"required interface" |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-596 |
UML 2 does not permit use of a state machine |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-600 |
"role binding" |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-599 |
multiplicity of the "role:ConnectableElement" |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML22-1084 |
UML2: No notation for BehavioredClassifier::ownedTrigger |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1083 |
UML 2/Templates -- single argument? |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1082 |
Use the new 'dot' notation in examples |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1085 |
page 467, Section 13.3.24 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1081 |
UML 2 Superstructure / CommonBehaviors / Incorrect types in text |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1080 |
7.3.41 Parameter (from Kernel, AssociationClasses)" |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1063 |
UML 2.0 issue: ownedMember xsi:type="uml:Stereotype" should be used |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1062 |
UML 2.0: CMOF/UML mixup for profiles |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1069 |
Required attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1068 |
Parameter::effect |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1065 |
UML 2.1 XMI Issue |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1064 |
UML 2.0: Inconsistencies in profile example XMI |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1073 |
parameter of operation isRedefinitionContextValid() is inconistently named |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1072 |
Compliance package L2 does not merge StructuredActions in the metamodel |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1071 |
The following properties should not subset DirectedRelationship::target |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1070 |
The following properties should not subset DirectedRelationship::source |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1067 |
Artifact::fileName |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1066 |
uml::Extension::ownedEnd should not subset uml::Association::ownedEnd |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1079 |
Figure 12.18: Small typo: "subsets ownedMember" not "ownedmember" |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1078 |
Page: 161 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1074 |
Transition guards cannot currently be evaluated because they have no contex |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1077 |
StateMachine::extendedStateMachine should have a multiplicity of 0..*. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1076 |
Behavior::context |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1058 |
UML 2.0 issue: Package Primitive Types not merged |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1057 |
Section: Appendix A: Diagrams |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1056 |
Section 7.2.1 of ptc/04-10-14 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1055 |
Section: 7.3.36 Operation |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1054 |
Section 8 Issue - Component Realization-Classifier multiplicity |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1053 |
Section: Actions, Figure 156 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1052 |
UML 2.1 Regressions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1051 |
Realization classifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1050 |
UML 2 issue: redefining isComposite on association ends |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1049 |
Classifier::parameter, Operation::parameter, and ConnectableElement::parame |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1048 |
Component::realization should NOT be derived |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1047 |
Rename ActivityGroup::activity to containingActivity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1046 |
Rename OpaqueAction::output to outputPin. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1045 |
Make ActivityGroup::containedNode a derived union |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1044 |
Make ActivityGroup::containedEdge a derived union |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1039 |
compliance levels L2 and L3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1038 |
Change type of WriteStructuralFeatureAction::value to ValueSpecification |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1037 |
Change type of WriteStructuralFeatureAction::value |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1061 |
UML 2.0: separate profile application from profile importing |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1060 |
UML 2.0: invalid package merge diagrams for compliance points |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1059 |
UML 2.0 issue: Profile::ownedStereotype should be derived |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1043 |
Rename LinkAction::input to inputPin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1042 |
Rename OpaqueAction::input to inputPin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1041 |
Rename InformationFlow::source |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1040 |
Rename InformationFlow::target |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1036 |
Rename ActivityPartition::subgroup to subpartition |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1035 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1034 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1033 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1026 |
body expression for Property::isConsistentWith(RedefinableElement) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1025 |
following imports from merged packages to unmerged packages should be remov |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1024 |
UML2 Superstructure Fig 2.2 Incomplete |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1023 |
Section: 14.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1020 |
Section: Common Behaviors |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1019 |
Section: Actions |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1022 |
7.3.22 InstanceSpecification |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1021 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1018 |
Section: Classes |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1017 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1016 |
Invalid stereotype in StandardProfile |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1015 |
UML 2 Super / miscellaneous figure-text discrepancies |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1028 |
Rename Package::ownedMember |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1027 |
Rename Constraint::namespace |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1030 |
Rename ActivityEdge::redefinedElement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1029 |
Rename Component::ownedMember |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1032 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1031 |
Rename ActivityNode::redefinedElement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1012 |
Section: 6.5 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1011 |
UML2 should specify default property ownership for association ends |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1002 |
Figure 430 references invalid metaclass |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1001 |
Section: 9.3.5 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1006 |
UML2 Navigability Impact on Tools |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1005 |
UML 2 XMI DTD requirement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-998 |
UML2 issue: {unrestricted} described in text but not BNF |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-997 |
UML Superstructure / Actions / Missing package heading |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1010 |
UML 2 Super / Undocumented properties |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1009 |
Page: 591,592 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1008 |
Core::Constructs::Operation |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1007 |
Interaction::lifeline should be ordered |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1004 |
UML 2 Classes Notation for association end ownership |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1003 |
connection point reference |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1014 |
UML 2 Super / Collaboration use issues (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1013 |
UML 2 Super / Collaboration use issues (01) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-1000 |
Section: 12.3.18 and 12.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-999 |
Section: 15.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-994 |
Section: 12.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-993 |
Page: 163 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-989 |
Section: 12.3.37 ObjectFlow |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-996 |
UML Superstructure / Actions / incorrect form for subsetting |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-995 |
Section: 12.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-990 |
OpaqueAction |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-975 |
ExecutableNode should be abstract in Figure 195. It is in Figure 197. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-979 |
Section: 12 and 13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-971 |
Page: 330 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-970 |
Section: 11.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-969 |
Section: Actions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-974 |
Actions should be able to overlap partitions, to support multiple participa |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-973 |
Section: 8.3.1 Page: 156 ff |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-965 |
Page: 591 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-961 |
Clarify caption of Figure 56 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-960 |
Section: Interactions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-953 |
Clarify first constraint on InputPin and OutputPin, move "only" to before " |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-952 |
LoopNode should move rather than copy values to/from loop variables |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-951 |
In Figure 210, put merge before Use Part to merge the incoming flows |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-950 |
Exceptions thrown across synchronous invocations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-949 |
Multiple exception handlers |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-955 |
Actions, CallBehaviorAction, third sentence, |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-954 |
The Syle Guidelines for Stereotype |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-959 |
CollaborationUse: Constraint 1, |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-958 |
ConditionalNode and LoopNode test and bodies should be ExecutableNodes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-957 |
ExpansionRegion |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-956 |
ControlFlow |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-964 |
Last element in transition BNF |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-962 |
Notation for connector end multiplicities. |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-963 |
ParameterSet, first line: "inputs *or* outputs". |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-942 |
In Activities, Figure 176, Action should be abstract |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-944 |
String is primitive but has structure. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-948 |
Solid triange notation for Association |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-947 |
The create stereotype on Usage dependency |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-939 |
Section: 12.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-946 |
Element to Constraint navigation |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-945 |
Disjointness should be independent of generalization |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-943 |
Semantics for instances applies to InstanceSpecification? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-926 |
Section: Appendix F |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-925 |
Section: E.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-920 |
Section: Appendix C Table 27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-919 |
Section: Appendix C Table 26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-922 |
Section: D.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-921 |
Section: 15.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-924 |
Section: D.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-923 |
Section: D.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-915 |
Section: 18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-914 |
Section: 18.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-913 |
Section: 18.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-918 |
Section: Appendix C Table 25 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-917 |
Section: Appendix B (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-916 |
Section: Appendix B |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-912 |
Section: 18.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-911 |
Section: 18.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-910 |
Section: 18.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-909 |
Section: 18.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-908 |
Section: 18.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-893 |
Section: 17.5.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-892 |
Section: 17.5.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-891 |
Section: 17.5.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-895 |
Section: 17.5.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-894 |
Section: 17.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-901 |
Section: 17.5.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-900 |
Section: 17.5.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-897 |
Section: 17.5.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-896 |
Section: 17.5.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-907 |
Section: 18.1.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-906 |
Section: 17.5.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-899 |
Section: 12 Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-898 |
Section: 17.5.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-903 |
Section: 17.5.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-902 |
Section: 17.5.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-905 |
Section: 17.5.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-904 |
Section: 17.5.18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-883 |
Section: 17.2.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-882 |
Section: 17.2.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-872 |
Expansion region description |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-871 |
ExpansionRegioin example, Figure 261: concurrent => parallel |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-870 |
Section: Activities, ExpansionRegion (05) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-879 |
mustIsolate: |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-878 |
No notation |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-875 |
Semantics of isAssured/isDeterminant in conditional node |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-874 |
Add constraint in LoopNode |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-873 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-890 |
Section: 17.5.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-889 |
Section: 17.5.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-888 |
Section: 17.5.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-885 |
Section: 17.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-884 |
Section: 17.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-887 |
Section: 17.5.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-886 |
Section: 17.5.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-881 |
Clarify the semantics of minimum multiplicity > 0 for streaming parameters |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-880 |
Figure 209 of Activites |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-877 |
Add constraints on conditional and loop nodes (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-876 |
Add constraints on conditional and loop nodes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-861 |
Section: 14.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-860 |
Section: 16.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-869 |
Section: Activities, ExpansionRegion (04) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-868 |
Section: Activities, ExpansionRegion (03) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-867 |
Section: Activities, ExpansionRegion (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-859 |
Section: 16.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-858 |
Section: 16.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-857 |
Section: 16.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-866 |
Section: Activities, ExpansionRegion |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-865 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-864 |
ValueSpecificationAction, Attribute section, is missing the return pin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-863 |
Section: Actions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-862 |
Section: Common Behavior |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-841 |
Section: 15.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-840 |
Section: Appendix A |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-837 |
Section: 15.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-836 |
Section: 15.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-839 |
Appendix C.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-838 |
Section: 15.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-833 |
Section: 15.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-832 |
Section: 15.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-843 |
Section: 15.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-842 |
Section: 15.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-844 |
Section: 15.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-831 |
Section: 15.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-830 |
Section: 15.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-817 |
Section: 14.3.26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-816 |
Section: 14.3.25 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-823 |
Section: 15.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-822 |
Section: 8.3.1 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-829 |
Section: 15.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-828 |
Section: 11.3.42 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-812 |
Section: 14.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-811 |
Section: 14.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-814 |
Section: 14.3.21 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-813 |
Section: 14.3.21 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-827 |
Section: 15.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-826 |
Section: 15.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-819 |
Section: 14.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-818 |
Section: 14.3.29 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-821 |
Section: 12.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-820 |
Section: 11.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-825 |
Section: 15.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-824 |
Section: 15.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-810 |
Section: 14.3.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-809 |
Section: 14.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-808 |
Section: 14.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-797 |
Section: 14.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-796 |
Section: 13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-795 |
Section: 13.3.30 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-807 |
Section: 14.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-806 |
Section: 14.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-799 |
Section: 14.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-798 |
Section: 14.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-803 |
Section: 14.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-802 |
Section: 14.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-801 |
Section: 14.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-800 |
Section: 14.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-794 |
Section: 13.3.29 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-793 |
Section: 13.3.28 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-792 |
Section: 13.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-805 |
Section: 14.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-804 |
Section: 14.3.3 & 14.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-791 |
Section: 13.3.26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-790 |
Section: 13.3.24 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-776 |
Section: 13.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-775 |
Section: 13.3.2 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-784 |
Section: 13.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-783 |
Section: 13.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-778 |
Section: 13.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-780 |
Section: 13.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-779 |
Section: 13.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-789 |
Section: 13.3.23 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-788 |
Section: 13.3.22 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-782 |
Section: 13.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-781 |
Section: 13.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-786 |
Section: 13.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-785 |
Section: 13.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-787 |
Section: 13.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-777 |
Section: 7.3.36 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-755 |
Section: 12.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-754 |
Section: 12.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-753 |
Section: 12.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-767 |
Section: 11.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-766 |
Section: 12.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-771 |
Section: 12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-770 |
Section: 12.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-758 |
Section: 12.3.38 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-757 |
Section: 12.3.37 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-765 |
Section: 12.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-764 |
Section: 12.3.47 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-760 |
Section: 12.3.43 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-759 |
Section: 12.3.41 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-774 |
Section: 12.3.49 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-773 |
Section: 12.3.46 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-772 |
Section: 13.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-761 |
Section: 12.3.44 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-769 |
Section: 12.3.51 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-768 |
Section: 12.3.50 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-752 |
Section: 12.3.34 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-751 |
Section: 12.3.33 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-738 |
Section: 12.3.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-737 |
Section: 12.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-736 |
Section: 12.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-735 |
Section: 12.3.14 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-730 |
Section: 12.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-741 |
Section: 12.3.6 & 12.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-740 |
Section: 12.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-739 |
Section: 12.3.18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-746 |
Section: 12.3.28 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-745 |
Section: 12.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-744 |
Section: 12.3.23 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-743 |
Section: 12.3.24 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-742 |
Section: 12.3.22 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-748 |
Section: 12.3.38 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-747 |
Section: 12.3.30 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-750 |
Section: 12.3.32 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-749 |
Section: 12.3.31 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-729 |
Section: 12.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-728 |
Section: 12.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-727 |
Section: 12.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-726 |
Section: 12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-725 |
Section: 12.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-716 |
Section: 12.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-715 |
Section: 12.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-714 |
Section: 12.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-721 |
Section: 12.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-720 |
Section: 12.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-719 |
Section: 12.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-683 |
Section: 11.3.25 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-682 |
Section: 11.3.24 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-629 |
Section: 7.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-631 |
Section: 8.3.1 - typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-630 |
Section: 8.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-628 |
Section: 7.3.34 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-627 |
Section: 7.3.33 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-637 |
Section: 9.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-635 |
Section: 9.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-632 |
Section: 8.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-633 |
Section: 9.20.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-634 |
Section: 9.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-638 |
Section: 9.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-554 |
Section: 7.3.43 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-562 |
An observed time value must be written into a structural feature |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-691 |
Section: 11.3.34 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-690 |
Section: 11.3.33 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-689 |
Section: 11.3.31 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-684 |
Section: 11.3.26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-694 |
Section: 11.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-693 |
Section: 11.3.36 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-686 |
Section: 11.3.28 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-687 |
Section: 11.3.29 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-692 |
Section: 11.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-688 |
Section: 11.3.30 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-685 |
Section: 11.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-588 |
Optional inputs |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-587 |
Preserve order in result of read actions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-582 |
Interactions chapter refers to ActivityInvocations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-583 |
Destruction semantics in StructuredClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-585 |
Figure 119 missing multiplicity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-584 |
Link maintenance in StructuredClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-591 |
ObjectNode, constraint 1 In ObjectNode |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-590 |
DestroyObjectAction semantics |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-589 |
IsReadOnly constriant |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-586 |
Notation for method |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-659 |
Section: 11.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-658 |
Section: 11.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-621 |
Section: 7.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-620 |
Section: 7.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-626 |
Section: 7.3.32 Page: 96-99 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-625 |
Section: 7.3.32 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-624 |
Section: 7.3.22 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-616 |
Section: 6.5.1: Error in example |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-619 |
Section: 7.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-622 |
Section: 7.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-618 |
Section: 7.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-617 |
Section: 7.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-678 |
Section: 11.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-677 |
Section: 11.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-680 |
Section: 11.3.22 -- significant revision? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-679 |
Section: 11.3.21 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-696 |
Section: 11.3.40 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-695 |
Section: 11.3.38 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-681 |
Section: 11.3.23 -- significant revision? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-672 |
Section: 11.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-676 |
Section: 11.3.18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-674 |
Section: 11.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-675 |
Section: 11.3.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-673 |
Section: 11.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-709 |
Section: 11.3.53 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-708 |
Section: 11.3.42 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-698 |
Section: 11.3.43 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-697 |
Section: 11.3.41 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-660 |
Section: 11.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-667 |
Section: 11.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-666 |
Section: 11.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-670 |
Section: 11.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-669 |
Section: 11.3.11 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-668 |
Section: 11.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-664 |
Section: 11.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-665 |
Section: 11.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-663 |
Section: 11.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-671 |
Section: 11.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-579 |
Connector multiplicity notation |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-578 |
Associations between interfaces |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-580 |
create dependency Figures 103 and 121 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-573 |
Transitivity in composition |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-581 |
underlined association name |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-577 |
Section: Classes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-572 |
Add concept "StateInvariant" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-574 |
Pin/parameter matching constraints |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-576 |
Section: Classes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-575 |
Section: CB/ACT |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-723 |
Section: 12.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-722 |
Section: 12.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-641 |
Section: 8.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-640 |
Section: 9.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-647 |
Section: 10.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-648 |
Section: 10.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-644 |
Section: 12.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-645 |
Section: 12.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-643 |
Section: 9.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-639 |
Section: 9.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-646 |
Section: 9.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-642 |
Section: 9.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-615 |
Section: 7.4.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-614 |
Section: 7.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-610 |
Section: 11.8.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-609 |
Section: 11.6.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-613 |
Section: 7.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-612 |
Section: 13.1.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-607 |
Section: 11.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-606 |
search for referenced item -- Section: 11.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-603 |
Figure 68 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-602 |
methods not defined under attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-611 |
Section: 13.1.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-605 |
Section: 11.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-604 |
Section: 11.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-608 |
Actor is a specialized Classifier and not BehavioredClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-711 |
Section: 12.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-710 |
Section: 11.3.54 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-713 |
{redefined } should be named {redefines } |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-712 |
Property string {bag} is redundant |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-718 |
Section: 12.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-717 |
Section: 12.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-703 |
Section: 11.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-701 |
Section: 11.3.46 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-700 |
Section: 11.3.45 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-707 |
Section: 11.3.52 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-706 |
Section: 11.3.51 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-705 |
Section: 11.3.50 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-699 |
Section: 11.3.44 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-704 |
Section: 11.3.49 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-702 |
Section: 11.3.47 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-596 |
unclear statement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-595 |
Text references Figure 8 and the correct figure number is 6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-599 |
Section is badly worded and does not make a lot of sense |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-598 |
clarify what a directed association is |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-600 |
typing error in the statement :unrestricted ? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-597 |
extra word in the last sentence of the paragraph under Attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-594 |
section 9.20.2 VisibilityKind lists two types of visibility |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-592 |
StructuredActivityNode specialized multiplicity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-601 |
What happened to real numbers |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-724 |
Section: 12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-662 |
Section: 11.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-661 |
Section: 11.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-655 |
Section: 10.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-654 |
Section: 10.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-652 |
Section: 10.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-656 |
Section: 10.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-650 |
Section: 10.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-653 |
Section: 10.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-649 |
Section: 10.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-651 |
Section: 10.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-566 |
Section: 14.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-563 |
Minor error in BNF of an message argument |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-568 |
Section: 14.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-569 |
Section: 14.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-571 |
StateInvariants/Continuations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-570 |
Section: Table 14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-567 |
Section: 14.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-535 |
Figure 78 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-532 |
Class InfrastructureLibrary::Core::Basic::Property |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-538 |
Section 11.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-537 |
simple time model" in CommonBehavior |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-544 |
The specification is fond of using 'typically.' |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-543 |
TimeObservationAction and DurationObservationAction |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-541 |
add an interaction fragment |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-540 |
Interactions model sequences of events |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-539 |
Clarify example in figure 133 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-485 |
Classes diagram of the Core::Constructs package |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-484 |
cross-reference missing |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-483 |
Relationship and DirectedRelationship in Core::Constructs |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-482 |
document appears to be inconsistent in how it handles concepts |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
UML22-250 |
Bad cross reference for InterfaceRealization Notation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-249 |
PrimitiveTypes access by UML (M1) models |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-253 |
Unclear which Property has aggregation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-252 |
Move Property::isId from MOF to UML |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-248 |
Notation for stereotypes on Comments and other elements |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-251 |
text-diagram out of synch in Infrastructure 11.4.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-254 |
Clarify isRequired |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-217 |
General ordering cycles |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-215 |
What exactly is a state list? |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-214 |
Section: 9.14.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-213 |
Section: 11.1.3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-212 |
Action inputs/outputs |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-219 |
Completion event modeling |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-216 |
Editorial bug in 2.1 Superstructure Convenience document |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-183 |
7.3.4 Association Class |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-264 |
Invalid mandatory compositions and associations |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-263 |
11.3.47 on StructuralFeatureAction (and related sections on subclasses) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-262 |
Section: 9.16.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-261 |
Section: 9.19.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-258 |
Section: 9.12.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-257 |
Merged Metam.:Property::class with redefinition of non-inherited property |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-256 |
navigating from link to link ends |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-255 |
ExtensionEnd description refers to old use of navigability |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-260 |
Section: 9.10.3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-259 |
Section: 9.13 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-285 |
Section: 15 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-291 |
Section: 14.3.10 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-290 |
Section: 14.3.14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-296 |
Section: e. g. 12.2. page 287 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-201 |
assembly connectors |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-200 |
New Issue on multiple guillemot pairs for same element |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-210 |
11.3.26 OpaqueAction |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-209 |
Definition of stereotype placement requires a name |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-206 |
the default for a Property should not be inconsistent with its type |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-204 |
packagedElement |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-203 |
ptc/06-01-02:14.3.14, Notation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-207 |
UML's support for null values and semantics is unclear |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-211 |
UML 2/ Super / SendSignalEvent erratum |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-199 |
Question on InfrastrucutreLibrary::BehavioralFeatures::Parameter |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-208 |
"Property::lowerValue" is not a good name |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-202 |
Fig 7.14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-275 |
Section: 17.5 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-283 |
Activity shape |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-235 |
text of specs and corresponding XMI specs should be clarified |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-234 |
UML 2: "isLeaf" |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-227 |
Section: 15.3.14 Transition |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-238 |
Figure 7.4 invalid redefines |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-237 |
EnumerationLiteral should constrain InstanceSpecification |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-233 |
Stereotype attributes inherited from Class |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-231 |
Section 11.4.1 "Classifier" (in Constructs) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-228 |
Notation (p 154, formal/05-07-04 ) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-230 |
Section 11.4.1 "Classifier" (in Constructs) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-229 |
Section 10.2.1 "Class" (in Basic) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-192 |
Section: 7.3.7 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-191 |
AssociationClass is severely underspecified |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-190 |
Show an example of correct notation for the metamodel |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-184 |
Optional name attribute in NamedElement is misleading and insufficient |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-197 |
UML 2 Super / Components / connectors to interfaces |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-187 |
reference to Figure 12.87 missing |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-186 |
Section: 14.4 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-194 |
No ObjectEvent corresponding to SendObjectAction |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-193 |
Fig 12.10 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-188 |
UML 2.1/Superstructure/ call triggers vs signal triggers |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-198 |
UML 2.2 RTF issue - line styles for profiles |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-195 |
UML 2 Super / Composite Structure / ambiguous constraint |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-132 |
Section: 15.3.12 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-131 |
Section: 11.5.1 DataType (as specialized) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-141 |
event parameters |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-130 |
Section: 11.3.13 TypedElement (as specialized) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-129 |
Section: 11.3.6 Classifiers diagram |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-139 |
Page: 62 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-125 |
Page: 129 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-124 |
Page: 369/370 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-136 |
Page: 157,162,163 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-127 |
9.1 BehavioralFeature package |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-126 |
Page: 532 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-133 |
Page: 423 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-92 |
Section: D.4 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-91 |
Section: 15.3.8 (second issue) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-90 |
Section: 18.3.6 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-89 |
Section: 17 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-102 |
Section: 8.3.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-99 |
Section: 7.3.36 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-107 |
Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-106 |
Clarify multiple inputs to expansion regions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-105 |
DataStoreNode has uniqueness, reverse constraint inherited from ObjectNode |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-87 |
Add constraints on conditional, loop, sequence to rule out node contents |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-86 |
Section: Activities, LoopNode |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-104 |
Misleading statement about multiplicity in AssociationClass |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-103 |
Client/supplier on dependencies |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-88 |
Constrain conditional node to have body pins if there is a result pin. |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-173 |
On page 26, Figure 7.9 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-172 |
choice of terminolgy for TransitionKind is non-intuitive |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-171 |
Section: 15.3.15 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-170 |
Section 8.3.2 sub-section "Notation" starting on page 149 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-169 |
inconsistency wrt UML2 classifier behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-168 |
keyword, "buildcomponent", and a stereotype, "buildComponent" |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-182 |
Element and Comment in Basic |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-181 |
Description of Element |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-180 |
Unclear relationship between the Basic and Abstractions packages |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-179 |
XMI file: Core::Constructs::Operation::bodyCondition should have upper boun |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-178 |
/qualifiedName attribute missing on Core::Constructs::NamedElement |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-177 |
Operation::ownedParameter should be ordered in XMI? |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-176 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-175 |
constraints owned by these properties have no context |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-174 |
Operation should be a specialization of TypedElement and MultiplicityElemen |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-167 |
section, 12.3.27 ExpansionRegion(from ExtarStructureActivities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-166 |
(merged) compliance levels L2 and L3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-165 |
(merged) compliance level L1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-164 |
Section: 14.3.20 Message (from BasicInteractions) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-163 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-33 |
StateMachine - Constraints |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-32 |
transtion |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-30 |
Inheritance of 'Enumerations' is not detailed |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-31 |
manage simultaneity of events |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-112 |
External exceptions. |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-111 |
Clarify which classifier or operation this is referring to |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-110 |
represents and occurrence keywords are switched |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-116 |
Section: Action/Activity |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-119 |
Input tokens to LoopNodes should be destroyed when the loop is done |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-118 |
Section: 8.3.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-123 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-122 |
Section: 12.3.2 Action |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-109 |
In Figure 12, ownedAttribute is bidirectional, in Figure 95, it is unidirec |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-108 |
StructuredActivityNode, Semantics, third paragraph, first sentence, |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-117 |
Section: 9.3.7 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-76 |
Section: 14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-75 |
Section: 14.3.18 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-74 |
RemoveStructuralFeatureValueAction specification |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-82 |
Decision node |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-81 |
Section: Actions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-72 |
Section: 13.3.17 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-71 |
Section: 13.3.11 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-78 |
Section 15 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-77 |
Section: 14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-69 |
Section: 12.3.40 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-68 |
Section: 12.3.33 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-84 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-83 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-65 |
Section: 10.3.11 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-85 |
Section: Interactions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-155 |
Section: Common Behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-154 |
Section: Classes (02) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-153 |
Section: Common Behavior (02) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-152 |
Section: Common Behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-151 |
Property ownership must be consistent across association redefinitions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-150 |
Missing notation for association classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-149 |
Page: 346-347 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-148 |
Page: 255 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-147 |
Behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-144 |
UML 2 - Invalid subsetting of composition ends |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-143 |
UML 2 Super / Actions / Compliance Levels of Actions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-162 |
Page: 53-55 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-161 |
"ownedType" is not a valid element |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-158 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-157 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-156 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-146 |
UML SuperStructure - Inconsistency re State Machine terms |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-145 |
Section: 14.3.20 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-160 |
Section: 16.3.3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-159 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-142 |
Page: 420 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-36 |
Connector - "provided Port" and "required Port" not defined Constraint 1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-48 |
Section: 9.14.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-42 |
Notation sections for TimeObservation and DurationObservation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-38 |
Connector - inconsistencies in Constraint[3] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-37 |
Connector - inconsistencies in Constraint [2] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-40 |
Connector - inconsistencies in Constraint[5] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-39 |
Connector - inconsistencies in Constraint[4] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-50 |
Presentation Options |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-44 |
useless example on p.330, Figure 247 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-43 |
Property defines an association "datatype" which is redundant |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-57 |
Multiple typos in ptc/04-10-02 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-56 |
Clarify the differences between redefining element and redefined element. |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-55 |
All sections |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-64 |
Section: 9.3.11 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-63 |
Section: 8.3.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-51 |
constrainedElement direction |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-52 |
Derived union notation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-61 |
Section: 9.3.7 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-60 |
Section: 9.3.6 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-62 |
Section: 8.3.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-58 |
Section: 8.3.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
UML22-59 |
Section: 9.3.4 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
MOF24-42 |
Relations |
UML 2.0
|
MOF 2.4
|
Resolved |
closed |
|
UMLR-75 |
Page: 107 |
UML 2.0
|
|
|
open |
|
UMLR-70 |
Section: Classes |
UML 2.0
|
|
|
open |
|
UMLR-72 |
Section: Classes |
UML 2.0
|
|
|
open |
|
UMLR-71 |
Section: Activities |
UML 2.0
|
|
|
open |
|
UMLR-40 |
Properties on Association for end objects |
UML 2.0
|
|
|
open |
|
UMLR-39 |
Notation for classifierBehavior |
UML 2.0
|
|
|
open |
|
UMLR-38 |
Contextualized attribute values Figures 121 |
UML 2.0
|
|
|
open |
|
UMLR-42 |
ReadStructuralFeatureAction |
UML 2.0
|
|
|
open |
|
UMLR-34 |
Section: Classes, Behavior |
UML 2.0
|
|
|
open |
|
UMLR-37 |
End objects of a link In the semantics of AssociationClass |
UML 2.0
|
|
|
open |
|
UMLR-36 |
Action for retrieving activity instance |
UML 2.0
|
|
|
open |
|
UMLR-44 |
Activities section |
UML 2.0
|
|
|
open |
|
UMLR-43 |
Section: 16.3.1 |
UML 2.0
|
|
|
open |
|
UMLR-48 |
Add constraints on ConditionalNode |
UML 2.0
|
|
|
open |
|
UMLR-47 |
ExpansionRegion (behavior in the shorthand notation) |
UML 2.0
|
|
|
open |
|
UMLR-46 |
Section: Activities : Why is exception type needed? |
UML 2.0
|
|
|
open |
|
UMLR-45 |
Section: Activities - clarification |
UML 2.0
|
|
|
open |
|
UMLR-103 |
Section: 7 |
UML 2.0
|
|
|
open |
|
UMLR-59 |
Section: 14.3.3 Page: 508+ |
UML 2.0
|
|
|
open |
|
UMLR-58 |
Section: 14.3.3 |
UML 2.0
|
|
|
open |
|
UMLR-51 |
Section: 10.3.1 |
UML 2.0
|
|
|
open |
|
UMLR-60 |
ConditionalNode inputs used by more than one test |
UML 2.0
|
|
|
open |
|
UMLR-55 |
Possibility to define a Collection as default Value needed |
UML 2.0
|
|
|
open |
|
UMLR-49 |
SequenceNode should have way to set output pins in CompleteStructured |
UML 2.0
|
|
|
open |
|
UMLR-80 |
Section: Sequence diagrams |
UML 2.0
|
|
|
open |
|
UMLR-32 |
Alternative entry and exit point notation is ambiguous |
UML 2.0
|
|
|
open |
|
UMLR-3 |
More explanation needed on Figure 339 |
UML 2.0
|
|
|
open |
|
UMLR-2 |
More examples |
UML 2.0
|
|
|
open |
|
UMLR-4 |
Parameterization of lifelines |
UML 2.0
|
|
|
open |
|
UMLR-19 |
Redefinitions of OCL constraints must be aligned with MOF2.0/UML2.0 class R |
UML 2.0
|
|
|
open |
|
UMLR-27 |
inconsistency in the action model |
UML 2.0
|
|
|
open |
|
UMLR-26 |
large overlap between structural features and variables |
UML 2.0
|
|
|
open |
|
UMLR-28 |
metaattribute isReadOnly |
UML 2.0
|
|
|
open |
|
UMLR-29 |
surface notation for state machines |
UML 2.0
|
|
|
open |
|
UMLR-30 |
Provide exception handling for all behaviors. |
UML 2.0
|
|
|
open |
|