UML22-21 |
UML 2 Issue: isUnique |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
UML22-457 |
New proposal for conjugate types for ports |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-459 |
Semantics of Ports in Components and CompositeStructures are incompatible |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-319 |
Explanation of Observation notation |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
UML25-345 |
Location: 9.6.4 Notation p 128: Confusing indentation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML22-307 |
Repr. of applied stereotypes and their properties insufficiently described |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
UML25-684 |
Typo in Interaction Example |
UML 2.5b1
|
UML 2.5
|
Duplicate or Merged |
closed |
|
UML22-1381 |
presentation option for transitions |
UML 2.0
|
UML 2.1.1
|
Resolved |
closed |
|
UML14-1046 |
Type vs. Implementastion class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML22-1380 |
Section: 7.3.10/Associations |
UML 2.1.2
|
UML 2.2
|
Duplicate or Merged |
closed |
|
UML14-1045 |
Compliance ambiguity |
UML 1.3
|
UML 1.4
|
Duplicate or Merged |
closed |
|
UML14-1044 |
Wording od OCL definition |
UML 1.1
|
UML 1.2
|
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 |
|
UML2-4 |
section 8.3.2, a "Connector" |
UML 1.5
|
UML 2.0
|
Resolved |
closed |
|
UML2-3 |
Property.association |
UML 1.5
|
UML 2.0
|
Resolved |
closed |
|
UML2-2 |
Activity Diagrams: Relax Traverse-to-Completion semantics |
UML 1.5
|
UML 2.0
|
Resolved |
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 |
|
UML241-47 |
No unambiguous way in UML 2.4 to serialize StructuredActivityNode |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
UML24-152 |
navigation only possible to generalization but not to specializations of elements |
UML 2.3
|
UML 2.4
|
Closed; No Change |
closed |
|
UML23-155 |
Japan Superstructure PAS Ballot Comments - comment 9 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
UML23-154 |
New proposal for conjugate types for ports |
UML 2.1.2
|
UML 2.3
|
Resolved |
closed |
|
UML23-153 |
proper content for Figure 13.8 |
UML 2.1
|
UML 2.3
|
Closed; No Change |
closed |
|
UML23-152 |
Section: 15.3.8 |
UML 2.1.1
|
UML 2.3
|
Resolved |
closed |
|
UML23-151 |
Section: 14.3.20 |
UML 2.0
|
UML 2.3
|
Resolved |
closed |
|
UML22-1375 |
7.3.41 Parameter (from Kernel, AssociationClasses)" |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
UML23-150 |
UML 2 Super / Activities / missing subsets |
UML 2.1
|
UML 2.3
|
Resolved |
closed |
|
UML22-1374 |
Profiles::ObjectNode has wrong default multiplicity |
UML 2.1
|
UML 2.1.1
|
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 |
|
UML25-682 |
InformationFlow cannot have an Activity as source or target |
UML 2.4.1
|
UML 2.5b1
|
Resolved |
closed |
|
UML25-681 |
Location p 162 ParameterSet associationends: Exceptions and parametersets |
UML 2.4.1
|
UML 2.5b1
|
Resolved |
closed |
|
UML23-147 |
LiteralReal has no default value. It would make sense if it had a value of 0 as for LiteralInteger. |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
UML14-1043 |
Change syntax of certain pre-defined operations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1042 |
Package symbol as a polygon |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML25-680 |
Profile::references_same_metamodel |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-679 |
Operation::isConsistentWith() |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-678 |
redefined states |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-677 |
Event pools for passive objects? |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-676 |
Who owns MessageEnds? |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML23-146 |
UML 2 chapter 17: template model cannot represent templates parameterized by value types |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
UML22-1372 |
Instance modeling does not take into account stereotypes properties |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-1371 |
Comments owned by Packages (02) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-1370 |
Comments owned by Packages |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-1369 |
section 15.3.14 Transition :: Constraints |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-1368 |
Regarding the quote on p128 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
UML22-1367 |
Section: Composite Structures/Abstract syntax |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
UML22-1366 |
ptc/06-01-02:14.3.14, Notation |
UML 2.1
|
UML 2.1.1
|
Resolved |
closed |
|
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 |
|
UML22-1142 |
Output tokens |
UML 2.1
|
UML 2.1.1
|
Duplicate or Merged |
closed |
|
UML14-1041 |
There is a bug in additional operation 1 of the Namespace element |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
UML14-1040 |
How to properly designate exception returned from message sent to Java obje |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
UML14-1039 |
In 3.23.1 "Notation" (Internationalization issues) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1038 |
No servant with object . minorcode=0 completed=NO |
UML 1.3
|
UML 1.4
|
Closed; No Change |
closed |
|
UML14-1037 |
The index shows incorrect section numbering for sections 2.9.4.1 to 2.9.4 |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1036 |
Setting Action as abstract in UML-MetaModel MDL to correspond to Semantics |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1035 |
Who owns an Event? |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1033 |
UML RTF 1.4 editorial comments (Part 9 - Statechart Diagrams) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1034 |
UML 1.4 RTF Issue: Namespace notation too specific |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1032 |
UML RTF 1.4 editorial comments (Part 6 - Use Case Diagrams) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1031 |
UML RTF 1.4 editorial comments (Part 3 - Behavioral Elements) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1030 |
UML RTF 1.4 editorial comments (Part 2 Diagram Elements) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
UML14-1029 |
UML 1.4 RTF Issue: Association generalization has notation but no semantics |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1028 |
UML 1.4 RTF Issue: Ordering of attribute values |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1023 |
UML 1.4 RTF issue: OCL: Unary operator "-" missing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1027 |
UML 1.4 RTF Issue: Multiple languages for uninterpreted strings |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1026 |
UML 1.4 RTF Issue: changeability in associations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1025 |
UML 1.4 RTF issue: OCL: grammar is ambigous |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1024 |
UML 1.4 RTF issue: OCL: navigation context in iterate |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1021 |
UML 1.4 RTF issue: OCL: Iterator declarators |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1020 |
OCL: Declarators for iterate |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1022 |
UML 1.4 RTF issue: OCL: Precedence of relational operators |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1019 |
In 2.10.4, semantics of Collaboration, the 1st sentence is confusing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1016 |
Page 2-114, 2nd paragraph. It should be collaboration template |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1015 |
Confusing wording |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1017 |
In 2.10.5, you give pattern a non-standard definition |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1018 |
Ad 3.69.3. In these paragraphs, it should be "Classifier" rather than "Cla |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1010 |
Terminology: Collaboration and Collaboration Template |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1014 |
use of the phrase "In the metamodel..." is unclear |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1013 |
why is AssociationRole is a subtype of Association? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1012 |
2. In 2.10.1, 3rd paragraph, it should be "OOram", not "OOFRam". |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1011 |
Focus is on 2.10 Collaborations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1009 |
Design patterns and collaboration templates. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1008 |
"Unused" data types |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1007 |
Notation for Namespace ownership |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1006 |
UML RTF 1.4 Issue: Typo in state exit |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1005 |
Misleading description of feature inheritance on roles. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1001 |
Incorrect example of constraining elements in collaborations. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1004 |
UML RTF 1.4 Issue: Messages do not have signatures |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1003 |
UML RTF 1.4 Issue: Guard condition in collaborations poorly named. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1002 |
UML RTF 1.4 Issue: Multi-objects in collaborations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-1000 |
UML RTF 1.4 Issue: Duplicate association end names from Constraint. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-999 |
UML RTF 1.4 Issue: Create action in collaborations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-998 |
UML RTF 1.4 Issue: What does it mean for ReturnAction to be synchronous? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-997 |
UML RTF 1.4 Issue: Action composition meta-modelled improperly: |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-994 |
UML RTF 1.4 Issue: Confusing example of sequence diagram |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-993 |
UML RTF 1.4 Issue: Arrowhead semantics in collaboration unclear |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-992 |
UML RTF 1.4: Description of context role, between state machine and model |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-996 |
UML RTF 1.4 Issue: Flow relationship has the incorrect semantics |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-995 |
UML RTF 1.4 Issue: <> keyword/stereotype |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-989 |
UML RTF 1.4 Issue: Deferred event ambiguity |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-988 |
UML RTF 1.4 Issue: Join in collaboration |
UML 1.2
|
UML 1.4
|
Resolved |
closed |
|
UML14-987 |
UML RTF 1.4 Issue: State constraint on host object |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-991 |
UML RTF 1.4 Issue: ownerScope and targetScope |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-990 |
UML RTF 1.4 Issue: Guard evaluation for choice points. |
UML 1.2
|
UML 1.4
|
Resolved |
closed |
|
UML14-986 |
UML RTF 1.4 Issue: Notation for call state |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-985 |
State machine name space |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-984 |
Issue Activity Package |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-983 |
ISSUE FOR UML, SECTION ActivityGraphs |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-982 |
Shouldn't the UML Package be allowed to own/reference UML 'Instances'? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-981 |
Inheritance of Stereotypes |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-980 |
Why is "FinalState" a separate metaclass ? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-977 |
OCL: Let-expressions |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-979 |
Invalid OCL expression in initial transition |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-978 |
OCL: Samples of invalid typing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-976 |
OCL: class operation has no 'self' |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-975 |
OCL: String literals |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-974 |
OCL: Numeric constants missing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-973 |
OCL: Literal collections |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-972 |
OCL: Enumeration types inconsistent with UML metamodel |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-971 |
OCL: Enumeration types |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-970 |
OCL: Feature calls on default target |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-967 |
OCL: Are keywords reserved or not |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-966 |
OCL: Consistency in grammar description |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-965 |
"Physical" Metamodel References in Diagrams (uml-rtf) |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-969 |
textual syntax cannot deal with identical class names in different package |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-968 |
OCL: Class context specification grammar incomplete |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-964 |
"Physical" Metamodel References (uml-rtf) |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-963 |
Precise "Physical" Metamodels Missing from Specification (uml-rtf |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-962 |
Language Name (uml-rtf) |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-961 |
OCL Error |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-960 |
Use of interfaces in associations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-959 |
Generalization should be meta-metamodel element |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-958 |
role concept in UML remains rather vague |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
UML14-957 |
OCL issue |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-956 |
Strange GENERAl USE RESTRICTION |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-955 |
Error in the third postcondition for String::concat on page 6-31 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-954 |
The not-equals operator, "<>", |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-953 |
Divide operator is incorrect |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-952 |
pages 6-28 to 6-29 of OCL documentation |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-951 |
page 6-10 of OCL documentation for 1.3alphaR5 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-948 |
The second postcondition on Integer::div is incorrect |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-950 |
The postcondition seems to be incorrect for sequence::subSequence |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-949 |
The postcondition on set::collect seems to be incorrect |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-947 |
(Minor) Activity diagram change recommendation |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-946 |
OCL Standard package |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-945 |
There is an association between between Constraint and ModelElement |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-944 |
OCL should allow one constraint to reference another |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-941 |
action state symbol/state symbol difficult to distinguish when drawn by ha |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-940 |
UML Semantics, OMG-UML V1.2 Use Cases July 1998, page 2-99 |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
UML14-943 |
UML has symbol for multiobject, not for multi-instances of other classifie |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-942 |
Dependencies (and other relationships) with role ends |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-939 |
Add Responsibilities as a new metatype |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-935 |
On aggregation. The white diamond name should be "shareable" |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-934 |
Metamodel and semantics for aggregations |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-938 |
Interface issue |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-937 |
Only single stereotyping is supported |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-936 |
Use of black diamond in the metamodel |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-933 |
Some attributes can be expressed in OCL |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
UML14-932 |
Widen the naming characteristics |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-931 |
BooleanExpression written in OCL or some other language? |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-927 |
Infix operator use should be clarified |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-930 |
Generalized change events |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-929 |
There are issues that make OCL hard to formalize--document ad/98-10-01 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-928 |
Definition of OclAny leads to problems when formalizing OCL |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-924 |
Common operations should be added to collection types in OCL |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-923 |
Add OCL operation to refer to all new instances created during operation |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-922 |
Need well defined way to extend OCL |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-926 |
Set of allInstances should be referrable by the class name |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
UML14-925 |
Add "Let"-like construct to OCL |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-919 |
Synchronous request |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
UML14-921 |
Notation says swimlanes are packages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-920 |
ModelElement to Partition multiplicity should be many |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-918 |
Asynchronous action |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
UML14-917 |
Not instantiable |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-916 |
UML RTF Issue: Normative MOF-Compatible version of UML |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-915 |
Core package-backbone diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-912 |
Issue: Missing role names |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-911 |
Issue: Inheritance inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-914 |
MOF does not support association attributes in metamodels. |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-913 |
issue: Missing association names |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-910 |
Issue: Action does not define attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-909 |
Issue: Name attribute inheritance |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-908 |
Issue: abstract class inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-907 |
Figure 2-18 : redundant attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-906 |
UML Semantics (page 109) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-905 |
Association attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-904 |
missing association names |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-903 |
Issue: inheritance inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-902 |
Diagram missing attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-900 |
Are subsystems instantiable? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-901 |
Abstract class inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-899 |
Associations as parts of a composite. |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-898 |
Section 5.17 of Notation Guide: No mapping is given |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-896 |
Notation section describing activity states needed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-897 |
Existance of classes in classes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-895 |
States leading to joins in activity models |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-894 |
Activities operate by and on objects |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-893 |
ClassifierInState does not satisfy one of its stated usages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-892 |
Rules 3 and 4 for Transitions in state machines should be limited |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-891 |
UML Semantics, section Common behavior |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-890 |
Notion of "conceptual" or "specification-only" not supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-889 |
OCL should allow the use of "let" expressions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-888 |
Text on page 2-49 section 2.2 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-887 |
Text in Figure 2.13.7.1 ActivityState seems to be incorrect |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-886 |
Need to have relative precedence and, or, xor |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-885 |
Need way to approximate comparisons |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-882 |
Change events issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-881 |
Collection operation size not defined for infinite collections |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-884 |
pre value of object |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-883 |
It"s mistake to automatically flatten collections of collections |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-880 |
States of an object not referenceable from OCL expression |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-879 |
Implicit transitive import between packages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-878 |
Protocol state diagrams issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-877 |
Changes to figure 15 and description of ClassifierRole on page 82 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-876 |
Semantics for dynamic invocation of concurrent activity models are missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-875 |
Collection type within OCL missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-874 |
Operation asSequence Issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-873 |
No discription of the association between Classifier and Parameter is give |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-872 |
Stereotypes on Dependency, page 43 of V 1.1 (figure 7) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-871 |
Reflexive association in section 5.20.2 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-870 |
The class "Subsystem" inherits from "GeneralizedElement" twice |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-869 |
Class "Model" is too prescriptive |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-868 |
Clarify how types of attributes and parameters should be instantiated |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-867 |
Merge "Class" and "Interface" into one class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-866 |
UML 1.1 issue on Associations |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-865 |
Extension Point |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-864 |
Specification for method in a derived class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-863 |
State diagrams: action expressions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-860 |
Responsibilities hardly figure in these documents |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-862 |
Permit multiple stereotyping on relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-861 |
General recommended use of UML |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-858 |
Aggregation is poorly defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-859 |
"Inheritance" connection used is a generalization relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-857 |
Page 98: arrowhead issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-856 |
Page 94 --editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-855 |
Page 82: Add explanation |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-854 |
Page 80: Confusion with headings |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-852 |
Page 72: Example needs rejigging |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-851 |
Page 71: Distinction between Dependency and Association |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-849 |
Page 67: Why is discriminator not discussed in terms of power types? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-850 |
Page 68 overlapping |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-853 |
Page 79: Poor choice of arrowhead |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-846 |
Page 52 figure 20 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-845 |
Typos on pages 24, 40, and 50 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-848 |
Page 58: Add index entry |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-847 |
Page 57: mathematical issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-844 |
Page 35/6: Why are attributes and association not inherited? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-843 |
Page 35/6: Use of word type is confusing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-841 |
Page 30: Class scope attribute underlined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-840 |
Page 29: Protected member |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-842 |
Page 35/6 : Stereotypes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-839 |
Page 26: rename reponsibilities, rules, modification histories etc. |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-838 |
Page 24 Section 5.4.3 para 1: missing compartments |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-837 |
Page 24: add link to Interface |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-835 |
Page 13: Packages are GeneralizableElements |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-834 |
Page 11: Operation-Call |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-836 |
Page 20: Section 4.3.1 could be misleading |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-833 |
Editorials on pages iv, v, 3, and 4 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-832 |
Typos on page 90, 151 plus errors in page numbering |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-831 |
Page 143: "uses" as a stereotype on Generalization |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-830 |
Page 143: uses is a stereotyped dependency |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-829 |
Page 136: Model package relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-828 |
Page 98: Transition is an aggregation of guards |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-827 |
Uses and extends not types of generalization |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-826 |
Page 93: use case |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-824 |
Discussion on Collaborations and Interactions is confusing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-823 |
Typos on pages 55 and 62 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-825 |
Page 93: Is Namespace really aggregeation of use cases? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-822 |
Page 50 Table 3 "refinement" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-818 |
Page 47: Dependency is a unidirectional, client-server |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-817 |
Page 45 dependency lines 2/3 between model elements not instances? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-820 |
Page 50: should stereotypes be defined at the subclass level? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-819 |
Page 50: "instance" should be changed to "instatiate" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-821 |
Page 50: table 3 component |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-814 |
Page 38 para 2 line 3, one of its containers is deleted |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-813 |
Page 35 Diagram (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-812 |
Page 35 -Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-811 |
Class to be defined as an intension |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-816 |
Aggregation of class? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-815 |
Page 40 table 2 Model Element class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-810 |
How to stop an interface realizing a Data Type ? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-809 |
Why does GeneralizableElement inherit from Namespace? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-806 |
Page 16 lost fact that Class realizes an interface |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-808 |
Page 16 ---editorial (Element Ownership) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-807 |
Is name space really a *composite aggregation* of model elements? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-805 |
Interface must also have features |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-804 |
Why is Classifier an Aggregate of Features? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-803 |
Collaboration as a Classifier |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-802 |
Interfaces and support classes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-801 |
UML Semantics, p 81, 145 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-798 |
UseCaseInstance badly defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-800 |
Extension/recommendation needed for inner/outer transitions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-799 |
Notation for state machine inheritance |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-793 |
Collaboration showing instances |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-792 |
Inconsistency between stereotype tables |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-796 |
Multiple transitions from initial states should be allowed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-795 |
Modeling of guards |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-794 |
Collaboration::constrainingElement semantics |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-797 |
Semantics of terminate transitions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-790 |
Stereotypes for superclasses do not apply to superclasses |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-789 |
Inconsistent use of stereotypes, tagged values, and metamodel |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-788 |
Class WFR (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-787 |
Modeling of realization/specification |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-791 |
Stereotype modeled in two ways |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-786 |
GeneralizableElement should not inherit from Namespace |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-785 |
Syntax for Sequence Expressions inconsistently used |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-784 |
Threads of control in Collaboration Diagrams |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-783 |
Control Flow types not modeled |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-782 |
RaiseAction and TimingMark are not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-781 |
Mapping of concurrent subregions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-780 |
"do" action not supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-779 |
Notation for iteration in sequence diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-778 |
"derived" not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-775 |
WFR for bound elements missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-774 |
The meta-type of template parameters |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-773 |
Dependency wrongly mapped |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-777 |
<>, <>, <>, <>, not well supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-776 |
Namespace in case of containment |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-772 |
Package importing transitive |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-771 |
"invoked" not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-770 |
Bad example for LCA, main source, main target |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-769 |
Transition WFR badly written |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-768 |
Entry/Exit actions execution order |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-767 |
CompositeStates with non-composite subregions allowed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-766 |
Message::base undefined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-765 |
AssociationEnd-AssociationEndRole inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-764 |
Argument::type not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-762 |
WFR for instance links |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-761 |
Well-formedness Rules for Action::actualArguments |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-760 |
CallAction::request |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-759 |
CallAction::isAsynchronous and CallAction::mode |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-763 |
MessageInstance not used |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-754 |
Node and Component parent |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-753 |
Qualifier badly modeled |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-758 |
Action::isAsynchronous and Action::script not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-757 |
Signal::isAsynchronous and Signal::direction not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-756 |
Request"s parents |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-755 |
"implementation" association not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-752 |
Signature conflicts across an inheritance hierarchy |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-751 |
Exotic uses of generalization |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-750 |
Set of inheritable features not defined |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-749 |
Correspondence between operation and method (02) |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-748 |
Correspondence between operation and method |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-744 |
Signature conflicts not well defined (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-743 |
Features and ownedElements (2) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-742 |
"feature" defined twice |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-747 |
Use of language-dependant type expressions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-746 |
Return types for BehavioralFeatures |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-745 |
Package importing not well supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-739 |
UML Semantics 1.1, p26, Operation::isPolymorphic |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-741 |
Features and ownedElements (1) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-740 |
Signature conflicts not well defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-738 |
OCL Specification 1.1, section 8 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-737 |
OCL specification 1.1, p. 14, 5.13, example |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-736 |
OCL specification 1.1, p. 15, 5.14, second last paragraph |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-733 |
OCL specification 1.1, p. 32 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-732 |
OCL specification 1.1, p. 10, 5.4.3, example 3 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-735 |
OCL specification 1.1, p. 24, 7.1.7 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-734 |
OCL specification 1.1, p. 30, 7.2.4 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-731 |
OCL specification 1.1, section 7.2.2 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-730 |
Definition of select and reject operations for Set"s is erranious |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-729 |
Difference between methods, attributes and operations not clear |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-728 |
Editorial issue: OCL spec 1.1, section 6.3, example 2, last row |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-727 |
UML 1.1 Semantics, section 8.2, page 66 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-726 |
Contents of section "Control Icons" is vague |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-723 |
Missing sentence |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-722 |
Editorial error in Semantics |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-725 |
Missing word - editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-724 |
Procedure undefined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-721 |
ActionState implicit deferring of events |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-720 |
internalTransition |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-718 |
Deep History Vertex |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-719 |
deferredEvent mentioned twice in Abstract Syntax |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-713 |
No mapping for send/receive time in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-717 |
Inconsistent definition of extends relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-715 |
No mapping for TimingMark in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-714 |
No mapping for "transition string" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-716 |
No notation for ActivityState |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-709 |
Inconsistent constraint for discriminator |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-708 |
Missing notation for templates |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-712 |
No mapping for swimlanes in Sequence Diagram |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-711 |
Property "derived" not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-710 |
Interface specifier not mapped |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-705 |
Well-formedness rules only expressed in English |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-704 |
Well-formedness rules missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-707 |
Confusing text |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-706 |
Missing mapping for directed constraint |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-703 |
Inconsistent definition of stereotype "thread" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-700 |
Stereotypes applied to more than one ModelElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-699 |
English contradicts OCL in rule for CompositeState |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-698 |
Misleading name Link.linkRole |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-697 |
Enumeration OperationDirectionKind obsolete |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-702 |
Inconsistent definition of stereotype " process" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-701 |
Inconsistent definition of enumeration |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-696 |
ordered missing for Constraint.constrainedStereotype |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-695 |
Inconsistent definition of stereotype "friend" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-694 |
Inconsistent definition of stereotype "thread" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-693 |
Wrong aggregation kind for templates |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-689 |
Inconsistent attachment of Activity Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-692 |
Method visibility |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-691 |
Feature.owner must be optional |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-690 |
Extension points of operations not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-688 |
Inconsistent definition of state machine attachment |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-687 |
Inconsistent format of signal/event |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-686 |
More arrow types than message kinds |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-684 |
Attachment of message in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-685 |
Inconsistent mapping of labels in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-682 |
UML 1.0: "role" should be "end" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-681 |
UML 1.0: Template example cannot be representaed in model |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-683 |
UML 1.0: Unknown model element "Qualifier" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-680 |
UML 1.0: Inconsistent name of stereotype "import" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-679 |
UML 1.0: multiplicity "unspecified" not possible |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-676 |
Inconsistent name space rules |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-675 |
UML 1.0: instances |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
UML14-678 |
UML 1.0: Stereotype "uses" applied to more than one class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-677 |
Inconsistent name for stereotype implementationClass |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-673 |
UML 1.0: Tagged value "location" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-672 |
UML 1.0: Inconsistent mapping of interface circles |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-669 |
UML 1.0: Attachment of messages in Collaboration Diagrams |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-671 |
UML 1.0: Node/Component Instances not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-670 |
UML 1.0: No notation for ModelElement.implementation etc. |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-674 |
UML 1.0: Inconsistent arrow heads for dependencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-666 |
UML 1.o: Qualified things in Collaborations |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-665 |
UML 1.0: Collaborations not well defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-668 |
UML 1.0: No notation for ClassifierRole.availableFeature |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-667 |
UML 1.0: Collaborations and Association (role) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-664 |
CallEvent: operation label in figure 18 is not present |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-663 |
Signal label in figure 18 is not present |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-662 |
Figure 15, AssociationRole class issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-659 |
Description of ActionSequence indicates that it is composition of Actions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-658 |
ActionSequence class issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-661 |
Collaboration package: constrainingElement aggregation misdrawn |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-660 |
Collaborations package--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-657 |
Reception class has wrong attribute |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-656 |
Figure 12 shows no attributes for exceptions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-655 |
Behavioral Features called context |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-654 |
Request class is not an abstract class as indicated |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-653 |
Action class is no abstract class as indicated |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-652 |
Description of ViewElement indicates that it is subclass of Element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-647 |
Inconsistency of UML metamodel |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-649 |
Node class shown as subclass of classifier |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-648 |
Node class issue (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-651 |
Comment class shown as subclass of ModelElement class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-650 |
Description of component shown as subclass of class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-645 |
UML Notation Guide, boolean properties |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-644 |
UML Notation Guide, association ends |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-646 |
Association between Method and Operation |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-643 |
UML stereotypes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-642 |
UML potential inconsistency about stereotypes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-641 |
Inconsistency of UML metamodel |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-640 |
Parameters/Attributes need Specification Classifiers |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-639 |
Predefined LinkEnd constraints issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-638 |
Predefined LinkEnd constraints shown as stereotypes in Notation Guide |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-636 |
diagram fragment at start of Model section on page 136 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-635 |
No notation defined in the Notation Guide |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-634 |
ActivityState in Figure 22 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-633 |
well-formedness rules for BehavioralFeature |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-637 |
Figure 8 (Semantics, p. 44) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-630 |
Figure 5 Semantics document (p. 16) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-629 |
Second para, Section 5.16.1: conflict with statement on p 141 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-632 |
Well-formedness rulw [2] for Class (Semantics, p. 27-28) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-631 |
Well-formedness rule [4] for Association |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-628 |
Section 5.16.1--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-627 |
Page 53 UML semantics: base class of TaggedValue not shown |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-624 |
Missing role descriptions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-623 |
ModelElement Associations (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-626 |
Page 44 UML 1.1 Semantics, figure 8: no base class for ViewElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-625 |
Page 44 UML 1.1 Semantics, figure 8: no component role name |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-622 |
ModelElement Associations (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-621 |
ElementOwnership subclass of ModelElement? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-619 |
Package dependencies (08) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-618 |
Package dependencies (07) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-620 |
Package dependencies (09) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-617 |
Package dependencies (06) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-616 |
Package dependencies (05) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-613 |
Package dependencies (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-612 |
UML 1.1 bug |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-615 |
Package dependencies (03) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-614 |
Package dependencies (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-609 |
Page 10 UML 1.1 Semantics, duplicate entries listed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-608 |
Page 98 of UML 1.1 Semantics, figure 18 (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-611 |
UML 1.1 Semantics: Partition (pp.121 123) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-610 |
Page 102 of UML 1.1, StateVertex class misses description |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-607 |
Page 98 of UML 1.1 Semantics, figure 18 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-606 |
Page 98 of UML 1.1 Semantics, figure 17 (04) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-605 |
Page 98 of UML 1.1 Semantics, figure 17 (03) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-604 |
Page 98 of UML 1.1 Semantics, figure 17 (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-603 |
Page 98 of UML 1.1 Semantics, figure 17 (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-598 |
Page 43 of UML Semantics, figure 7 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-597 |
Page 43 UML 1.1 Semantics, figure 7 --editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-600 |
Page 46 of UML 1.1 Semantics, description of associations for ModelElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-599 |
Page 44 UML 1.1 Semantics, figure 8 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-602 |
Page 47 of UML 1.1 Semantics, description of ViewElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-601 |
Page 47 of UML 1.1 Semantics, description of Refinement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-596 |
Page 16 of UML Semantics, figure 5 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-595 |
Page 62---editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-594 |
Page 62 "PseudostateKind"--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-592 |
Page 61: CallConcurrencyKind and EventOriginKind not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-593 |
Page 61 "EnumerationLiteral"--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-587 |
Page 50 table 3: Dependency Model elements (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-586 |
Page 50 table 3: Dependency model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-591 |
Page 60 figure 10: Data types |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-590 |
Page 9 figure 2: foundation packages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-589 |
Page 137 table 6: Model management - Standard Elements |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-588 |
Page 50 table 3: Component model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-585 |
Page 50 table 3: Auxiliary Elements-Standard Elements (Component model ele |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-584 |
Page 40 table2: Generalization model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-583 |
page 40 table2: Classifier model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-582 |
Page 40 table 2:Constraints Model |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-581 |
Page 40, table 2: Core - Standard Elements |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-580 |
Page 54 - ConstrainedStereotype |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-579 |
Page 39 - ModelElement/Dependency associations |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-578 |
Page 16- The association from parameter to classifier has a 1-1 cardinalit |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-577 |
Page 121 - Partition has no parent class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-576 |
Page 98: ActionSequence has no parent class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-572 |
Page 60 - GraphicMarker |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-574 |
Page 35/37 - AssociationRole |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-573 |
Page 60 - MultiplicityRange |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-575 |
Page 81: message has no parent class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-571 |
Page 60 - visibilityKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-569 |
page 60 - EventOriginKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-568 |
page 60 - CallConcurrencyKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-570 |
Page 60 - PseudostateKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-564 |
UML Documentation--Typos (05) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-565 |
UML Documentation--Typos (06) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-566 |
UML Documentation--Typos (07) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-567 |
Error on association owners |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-562 |
UML Documentation--Typos (03) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-561 |
UML Documentation--Typos (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-560 |
UML Documentation-Typos (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-563 |
UML Documentation--Typos (04) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML25-672 |
Problems with OCL definition of Package::makesVisible |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-671 |
an instance spec should be a legitimate value of a property typed by a classifier |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-668 |
A comment is a specialization of Element |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-667 |
Surplus classifier field serialized in Superstructure.xmi |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-670 |
Attribute is represented by Property |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-669 |
Operation "isConsistentWith" is not overridden for any RedefinableElement |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-664 |
Question About Arrows In Communication Diagramms |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-663 |
Constraint [1] uses undefined attribute "ownedAttribute |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-662 |
Inconsistency: CentralBufferNode (ch .12.3.16) and fig. 12.15 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-665 |
missing words in section 14.1 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-673 |
Incomplete sentence |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-666 |
DurationObservation#event should be ordered |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-661 |
LifeLine instead of Lifeline |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-607 |
UML 2 Super/Templates/Inconsistent organization |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-606 |
UML 2 Superstructure -Incompatible use of term link |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-604 |
UML 2.0 Issue: Semantics of Provided and Required Interfaces |
UML 1.4.2
|
UML 2.5
|
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-615 |
9.3.11 Port (from Ports) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-614 |
.3.44 Property (from Kernel) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-610 |
UML2 super/CommonBehavior/Opaque behavior : bad OO modelling |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-611 |
7.3.24 Interface (from Interfaces) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-605 |
UML 2 Superstructure - cross-hair notation for nested classes |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-612 |
9.3.6 Connector (from InternalStructures) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-613 |
8.3.1 Component (from BasicComponents, PackagingComponents) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-630 |
UML 2.3: Transitions outgoing junction vertexes should be allowed to have triggers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-622 |
inconsistent Generalization subsections in spec format |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-621 |
notational standard for {subsets x} in textual contexts |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-629 |
15.3.11 State (from BehaviorStateMachines, ProtocolStateMachines) |
XMI 1.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-623 |
"Class" should read "Classifier" in Generalization subsection for Behaviore |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-620 |
15.3.14 Transition (from BehaviorStateMachines) |
XMI 1.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-619 |
15.3.10 Region (from BehaviorStateMachines) |
UML 1.4.2
|
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-626 |
UML2 Super / Templates / ordering of subExpressions |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-617 |
15.3.16 Vertex (from BehaviorStateMachines) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-616 |
Artifact (from Artifacts) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-625 |
UML 2 Super/ Classes / issue with Property::isComposite |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-618 |
15.3.8 Pseudostate (from BehaviorStateMachines) |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-675 |
Modeling sent messages in State Machines |
UML 2.3b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-674 |
TestIdentityAction for datatypes |
FUML 1.0b2
|
UML 2.5
|
Resolved |
closed |
|
UML25-660 |
Behavior should be derived from Classifier, not Class |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-659 |
Package merge on Class metatype causes semantic issues - particularly with state machine context |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-648 |
Error in UML diagrams? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-647 |
Suggestions for editorial changes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-654 |
how to instantiate associations between stereotypes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-653 |
Core package caption wrong |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-658 |
Add an example for the lifeline head shape |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-657 |
color of the notation is specified |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-656 |
The property packagedElement: PackageableElement [*] is not a derived property and should not be prefixed with "/" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-655 |
Opposite ends of derived unions should be derived unions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-651 |
Use of term "locus of control" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-650 |
V2.4.1 from 11-08-05 on page 14 in Figure 7.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-646 |
default is wrong |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-645 |
V2.4.1 from 11-08-05 on page 14 in Figure 7.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-649 |
Reference in index to item that does not exist in contents |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-652 |
incorrect upper value of coveredBy of Lifeline |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-632 |
ChangeEvent association mismatch |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-631 |
EnumerationLiterals in the XMI |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-635 |
"A_realization_abstraction_component" is useless |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-634 |
Subpart I and II are missing in Bookmarks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-644 |
default value of ClassifierTemplateParameter#allowSubstitutable is "..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-643 |
Figure 15.2 does not include TransitionKind |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-640 |
role "interval" appears "interva" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-639 |
OpaqueBehavior#body attributes "nonunique" truncated as "nonuni..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-642 |
misspelling: io-oargument |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-641 |
OpaqueBehavior#body attributes "nonunique" truncated as "nonuni..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-636 |
RedefinableElement (from Kernel) is preferable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-633 |
UML Superstructure Specification |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-637 |
poor figure resolution and a misspelling: fal...( false ) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-638 |
{ordered} is rather far from +bodyOutput |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-601 |
UML 2 Super and Infra/ defualt property of Parameter::effect |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-602 |
Associations between interfaces |
UML 1.4.2
|
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-499 |
Association notation for properties does not allow representation of aggregation |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-498 |
UML2.5 issue: incorrect use of oclKindOf()->notEmpty() |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-497 |
wrong multiplicity of redefining states |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-496 |
Keywords are inconsistently defined and applied |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-487 |
InformationFlow::sources_and_target_kind |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-494 |
UML2.5 issue: clause 7.7.5 does not correctly refer to Instantiate stereotype |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-493 |
UML 2.5 - clause 14 does not put Examples at the correct heading level |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-489 |
Table C.1 apply |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-488 |
Metaclass operations incomplete |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-492 |
UML2.5 issue: clause 10 Signal and Reception |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-491 |
Conflict in use of unlimited natural |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-495 |
UML 2.5: ActivityPartition::represents keywords |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-490 |
UML 2.5 FTF - Clause 17 Interactions, Section 17.2.3 Semantics, subsection Interaction |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-486 |
Classifier::hasVisibilityOf(...) |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-485 |
Two entries |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-519 |
About UseCase description |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-518 |
Annex B summary table |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-529 |
actors of a use case express the requirements of its subject(s) regarding its/their environment. |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-528 |
UML: Parameter Direction and Effect |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-523 |
UML 2.5 Issue: specification for qualified association ends is in wrong clause |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-522 |
UML 2.5 class_name |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-526 |
Event pools for passive objects |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-525 |
Behavior after exceptions are encountered |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-521 |
UseCases editorial change |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-520 |
The current criteria used in UML for BehavioralFeature::isDistinguishable() is insufficient in practice |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-517 |
Clarify that stereotypes can be applied to UML DI |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-516 |
UML2.5 clause 17 keyword inconsistency |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-524 |
Completion events disambiguation |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-527 |
UML 2.5: Clarification of semantics for CreateLinkAction and DestroyLinkAction |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-530 |
UML 2.5 FTF Receptions may not have a method |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-414 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Or Pre-conditions appears limiting |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-417 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Clarification meaning of not part of the subject |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-416 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Point to Figures to help explain subject vs owner |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-415 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Initiating ? Interacting with |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-420 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Omitted conditions are true |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-419 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Easy |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-418 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Additional behavior vs Additional use case |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-422 |
Location: 18.1.4 Notation P. 688 - Point to diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-421 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Clarify role of owner |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-574 |
State Machine Package--Compliance |
RAS 2.0b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-573 |
Actions need to be independent from Activities |
RAS 2.0b1
|
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-566 |
Composite structures/contradictory constraint on connector |
RAS 2.0b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-568 |
UML 2 Super/Interfaces |
RAS 2.0b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-571 |
Issue in UML 2 CombinedFragment class |
RAS 2.0b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-570 |
Issue in UML 2 Message class |
RAS 2.0b1
|
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-569 |
Issue in UML 2 Message class |
RAS 2.0b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-572 |
Issue in UML 2 Gate class |
RAS 2.0b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-503 |
Interactions needs to fix Gate name Distinguishability rules |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-502 |
ActionInputPin notations missing |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-515 |
UML 2.5's Collaboration semantics is inconsistent with Collaboration::collaborationRole |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-514 |
UML2.5's Connector role constraint excludes inherited roles |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-505 |
Message Constraint signature_is_Signal only merely refers to Signal.ownedAttributes as parameters of a Message signature |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-504 |
Classifier operation inherit(NamedElement[*]) : NamedElement[*] |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-511 |
Forked association notation ill-formed |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-501 |
UML 2.5 Beta 1 9.5.3 Qualifiers |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-500 |
Transition redefinition |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-513 |
parts should be allowed to show their interfaces |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-512 |
Behavior is not allowed to be source or target of an InformationFlow |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-510 |
UML 2.5 FTF] Editorial / §15.5.1 p429 |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-509 |
Inheriting Connectors |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-507 |
UML 2.5 FTF 14.2.3 Page 327 Typo |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-506 |
Incorrect text on state list notation interchange |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-508 |
UML 2.5 FTF 15.3.3 Page 406 decisionInputBehavior rather than decisionInput |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-582 |
UML 2 Super/Components/missing description of Connector::contract |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-581 |
UML 2 Super/Interactions/notation for accessing a static feature |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-584 |
Missing notation for Behaviors in a BehavioredClassifier |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-583 |
Name without a colon for Property in Composite Structures |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-586 |
Profiles in Compliance Level 1? |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-585 |
Redundant parameter specifications for Operation and Behavior |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-576 |
There is no "precise mapping |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-579 |
UML 2 Super/Activities/Class-Activity association missing |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-578 |
UML2 super&infra/Profiles/ownership of Image |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-588 |
Figures 103 and 121 use <> dependencies |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-587 |
. <> on Usage |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-580 |
UML 2 Super/Templates/Template substitution symbol problematic |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-577 |
Port should specialize featuringClassifier |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
UML25-575 |
Semantics section of StructuralFeature |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
UML25-538 |
Clarification of use of BNF for textual notations |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-537 |
ActivityParameterNode notation |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-539 |
Avoid covariant parameters in metamodel operation redefinition |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-536 |
The resolution to Issue 18528 contains incorrect OCL and operation names |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-535 |
The resolution to issue 18415 contains invalid OCL |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-546 |
Wording corrections in Behavior Diagrams and Activity Diagram Labels |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-545 |
Labels for generalization sets in UML DI |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-541 |
Classifier and state annotations in UML DI |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-540 |
Dashed interaction lifelines in UML DI |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-532 |
Action operation redefinition is invalid |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-531 |
Association::endType() is inconsistent |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-534 |
Improve documentation of how derived properties are calculated |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-533 |
The resolution to 18697 contains errors |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-544 |
Template parameter rectangles |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-543 |
Ownership of property qualifier rectangles |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-542 |
Dependencies with more than two ends in UML DI |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-432 |
Location: 18.1.5 Examples Figure 18-9. 690 - Description does not match figure 18-9 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-431 |
Location: 18.1.5 Examples Figure 18-2. 689 - Explain about multiplicity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-424 |
Location: 18.1.4 Notation P. 688 - Point to diagram (03) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-423 |
Location: 18.1.4 Notation P. 688 - Point to diagram (02) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-429 |
Location: 18.1.4 Notation P. 688 - Point to diagram (08) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-428 |
Location: 18.1.4 Notation P. 688 - Point to diagram (07) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-427 |
Location: 18.1.4 Notation P. 688 - Point to diagram (06) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-426 |
Location: 18.1.4 Notation P. 688 - Point to diagram (05) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-430 |
Location: 18.1.5 Examples Figure 18-2. 689 - Explain about «Subsystem» |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-436 |
Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - At least one actor |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-435 |
Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - At least one actor |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-425 |
Location: 18.1.4 Notation P. 688 - Point to diagram (04) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-433 |
Location: 18.1.5 Examples Figure 18-10. 691 - Duplicate Diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-434 |
Location: 18.2 Classifier Descriptions Include Constraints. 696 - Includes must be a DAG |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-483 |
UML 2.5 issue: Clause 6.3 should contain a definition of "execution scope" |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-482 |
Fixed-point issues with the definition of default values for literals |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-475 |
Fix the notation to allow assignment of a decision to partition when the swimlanes are not practical. |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-474 |
UML association semantics vis-a-vis Interfaces (and other types of classifiers) |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-473 |
confusing wording and terminology for TransitionKind in the section Transition kinds relative to source. |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-470 |
Section 11: feature inheritance should be orthogonal to the topology of well-formed connections in a structured classifi |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-469 |
ConnectableElement-end" has @isOrdered='true' |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |