| UAF13-18 |
UML::Property.defaultValue has upper multiplicity of 1 even though Property is a MultiplicityElement |
UML 2.5.1
|
UAF 1.3b1
|
Deferred |
closed |
|
| CORBA34-274 |
when is a connection a "bi-directional connection"? |
UML 2.0
|
CORBA 3.4
|
Deferred |
closed |
|
| 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 |
|
| UMLR-748 |
Thing |
UML 2.5
|
$issue.fixedSpecification.name
|
Deferred |
closed |
|
| UML22-319 |
Explanation of Observation notation |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UMLR-699 |
Notation of a reception: Keyword <> is superfluous |
UML 2.5
|
$issue.fixedSpecification.name
|
Deferred |
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 |
|
| OCL231-38 |
Lack of features commonly used in OCL |
UML 1.1
|
OCL 2.3.1
|
Resolved |
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 |
|
| DDS4CCM_-24 |
Section 7.2.3: Line 38-39 starting with "note that events" doesn't read |
UML 2.2
|
DDS4CCM 1.0b2
|
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 |
|
| OCL2-6 |
Section 6.6.2 |
UML 1.4
|
OCL 2.0b2
|
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-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-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-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-567 |
Concept of 'port side' not to be found in metamodel |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-565 |
Description text for CollaborationOccurrence unclear |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-564 |
Editrial error in Section: 9.3.4 ? |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-563 |
Association collaborationRole |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-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 |
|
| UML25-472 |
The derived property Classifier::/inheritedMember does not correctly define the meaning of inheritance |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-471 |
UML 2.5 issue: structural features with isStatic = true may not have a slot in InstanceSpecifications |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-478 |
Notation for state machine specializations |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-477 |
UML2.5 issue : missing constraints on aggregation / composition |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-476 |
Two different Dashed Arrow Styles for Reply message in Figure 17.2 Interaction Example |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-481 |
Error in Dependency notation example |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-480 |
Error in diagram using StringExpressions |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-479 |
Inconsistent template binding notation example |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-468 |
UML2.5: clarification about the semantics of redefinition |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-467 |
Lifeline has no type. |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-466 |
Location: Table B.1 UML Keywords p 778 - Use of # in Semantics col |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-484 |
UML 2.5 issue; the word "individual" is incorrect in 9.8 |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-451 |
Location: B.4.4 State Shapes P. 752 - State List Limitations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-450 |
Location: B.2.4 P. 739 - confusing model and diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-441 |
Location: Table 21-1 PrimitiveType semantics Real P. 726 - IEEE 754 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-440 |
Location: 21.1 Summary P. 726 - Missing header |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-438 |
Location: Figure 18-3 Example Extend p.689 - Circle on comment "anchor" not standard |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-437 |
Location: 18.1.1 Summary p 685 - emergent behavior |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-445 |
Location: Table 21-1 String P. 726 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-444 |
Location: Table 21-1 P. 726 - Title of table not great |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-443 |
Location: 21.2 Semantics P. 726 - Subsection title |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-442 |
Location: Table 21-1 PrimitiveType semantics Real P. 726 - Real Number representation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-448 |
Location: Figure 21-3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-447 |
Location: Table 21-1 P. 726 - Row ordering |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-446 |
Location: Table 21-1 Unlimited Natural P. 726 - Infinity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-439 |
Location: Figure 20-4 and accompanying text P. 719 - InformationItem can represent multiple types? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-449 |
Location: B.2.3 P. 738 - confusing model and diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-595 |
Active and passive |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-594 |
P.58 Missing closing bracket in second constraint |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-592 |
"required interface" |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-591 |
Compliance points - Diagram Interchange |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-596 |
UML 2 does not permit use of a state machine |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-598 |
included use case wrongly referred to as the including use case |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-597 |
check the BNF example given in the text |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-590 |
Bidirectional messages to a port object |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-589 |
Figures 120 and 121 |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-600 |
"role binding" |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-599 |
multiplicity of the "role:ConnectableElement" |
UML 2.0
|
UML 2.5
|
Resolved |
closed |
|
| UML25-593 |
P.35 Typo in OCL definition of isDistinguishableFrom query |
UML 1.4.2
|
UML 2.5
|
Resolved |
closed |
|
| UML25-553 |
misleading omission |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-552 |
Validation errors in UML metamodel |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-547 |
PrimitiveTypes::UnlimitedNatural lacks an XML-compatible serialization for the 'unbounded' value |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-549 |
Assocation display options too narrow |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-548 |
Annex E lacks sub-clauses for the XMI details for StandardProfile and UMLDI |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-551 |
UML 2.5 issue: subsettingContext() has incorrect logic |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-550 |
Headed composite and not ownedElement |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-554 |
Activity::structuredNode is incorrectly marked as readOnly = true |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-456 |
Location: Annex C Keywords p 777 - Capitalization of «trace» |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-455 |
Location: Annex C Keywords P. 777 - Previously unmentioned constraints given in Keywords Annex |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-453 |
Location: B.6 UMLILabel Constraints. P 766 - Use Case Oval. |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-452 |
Location: B.6 Classifier Description UMLInheritedStateBorderKind [Enumeration] Literals p 763 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-458 |
Location: Table B.1 UML Keywords p 778 - Keywords should be in index |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-457 |
Location: Annex C Keywords p 777 - Capitalization of «create» |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-464 |
Location: Index p. 796 among others - Index items with only one page |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-463 |
Location: Index p 795 - Index of "is" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-460 |
Location: Index |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-459 |
Location: Annex C Keywords P. 780 - Bizarre definition of statemachine |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-454 |
Location B.6 UMLStateShape statelist p 770 - StateList Limitations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-462 |
Location: Index p 793 - emergent behavior |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-465 |
Location: Index Mis. - Missing terms in the Index |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-461 |
Type: Structural - Location Index p 790, 794, |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-394 |
Location: 15.5.1 - typo |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-393 |
Location: Figure 15.57 page 426 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-399 |
Location: 17.2.3 Semantics Interaction Fragments p 607 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-398 |
17.1.5 Interaction Diagram Variants p 607 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-397 |
Location: p 484 - Exception store |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-396 |
Location: Figure 15-23 p.411 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-391 |
Location: Figure 15-23 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-390 |
Location: p. 357 StateMachine Redefinition |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-389 |
Location: p. 338 Transition execution sequence |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-388 |
Location: p. 338 Transition execution sequence |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-395 |
Location: Figure 15-63 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-387 |
Location: p. 337 Conflicting Transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-392 |
Location: Page 413, 15.3.2 Abstract Syntax Control Nodes Figure 15-26 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-386 |
Location: p. 337 Conflicting Transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-317 |
What is Intentionally Not specified? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-316 |
What is aggregation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-311 |
inout parameters and effects |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-310 |
Effect Intent |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-308 |
Return Parameter order |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-307 |
Default value of readonly should be referenced |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-313 |
Parameter Sets |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-312 |
isException and direction and effect |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-320 |
Location: 9.5.3 p 122 In the common case |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-319 |
Location: 9.5.3 p 121 Why not all empty |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-314 |
Use isReadOnly default |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-315 |
Redefinition does not allow for overloading |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-318 |
What is Intentionally Not specified? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-309 |
Return Parameter pronoun |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-223 |
Two categories is not enough |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-222 |
UML Semantics |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-224 |
Semantics Areas section not clear |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-413 |
Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Variants are not defined |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-412 |
Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Actors need not initiate |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-411 |
Location: 18.1.3 Semantics Use Cases and Actors P. 685 - Are actors mandatory? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-405 |
Location: Pg. 615, Figure 17.4.3: Semantics, Sub-clause: Messages |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-404 |
Pg. 613, Clause 17.3.4: Notation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-403 |
Location: Pg. 612, Clause 17.2.5 - Minor rewording to Clause 17.2.5 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-402 |
Location: Pg. 612, Figure 17.5 - Modify Figure 17.5 to enhance readability |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-410 |
Location: 18.1.1 Summary P. 685 - A Subject may only refer to a single system |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-409 |
General value lifeline Row p 647 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-408 |
Location: Table 17.6 entire table p 646 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-401 |
Pg. 611, Clause 17.2.5: Examples - : Insert formal in reference to gates in the Examples clause (17.2.5) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-400 |
Location: 17.2.4 Notation ExecutionSpecification p608 - : Specification of color |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-407 |
Location: LostMessage Row p 639 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-406 |
Pg. 617, Figure 17.4.3: Semantics, Sub-clause: Gates - Replace formal with actual in Clause 17.4.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-264 |
Default value for LiteralString |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-263 |
Optional String Multiplicity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-256 |
Excessive null checks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-255 |
Single and set of aren't really parallel |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-252 |
Missing a |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-251 |
inconsistent spacing on diagram |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-260 |
TypedElement description could be expanded |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-259 |
It seems to me that a relationship requires a minimum of two relatedElements |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-254 |
Use of the diamond symbol (?)needs to be explained |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-253 |
Instantiate Dependency |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-261 |
Generalization Relationship to itself? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-262 |
Negatively phrased sentence |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-258 |
Sentence difficult to read |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-257 |
allNamespace description doesn't match OCL |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-338 |
Location p 152 Generalization Attributes: IsSubstitutable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-340 |
Location p 153 complete_and_disjoint: Abstract Implication |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-339 |
Location p 153 complete_and_disjoint: Complete vs covering? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-334 |
Location: p 145 CallConcurrencyKind [Enumeration - blocks -- > locks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-333 |
Location: p 145 (3X) Detail: simultaneously -- > concurrently |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-337 |
Location p 146 Classifier Description: isAbstract |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-336 |
Location p 145 Classifier Description: objects -> instances |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-343 |
Location p 162 two_parameter_sets: Why |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-342 |
Location p 157 isConsistentWith: missing rules |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-341 |
Location p 154 Association Ends: Instances of multiple classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-344 |
Location p 162 ParameterSet constraints input: Exceptions and parameterset |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-335 |
Location p 145 Classifier Description - objects -> instances |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-249 |
While-->And |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-248 |
Unclear description of multiplicities |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-243 |
Imports |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-242 |
ElementImport cannot be further imported |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-247 |
Confusing description of types |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-238 |
Note refers to an undiscussed concept |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-240 |
Packageable Elements and Imports |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-239 |
Missing word |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-246 |
Missing TypedElement - use of the term constrained seems to be circular |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-245 |
Missing TypedElement |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-250 |
Missing OCL |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-241 |
Packageable Elements and Imports (02) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-244 |
Incorrect text describing diagram elements |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-358 |
Location 13.1 Summary p 305 - Use of the word emergent |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-357 |
Operations p 245 (2X) typo |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-355 |
Location Figure 11-23 s p.217 - Instance/roll names |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-354 |
Location Figure 11-22 s p.216 - Title doesnt match contents |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-351 |
Location: Constraints p 193 - Missing constraint? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-350 |
Location 10.4.4 Notations p.188 - Reception compartment |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-349 |
Location 10.3.3 Signals p.186 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-348 |
10.2.4 Notation p 184. - Enumeration attributes and operations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-346 |
Location: 10.2.3 Enumeration p. 184: New EnumerationLiterals |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-347 |
Location: 10.2.4 Notation p 184 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-353 |
Location Figure 11-21 s p.216 - Instance/roll names |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-356 |
Location Figure 11-23 s p.217 - Instance/roll names (02) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-352 |
Location: Figure 11-3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-281 |
Wrong Reference |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-280 |
missing headings |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-290 |
Min/Max |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-289 |
Two anonymous invariants |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-292 |
8.6 p 100 isCompatibleWith() ..save space |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-291 |
Save Space |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-288 |
result() error |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-287 |
French |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-284 |
Invariant name |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-283 |
Improve readability of constraint names |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-295 |
Association Descriptions not that useful |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-294 |
IsNull not Boolean |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-282 |
Duration Definition |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-286 |
Set--> List |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-285 |
Why is value optional |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-293 |
Turing Machine lurking paradox? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-323 |
Location: 9.6.3 Operations p 127 Undefined ? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-322 |
Location: 9.5.3 p 121 Cant qualifiers be queries? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-330 |
Location: 9.8.4 Notation p 141 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-329 |
Location: 9.8.3 Semantics p 139 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-326 |
Location: 9.6.4 Notation p 128 Is return a reserved parameter name? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-325 |
Location: 9.6.4 Notation p 127 Simplify description of syntax |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-321 |
Location: 9.5.3 p 122 Qualifiers must be enumerated type |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-324 |
Location: 9.6.3 Operations p 127 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-328 |
Location: 9.7.5 Examples p 135 Political Correctness |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-327 |
Location: 9.7.5 Examples p 134 Generalization Sets |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-331 |
Location: 9.8.4 Notation p 141 representing the roles vs representing the instances |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-332 |
Location: 9.9 Classifier Descriptions Association Ends p 144 Behavioral --> Behavior |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-237 |
Clarification of imports |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-236 |
Namespace Abstract Syntax incorrect |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-230 |
Add reference to association notation section |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-229 |
How does dot notation work |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-227 |
Extraneous Note |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-226 |
Sentence does not make sense |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-233 |
Owning Comments |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-232 |
Root Abstract Syntax missing adornments/metamodel incorrect |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-234 |
Owning Rules |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-231 |
Owning Comments |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-225 |
Figure 6.1 does not relate to rest of Specification |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-235 |
Can Comments own comments? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-228 |
What type of slash? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-367 |
Location: Page 330, 331, 333, 14.2.3, Page 347, 14.2.4, Page 375, 14.5 PseudostateKind |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-366 |
Location: Page 329 States - Stable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-362 |
Location: Page 315 Association ends - Explain about having no nestedClassifier |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-361 |
Location: Page 313, 13.2.4 Notation relative |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-369 |
Location: Page 341, 14.2.4 - Example for graphical expression of behavior in states |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-365 |
Location: Page 328 Regions 14.2.3 - Text about regions without initial state |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-371 |
Location: Page 346, State List Notations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-370 |
Location: Page 341, State - More examples needed |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-368 |
Location: Page 338, Transition selection algorithm - Maximal Set |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-364 |
Location: 14.2.1 Summary - Behavior StateMachines for UseCases |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-363 |
Location: 14.1 Summary p 326 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-360 |
Location Behavior Parameters p 307 - Streaming and Multiplicity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-359 |
Location Behavior Parameters p 307 - Optional with default value |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-304 |
Alterative Scopes? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-303 |
Multiplicity of 0..0 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-301 |
Location p.112 (9.3 Classifier Templates) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-300 |
Incompatible with SysML |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-297 |
the parent of a Classifier is not its owner. |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-302 |
Location: p.116 (9.4.3 Semantics) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-298 |
What is inherited or not |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-299 |
Inherited members |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-306 |
Redefinable Static attributes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-305 |
Examples of alternative scopes? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-296 |
Objects? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-378 |
Location: p. 329 State Configurations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-377 |
Location: p. 328 Regions - Resolve intentional ambiguity |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-373 |
Location: Transition , bottom of page 352 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-372 |
Location: Page 347, 14.2.4 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-376 |
Location: p 378 State Description - What is hidden? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-375 |
Location: p 373 outgoing_from_initial - Limitations on guards |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-374 |
Page 353, 14.2.4 - StateMachine symbols on graphical representations of Transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-382 |
Location: p. 333 FinalState |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-381 |
Location: p. 331 Exiting a State - Clarification of Exiting a State |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-385 |
Location: p. 337 2nd ¶ |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-384 |
Location: p. 336 Compound transitions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-383 |
Location: p. 333 Transitions - How do multiple triggers work? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-379 |
Location: p. 330 Deferred Events - Value of Deferred Events |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-380 |
Location: p. 331 Explicit Entry - Clarification of Explicit Entry |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-268 |
Unlimited Natural |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-267 |
String concrete syntax is missing |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-270 |
BNF rules allow for a real 0 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-269 |
Notation: Real |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-266 |
LiteralNull semantics |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-265 |
Default value for LiteralReal |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-279 |
Always non-negative |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-278 |
Duration |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-274 |
set - > list |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-273 |
Plural headers when class name is singular |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-276 |
body text strings |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-275 |
sentence unclear |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-271 |
Past vs Present |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-277 |
String expression notation missing |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-272 |
{ordered} at wrong end |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UMLDI-20 |
UML diagram interchange: limitation of complex properties |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-19 |
A schema definition has to be added for the completeness of the specificati |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-5 |
Introduce a 'Nesting Guide' |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-4 |
Change role name in DI metamodel |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-14 |
UML diagram interchange: unit of measurement |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-13 |
UML diagram interchange: translucent property unnecessary? |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-12 |
UML diagram interchange: do diagrams have to be nodes? |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-16 |
UML diagram interchange: containment vs reference |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-15 |
UML diagram interchange: association as a graph node |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-7 |
UML diagram interchange: inappropriate diagram properties |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-6 |
UML diagram interchange: views may need more context |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-11 |
UML diagram interchange: cut-out diagram feature |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-10 |
UML diagram interchange: dubious value of leaf elements |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-18 |
Rename the specification to OMG Diagram Interchange Specification |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-17 |
UML 2 Diagram Interchange / Assigning icons to stereotypes |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-9 |
UML diagram interchange: more features in schema? |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-8 |
UML diagram interchange: limitation of complex properties |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-1 |
property CoreSemanticModelBridge.element |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-3 |
Allow a Diagram Element to represent multiple Model Elements |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UMLDI-2 |
UML Diagram interchange -- change Rational ref to IBM |
UMLDI 1.0b1
|
UMLDI 1.0
|
Resolved |
closed |
|
| UML25-219 |
Incarnation ? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-218 |
Show how UML is a MOF metamodel |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-214 |
Conformance definitions ? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-213 |
Impact of merging profiles isn't small |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-217 |
Keyword Usage |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-216 |
ISO version of UML 2? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-220 |
Within the System |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-212 |
Capture Submitters, Supporters, etc |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-221 |
Modeling Individuals |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-215 |
DI Conformance implies Model Interchange Conformance |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-191 |
Clarification on the semantics of Multiplicities |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-190 |
Clarification on the semantics of UML |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-189 |
Conformance point |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-193 |
Clarification on the semantics of Properties |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-192 |
Clarification on the semantics of Parameters |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-197 |
Clarification on the semantics of Manifestation |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-196 |
Clarification on the aim of Collaborations |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-195 |
Clarification on the semantics of ports in Encapsulated Classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-194 |
Clarification on the semantics of Connectors within Structured Classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-198 |
Declassifying of Annex D |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-200 |
Missing word in section 7.4.3, "Semantics" |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-199 |
Four typos |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-206 |
ElementImport semantics |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-205 |
Same name" vs. "indistinguishable name" |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-211 |
Missing Table of Figures, Table of Tables - Location: TOC p 10 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-210 |
Minor vs Major revision |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-204 |
Further clarify Element ownership constrains |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-203 |
Semantic conformance implies Abstract Syntax conformance |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-207 |
isConsistentWith() definition broken |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-202 |
Suggested improvements to conformance section |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-209 |
Section 11.5. - Clause 11: Structured Classifiers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-201 |
PDF links to Primitive Types don't work |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML25-208 |
Superfluous word on p309 |
UML 2.5b1
|
UML 2.5
|
Resolved |
closed |
|
| UML24-111 |
Problem with ExtensionEnd::lower |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-108 |
UML state machines: inconsistent subset of StateMachine::extendedStatemachine |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-107 |
isDerived with DefaultValue |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-104 |
Change all properties typed by data types to aggregation=none |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-103 |
Give all constraints unique names within their context. |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-110 |
UML 2.4 - ConditionalNode - Semantics |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-109 |
DecisionNode at all guards evaluated to false |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-101 |
EnumerationHasOperations : UML::VisibilityKind::bestVisibility |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-100 |
Parameter have Effects |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-106 |
Property::isID should not be optional |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-112 |
stereotype <> for defining parameterized classes is nowhere defined |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-105 |
UML 2.4 - Interaction |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-102 |
The metamodel contains instances of Model |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-80 |
xmi files in the 2.4 RTF deliverables have cmof tags contained in a non-XMI root element |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-82 |
Operation::isConsistentWith |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-81 |
UML2.4: StandardProfileL2 & L3 are incomplete as delivered |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-84 |
bodyCondition and isQuery |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-83 |
isConsistentWith |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-74 |
"unique" annotation |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-77 |
The stereotype «Create» and keyword «create» are both defined in the UML 4 document |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-76 |
Figure 9.2 (Abstractions subpackage dependencies) has wrong dependency |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-79 |
"isStatic" property of Feature no longer appears in any diagram |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-78 |
coveredBy : InteractionFragment [0..1] should be [*] |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-85 |
redefinitionContext of Property |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-73 |
Ambiguous constraints for transitions |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-72 |
Typo: isStric => isStrict |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-75 |
Qualified name is incorrectly claimed to be unambiguous |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-68 |
UML 2.4: Add package:URI |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-67 |
UML 2.4: Add Property::isId |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-71 |
UML 2.4: Inconsistent rendering of OCL in UML metamodel |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-70 |
Over-general sentence about MOF and Profiles |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-69 |
UML 2.3 Superstructure: Non-sensible text for modelLibrary stereotype |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-58 |
UML 2.3, Figure 18.1 |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-57 |
Term "method activation" deprecated? |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-66 |
UML 2.3 Issue: Constraint InformationFlow.sources_and_target_kinds |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-65 |
NamedElement::clientDependency constrained to subset DirectedRelationship::source |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-64 |
Figure 7.10 shows Feature::isStatic as abstract |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-59 |
split the addition of generalization relationships among association in 14977 in two parts |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-62 |
It seems odd to say that Service computes a value. |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-61 |
Create |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-63 |
issues relating to Figure 7.14 - The Packages diagram of the Kernel package |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-60 |
Auxiliary |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-130 |
MultiplicityElement constraint 1 inconsistent with possible [0..0] multiplicity |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-128 |
Figure 7.31 propose an association-like notation for attributes |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-127 |
Statement mistake |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-129 |
Section numbering |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-124 |
UML 2.4: Figure 7.31 shows the dot at the wrong end. |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-123 |
UML 2: Multiplicity of Lifeline's coveredBy is incorrectly specified |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-116 |
Fix minor inconsistencies between infrastructure specification document & metamodel |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-115 |
Missing relation between "Namespaces" package and "Ownerships" package in fig. 9.2 (p. 30)? |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-120 |
Deep history for orthogonal states |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-119 |
Parameter semantics related to Behavior and BehavioralFeature |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-118 |
Property.isReadOnly is redundant with StructuralFeature.isReadOnly |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-122 |
Part document structures in Infrastructure need to conform to ISO Standard Document Template Conventions |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-121 |
Big UML 2.4 problem: missing defaults in XMI |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-114 |
Operation with multiple return parameter |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-113 |
Wrong constraint on Operation::bodyCondition |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-117 |
Be explicit that type does not need to be set for LiteralBoolean etc. |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-126 |
Constraint is Wrong |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-125 |
Wrong Classifier Name |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-49 |
UML2 - Invalid constraint for Actor |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-48 |
Detailed modeling of the Standard Profiles |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-52 |
UML 2 issue - misleadingly named associations |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-51 |
Meaning of BodyCondition and its alignment with OCL |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-53 |
Resolution to issue 14063 |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-55 |
Issue 14287 and 13330 resolutions are inconsistent and incorrectly applied. |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-54 |
UML 2 Subclasses of Classifier should subset redefinedClassifier when they redefine |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-47 |
MessageEvents |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-46 |
Association owned derived union |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-50 |
composite tags |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-56 |
UML2 Issue: OCL in resolution 11114 is incorrect |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-45 |
UML2.3 definition of Classifier::hasVisibilityOf is circular |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-44 |
UML2.3: Missing subsetting from A_redefinedClassifier_classifier in XMI |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-29 |
loopVariable ownership |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-95 |
Association conflicts with MemberEnds IsDerived flags |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-94 |
Fix association end multiplicities |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-98 |
Multiplicity Element Is MultiValued With Default Value |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-97 |
Derived properties that are not marked read-only |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-89 |
Message's signature is still derived property (in text only): |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-88 |
UML 2 issue: UML 2.4 normative deliverables should be published in MOF2.4 / XMI 2.4 format |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-96 |
Redefinition of association-owned ends requires association generalization |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-93 |
Fix 14977 vs. 14638 |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-92 |
Association-owned association end name changes |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-87 |
The resolution to issue 13993 that moved PrimitiveTypes to an independent package contained a mistake |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-86 |
Missing subsetting of redefinitionContext by Property::owningAssociation |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-99 |
InstanceValue has no type |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-90 |
DestructionOccurenceSpecification is inherited from OccurenceSpecification instead of MessageOccurenceSpecification |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-91 |
DestructionOccurenceSpecification text in Semantics still refers to events |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-38 |
serialization of a profile should always include the nsURI and nsPrefix tags |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-37 |
Incomplete resolution to 10826 |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-31 |
Definition of Behavior::context is not correct |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-30 |
Context of a behavior owned as a nested classifier |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-32 |
Matching subsettting across association ends |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-43 |
Activity vs Action completion |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-42 |
Enumeration Literal |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-40 |
Lack of graphical example of multi-element Dependency Notation |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-39 |
Poor example of Dependency notation |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-41 |
Figure 7.15 |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-35 |
The containment between Activity and StructuredActivityNode has one end redefining and the other subsetting |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-34 |
UML 2: property redefinitions should be symmetric across associations |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-36 |
Subsetting clauses should show the subsetted property fully qualified. |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML23-145 |
Semantics of the AddVariableValueAction |
UML 2.2
|
UML 2.3b1
|
Resolved |
closed |
|
| UML24-15 |
Errros with some "subsets" and redefines" where the contexts of subsetting/redefintion do not conform |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-14 |
Attributes without a type |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-10 |
UML 2 Events referred to by OccurrenceSpecifications should be optional |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-13 |
Associations with same name that live in different packages violate unique name constraint |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-12 |
All enumertion literals in the model have their "classifier" collections empty |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-4 |
Constraint [3] on TestIdentityAction is incorrect |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-3 |
Constraint [1] for WriteStructuralFeatureAction is incorrect |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-7 |
UML2 - derivation for DeploymentTarget.deployedElement is invalid |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-6 |
UML2 - non-unique association names in L3.merged.cmof |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-11 |
Some owned operations with OCL expression bodies but without their "isQuery" set to "true" |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-8 |
UML2 - definition of Property.opposite is wrong |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-5 |
Parameter type of MultiplicityElement::includesMultiplicity() |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-9 |
UML2: Incomplete definition for Activity.structuredNode |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML23-143 |
What is "top-tier packages of the UML metamodel"? |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-125 |
Names of ownedEnds that were there in UML 2.1.1 are missing in UML 2.2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-127 |
notation of objet flow <> and <> |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-126 |
UML 2.3 draft, 11.3.1 - AcceptCallAction |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-124 |
Duplicate association in normative UML 2.3 superstructure file |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-123 |
Japan Infrastructure PAS Ballot Comments - comment 9 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-122 |
Japan Infrastructure PAS Ballot Comments - comment 8 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-118 |
Japan Infrastructure PAS Ballot Comments - comment 4 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-117 |
Japan Infrastructure PAS Ballot Comments - comment 3 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-114 |
Japan Superstructure PAS Ballot Comments - comment 20 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-113 |
Japan Superstructure PAS Ballot Comments - comment 19 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-121 |
Japan Infrastructure PAS Ballot Comments - comment 7 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-120 |
Japan Infrastructure PAS Ballot Comments - comment 6 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-116 |
Japan Infrastructure PAS Ballot Comments - comment 2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-119 |
Japan Infrastructure PAS Ballot Comments - comment 5 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-115 |
Japan Infrastructure PAS Ballot Comments - comment 1 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML241-12 |
UML type Real specification |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-11 |
Interface element - associations multiplicity not defined |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-9 |
Property::isID |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-6 |
Wrong package name on several Figures |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-10 |
Missing Namespace in Dependencies package definition? |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-3 |
typo on page 46 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML24-1 |
typo in new attribute name |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-2 |
CMOF missing several redefined property relationships |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML23-95 |
Setting Classes-Interfaces-Interface-ownedAttribute would fail to populate Classes-Kernel-Property-owner |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-94 |
Incorrect OCL in Infrastructure.xmi for 'Core-Constructs-Operation-isConsistentWith' |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-99 |
Japan Superstructure PAS Ballot Comments - comment 4 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-98 |
Japan Superstructure PAS Ballot Comments - comment 3 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-93 |
Language unit of Usage |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-92 |
Documentation of merge increments in the superstructure |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-97 |
Japan Superstructure PAS Ballot Comments - comment 2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-96 |
Japan Superstructure PAS Ballot Comments - comment 1 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML24-23 |
is composite, but does not subset ownedElement |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-22 |
wrong Actor's constraint [1]" |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-20 |
AcceptEventAction notation |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-19 |
Some associations in the normative XMI has one memberEnd |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-18 |
Namespace collission due to package import |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-17 |
Cycles in package imports |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-16 |
Errors with types of association ends not conforming to their subsetted ends |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-28 |
Unclear constraint on stereotype associations |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-26 |
remove BehavioredClassifier::ownedTrigger |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-25 |
lowered multiplicity |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-21 |
Issue on generalization |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-24 |
is composite and subsets not derived composite property: |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML24-27 |
UML is vague about which Element should own Comments |
UML 2.3
|
UML 2.4
|
Resolved |
closed |
|
| UML23-129 |
UML 2.3: Errors in example serialization for Profiles in Chapter 18 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-128 |
errors in OCL statements of Additional Operations? |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-132 |
Value of a Property |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-131 |
Interface-redefinedInterface should subset Classifier-redefinedClassifier |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-142 |
'false' is not a member of VisibilityKind |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-141 |
Guard of activity edge should be optional |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-140 |
Bug in Core::Abstractions::Super::Classifier::hasVisibilityOf |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-130 |
Ordered derived unions |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-135 |
Package Extension |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-134 |
Wrong Spelling for "development" |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-133 |
Cyclick dependency |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-138 |
Invalid type for NamedElement.namespace |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-137 |
Invalid type for Slot.value |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-139 |
Minor bug in Namespace::importMembers() query |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-136 |
Contents of Dependencies package |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-101 |
Japan Superstructure PAS Ballot Comments - comment 6 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-100 |
Japan Superstructure PAS Ballot Comments - comment 5 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-109 |
Japan Superstructure PAS Ballot Comments - comment 15 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-105 |
Japan Superstructure PAS Ballot Comments - comment 11 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-104 |
Japan Superstructure PAS Ballot Comments - comment 10 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-111 |
Japan Superstructure PAS Ballot Comments - comment 17 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-110 |
Japan Superstructure PAS Ballot Comments - comment 16 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-102 |
Japan Superstructure PAS Ballot Comments - comment 7 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-107 |
Japan Superstructure PAS Ballot Comments - comment 13 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-106 |
Japan Superstructure PAS Ballot Comments - comment 12 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-103 |
Japan Superstructure PAS Ballot Comments - comment 8 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-108 |
Japan Superstructure PAS Ballot Comments - comment 14 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-112 |
Japan Superstructure PAS Ballot Comments - comment 18 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML241-22 |
Irritating occurrence of subsystem stereotype in use case example diagrams |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-21 |
UML 2.4: NamedElement.ownedRule could be ordered |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-19 |
property.opposite |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-18 |
ProfileApplication::appliedProfile as "importedProfile" instead of "appliedProfile" |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-25 |
ChangeEvent::changeExpression should be of type ValueSpecification |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-24 |
Validity duration of implicitly assigned parameters in SignalEvent/CallEvent |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-17 |
XMI in small caps |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-16 |
Core Package versus Construct Package |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-20 |
UML Appendix A : Figure A.3 Two Diagrams of Packages |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-15 |
XML Metadata Interchange (XMI) - p9 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-14 |
XML Metadata Interchange (XMI) |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-23 |
Implicit parameter assignment may cause name clashes |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-13 |
Number of Compliance Levels |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-2 |
Presentation options of statemachine transitions: Figure 15.45 is ambiguous or wrong |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-1 |
Can a Generalization really be in multiple GeneralizationSets? |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-5 |
No Rules for Element Names |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-4 |
Figure 15.32 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-8 |
Figure 15.32 |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML241-7 |
Typo: "joint" should say "join" |
UML 2.4
|
UML 2.4.1
|
Resolved |
closed |
|
| UML22-1122 |
Diagram metaclass shall be introduced and shall be subclass of Element |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1121 |
Setting structural features of a data type |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1124 |
Figure 7.14: "Type" does not show its inheritance from "PackageableElement" |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1123 |
ConnectorEnd shall have references to provided or required interfaces |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1134 |
constraining Classifiers |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1129 |
Section: 9.3.11 p 182 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1127 |
Section: 9.3.8 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1136 |
Change multiplicity of ClassifierTemplateParameter role |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1135 |
Any ownedBehavior should be able to have AcceptEventAction |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1138 |
TimeEvent |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1137 |
Figure 14.5 - Messages. |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1140 |
Section: 7.3.7 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1139 |
Figures 9.4 identical to figure 9.3 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1120 |
Flowing data into decision input behaviors |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1119 |
Section: Composite Structures |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1107 |
issue regarding required and provided interfaces |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1106 |
UML 2: Semantics of isOrdered need to be clarified |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1118 |
Ptc/06-04-02/Pg 188 |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1117 |
Section: 7.3.32 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1116 |
A notation for Trigger |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1102 |
Section: Activities - Action semantic clarification |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1101 |
Section: Activities -StartClassifeirBehaviorAction and classifier behaviors |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1100 |
Section: Activities - isSingleExecution default |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1115 |
consistent descriptions of semantics of event consumption needed |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1114 |
section 13.3.2 doc ptc/2006-04-02, v.2.1 |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1113 |
Uses notation "Subsets Element::ownedElement" and similar |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1112 |
UML2: Behavior without a specification should not be a classifier behavior |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1109 |
Figure 13.8 shows the wrong diagram |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1108 |
Section: 13.3.25 |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1111 |
Section: 13 SimpleTime |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1110 |
Section: 13.2 |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1084 |
UML2: No notation for BehavioredClassifier::ownedTrigger |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1083 |
UML 2/Templates -- single argument? |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1082 |
Use the new 'dot' notation in examples |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1099 |
Section: Activities - Join node edge constraint |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1098 |
Section: Activities - Offer ordering on joins |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1097 |
Section: Activities - Multiple activity parameters nodes for a single inout |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1087 |
Section: 9.3.13 - connectors |
UML 2.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1096 |
Section: Activities - Semantics of fork node wording |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1095 |
ReadLinkAction |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1094 |
Section: Activities - Weight notation |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1093 |
Section: Activities - Weight description |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1092 |
Section: Activities |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1091 |
Section: 9.3.11 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1090 |
Section: 9.3.11 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1089 |
Section: 9.2 |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1086 |
Section: 13.3.24 Signal (from Communications) |
UML 2.1.1
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1085 |
page 467, Section 13.3.24 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML23-53 |
Figure 18.15 does not reflect the example before |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-52 |
The XMI document contains elements which should be |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-47 |
chapter 2.2, p.3 Last paragaph, second sentence |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-46 |
"Associations" part of the "9.10.3 Slot" chapter/section |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-44 |
In paragraph 4, the text should read "Class has a derived association ...". Currently, the sentence is missing "a". |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-43 |
In paragraph 2, the package reference to InfrastructureLibrary::Constructs::Class omits intermediate package "Core" |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-50 |
18.3.6 Typo in Profile section |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-49 |
Section: Fig. 7.15: subsets at wrong side |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-41 |
Figure 13.2 shows class InfrastructureLibrary::Profiles::Element. Section 13 doesn't define a class named Element. |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-42 |
Figure 13.2 shows an association between ProfileApplication and Profile that has role "appliedProfile |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-48 |
Section: Chapter 2.2 Compliance levels |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-45 |
In the Attributes section, "integer" should be capitalized |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-51 |
Section: 18.3.2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-23 |
UML 2.2 Profiles Issue: Stereotypes extending multiple metaclasses are ill-formed as metamodel equivalents |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-17 |
UML 2: conflicting specifications for how to calculate context for a Behavior |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-16 |
use of "internal" transition is used incorrectly in many places where "local" should be used. |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-18 |
default multiplicty of association ends are defined more than one |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-25 |
Section: 7.4 Diagrams text on page 144 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-24 |
UML 2.2 Beta1 Figure 12.18 is misleading about Parameter::effect : ParameterEffectKind [0..1] |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-28 |
Figure 12.95 - "Fork node example" |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-27 |
UML2 : Lifeline identity for InteractionUse |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-22 |
In the XMI, Ownerships::Element erroneously includes an association for ownedComment. |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-21 |
In the XMI, Ownerships::Element fails to include a superClass attribute for Elements::Element |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-20 |
Section: 9.8.3 XMI fails to include a "lower" attribute |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-19 |
The UML XMI fails to include an ownedRule for the Constraint specified for an OpaqueExpression |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-26 |
"Table 7.3 - Graphic paths included in structure diagrams" on pp.143-144 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-15 |
Statemachine diagram in section 15.3.12 diagram 15.42 (and the text above) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-88 |
Propagate RTF 2.3 changes to Infrastructure |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-87 |
Need to copy down merged content to make constraints parse in receiving package |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-86 |
Remove InputPint from StructuredActivities |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-85 |
BNF of Constructs::Property |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-84 |
Ambiguity in the names of the stereotypes in the standard profiles |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-91 |
The primitive types in the UML 2.3 infrastructure.xmi are private; they should be public |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-90 |
Difference between OCL and text in constraint [2] of 15.3.15 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-89 |
Remove redundantant constraint [2] in 7.3.4 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-73 |
UML 2.2 Issue - availability of PrimitiveTypes for UML models |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-72 |
lowerBound/upperBound constraints and derivations wrong |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-81 |
UML2: Missing semantics in definition of RedefinableTemplateSignature with multiple parents |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-80 |
remove StructuredActivities::ActivityGroup |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-83 |
Profile::allOwningPackages |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-82 |
Properties need not be owned |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-71 |
Operation-interface should subset Feature-featuringClassifier and NamedElement-namespace |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-70 |
UML2.2 chapter 16 : Actor constraint [1] has invalid OCL |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-76 |
UML2: error in definition of Class::nestedClassifier |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-75 |
confusion re diagram on p. 83 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-79 |
Currently is it possible for a Classifier to specialize the same classifier directly more than once |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-77 |
nestedClassifier |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-74 |
Section 9.9 should classifier be added to the diagram on p 50? |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-78 |
type mismatch |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-32 |
Section 12.3.48 on page 412 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-34 |
Figure 7.1 shows no dependency |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-33 |
Section 2.3 para 1 needs to be re-written |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-40 |
Section 13 "Core::Profiles" inconsistency |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-39 |
Should the definition of Element state that it reuses the definition of Element from Abstractions::Elements? |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-37 |
The "Generalizations" heading is missing before the "ValueSpecification" bullet. |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-36 |
Paragraph 5: The text states that class Comment has no generalizations |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-31 |
UML 2 7.3.3 : incorrect text about aggregationKind in associations |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-29 |
Table 12.1 - "Graphic nodes included in activity diagrams", |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-30 |
Generalizations" for StructuredActivityNode on p. 417 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-38 |
Two issues regarding Figure 10.2: 1 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-35 |
Parameter is part of the BehavioralFeatures package. |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-65 |
Validator issues with TestCase 2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-64 |
current definition of a 'local' transition does not allow the case to have a local transition |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-59 |
Figures 9.17 and 9.19 and related text |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-58 |
what's the difference > between weight=1 and weight=*? |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-63 |
Clarify that input pins do not accept more tokens than their actions can immediately consume |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-62 |
The OCL for /required interfaces of Component is using ports.provided instead of ports.required |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-67 |
Clarification need on circle plus notation for containment |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-66 |
Color errors on figures in UML 2.2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-69 |
Figure 7.38 needs to be revised |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-68 |
Activity groups should be named |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-57 |
Table 2.2 Example feature support statement references Note (4) and Note (5) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-56 |
Description of Level 1 diagram does not make sense with respect to figure 2.2 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-61 |
Clarify how the provided and required interfaces of a Port are calculated |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-60 |
Missing keyword? |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-54 |
Replace "extensionClock" with "extension_Clock" and "baseClass" with "base_Class" |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-55 |
URIs do not refer to existing resources (404 errors) Annex H |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-14 |
Section: 14.3.13 Interaction (from BasicInteraction, Fragments) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-13 |
Notation for ExecutionSpecification |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-6 |
Section: 7.3.39 PackageImport (from Kernel) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-5 |
Section: 7.3.12 Dependency (from Dependencies) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-11 |
Val(MyCar.Interaction [SVWB |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-10 |
Section: 12.3.14 Figure 12.29 on page 320 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-8 |
Section: 14.3.24 MessageSort (from BasicInteractions) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-7 |
Section: 14.3.3 CombinedFragment (from Fragments) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-9 |
"description" section of the Behavior metaclass |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-2 |
Parameter isn't package (Heading 2 level) |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-1 |
Super package should import NamedElement from the Visibilities package, not Namespaces |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-12 |
description of Interaction provided by the Semantic section inconsistent |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-4 |
Section: 14.3.20 Actors in Interactions |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML23-3 |
Figure 9.20 |
UML 2.2
|
UML 2.3
|
Resolved |
closed |
|
| UML22-1081 |
UML 2 Superstructure / CommonBehaviors / Incorrect types in text |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1080 |
7.3.41 Parameter (from Kernel, AssociationClasses)" |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1063 |
UML 2.0 issue: ownedMember xsi:type="uml:Stereotype" should be used |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1062 |
UML 2.0: CMOF/UML mixup for profiles |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1069 |
Required attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1068 |
Parameter::effect |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1065 |
UML 2.1 XMI Issue |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1064 |
UML 2.0: Inconsistencies in profile example XMI |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1073 |
parameter of operation isRedefinitionContextValid() is inconistently named |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1072 |
Compliance package L2 does not merge StructuredActions in the metamodel |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1071 |
The following properties should not subset DirectedRelationship::target |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1070 |
The following properties should not subset DirectedRelationship::source |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1067 |
Artifact::fileName |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1066 |
uml::Extension::ownedEnd should not subset uml::Association::ownedEnd |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1079 |
Figure 12.18: Small typo: "subsets ownedMember" not "ownedmember" |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1078 |
Page: 161 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1075 |
Issue regarding "Action::effect : String" |
UML 1.3
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1074 |
Transition guards cannot currently be evaluated because they have no contex |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1077 |
StateMachine::extendedStateMachine should have a multiplicity of 0..*. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1076 |
Behavior::context |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1058 |
UML 2.0 issue: Package Primitive Types not merged |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1057 |
Section: Appendix A: Diagrams |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1056 |
Section 7.2.1 of ptc/04-10-14 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1055 |
Section: 7.3.36 Operation |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1054 |
Section 8 Issue - Component Realization-Classifier multiplicity |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1053 |
Section: Actions, Figure 156 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1052 |
UML 2.1 Regressions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1051 |
Realization classifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1050 |
UML 2 issue: redefining isComposite on association ends |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1049 |
Classifier::parameter, Operation::parameter, and ConnectableElement::parame |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1048 |
Component::realization should NOT be derived |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1047 |
Rename ActivityGroup::activity to containingActivity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1046 |
Rename OpaqueAction::output to outputPin. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1045 |
Make ActivityGroup::containedNode a derived union |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1044 |
Make ActivityGroup::containedEdge a derived union |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1039 |
compliance levels L2 and L3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1038 |
Change type of WriteStructuralFeatureAction::value to ValueSpecification |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1037 |
Change type of WriteStructuralFeatureAction::value |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1061 |
UML 2.0: separate profile application from profile importing |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1060 |
UML 2.0: invalid package merge diagrams for compliance points |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1059 |
UML 2.0 issue: Profile::ownedStereotype should be derived |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1043 |
Rename LinkAction::input to inputPin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1042 |
Rename OpaqueAction::input to inputPin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1041 |
Rename InformationFlow::source |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1040 |
Rename InformationFlow::target |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1036 |
Rename ActivityPartition::subgroup to subpartition |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1035 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1034 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1033 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1026 |
body expression for Property::isConsistentWith(RedefinableElement) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1025 |
following imports from merged packages to unmerged packages should be remov |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1024 |
UML2 Superstructure Fig 2.2 Incomplete |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1023 |
Section: 14.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1020 |
Section: Common Behaviors |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1019 |
Section: Actions |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1022 |
7.3.22 InstanceSpecification |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1021 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1018 |
Section: Classes |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1017 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1016 |
Invalid stereotype in StandardProfile |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1015 |
UML 2 Super / miscellaneous figure-text discrepancies |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1028 |
Rename Package::ownedMember |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1027 |
Rename Constraint::namespace |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1030 |
Rename ActivityEdge::redefinedElement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1029 |
Rename Component::ownedMember |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1032 |
Replace {redefines redefinedElement} |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1031 |
Rename ActivityNode::redefinedElement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1012 |
Section: 6.5 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1011 |
UML2 should specify default property ownership for association ends |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1002 |
Figure 430 references invalid metaclass |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1001 |
Section: 9.3.5 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1006 |
UML2 Navigability Impact on Tools |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1005 |
UML 2 XMI DTD requirement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-998 |
UML2 issue: {unrestricted} described in text but not BNF |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-997 |
UML Superstructure / Actions / Missing package heading |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1010 |
UML 2 Super / Undocumented properties |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1009 |
Page: 591,592 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1008 |
Core::Constructs::Operation |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1007 |
Interaction::lifeline should be ordered |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-1004 |
UML 2 Classes Notation for association end ownership |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1003 |
connection point reference |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1014 |
UML 2 Super / Collaboration use issues (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1013 |
UML 2 Super / Collaboration use issues (01) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-1000 |
Section: 12.3.18 and 12.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-999 |
Section: 15.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-994 |
Section: 12.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-993 |
Page: 163 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-989 |
Section: 12.3.37 ObjectFlow |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-996 |
UML Superstructure / Actions / incorrect form for subsetting |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-995 |
Section: 12.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-990 |
OpaqueAction |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-975 |
ExecutableNode should be abstract in Figure 195. It is in Figure 197. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-979 |
Section: 12 and 13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-971 |
Page: 330 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-970 |
Section: 11.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-969 |
Section: Actions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-974 |
Actions should be able to overlap partitions, to support multiple participa |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-973 |
Section: 8.3.1 Page: 156 ff |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-965 |
Page: 591 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-961 |
Clarify caption of Figure 56 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-960 |
Section: Interactions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-953 |
Clarify first constraint on InputPin and OutputPin, move "only" to before " |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-952 |
LoopNode should move rather than copy values to/from loop variables |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-951 |
In Figure 210, put merge before Use Part to merge the incoming flows |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-950 |
Exceptions thrown across synchronous invocations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-949 |
Multiple exception handlers |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-955 |
Actions, CallBehaviorAction, third sentence, |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-954 |
The Syle Guidelines for Stereotype |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-959 |
CollaborationUse: Constraint 1, |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-958 |
ConditionalNode and LoopNode test and bodies should be ExecutableNodes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-957 |
ExpansionRegion |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-956 |
ControlFlow |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-964 |
Last element in transition BNF |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-962 |
Notation for connector end multiplicities. |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-963 |
ParameterSet, first line: "inputs *or* outputs". |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-942 |
In Activities, Figure 176, Action should be abstract |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-935 |
Section: 12 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-934 |
token |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-944 |
String is primitive but has structure. |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-937 |
``conditional node or conditional node'' delete one. |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-936 |
add the rule of ``natural termination'' |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-948 |
Solid triange notation for Association |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-947 |
The create stereotype on Usage dependency |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-939 |
Section: 12.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-938 |
Delete sentence |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-946 |
Element to Constraint navigation |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-945 |
Disjointness should be independent of generalization |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-943 |
Semantics for instances applies to InstanceSpecification? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-933 |
UML 2 -- Need explanations of XMI structure and usage |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-932 |
token movement |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-931 |
output tokens (02) |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-927 |
Section: 12 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-926 |
Section: Appendix F |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-925 |
Section: E.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-930 |
text p.297 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-929 |
Section 12 (03) |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-928 |
Section 12 (02) |
UML 1.4.2
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-920 |
Section: Appendix C Table 27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-919 |
Section: Appendix C Table 26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-922 |
Section: D.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-921 |
Section: 15.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-924 |
Section: D.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-923 |
Section: D.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-915 |
Section: 18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-914 |
Section: 18.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-913 |
Section: 18.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-918 |
Section: Appendix C Table 25 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-917 |
Section: Appendix B (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-916 |
Section: Appendix B |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-912 |
Section: 18.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-911 |
Section: 18.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-910 |
Section: 18.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-909 |
Section: 18.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-908 |
Section: 18.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-893 |
Section: 17.5.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-892 |
Section: 17.5.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-891 |
Section: 17.5.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-895 |
Section: 17.5.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-894 |
Section: 17.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-901 |
Section: 17.5.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-900 |
Section: 17.5.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-897 |
Section: 17.5.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-896 |
Section: 17.5.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-907 |
Section: 18.1.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-906 |
Section: 17.5.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-899 |
Section: 12 Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-898 |
Section: 17.5.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-903 |
Section: 17.5.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-902 |
Section: 17.5.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-905 |
Section: 17.5.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-904 |
Section: 17.5.18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-883 |
Section: 17.2.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-882 |
Section: 17.2.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-872 |
Expansion region description |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-871 |
ExpansionRegioin example, Figure 261: concurrent => parallel |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-870 |
Section: Activities, ExpansionRegion (05) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-879 |
mustIsolate: |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-878 |
No notation |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-875 |
Semantics of isAssured/isDeterminant in conditional node |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-874 |
Add constraint in LoopNode |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-873 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-890 |
Section: 17.5.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-889 |
Section: 17.5.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-888 |
Section: 17.5.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-885 |
Section: 17.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-884 |
Section: 17.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-887 |
Section: 17.5.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-886 |
Section: 17.5.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-881 |
Clarify the semantics of minimum multiplicity > 0 for streaming parameters |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-880 |
Figure 209 of Activites |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-877 |
Add constraints on conditional and loop nodes (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-876 |
Add constraints on conditional and loop nodes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-853 |
UML 2 Super / Conformance / inconsistencies |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-852 |
UML 2 Super / General / missing merges |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-851 |
UML 2 Super / General / improper subsetting |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-855 |
UML 2 Super / General / invalid subset rule too strict |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-854 |
UML 2 Super / Kernel / excessive restriction on redefinition |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-861 |
Section: 14.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-860 |
Section: 16.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-869 |
Section: Activities, ExpansionRegion (04) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-868 |
Section: Activities, ExpansionRegion (03) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-867 |
Section: Activities, ExpansionRegion (02) |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-859 |
Section: 16.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-858 |
Section: 16.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-857 |
Section: 16.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-856 |
UML 2 Super / Common Behaviors / missing multiplicites |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-866 |
Section: Activities, ExpansionRegion |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-865 |
Section: Activities |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-864 |
ValueSpecificationAction, Attribute section, is missing the return pin |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-863 |
Section: Actions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-862 |
Section: Common Behavior |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-841 |
Section: 15.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-840 |
Section: Appendix A |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-837 |
Section: 15.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-836 |
Section: 15.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-835 |
Action Semantics Section: 9.5 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-839 |
Appendix C.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-838 |
Section: 15.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-834 |
Specification: Action Semantics Section: 9.5 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-833 |
Section: 15.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-832 |
Section: 15.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-843 |
Section: 15.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-842 |
Section: 15.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-850 |
UML 2 Super / Collaborations / improper subset |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-849 |
Profiles::ObjectNode has wrong default multiplicity |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-848 |
Profiles::ExtensionEnd has wrong default multiplicity |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-845 |
Should Profiles::Image be an Element? |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-844 |
Section: 15.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-847 |
Remove redundant superclass for Element |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-846 |
OCL for Property::opposite() is incorrect: |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-831 |
Section: 15.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-830 |
Section: 15.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-817 |
Section: 14.3.26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-816 |
Section: 14.3.25 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-823 |
Section: 15.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-822 |
Section: 8.3.1 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-829 |
Section: 15.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-828 |
Section: 11.3.42 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-812 |
Section: 14.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-811 |
Section: 14.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-815 |
Section: 14.3.24 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-814 |
Section: 14.3.21 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-813 |
Section: 14.3.21 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-827 |
Section: 15.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-826 |
Section: 15.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-819 |
Section: 14.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-818 |
Section: 14.3.29 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-821 |
Section: 12.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-820 |
Section: 11.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-825 |
Section: 15.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-824 |
Section: 15.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-810 |
Section: 14.3.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-809 |
Section: 14.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-808 |
Section: 14.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-797 |
Section: 14.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-796 |
Section: 13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-795 |
Section: 13.3.30 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-807 |
Section: 14.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-806 |
Section: 14.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-799 |
Section: 14.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-798 |
Section: 14.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-803 |
Section: 14.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-802 |
Section: 14.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-801 |
Section: 14.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-800 |
Section: 14.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-794 |
Section: 13.3.29 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-793 |
Section: 13.3.28 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-792 |
Section: 13.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-805 |
Section: 14.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-804 |
Section: 14.3.3 & 14.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-791 |
Section: 13.3.26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-790 |
Section: 13.3.24 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-776 |
Section: 13.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-775 |
Section: 13.3.2 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-784 |
Section: 13.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-783 |
Section: 13.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-778 |
Section: 13.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-780 |
Section: 13.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-779 |
Section: 13.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-789 |
Section: 13.3.23 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-788 |
Section: 13.3.22 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-782 |
Section: 13.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-781 |
Section: 13.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-786 |
Section: 13.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-785 |
Section: 13.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-787 |
Section: 13.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-777 |
Section: 7.3.36 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-755 |
Section: 12.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-754 |
Section: 12.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-753 |
Section: 12.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-767 |
Section: 11.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-766 |
Section: 12.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-771 |
Section: 12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-770 |
Section: 12.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-758 |
Section: 12.3.38 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-757 |
Section: 12.3.37 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-756 |
Profiles:Extension End |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-765 |
Section: 12.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-764 |
Section: 12.3.47 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-763 |
UML 2 super/templates/ |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-760 |
Section: 12.3.43 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-759 |
Section: 12.3.41 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-774 |
Section: 12.3.49 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-773 |
Section: 12.3.46 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-772 |
Section: 13.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-762 |
UML 2 Super/templates/inexplicable constraint on defaults |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-761 |
Section: 12.3.44 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-769 |
Section: 12.3.51 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-768 |
Section: 12.3.50 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-752 |
Section: 12.3.34 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-751 |
Section: 12.3.33 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-738 |
Section: 12.3.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-737 |
Section: 12.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-736 |
Section: 12.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-735 |
Section: 12.3.14 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-731 |
MultiplicityElement BNF too restrictive |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-730 |
Section: 12.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-741 |
Section: 12.3.6 & 12.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-740 |
Section: 12.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-739 |
Section: 12.3.18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-746 |
Section: 12.3.28 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-745 |
Section: 12.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-744 |
Section: 12.3.23 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-734 |
Used of "Redefines ...from Abstractions" in descriptions is misleading |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-733 |
BNF Notation for Operation is too restrictive |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-732 |
Incomplete BNF for Property |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-743 |
Section: 12.3.24 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-742 |
Section: 12.3.22 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-748 |
Section: 12.3.38 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-747 |
Section: 12.3.30 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-750 |
Section: 12.3.32 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-749 |
Section: 12.3.31 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-729 |
Section: 12.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-728 |
Section: 12.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-727 |
Section: 12.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-726 |
Section: 12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-725 |
Section: 12.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-716 |
Section: 12.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-715 |
Section: 12.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-714 |
Section: 12.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-721 |
Section: 12.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-720 |
Section: 12.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-719 |
Section: 12.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-683 |
Section: 11.3.25 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-682 |
Section: 11.3.24 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-629 |
Section: 7.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-631 |
Section: 8.3.1 - typo |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-630 |
Section: 8.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-628 |
Section: 7.3.34 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-627 |
Section: 7.3.33 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-637 |
Section: 9.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-636 |
Section: 9.3.3 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-635 |
Section: 9.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-632 |
Section: 8.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-633 |
Section: 9.20.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-634 |
Section: 9.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-638 |
Section: 9.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-561 |
InfrastructureLibrary defines, but should not use package merge |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-557 |
section 2.10.4.1 detailed semantics of collaborations |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-554 |
Section: 7.3.43 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-559 |
Interactions |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-558 |
Section: 7.3.44 - OCL incorrect |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-555 |
Section: 7.2.8 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-560 |
UML 2 Super Basic Interactions |
UML 1.4.2
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-562 |
An observed time value must be written into a structural feature |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-556 |
Classes |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-691 |
Section: 11.3.34 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-690 |
Section: 11.3.33 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-689 |
Section: 11.3.31 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-684 |
Section: 11.3.26 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-694 |
Section: 11.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-693 |
Section: 11.3.36 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-686 |
Section: 11.3.28 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-687 |
Section: 11.3.29 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-692 |
Section: 11.3.35 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-688 |
Section: 11.3.30 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-685 |
Section: 11.3.27 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-588 |
Optional inputs |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-587 |
Preserve order in result of read actions |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-582 |
Interactions chapter refers to ActivityInvocations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-583 |
Destruction semantics in StructuredClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-585 |
Figure 119 missing multiplicity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-584 |
Link maintenance in StructuredClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-591 |
ObjectNode, constraint 1 In ObjectNode |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-590 |
DestroyObjectAction semantics |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-589 |
IsReadOnly constriant |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-586 |
Notation for method |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-659 |
Section: 11.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-658 |
Section: 11.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-621 |
Section: 7.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-620 |
Section: 7.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-626 |
Section: 7.3.32 Page: 96-99 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-625 |
Section: 7.3.32 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-624 |
Section: 7.3.22 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-616 |
Section: 6.5.1: Error in example |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-619 |
Section: 7.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-622 |
Section: 7.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-618 |
Section: 7.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-623 |
Stereotypes applying in UML 2.0 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-617 |
Section: 7.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-678 |
Section: 11.3.20 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-677 |
Section: 11.3.19 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-680 |
Section: 11.3.22 -- significant revision? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-679 |
Section: 11.3.21 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-696 |
Section: 11.3.40 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-695 |
Section: 11.3.38 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-681 |
Section: 11.3.23 -- significant revision? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-672 |
Section: 11.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-676 |
Section: 11.3.18 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-674 |
Section: 11.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-675 |
Section: 11.3.17 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-673 |
Section: 11.3.15 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-709 |
Section: 11.3.53 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-708 |
Section: 11.3.42 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-698 |
Section: 11.3.43 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-697 |
Section: 11.3.41 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-660 |
Section: 11.3.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-667 |
Section: 11.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-666 |
Section: 11.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-670 |
Section: 11.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-669 |
Section: 11.3.11 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-668 |
Section: 11.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-664 |
Section: 11.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-665 |
Section: 11.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-663 |
Section: 11.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-671 |
Section: 11.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-579 |
Connector multiplicity notation |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-578 |
Associations between interfaces |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-580 |
create dependency Figures 103 and 121 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-573 |
Transitivity in composition |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-581 |
underlined association name |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-577 |
Section: Classes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-572 |
Add concept "StateInvariant" |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-574 |
Pin/parameter matching constraints |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-576 |
Section: Classes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-575 |
Section: CB/ACT |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-723 |
Section: 12.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-722 |
Section: 12.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-641 |
Section: 8.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-640 |
Section: 9.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-647 |
Section: 10.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-648 |
Section: 10.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-644 |
Section: 12.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-645 |
Section: 12.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-643 |
Section: 9.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-639 |
Section: 9.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-646 |
Section: 9.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-642 |
Section: 9.3.12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-615 |
Section: 7.4.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-614 |
Section: 7.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-610 |
Section: 11.8.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-609 |
Section: 11.6.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-613 |
Section: 7.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-612 |
Section: 13.1.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-607 |
Section: 11.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-606 |
search for referenced item -- Section: 11.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-603 |
Figure 68 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-602 |
methods not defined under attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-611 |
Section: 13.1.2 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-605 |
Section: 11.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-604 |
Section: 11.3.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-608 |
Actor is a specialized Classifier and not BehavioredClassifier |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-711 |
Section: 12.1 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-710 |
Section: 11.3.54 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-713 |
{redefined } should be named {redefines } |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-712 |
Property string {bag} is redundant |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-718 |
Section: 12.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-717 |
Section: 12.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-703 |
Section: 11.3.48 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-701 |
Section: 11.3.46 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-700 |
Section: 11.3.45 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-707 |
Section: 11.3.52 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-706 |
Section: 11.3.51 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-705 |
Section: 11.3.50 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-699 |
Section: 11.3.44 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-704 |
Section: 11.3.49 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-702 |
Section: 11.3.47 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-596 |
unclear statement |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-595 |
Text references Figure 8 and the correct figure number is 6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-599 |
Section is badly worded and does not make a lot of sense |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-598 |
clarify what a directed association is |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-593 |
Terminology Issue |
UML 1.4.2
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-600 |
typing error in the statement :unrestricted ? |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-597 |
extra word in the last sentence of the paragraph under Attributes |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-594 |
section 9.20.2 VisibilityKind lists two types of visibility |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-592 |
StructuredActivityNode specialized multiplicity |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-601 |
What happened to real numbers |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-724 |
Section: 12 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-662 |
Section: 11.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-661 |
Section: 11.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-655 |
Section: 10.3.10 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-654 |
Section: 10.3.9 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-657 |
Section: 10.4 |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-652 |
Section: 10.3.6 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-656 |
Section: 10.3.11 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-650 |
Section: 10.3.4 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-653 |
Section: 10.3.8 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-649 |
Section: 10.3.3 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-651 |
Section: 10.3.5 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-565 |
ReduceAction |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-564 |
UML 2 Super / Incorrect statement on port visibility |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-566 |
Section: 14.3.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-563 |
Minor error in BNF of an message argument |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-568 |
Section: 14.3.14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-569 |
Section: 14.3.16 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-571 |
StateInvariants/Continuations |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-570 |
Section: Table 14 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-567 |
Section: 14.3.13 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-553 |
DataType attributes UML 2 Super (ptc/04-10-02) |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-458 |
UML 2.2 superstructure section 9.3.11 page 184: Port.isService |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-456 |
Could you please clarify what does the UML2 specifications intend for "provided port" and "required port"? |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-455 |
Inconsistency in Superstructure 2.2 p. 550 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-454 |
InstanceSpecifications |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-453 |
specificMachine association should be changed to be type StateMachine |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-452 |
p269-p270 Constraint |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-451 |
operation allConnections |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-450 |
TYPO p.54 Additional Operations |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-446 |
Classifier has association end "attribute" |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-445 |
Typo 9.3.13 p190 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-449 |
Metaclass Property is denoted in Interfaces Package on p.36 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-448 |
7.3.33 p100 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-447 |
Property 7.3.44 p125 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-444 |
7.3.44 additional operation P128 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-399 |
first paragraph of section 7.8 UML kernel |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-398 |
Section: 7.3.7 and 8.3.1 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-401 |
Port |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-400 |
Section 14 Interaction |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-389 |
Section: 15.3.11/Notation |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-388 |
Section 11.3.25 gives the definition of MultiplicityExpression::isConsisten |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-396 |
interpreting InstanceSpecification |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-395 |
Figure showing an AssociationClass as a ternary association |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-391 |
Section: 7.3.10/Associations |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-390 |
Section: 13.3.3/ Changes from previous UML |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-394 |
Car dependency example |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-393 |
Section: 12.3.8/Generalizations |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-387 |
qualifiers |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-397 |
Section: 15 StateMachines: doActivity and internal transitions |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-392 |
Section: 7.3.10/Associations - insert reference |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-432 |
Unspecified constraint [1] on ActivityNode |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-431 |
constraint [4] on AcceptEventAction and unordered result:OutputPin property |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-434 |
figure 13.12 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-433 |
Unspecified constraint [1] on ActivityNode (StructuredActivities) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-436 |
Clarification on use of Profiles. |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-435 |
Property Additional Operations, page 127. |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-443 |
7.3.44 Property P128 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-442 |
18.3.8 Stereotype |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-430 |
Unspecified constraint [3] on Activity |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-440 |
Typo P205 10.3.4 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-439 |
On the table 2.3, page 8 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-438 |
On the communication diagram in Fig 6.2 (second issue) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-437 |
On the communication diagram in Fig 6.2 (P12) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-441 |
7.3.11 DataType, P61 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-383 |
UML 2.1.2:18.3.5 Package (from Profiles) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-382 |
UML Super 2.1.2:Feature |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-384 |
A final node that returns to the caller but leaves alive any parallel flow |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-380 |
section '10.3.12 Property (from Nodes)' |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-379 |
PackageableElement (from Kernel), subsection: "Attribute" |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-386 |
CMOF file for UML2 does not have derived Associations marked as such |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-385 |
Section: 8.3.3 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-378 |
description of MessageOccurenceSpecification |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-377 |
The list of literal described for the ennumeration MessageSort is not compl |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-381 |
undefined term 'Element::redefinedElement' occurs three times in standard |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-419 |
Section: 7.4 figure 7.1 missing dependency |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-418 |
UML2: Need a better mechanism for integrating UML2 Profiles |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-421 |
Regression in XMI from UML 2.1.2 to UML 2.2 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-420 |
Section: 2.2-2.4 compliance level clarifiction needed |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-424 |
Unspecified constraint [1] on AcceptEventAction |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-423 |
Incorrect OCL expression for constraint [1] on BehavioredClassifier |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-415 |
OCL 2.0 8.2 Real |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-414 |
UML2 issue regarding RedefinableTemplateSignature |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-427 |
Unspecified constraint [1] on ActivityEdge (CompleteStructuredActivities) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-426 |
Unspecified constraint [2] on ActivityEdge |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-429 |
Unspecified constraint [2] on Activity |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-428 |
Unspecified constraint [1 on Activity |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-417 |
Section 7.3.50 "substitution" |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-416 |
Keyword ambiguity for DataType Section |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-425 |
Unspecified constraint [1] on ActivityEdge |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-422 |
Section: 9.3.8 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-406 |
Section 10.3.10 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-405 |
definition of RedefinableElement::isLeaf |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-404 |
Behavior's parameter list |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-403 |
PackageMerge relationships |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-413 |
Section: 7.3.36 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-412 |
Section: 11.3.30,12.3.23 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-410 |
Section: 13.3.3 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-411 |
Section: 12.2 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-408 |
The behavior of an OpaqueExpression should itself be opaque |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-409 |
Section: 13.3.23 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-402 |
Classifiers |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-407 |
Section: 7.3.35 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-468 |
Packaging Issues with Stereotype Extension |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-467 |
inconsistency with how constraints are specified in UML and OCL |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-470 |
Allowing multiple Associations in a Package with the same name |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-469 |
P479L.14 Section "Notation" in 14.3.10 ExecutionOccurences - Typo |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-472 |
Figure 18.2 (which describes the contents of the Profiles package) is currently misleading |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-466 |
ParameterableElement as a formal template parameter |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-465 |
UML. Clarify relationship of Substitution and InterfaceRealization |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-462 |
UML2 section 8.3.1 OCL derivations on Component.provided and Component.required are still invalid |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-464 |
transitionkind Constraints |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-463 |
UML 2.2 figure 8.10 has arrows the wrong way around |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-461 |
UML2.2 Section 9.3.1 Presentation Options section |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-460 |
UML 2.2 Section 9.3.1 nested classes paragrpah in wrong chapter |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-471 |
Figure 2.2 contains more than four packages, description referes to four packages |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-535 |
Figure 78 |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-532 |
Class InfrastructureLibrary::Core::Basic::Property |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-531 |
In 2.13.3, the first sub-section about ActivityGraph is not numbered |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-529 |
missing closing parenthesis |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-528 |
The Composition section does not follow the usual conventions |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-526 |
In "2.9.3.5 Instance", numbering of different well-formedness rules wrong |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-525 |
The numbering of the sub-sections in 2.7.2 is wrong |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-523 |
Associations section of element JumpHandler |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-522 |
Remove one of the dots between protectedAction and availableOutput |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-524 |
UML 2.0 infra and super Constraints Diagram of the Kernel |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-527 |
The section about Procedure does not contain any well-formedness rules |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-530 |
At the bottom of the page, the characters "antics." should be removed |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-549 |
Inconsistent use of 'Element' between MOF and UML |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-548 |
Missing XMI tags in spec and XMI rendition of metamodel |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-504 |
ptc-03-09-15/Constructs::Class superClass property |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-503 |
ptc-03-09-15/Non-navigable ends with no role names nor multiplicities |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-502 |
UML 2 Issue: Message notation |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-508 |
Why not using the UML1 activity symbol for UML2 actions? |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-507 |
Multiplicity seems to be broken - UML2 Infra & Super |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-499 |
UML 2 Super / Dependency / ownership of dependencies |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-498 |
Clarification of Information Flow semantics |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-497 |
Activity diagram problems |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-490 |
UML 2 Infra/Metamodel::Constructs/invalid OCL constraint for "opposite" |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-489 |
UML 2 Super/Metamodel::Kernel/missing merges |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-488 |
UML 2 Super/Package merge/redefinitions issue - lost association ends |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-487 |
UML 2 Super/Metamodel::Super/missing merge |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-493 |
raisedException |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-492 |
UML 2 Super / Templates / TemplateParameter not named |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-491 |
UML 2 Super/pg.75/kinds of changeability |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-496 |
Section 9.3.4 page 161, Presentation Option |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-495 |
UML 2 Super / Kernel features / cannot exclude superclass properties |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-494 |
Syntax of names |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-501 |
UML 2 Issue: definition of navigability |
UML 1.5
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-500 |
Use 'represent' for the relationship of a model |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-506 |
Rose Model of UML 2.0 spec |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-505 |
ptc-03-09-15/Relationships among Core packages |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-547 |
Move Comment into Basic and add Kind |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-546 |
Unconsistent Profile extension description (02) |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-545 |
Unconsistent association extension description |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-538 |
Section 11.7 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-537 |
simple time model" in CommonBehavior |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-551 |
Problem with diagram references in Profiles section |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-550 |
Design principles |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-544 |
The specification is fond of using 'typically.' |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-543 |
TimeObservationAction and DurationObservationAction |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-541 |
add an interaction fragment |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-540 |
Interactions model sequences of events |
UML 2.0
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-539 |
Clarify example in figure 133 |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-552 |
DataType attributes UML 2 Super (ptc/04-10-02) |
UML 1.4.2
|
UML 2.1
|
Resolved |
closed |
|
| UML22-486 |
UML 2 Super/Metamodel::Constructs/owningComment |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-485 |
Classes diagram of the Core::Constructs package |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-484 |
cross-reference missing |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-483 |
Relationship and DirectedRelationship in Core::Constructs |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-482 |
document appears to be inconsistent in how it handles concepts |
UML 2.0
|
UML 2.1
|
Resolved |
closed |
|
| UML22-477 |
Designates a Generalization |
UML 1.4
|
UML 2.1
|
Resolved |
closed |
|
| UML22-476 |
Namespace issue (UML 1.4 formal/2002-09-67, 2.5.3.26 Namespace ) |
UML 1.4
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-481 |
relationship should just be a cross-reference |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-480 |
formal/03-03-01 : Omission of definition of Class "Action" |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-473 |
Specify XMI parameters for the UML / XMI interchange format |
UML 1.3
|
UML 2.1
|
Resolved |
closed |
|
| UML22-479 |
logic upperbound is the same as the lower bound. |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-478 |
2.5.2.27 ModelElement |
UML 1.4
|
UML 2.1
|
Resolved |
closed |
|
| UML22-511 |
UML 2 Super / Classes / dependencies should be unidirectional |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-510 |
two classes "NamedElement |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-515 |
well-formedness rules are not numbered correctly |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-514 |
number of the figure is wrong |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-519 |
In the last paragraph, the period after the word "collections" on the secon |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-518 |
In paragraph 5, the addition of 2, 5, 7 and -3 does not yield 9 but 11 |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-517 |
The multiplicity of association named subaction of type Action ill formed |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-521 |
Operations and derived attributes |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-509 |
class "InfrastructureLibrary.core.constructs.Association", |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-513 |
remove paragraph |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-512 |
UML 2 Infra/Metamodel/missing derivation indicators |
UML 1.5
|
UML 2.1.2
|
Resolved |
closed |
|
| UML22-516 |
multiplicity of the association named "type" of type DataType |
UML 1.5
|
UML 2.1
|
Resolved |
closed |
|
| UML22-327 |
Behaviors Owned by State Machines |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-326 |
Section: 12.3.41 Streaming parameters for actions |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-316 |
Section: 13.3.24 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-315 |
Section: 15.3.14 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-321 |
Wrong subsets |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-320 |
Section: 15.3.11 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-328 |
information flow source and target |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-318 |
description of 14.3.24 MessageSort (from BasicInteractions) - typo |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-317 |
drawing a frame to represent Combined Fragment or an Interaction Occurrence |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-325 |
Section: 14 Interactions: Lifeline representing an actor |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-324 |
Section: 9 Composite Structures / Port notation |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-323 |
Section: 16.3.2 Classifier (from UseCases) |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-322 |
Section 18.3.1 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-247 |
Section: Common Behavior - isReentrant should default to true |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-246 |
Actions on non-unique properties with location specified |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-243 |
Section: Actions - Output of read actions for no values |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-242 |
Section: Actions - InputPin semantics wording |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-245 |
Section: Activities - Output pin semantics clarification |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-244 |
Section: Activities - ForkNode semantics wording |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-241 |
Section: Activities - Preserving order of multiple tokens offered. |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-250 |
Bad cross reference for InterfaceRealization Notation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-249 |
PrimitiveTypes access by UML (M1) models |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-253 |
Unclear which Property has aggregation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-252 |
Move Property::isId from MOF to UML |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-248 |
Notation for stereotypes on Comments and other elements |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-251 |
text-diagram out of synch in Infrastructure 11.4.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-254 |
Clarify isRequired |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-375 |
definition of 'isCompatibleWith' for ValueSpecification |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-374 |
formal definitions of 'isCompatibleWith' (pages 622, 647, 649) |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-373 |
association 'ownedTemplateSignature' of a Classifier |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-376 |
term 'templatedElement' not defined |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-309 |
Usage of "Element::ownedMember" |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-308 |
Consistency in description of ends owned by associations |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-306 |
Section: 12.3.30 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-312 |
Section: 15.3.12 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-311 |
"PackageableElement::visibility" uses "false" as default value |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-302 |
Mismatch between Superstructure ptc/06-04-02 and XML Schema ptc/06-04-05 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-301 |
Page: 155, 162 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-305 |
Section: 17/17.5.7 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-304 |
Port.provided:Interface |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-300 |
Section: 14.3.28 ReceiveSignalEvent (from BasicInteractions) |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-299 |
Section: 12.3.38 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-303 |
UML2: Actor cannot have ownedAttributes |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-314 |
State Machines |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-313 |
Section: 18.3.8 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-310 |
"Constraint::context" is marked as derived in the metaclass description |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-222 |
discrepancies between package dependencies and XMI file for Superstructure |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-224 |
Section: Figure 14.5 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-223 |
Section: Appendix F |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-218 |
Section: 8.3.1 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-217 |
General ordering cycles |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-215 |
What exactly is a state list? |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-214 |
Section: 9.14.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-213 |
Section: 11.1.3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-212 |
Action inputs/outputs |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-225 |
Section: 7.3.44 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-221 |
Section: 7.2 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-220 |
Page: 64 & 112 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-219 |
Completion event modeling |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-216 |
Editorial bug in 2.1 Superstructure Convenience document |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-183 |
7.3.4 Association Class |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-334 |
UML 2.2 scope statement |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-333 |
Property::isAttribute() query needs no argument |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-330 |
Section: 11.4 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-329 |
Section: 11.4 Classifiers Diagram |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-340 |
Actor concept was indeed changed |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-339 |
Section: 13.3.3 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-343 |
composite subsets |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-342 |
UML 2.1.2: Path names for CMOF files |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-332 |
Section: 7.3.21 figure 7.47 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-331 |
Section: 7.3.21 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-337 |
Section: Abstractions (02) |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-336 |
Section: Constructs |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-338 |
Namespace URI for Standard Profile(s) |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-335 |
Section: Abstractions |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-341 |
Section: 14.3.3 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-264 |
Invalid mandatory compositions and associations |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-263 |
11.3.47 on StructuralFeatureAction (and related sections on subclasses) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-262 |
Section: 9.16.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-261 |
Section: 9.19.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-258 |
Section: 9.12.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-257 |
Merged Metam.:Property::class with redefinition of non-inherited property |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-265 |
Invalid redefinitions introduced into metamodel |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-267 |
Section: 13.2 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-266 |
Section: 11.3.5 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-256 |
navigating from link to link ends |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-255 |
ExtensionEnd description refers to old use of navigability |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-260 |
Section: 9.10.3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-259 |
Section: 9.13 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-270 |
Section: 7.3.3 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-269 |
Figure 7.31 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-268 |
Section: Annex C.1 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-355 |
StructuredActivityNode [UML 2.1.1] |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-357 |
UML2 Issue - 'abstract' not listed in keyword Annex |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-356 |
UML2 issue: ProfileApplication treated as Import |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-348 |
context of Constraint |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-347 |
Section: 18.3.6 Profile (from Profiles) |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-354 |
Section: 7.3.33 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-353 |
In section 7.3.12 Figure 7.38 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-351 |
Incorrect word renders sentence meaningless: Chap. 12.3.41 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-350 |
The section titled "Changes from previous UML" is not complete |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-346 |
first constraint for CombinedFragment |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-345 |
Section: 12.3.1 AcceptEventAction |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-344 |
RedefinableTemplateSignature |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-352 |
ElementImport |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-349 |
UML 2.1.1 - fig 7.14 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-287 |
Section: 7 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-286 |
Section: 15 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-285 |
Section: 15 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-295 |
UML 2.1 Spec, Interactions: 14.3.18 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-294 |
UML 2.1 Spec, Interactions: 14.3.18 - InteractionUse |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-293 |
A_outgoing_source and A_incoming_target should not be bidirectional |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-289 |
UML 2 Superstructure/Components/overly stringent constraints |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-288 |
AcceptCallAction has not operation |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-291 |
Section: 14.3.10 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-290 |
Section: 14.3.14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-297 |
UML2: notation issue |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-296 |
Section: e. g. 12.2. page 287 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-292 |
A_end_role should not be bidirectional |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-298 |
ReplyAction::replyValue type is incorrct |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-201 |
assembly connectors |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-200 |
New Issue on multiple guillemot pairs for same element |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-210 |
11.3.26 OpaqueAction |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-209 |
Definition of stereotype placement requires a name |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-206 |
the default for a Property should not be inconsistent with its type |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-205 |
Section: 7.3.10 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-204 |
packagedElement |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-203 |
ptc/06-01-02:14.3.14, Notation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-207 |
UML's support for null values and semantics is unclear |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-211 |
UML 2/ Super / SendSignalEvent erratum |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-199 |
Question on InfrastrucutreLibrary::BehavioralFeatures::Parameter |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-208 |
"Property::lowerValue" is not a good name |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-202 |
Fig 7.14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-370 |
Table 8.2 must be named "Graphic paths..." instead of "Graphic nodes..." |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-369 |
Datatypes in UML profiles |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-364 |
TemplateSignature / TemplateParameter / StructuredClassifier |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-363 |
inability to specify ordering of messages connected to gates is problematic |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-372 |
The semantics of an assembly connector remains unspecified |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-371 |
Table 8.2 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-362 |
UML2: Missing ActionOutputPin |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-361 |
The spec needs to clarify the isConsistentWith() method for transitions |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-367 |
paragraph on "deferred events" on page 552 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-366 |
Section 14.3.19 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-360 |
Figure 7.6 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-359 |
Section: 12 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-368 |
15.3.14: This paragraph refers to signal and change events |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-358 |
Section: 8.3.2 Connector |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-365 |
UML 2.1.1 Issue: Invalid association end in Figure 7.20 |
UML 2.1.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-275 |
Section: 17.5 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-274 |
UML 2 state machines / entry point outgoing transitions |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-278 |
Page 60 of the pdf |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-277 |
UML2: Parameter::isException overlaps with Operation::raisedException |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-279 |
uml.xsd schema file in ptc/2006-04-05 is not correctly generated |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-284 |
UML2: ReadSelfAction with a context cannot access behavior owned attributes |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-283 |
Activity shape |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-273 |
12.3.27 ExpansionRegion |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-272 |
12.3.26 ExpansionNode |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-281 |
Meaning of Constraint visibility |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-280 |
Section: 7.3.38 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-276 |
Section: 12.3.2 Action |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-271 |
redefined properties |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-282 |
Change references in Infra- and Superstructure to UML 2.1.1- URGENT ISSUE- |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-240 |
Section: Activities - Pin ordering semantics |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-239 |
Section Activities: Default weight |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-235 |
text of specs and corresponding XMI specs should be clarified |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-234 |
UML 2: "isLeaf" |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-227 |
Section: 15.3.14 Transition |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-226 |
Section: 7 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-238 |
Figure 7.4 invalid redefines |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-237 |
EnumerationLiteral should constrain InstanceSpecification |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-233 |
Stereotype attributes inherited from Class |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-232 |
Section: 12.3.8 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-231 |
Section 11.4.1 "Classifier" (in Constructs) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-228 |
Notation (p 154, formal/05-07-04 ) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-230 |
Section 11.4.1 "Classifier" (in Constructs) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-229 |
Section 10.2.1 "Class" (in Basic) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-236 |
Section: 15.3.12 |
UML 2.1.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-192 |
Section: 7.3.7 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-191 |
AssociationClass is severely underspecified |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-190 |
Show an example of correct notation for the metamodel |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-185 |
Page: 338, 339 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-184 |
Optional name attribute in NamedElement is misleading and insufficient |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-197 |
UML 2 Super / Components / connectors to interfaces |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-187 |
reference to Figure 12.87 missing |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-186 |
Section: 14.4 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-194 |
No ObjectEvent corresponding to SendObjectAction |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-193 |
Fig 12.10 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-189 |
Page: 625 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-188 |
UML 2.1/Superstructure/ call triggers vs signal triggers |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-196 |
Section: 12.3.48 |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UML22-198 |
UML 2.2 RTF issue - line styles for profiles |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-195 |
UML 2 Super / Composite Structure / ambiguous constraint |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-132 |
Section: 15.3.12 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-131 |
Section: 11.5.1 DataType (as specialized) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-141 |
event parameters |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-140 |
Meaning of navigability |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-130 |
Section: 11.3.13 TypedElement (as specialized) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-129 |
Section: 11.3.6 Classifiers diagram |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-139 |
Page: 62 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-138 |
page 134, Chapter 11.4.1 |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-137 |
page 97, Chapter 10.2.2. MultiplicityElement |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-125 |
Page: 129 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-124 |
Page: 369/370 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-136 |
Page: 157,162,163 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-135 |
ObjectNode |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-127 |
9.1 BehavioralFeature package |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-126 |
Page: 532 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-134 |
UseCase and Actors |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-133 |
Page: 423 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-128 |
Section: 10.1 Types Diagram |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-93 |
Figure 179 (Control nodes) |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-92 |
Section: D.4 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-91 |
Section: 15.3.8 (second issue) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-90 |
Section: 18.3.6 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-89 |
Section: 17 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-102 |
Section: 8.3.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-101 |
Section: Actions |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-100 |
CombinedFragment Loop notation |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-99 |
Section: 7.3.36 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-98 |
editorial in section 12 |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-97 |
UML 2 Different constraints for Property in Super and Infra |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-107 |
Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-106 |
Clarify multiple inputs to expansion regions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-105 |
DataStoreNode has uniqueness, reverse constraint inherited from ObjectNode |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-87 |
Add constraints on conditional, loop, sequence to rule out node contents |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-86 |
Section: Activities, LoopNode |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-96 |
rewording isuse? |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-95 |
reword sentence |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-94 |
A test cannot be empty |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-104 |
Misleading statement about multiplicity in AssociationClass |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-103 |
Client/supplier on dependencies |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-88 |
Constrain conditional node to have body pins if there is a result pin. |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-2 |
Starting state machine |
UML 1.4
|
UML 2.2
|
Resolved |
closed |
|
| UML22-3 |
Starting a state machine |
UML 1.4
|
UML 2.2
|
Resolved |
closed |
|
| UML22-5 |
saying {nonunique} on one end of a binary association is meaningless |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-4 |
behaviour of the shallow history state and deep history state |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-173 |
On page 26, Figure 7.9 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-172 |
choice of terminolgy for TransitionKind is non-intuitive |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-171 |
Section: 15.3.15 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-170 |
Section 8.3.2 sub-section "Notation" starting on page 149 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-169 |
inconsistency wrt UML2 classifier behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-168 |
keyword, "buildcomponent", and a stereotype, "buildComponent" |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-182 |
Element and Comment in Basic |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-181 |
Description of Element |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-180 |
Unclear relationship between the Basic and Abstractions packages |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-179 |
XMI file: Core::Constructs::Operation::bodyCondition should have upper boun |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-178 |
/qualifiedName attribute missing on Core::Constructs::NamedElement |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-177 |
Operation::ownedParameter should be ordered in XMI? |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-176 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-175 |
constraints owned by these properties have no context |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-174 |
Operation should be a specialization of TypedElement and MultiplicityElemen |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-167 |
section, 12.3.27 ExpansionRegion(from ExtarStructureActivities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-166 |
(merged) compliance levels L2 and L3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-165 |
(merged) compliance level L1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-164 |
Section: 14.3.20 Message (from BasicInteractions) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-163 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-22 |
UML 2 Issue: Qualified pathnames |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-35 |
show object flow or interactions |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-34 |
UML 2 Super/Interactions/Need constraints that cover multiple Lifelines |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-24 |
ptc-03-09-15/Separate classification and generalization in Core::Basic |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-23 |
Ports in Protocol State Machines |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-33 |
StateMachine - Constraints |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-32 |
transtion |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-27 |
UML2 Super/Kernel Classes |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-26 |
UML Superstructure FTF : isRoot property disappeared |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-30 |
Inheritance of 'Enumerations' is not detailed |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-29 |
Part subtype |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-31 |
manage simultaneity of events |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-25 |
Federated models - UML2 issue |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-28 |
UML 2.0 Kernel Operations Diagram and Features Diagram and mdl |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-112 |
External exceptions. |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-111 |
Clarify which classifier or operation this is referring to |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-110 |
represents and occurrence keywords are switched |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-114 |
Events in Sequence diagram |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-113 |
1. Deployment |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-116 |
Section: Action/Activity |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-115 |
Nested Nodes |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-119 |
Input tokens to LoopNodes should be destroyed when the loop is done |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-118 |
Section: 8.3.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-123 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-122 |
Section: 12.3.2 Action |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-109 |
In Figure 12, ownedAttribute is bidirectional, in Figure 95, it is unidirec |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-108 |
StructuredActivityNode, Semantics, third paragraph, first sentence, |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-117 |
Section: 9.3.7 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-120 |
Return message |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-121 |
multiplicity should not be used/shown in an communicates association |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-76 |
Section: 14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-75 |
Section: 14.3.18 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-74 |
RemoveStructuralFeatureValueAction specification |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-73 |
inconsistent description |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-82 |
Decision node |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-81 |
Section: Actions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-80 |
UML 2 Super / Kernel / invalid restriction in isConsistentWith() |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-67 |
namespace |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-66 |
Figure 89 on page 158 is incorrect |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-72 |
Section: 13.3.17 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-71 |
Section: 13.3.11 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-70 |
UML2/Infra section 11.6.2/ Enumerations should not have attributes |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-79 |
Default values for ValueSpecification are not specified properly |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-78 |
Section 15 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-77 |
Section: 14 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-69 |
Section: 12.3.40 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-68 |
Section: 12.3.33 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-84 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-83 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-65 |
Section: 10.3.11 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-85 |
Section: Interactions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-155 |
Section: Common Behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-154 |
Section: Classes (02) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-153 |
Section: Common Behavior (02) |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-152 |
Section: Common Behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-151 |
Property ownership must be consistent across association redefinitions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-150 |
Missing notation for association classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-149 |
Page: 346-347 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-148 |
Page: 255 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-147 |
Behavior |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-144 |
UML 2 - Invalid subsetting of composition ends |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-143 |
UML 2 Super / Actions / Compliance Levels of Actions |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-162 |
Page: 53-55 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-161 |
"ownedType" is not a valid element |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-158 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-157 |
Section: Classes |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-156 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-146 |
UML SuperStructure - Inconsistency re State Machine terms |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-145 |
Section: 14.3.20 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-160 |
Section: 16.3.3 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-159 |
Section: Activities |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-142 |
Page: 420 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-36 |
Connector - "provided Port" and "required Port" not defined Constraint 1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-46 |
isComposite inconsistency in UML 2.0 and MOF 2.0 |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-48 |
Section: 9.14.1 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-47 |
should retain Comment and its associations to Element |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-42 |
Notation sections for TimeObservation and DurationObservation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-41 |
completion transitions |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-38 |
Connector - inconsistencies in Constraint[3] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-37 |
Connector - inconsistencies in Constraint [2] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-40 |
Connector - inconsistencies in Constraint[5] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-39 |
Connector - inconsistencies in Constraint[4] |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-50 |
Presentation Options |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-49 |
Use case extension inconsistencies |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-45 |
AssociationClass |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-44 |
useless example on p.330, Figure 247 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-43 |
Property defines an association "datatype" which is redundant |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-57 |
Multiple typos in ptc/04-10-02 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-56 |
Clarify the differences between redefining element and redefined element. |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-55 |
All sections |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-54 |
ClassifierInState not supported in UML2.0 ? |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-64 |
Section: 9.3.11 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-63 |
Section: 8.3.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-51 |
constrainedElement direction |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-53 |
Association specialization semantics |
UML 1.4.2
|
UML 2.2
|
Resolved |
closed |
|
| UML22-52 |
Derived union notation |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-61 |
Section: 9.3.7 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-60 |
Section: 9.3.6 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-62 |
Section: 8.3.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-58 |
Section: 8.3.2 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-59 |
Section: 9.3.4 |
UML 2.0
|
UML 2.2
|
Resolved |
closed |
|
| UML22-7 |
Reentrancy 1 |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-6 |
Suspension Region |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-18 |
UML 2 Super / Missing OCL constraints |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-17 |
03-04-01 Chap 2 p. 112/Components: Different ways to wire components |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-20 |
UML 2 Issue: AssociationEnd |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-19 |
instantiations of Classifiers |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-15 |
Section 9.3.3 |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-14 |
UML 2 Super/Interactions/missing OCL constraints |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-10 |
UML 2 Super/Metamodel/redefinition and substitutability |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-9 |
Target pin notation |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-12 |
Notes versus curly braces |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-11 |
Activity OCL |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-16 |
UML2 super/ad-03-04-01/Derived attributes and associations |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-13 |
UML 2 super / Dependencies / improper subsetting? |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML22-8 |
State extension |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UML14-557 |
Feature;ModelElement |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-377 |
Corrections and improvements to glossary definitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-376 |
The name "required interface" is misleading |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-373 |
UML 2.0 significant typo - collaboration diagram |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-372 |
targetScope on StructuralFeature and AssociationEnd |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-375 |
Specification of parametric models |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-374 |
Excessive syntactic and semantic overlap between structured Classifiers |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-371 |
UML Superstructure: 03-08-02 / <> |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-370 |
ad-03-04-01 Chap 3 p. 151 Table 3/Composite structures: ComplexPort |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-369 |
ad-03-04-01 Chap3 p.146/Composite structures: Connected elements constraint |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-368 |
Chap 3 p. 142-143 Figure 3-35 /Composite structures: Port multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML22-1 |
Semantics of firing compound transitions still appears to be circular |
UML 1.3
|
UML 2.2
|
Resolved |
closed |
|
| UML14-405 |
Clarify termination of asynchronous invocations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-404 |
Appendix A Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-403 |
Section 17 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-396 |
Section 8.3.3 Realization |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-395 |
Section 8.3.1 Component |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-401 |
Section 14.4 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-400 |
Section 14.4 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-394 |
Section 8.3.1 Component |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-399 |
Section 14.3.14 Message |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-398 |
Section 10 Deployments |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-393 |
Section 8.1 Overview |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-402 |
Section 14.4 Diagrams (02) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-397 |
Section 9.4 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-450 |
UML2 Super/Ports |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-449 |
UML2 Super/Connector |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-457 |
UML 2 Super / Activities / association end naming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-456 |
UML 2 Super / Activities / inconsistency in representing subsetting |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-454 |
UML 2 Super/Activities/assocition end specialization consistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-452 |
subsettedProperty->forAll(sp | isDerivedUnion) ? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-451 |
UML2 Super/Connector End |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-455 |
UML 2 Super/Activities/invalid multiplicity 0 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-447 |
UML2 Super/Structured Classes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-453 |
UML 2 Super/Activities/end naming consistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-448 |
Page 164 - there are two constraints sections for Connector |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-444 |
UML 2.0 Superstructure Derived Union vs. derivationExpression? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-443 |
UML 2.0 Superstructure reccomendation (derived unions) |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-442 |
UML 2 Super / use cases / incorrect comments in notation section |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-441 |
Error in definition of PackageMergeKind |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-446 |
UML2 Super/parts |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-445 |
UML2 Super/Composite Classes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-437 |
section 9 (State Machines) of 3rd revision |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-436 |
UML 2 Super/Actions/PrimitiveFunction missing properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-434 |
Time trigger notation in state machines |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-433 |
No way to represent "uninterpreted" actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-438 |
UML 2 Super/Actions/non-existent feature "multiplicity" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-435 |
Notation when guards are used in conjunction with triggers in transitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-440 |
UML 2.0 Superstructure 3rd revision - Owner of triggers? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-439 |
UML 2 Super/Action/featuringClassifier misinterpreted |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-386 |
UML 2 Issue: Connector types |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-385 |
glossary |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-383 |
Abandon the OMGS4LMMA |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-382 |
14.3: StateInvariant and ExecutionOccurrence |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-381 |
UML 2.0 Superstructure FTF issue - Profiles |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-380 |
Removal of gratuitous restrictions to software applications |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-388 |
Section 7.3.1 ElementImport |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-387 |
UML 2 Issue: Include(s) and Extend(s) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-379 |
Diagram Taxonomy corrections |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-378 |
Inconsistent use of terms "implement" and "realize" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-392 |
Section 7.18 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-391 |
Section 7.15.3 Interfaces |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-384 |
Change 'Part' to 'Role. |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-390 |
Section 7.13.2 Package Merge |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-389 |
Section 7.3.5 PackageImport |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-412 |
concurrent vs. parallel ExpansionRegions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-411 |
Use Case Metamodel - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-420 |
Operation without - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-419 |
Components and artifacts: Dependency problem - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-416 |
AcitivityEdge: weight=all vs weight=null - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-415 |
Large diamond for binary associations legal? - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-418 |
Guard conditions at fork nodes - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-417 |
Token flow semantics: Implicit fork and join - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-409 |
Multiobject in UML2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-408 |
Outputting constants |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-414 |
Diagrams, Diagrams, Diagrams ... UML 2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-413 |
Binary associations decorated with large diamonds legal? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-407 |
Protocol machines do not subset state invariant |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-406 |
Conditions for parameter sets (02) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-410 |
ActivityFinalNode and running actions - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-431 |
Incorrect usage/definition of "emergence" in Common Behavior Chapter |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-427 |
The node "Order cancel request" that appears in figure 6-86 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-426 |
GeneralizationSet Description clarification - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-429 |
Typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-428 |
Order cancel request |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-423 |
Package Extensibility <> - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-422 |
Dependency notation for interfaces - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-421 |
Inconsistency concerning VisibilityKind - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-424 |
does "is not instantiable" imply "isAbstract"? - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-425 |
Activity nodes and Stereotypes - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-432 |
Missing actual arguments in submachines states |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-430 |
/pages 485,487,495/mixed names for state machine diagram |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-466 |
UML 2 Super / state machines / incorrect property redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-465 |
UML 2 Super / state machines / non-existent property reference |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-462 |
Ambuiguity in value pin evaluation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-461 |
page 136, "BasicComponents", |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-468 |
UML 2 Super / state machines / non-existent return type |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-467 |
UML 2 Super / state machines / misplaced operation definition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-458 |
UML 2 Super / Activities / subsetting two properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-460 |
Consistent Naming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-464 |
UML 2 Super / state machines / oclIsKindOf arguments error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-459 |
UML2 Super/Signal |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-463 |
UML 2 Super/State machines/pseudostate name consistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-469 |
UML 2 Super / use cases / invalid subsetting |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-366 |
ad-03-04-01 Chap 3 p. 137/Composite structures: Connector multiplicity >2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-365 |
ad-03-04-01 Chap 2 p. 118 Figure 2-15/Components: Wiring notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-367 |
ad-03-04-01 Chap 3 p. 137-138/Composite structures: Connector semantics |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-364 |
UML 2 Infras./Interactions/ execution occurrence should not be abstract |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-219 |
Typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-225 |
7.4.1 Multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-224 |
7.3.1 ElementImport |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-218 |
Clarify that profiles can contain model libraries |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-217 |
Notation for anonymous instance |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-221 |
UML Superstructure 03-08-02: Loop node notation missing |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-220 |
UML Superstructure: 03-08-02 -- typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-215 |
Notation for attributes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-214 |
Property string undefined |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-226 |
InstanceSpecification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-216 |
Instantiates stereotype |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-223 |
No notation defined for suppressing attributes or operations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-222 |
Notation mismatch for the realization dependency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-177 |
Parameter set corrections 3 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-181 |
Streaming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-180 |
Parameter set corrections 6 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-179 |
Parameter set corrections 5 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-178 |
Parameter set corrections 4 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-332 |
Outgoing edges of initial nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-331 |
Port is a Property in XMI |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-326 |
InformationFlow realization |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-325 |
Dependency multiplicity to CollaborationOccurrence |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-330 |
Ports as properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-329 |
partWithPort without ports |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-323 |
Control pins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-322 |
Profiles in fixed repositories |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-328 |
Association end names and part types |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-327 |
Deployment location |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-333 |
Guards on initial nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-324 |
Control at joins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-228 |
7.11.2 Association |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-227 |
7.10.1 Operation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-234 |
UML 2 Super/Metamodel::IntermediateActivities/redundant merge error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-233 |
BehaviorStateMachines/missing owningState end name |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-238 |
UML 2 Super/Metamodel::Kernel::DataTypes/missing renames |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-237 |
AuxiliaryConstructs::Templates::Operation/extra space |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-232 |
UML 2 Super/Metamodel::BasicBehaviors/package merge issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-231 |
7.15.3 Interface |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-235 |
UML 2 Super/Metamodel::Communications/redundant merge error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-229 |
7.14.1 Abstraction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-236 |
UML 2 Super/Metamodel::Nodes/redundant merge error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-230 |
7.14.6 Realization |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-195 |
Pins on structured nodes 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-194 |
Pins on structured nodes 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-203 |
Action packaging |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-202 |
BroadcastSignalAction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-196 |
Time spec text |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-200 |
Update actions for isUnique |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-193 |
ExpansionRegion |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-197 |
Partition semantics |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-198 |
Activity frame and parameter nodes 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-201 |
actions on properties that are association ends |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-199 |
Activity frame and parameter nodes 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-347 |
Flows across SAN boundaries |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-346 |
Initial nodes in structured actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-345 |
Parameters in Features and Common Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-342 |
Clarify join specs referencing control flow edges |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-341 |
Combining joined tokens |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-349 |
AcceptCallAction in SAN |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-348 |
Terminating a SAN |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-344 |
Join example |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-343 |
Clarify join rules |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-336 |
Side effects of value specifications |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-335 |
Activity final clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-339 |
ReadSelfAction with no host |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-338 |
Decision behaviors on control tokens |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-340 |
Clarify ReadSelfAction in activity behaviors |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-337 |
Guard evaluation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-334 |
Caption typo |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-291 |
Confusion regarding XMI for use of stereotypes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-290 |
Actors that are outside and inside the system |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-289 |
UML2 super/pgs.17 + 598/"topLevel" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-288 |
Actor |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-287 |
Multiplicity of Regions owning Transitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-286 |
State list |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-285 |
UML 2.0 serious layout problems with activity diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-284 |
Stereotypes for Actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-283 |
UML Superstructure: 03-08-02 / Typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-282 |
UML 2 Super/Compliance points/confusing and redundant |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-281 |
UML 2 Super/pg.81/semantics of subsetting-specialization-redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-280 |
UML 2 Super/pg.379/anyTrigger clarifications |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-279 |
UML 2 Super/pg. 556/notation for template binding inconsistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-278 |
UML 2 Super/pg. 471/choice pseudostate notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-277 |
UML 2 Super/pg.471/unclear terminate state semantics |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-276 |
UML 2 Super/pg.519/multiplicity semantics of use case associations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-295 |
Question about InterruptibleActivityRegion |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-294 |
fig 141 p205 and 7.13.2 p101 / just what sort of relationship is < |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-293 |
Metamodel for applying a stereotype |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-292 |
Association not affecting ends |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-275 |
UML 2 Super/pg.427/missing notation description for lifelines |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-274 |
UML 2 Super/pg.429/incorrect constraint for Message |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-273 |
UML 2 Super/pg.416/incorrect multiplicities for event occurrence |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-272 |
UML 2 Super/pg.395/multiple meaning of exception |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-271 |
UML 2 Super/pg.235/missing semantics of destroy action |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-270 |
UML 2 Super/pg.130/incorrect stereotype name |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-267 |
UML 2 Super/pg.109/Permission redundant |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-265 |
UML 2 Super/pg.64/Classifier redefinition notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-266 |
UML 2 Super/pg.95/attributes in data types clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-268 |
UML 2 Super/pg.99/misnamed "packageMerge" attribute |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-269 |
UML 2 Super/pg.130/missing notation explanation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-264 |
UML 2 Super/pg.79/underlined operation syntax missing |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-312 |
PackageMerge (from Kernel) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-311 |
Sequence diagram conditions on Message arrows |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-319 |
UML2 Super/Instances |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-318 |
UML2 Super/Ports |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-310 |
Recommendation for InteractionOccurrences |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-309 |
UML 2 Super / Interactions / No way to model reply messages |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-321 |
description of Component on page 137 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-320 |
Figure 61 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-313 |
UML2.super (or infra)/Profiles-Stereotype (18.3.7) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-317 |
UML 2 Super/Components & Deployment chapters missing OCL constraints |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-316 |
UML2 Super/Profiles |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-314 |
UML2 Super/Composite Structures |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-308 |
UML Superstructur 03-08-02: Notation for ConditionalNode is missing |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-315 |
UML2 Super/Kernel::Classifier |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-263 |
UML 2 Super/pg.78/missing return types syntax |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-262 |
UML 2 Super/pg.78/operation redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-258 |
UML 2 Super/Metamodel::UseCases/Extend and Include are not NamedElements |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-257 |
UML 2 Super/Metamodel/missing namespaces for metaclasses |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-254 |
UML 2 Super/Metamodel/Mis-named Manifestation class |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-253 |
UML 2 Super/Metamodel::Templates/missing return type |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-261 |
UML 2 Super/Spec/completing mandatory sections |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-252 |
UML 2 Super/Metamodel::CommonBehaviors/redundant class? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-256 |
UML 2 Super/Metamodel/missing owners for metaclasses |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-255 |
UML 2 Super/Metamodel/mis-spelled implementingClassifier" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-260 |
UML 2 Super/Metamodel/missing source and target for InformationFlow |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-259 |
ProtocolStateMachines/ProtocolStateMachine not a type of Feature |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-209 |
Protocol state machines are not pre/postconditions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-212 |
Replace "initial value" with "default value". |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-211 |
TimeObservationAction can't return values |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-208 |
Diamond notation for merge junctions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-207 |
Activity attributes on Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-213 |
Kernel::Classifier missing "attribute" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-210 |
Interactions view of state machines/activities |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-206 |
Concrete Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-204 |
Composite structure dependent on Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-205 |
Complex port |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-307 |
UML 2 Super / Interactions / no create message |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-306 |
UML2 Super / Primitive Types / implementation issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-296 |
UML super/Section 2/Compliance points |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-300 |
Defenition of redefines????? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-299 |
UML 2 super/Composite Classes/Connecting parts of parts |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-303 |
UML2 Super / association end naming convention |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-302 |
UML2 Super / Classes/ Incorrect reference to "access" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-305 |
UML 2 Super / State machines-CommonBehavior / undefined owner of triggers |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-304 |
UML2 Super / SimpleTime package / missing multiplicities |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-298 |
fig236 Datastore example/Datastore should not directly linked with actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-297 |
UML 2 Super/p125 and p126/typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-301 |
What does redefines mean in package extensibility? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-356 |
UML 2 Super / Interfaces / Cannot nest classes in interfaces |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-355 |
UML 2 Super / state machines / restriction on redefining transitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-352 |
Typo on Notation for CombinedFragment? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-351 |
Visibility of a Package |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-359 |
UML 2 Super / Simple Time / incorrect multiplicities |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-358 |
UML 2 Super / Interface / missing owner of operation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-361 |
UML 2 Super / Package Templates / StringExpression inconsistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-360 |
UML 2 Super / Activities / inconsistent naming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-353 |
Figure 395 requires a lot more explanation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-363 |
UML 2 super / Templates / parameters cannot have names |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-362 |
UML 2 Super / Deployments / node composition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-350 |
Questions about CentralBufferNode semantic |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-354 |
UML 2 super / state machines / entry and exit actions cannot be redefined |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-357 |
UML 2 super / Activities / structured activity node contradiction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-244 |
UML 2 Infra/Section 5.9/missing merge rules |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-243 |
UML 2 Super/Metamodel/package merge and visibility |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-247 |
UML 2 Super/Metamodel::BasicActivities/inGroup problem |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-246 |
UML 2 Super/Metamodel::StructuredClasses/erroneous association |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-245 |
UML 2 Super/Package Merge/redefinition rules and standard OO languages |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-241 |
UML 2 Super/Metamodel::Constructs/inconsistency with Kernel |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-240 |
UML 2 Super/Metamodel::BasicBehaviors/missing redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-250 |
UML 2 Super/Package Merge/missing rule for operations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-249 |
UML 2 Super/Metamodel::Compliance::L3/Missing merges |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-242 |
UML 2 Super/Metamodel/merging of non-redefinable model elements |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-239 |
UML 2 Super/Metamodel::Kernel::Packages/missing redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-248 |
UML 2 Super/Metamodel::StructuredActivities/double redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-251 |
Profile/inability to attach a stereotype to an element |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-191 |
SendObjectAction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-190 |
Clarification of insert |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-185 |
Colon notation for pins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-184 |
Local pre/postcondition example |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-182 |
Parameter semantics clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-192 |
ExceptionHandler 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-189 |
No-token activity termination clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-187 |
Notation for for global pre/postconditions actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-183 |
Behavior execution instances |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-188 |
Notation for isSynchronous |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-186 |
Value Pin notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-171 |
ObjectFlowEffect |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-170 |
Optional parameters |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-176 |
Parameter set corrections 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-174 |
ObjectNode.isUnique |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-173 |
Reentrancy 3 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-169 |
Pin multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-175 |
Parameter set corrections 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-172 |
ExecutableNode, ControlNode should be abstract |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-133 |
UML's use of the word "unique" for multiplicity is ambiguous |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-132 |
UML 2.0 Superstructure: Operation vs. Attribute notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-135 |
The description of DataType is plainly wrong in the specification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-134 |
notation for shared aggregation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-139 |
Question on Connectors - fig 2-17 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-138 |
There appears to be a typo on page 2-148, in section 2.12.2.13 on StubState |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-137 |
Well-Formedness Rules for Procedure on Common Behavior Package |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-141 |
An error in Figure 464 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-140 |
PackageableElement |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-145 |
Figure 63 missing notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-144 |
Interface Figure 62 uses wrong notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-136 |
Description of GeneralizationSet |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-142 |
Section 1.3, ElementImport semantics on page 10 of ad/2003-04-01 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-143 |
Obsolete notation used in state machine - transition examples |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-55 |
Profile Notation |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-54 |
Appendix A, UML Standard Elements |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-58 |
Issue: Conflicting WFRs on Transition |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-57 |
Add Multiplicity to Parameter. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-56 |
Events, signals, stimuli, etc. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-53 |
Clarify the origin of an Action in a Collaboration. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-168 |
Pin/parameter matching 4 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-167 |
Pin/parameter matching 3 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-158 |
Weight=all |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-157 |
Provide notations for Loop and Conditional |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-163 |
Multiple outputs of object flow transformations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-162 |
Keywords or properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-159 |
Tokens at fork |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-161 |
ExpansionRegions keywords |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-165 |
Pin/parameter matching 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-160 |
ActivityFinalNode |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-166 |
Pin/parameter matching 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-164 |
Pins owned twice |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-131 |
representation of arrays of values in an action language |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-130 |
2.5.2.29 Node |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-128 |
2.5.2.15 Dependency |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-123 |
2.5.2 Abstract Syntax |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-122 |
Section: 2.5.2.10 Classifier |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-129 |
2.5.2 Abstract Syntax |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-121 |
Designates a Generalization (02) |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-125 |
2.5.2.27 ModelElement |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-126 |
2.5.2.10 Classifier |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-124 |
2.5.2.16 Element |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-127 |
2.5.2 Abstract Syntax |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-69 |
Using or implementing an interface of a Subsystem |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-68 |
XML attribute "isPolymorphic" does not exist in UML 1.3 or UML 1.4 XMI DTD |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-72 |
Compliance to the UML" pp xxxi -- Editorial? |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-71 |
Nameclash in UML 1.4 |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-70 |
Using OCL at the meta-model level |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-151 |
running a Check Model in Rose you get the following errors |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-154 |
Clarify wording on executable activity nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-153 |
Outgoing edges from input pins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-150 |
UML2 super/pg. 580/Stereotype typo |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-149 |
UML2 super/pg.470/entry and exit points for composite states |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-148 |
Multiplicities diagram in section 7.4 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-156 |
Action should be concrete |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-155 |
Edge constraint for control nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-146 |
Strange notation in Figure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-152 |
Variable and Pin multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-147 |
No Glossary in 03-08-02 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-49 |
MOF rules should disallow certain composition relationships |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-48 |
Notation for inherited associations |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-52 |
Conflicting constraint between ActivityGraph and StateMachine. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-51 |
Attributes obsolete in UML 1.3 |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-50 |
Interface of an object |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-46 |
Why is a StateMachine's top a State instead of a CompositeState? |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-47 |
Document 99-06-08 - UML Spec |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-7 |
issues and bugs on the UML 1.4 Draft |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-6 |
class TaggedValuewill two association-ends with the same name "stereotype" |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-14 |
Figure 2-15 of the uml 1.4 spec |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-13 |
page 2-163, the statemachine semantics escription |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-16 |
isPolymorphic is never in a diagram |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-15 |
well-formedness rule for Package is missing inUML 1.4 |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-10 |
it's => its on page 3-150. |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-9 |
Wf 2 for AssociationEnd |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-8 |
2.9.2 Abstract Syntax |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-12 |
Notation example typo in Fig. 3-99 |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-11 |
The glossary entry "call" should be "call state". |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-3 |
elimination of the Association Class TemplateParameter |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-2 |
2) Page 2-49, additional operation #7 for Classifier |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-5 |
Remove uses of multiple inheritance from UML meta model |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-4 |
Who owns a Comment? |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1 |
Page 2-47, well-formedness rule #2 for Classifier |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| SYSML11-131 |
Section: 11.3.2.2 ControlOperator |
UML 2.1.1
|
SysML 1.1
|
Resolved |
closed |
|
| OCL2-1 |
Section 6.6.7 |
UML 1.4
|
OCL 2.0b2
|
Resolved |
closed |
|
| MOF24-42 |
Relations |
UML 2.0
|
MOF 2.4
|
Resolved |
closed |
|
| UML15-10 |
UML2 super/Profile/Unconsistent association extension description |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-12 |
Correction to 7336 |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-11 |
Dependency errors |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-9 |
UML2 super/Profile/Unconsistent Profile extension description |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-8 |
UML 2 Super Issue re: DI compliance |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-7 |
UML 2/ Inconsistencies in usage of package merge |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-6 |
UML 2 Super/Infra: no notation for "isQuery" characteristic of Operations |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-5 |
UML 2 Super/Infra: return type of an operation |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-4 |
Need to documetn diagramming conventions for association ends |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-3 |
Remove Package Templates? Feedback requested |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-2 |
UML 2 Super/state machines/Maximum one region |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML15-1 |
StartOwnedBehaviorAction |
UML 1.4.2
|
UML 1.5
|
Resolved |
closed |
|
| UML2-1 |
super AND infra / Section 11.8.3 of Infra, 7.13.2 of Super / PackageMerge |
UML 1.5
|
UML 2.0
|
Resolved |
closed |
|
.type))
) should be available on all namespace elements.
indicates that the association (with the implicit name of parameter)
), so we have an updated variant.
. Typo - First para., pg 540, put a space between "as" and "well" In sub-section Notation, begin a new paragraph with the second sent. of the current 3rd paragraph
, not all state machines do--
