Unified Modeling Language Avatar
  1. OMG Specification

Unified Modeling Language — Closed Issues

  • Acronym: UML
  • Issues Count: 903
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
UML22-1381 presentation option for transitions UML 2.0 UML 2.1.1 Resolved closed
UML22-1379 Figure 109, p162 UML 2.0 UML 2.1 Resolved closed
UML22-1378 LinkEndData - Inconsistency with Figure 146 UML 2.0 UML 2.1 Closed; No Change closed
UML22-1377 UML-2 deployment diagram notation UML 2.0 UML 2.1 Resolved closed
UML22-1376 section on connectors in the component chapter UML 2.0 UML 2.1 Resolved closed
UML22-1375 7.3.41 Parameter (from Kernel, AssociationClasses)" UML 2.1 UML 2.1.2 Resolved closed
UML22-1374 Profiles::ObjectNode has wrong default multiplicity UML 2.1 UML 2.1.1 Resolved closed
UML22-1373 Section: 12.3.52 UML 2.0 UML 2.1 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
UML22-1141 Section: Activities: Modifications to the approved resolution of 10815 SysML 1.0 UML 2.1.2 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-1133 defaultClassifier of ClassifierTemplateParameter SysML 1.0 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-1128 Wrong notation description SysML 1.0 UML 2.1.2 Resolved closed
UML22-1127 Section: 9.3.8 UML 2.1.1 UML 2.1.2 Resolved closed
UML22-1126 page 449 chapter 13.3.24 (Signal (from Communications) SysML 1.0 UML 2.1.2 Resolved closed
UML22-1125 UML 2 superstructure -- figure 9.4 is duplicate of figure 9.3 SysML 1.0 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-1132 composite values SysML 1.0 UML 2.1.2 Resolved closed
UML22-1131 Section: 9 composite structures SysML 1.0 UML 2.1.2 Resolved closed
UML22-1130 "representation" SysML 1.0 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-1105 Profile Structure Diagrams are missing from Annex A SysML 1.0b1 UML 2.1.2 Resolved closed
UML22-1104 Missing inheritance in 9.3.12 SysML 1.0b1 UML 2.1.2 Resolved closed
UML22-1103 No default value specified for Generalization::isSubstitutable SysML 1.0b1 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-1088 A notation for Trigger SysML 1.0b1 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
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-987 p. 732: Show examples of new stereotype notation RAS 2.2 UML 2.1 Resolved closed
UML22-986 p. 732: Change example to be consistent with new definition of Clock RAS 2.2 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-983 Make instance model consistent with new definition of Clock RAS 2.2 UML 2.1 Resolved closed
UML22-982 p. 729: Extend the Clock example to show metaclass property RAS 2.2 UML 2.1 Resolved closed
UML22-985 p. 731: Make example consistent with new definition of Clock. RAS 2.2 UML 2.1 Resolved closed
UML22-984 p. 731: Make this example consistent with the new definition of Clock RAS 2.2 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-988 pp. 733-734: Add association as valid graphic path RAS 2.2 UML 2.1 Resolved closed
UML22-991 TimeExpression RAS 2.2 UML 2.1 Resolved closed
UML22-990 OpaqueAction UML 2.0 UML 2.1 Resolved closed
UML22-992 abstract Action in Activity diagram RAS 2.2 UML 2.1 Resolved closed
UML22-981 p. 728: New presentation options. Replace the following paragraph RAS 2.2 UML 2.1 Resolved closed
UML22-980 p. 721: Allow stereotypes to have properties that are typed by metaclasses RAS 2.2 UML 2.1 Resolved closed
UML22-968 Can't specify mutator semantics for derived properties RAS 2.2 UML 2.1 Resolved closed
UML22-967 Section: 12.3.37 RAS 2.2 UML 2.1 Resolved closed
UML22-976 MessageEnd RAS 2.2 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-978 Incorrect Communication Domain Model RAS 2.2 UML 2.1 Resolved closed
UML22-977 Obsolete term EventOccurrence still used in multiple places RAS 2.2 UML 2.1 Resolved closed
UML22-972 Notation of Attributes and Associations subsections RAS 2.2 UML 2.1.2 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-966 OpaqueAction RAS 2.2 UML 2.1 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-941 Profile Semantics, pag 723 RAS 2.2 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-940 policy to describe the Associations sub section of a meta class description RAS 2.2 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-534 In normative XMI file for the metamodel, no Associations have a name. XMI 2.0 UML 2.1 Resolved closed
UML22-533 UML 2 Super/Interactions/Constraints for create messages XMI 2.0 UML 2.1 Resolved closed
UML22-536 UML2 Infra/11.5.1/Invalid reference to Attribute class XMI 2.0 UML 2.1 Resolved closed
UML22-535 Figure 78 UML 2.0 UML 2.1.2 Resolved closed
UML22-532 Class InfrastructureLibrary::Core::Basic::Property UML 2.0 UML 2.1 Resolved closed
UML22-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-542 XMI schema RAS 2.0b1 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-475 Sending a signal after a delay XMI 1.3 UML 2.1.2 Resolved closed
UML22-474 Does visibility apply to creating an destroying links? XMI 1.2 UML 2.1 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-520 UML 1.5 table of contents XMI 2.0 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

Issues Descriptions

presentation option for transitions

  • Key: UML22-1381
  • Legacy Issue Number: 7643
  • Status: closed  
  • Source: Missouri University of Science and Technology ( Thomas Weigert)
  • Summary:

    The presentation option for transitions, p.599 of UML2-Super.book.040814.pdf, has the following two short-comings: * It does not make clear that this presentation option is mapped to an Activity as the effect Behavior, albeit all the mapping described subsequently assumes that this is the case. * The mapping for the action sequence symbol is ambiguous.

  • Reported: UML 2.0 — Thu, 19 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1.1
  • Disposition Summary:

    see above
  • Updated: Thu, 12 Mar 2015 01:38 GMT

Figure 109, p162

  • Key: UML22-1379
  • Legacy Issue Number: 7434
  • Status: closed  
  • Source: Silogic ( Yves BERNARD)
  • Summary:

    Figure 109, p162: according to the metamodel presented in figure 100, I think that the dependencies shown in this diagram are inverted.
  • Reported: UML 2.0 — Mon, 7 Jun 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    Discussion
    This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
    Disposition: Closed - No Change
  • Updated: Sun, 8 Mar 2015 15:16 GMT

LinkEndData - Inconsistency with Figure 146

  • Key: UML22-1378
  • Legacy Issue Number: 7182
  • Status: closed  
  • Source: PostFinance ( Karl Guggisberg)
  • Summary:

    LinkEndData defines an association "input" which is not depicted in Figure 146.

    Is this a derived association, as described below in Constraint [3] ? Should its name be changed to "/input" ?

  • Reported: UML 2.0 — Sun, 21 Mar 2004 05:00 GMT
  • Disposition: Closed; No Change — UML 2.1
  • Disposition Summary:

    No Data Available
  • Updated: Sun, 8 Mar 2015 15:16 GMT

UML-2 deployment diagram notation

  • Key: UML22-1377
  • Legacy Issue Number: 6924
  • Status: closed  
  • Source: International Business Machines ( Anders Ek)
  • Summary:

    An issue concerning UML-2 deployment diagram notation.

    The ExecutionEnvironment notation is a Node symbol with a keyword within guillemots. But what is the keyword? The text says <<ExecutionEnvironment>> but in the examples says <<container>> (figure 136) and <<execution env>> (Table 8, covering the symbols in a deployment diagram).

  • Reported: UML 2.0 — Mon, 26 Jan 2004 05:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Sun, 8 Mar 2015 15:13 GMT

section on connectors in the component chapter

  • Key: UML22-1376
  • Legacy Issue Number: 7364
  • Status: closed  
  • Source: Missouri University of Science and Technology ( Thomas Weigert)
  • Summary:

    The section on connectors in the component chapter does not add any new functionality to the connectors defined in internal structure. It does provide an additional notation for assembly connectors. There is no reason to have this section in components. Everything that is said semantically about connectors here applies equally to the more general connector. Suggestion: Do not subtype connector in component but move the content of this section to the connector section in internal structure and merge with the section there. Adjust the examples to apply to structured classifiers in general (i.e., delete the component symbol). Further, the ConnectorKind should be derived as it is determined by the manner in which the connector is attached to connectable elements. Deriving this connector ensures that constraints are always true and allows to do away with some consistency constraints. (Actually, it is not clear what the value of this attribute is, as it is already determined from the attachments.) Alternatively, if the presentation option is not in general desired (albeit I cannot see why this additional consistency would not be wanted), the text can be moved up but the presentation option can be added in this section.
  • Reported: UML 2.0 — Wed, 19 May 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    Moving all of BasicComponents.Connector into InternalStructures, although perhaps strategically a good idea, seems like a bridge too far for the RTF. Also Thomas is not entirely accurate when he says it adds no new functionality apart from the notation. In particular BasicComponents adds the idea of a connector contract, which is a set of Behaviors.
    Therefore I propose that we leave the text where it is, albeit we should fix the many bugs in it that are the topics of this and other issues.
    However the proposal that kind:ConnectorKind should be derived is entirely sensible, especially since the current constraints on connector kind are the topic of numerous issues (7248-7251).
  • Updated: Sun, 8 Mar 2015 15:08 GMT

7.3.41 Parameter (from Kernel, AssociationClasses)"

  • Key: UML22-1375
  • Legacy Issue Number: 9338
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Please note however, that (as far as I can see) Parameter only occurs in Kernel, NOT in AssociationClasses. So the correct statement would be "Parameter (from Kernel). This might bear a relation to the already existing FTF issue 8117.

  • Reported: UML 2.1 — Mon, 30 Jan 2006 05:00 GMT
  • Disposition: Resolved — UML 2.1.2
  • Disposition Summary:

    This is an exact duplicate of issue 9337 Revised Text: N/A Disposition: Duplicate
  • Updated: Sun, 8 Mar 2015 14:22 GMT

Profiles::ObjectNode has wrong default multiplicity

  • Key: UML22-1374
  • Legacy Issue Number: 8455
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    ObjectNode::upper should have default multiplicity unbounded (“*”) in order of object nodes to be multi-valued by default.

    Recommendation:

    Redefine inherited MultiplicityElement::upper to have default “*” in ObjectNode.
  • Reported: UML 2.1 — Fri, 4 Mar 2005 05:00 GMT
  • Disposition: Resolved — UML 2.1.1
  • Disposition Summary:

    See issue 8454 for disposition
  • Updated: Sun, 8 Mar 2015 14:22 GMT

Section: 12.3.52

  • Key: UML22-1373
  • Legacy Issue Number: 8277
  • Status: closed  
  • Source: U. S. Geological Survey ( Jane Messenger)
  • Summary:

    The association activityScope:Activity[0..1] substes owner as indicated in fit. 195. Add OCL notation to Constraints. Type - lower case the second letter in the second sentence of sub-section Additional Operations.
  • Reported: UML 2.0 — Mon, 14 Feb 2005 05:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    OCL is duplicate with 6346. Subsets addressed in issue 9000.
  • Updated: Sun, 8 Mar 2015 14:18 GMT

Section: Composite Structures/Abstract syntax

  • Key: UML22-1367
  • Legacy Issue Number: 11503
  • Status: closed  
  • Source: Validas AG ( Reinhard Jeschull)
  • Summary:

    There are two diagrams on page 164, 'Connectors' and 'The port metaclass'. The two diagrams are the same. Can you send me the picture of this diagram via e-mail? We need it to create a metamodel.

  • Reported: UML 2.1.1 — Thu, 20 Sep 2007 04:00 GMT
  • Disposition: Resolved — UML 2.1.2
  • Disposition Summary:

    withdrawn, this issue has been resolved
  • Updated: Fri, 6 Mar 2015 22:56 GMT

ptc/06-01-02:14.3.14, Notation

  • Key: UML22-1366
  • Legacy Issue Number: 9606
  • Status: closed  
  • Source: The MathWorks ( Alan Moore)
  • Summary:

    The following notation expression isn’t well formed:

    <interactionconstraint> ::= [‘[‘ (<Boolean-expression’ | ‘else‘) ‘]’]
  • Reported: UML 2.1 — Mon, 24 Apr 2006 04:00 GMT
  • Disposition: Resolved — UML 2.1.1
  • Disposition Summary:

    withdrawn by submitter
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Events

  • Key: UML22-1365
  • Legacy Issue Number: 7638
  • Status: closed  
  • Source: International Business Machines ( Anders Ek)
  • Summary:

    'Events' are in the spec defined as standalone entities using the Trigger concept. In the ongoing FTF work the relation between event and trigger has been changed and the has been changed and there is now an Event metaclass in addition to the existing Trigger class. However, the text does not give any syntax for defining standalone event and it does not state how to refer to an event defined as a standalone entity from e.g. a transition in a statemachine. So two issues: - syntax for standalone events - clarification the how to refer to standalone events from e.g. transitions in statemachines
  • Reported: UML 2.0 — Wed, 18 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Additional events for Interactions

  • Key: UML22-1364
  • Legacy Issue Number: 7637
  • Status: closed  
  • Source: X-Change Technologies and Klocwork ( Joaquin Miller for Nikolai Mansurov)
  • Summary:

    13.1 Overview of Common Behaviors discusses occurrences for which there is no event in the FAS nor in the proposed revision to triggers and events. Figure 307 - Invocation Domain Model shows occurrences of Start, Termination, Trigger, and CallBehavior events. Figure 308 - Communication Domain Model shows occurrences of Invocation and Receiving events. Figure 309 - Domain Model Showing Request Kinds shows occurrences of SendInvocation, CallInvocation, SendRequest, Call Request, Signal, and Call events. These are all discussed in the text, along with occurrences of change and time events. Figure 310 - Domain Model Showing Event Kinds shows two supertypes, for occurrences of Trigger and Spontaneous events. These are discussed in the text. It appears that AcceptEventAction is intended to be used with any kind of event and AcceptCallAction for call request events. [by Nick:] I've reviewed the effects of the proposed alignment of event/occurences/types on Interactions. I believe, the proposed changes will have a very positive effect indeed on making the new Interactions a better part of the overall spec. I would suggest that we do add more subtypes of event in order to have a better match with Interactions: - CreationEvent - DestructionEvent - ExecutionStartEvent - ExecutionFinishEvent

  • Reported: UML 2.0 — Mon, 16 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Incorrect constraints on Pin and ObjectFlow On Pin

  • Key: UML22-1363
  • Legacy Issue Number: 7631
  • Status: closed  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Incorrect constraints on Pin and ObjectFlow On Pin, the constraint isUnique = false introduced by 6090 should be on ObjectNode, and the text should be "Object nodes are not unique typed elements." On ObjectFlow, Constraints (BasicActivities), rule 1 still reflects the time when pins were connected to actions by flows, during the submission process. It should be "Object flows may not have actions at either end.".

  • Reported: UML 2.0 — Sun, 15 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

resolution to issue 6093 removed too much constraint

  • Key: UML22-1362
  • Legacy Issue Number: 7630
  • Status: closed  
  • Source: Universitaet Paderborn ( Jan Hendrik Hausmann)
  • Summary:

    The resolution to issue 6093 removed too much constraint. It should be left in place for decision, merge, and fork nodes.

  • Reported: UML 2.0 — Fri, 13 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Section: 9.3.12

  • Key: UML22-1361
  • Legacy Issue Number: 7613
  • Status: closed  
  • Source: Missouri University of Science and Technology ( Thomas Weigert)
  • Summary:

    The notation for property states that the namestring is as in the Classes chapter, and gives an incorrect chapter number. In fact, the namestring syntax is as for properties in the Classes chapter in Kernel, which should be properly referenced.
  • Reported: UML 2.0 — Tue, 3 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Section: 7.11.4

  • Key: UML22-1360
  • Legacy Issue Number: 7612
  • Status: closed  
  • Source: Missouri University of Science and Technology ( Thomas Weigert)
  • Summary:

    The notation for properties is missing in this section. There are references to examples in other sections, and the notation for AssociationClasses is defined, but there is no notation described for properties
  • Reported: UML 2.0 — Tue, 3 Aug 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    This is a duplicate of issue 7575
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Notation for property has gone missing

  • Key: UML22-1359
  • Legacy Issue Number: 7575
  • Status: closed  
  • Source: Missouri University of Science and Technology ( Thomas Weigert)
  • Summary:

    Notation for property has gone missing. The notation section merely states that "Notation for properties is defined separately for their use as attributes and association ends." Give details for the namestring for attributes and for association ends (the latter is currently described in the association section, but probably should be described in the property section and referenced from the association section). The namestring for attributes is not described at all.

  • Reported: UML 2.0 — Sun, 11 Jul 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

ReadSelfAction

  • Key: UML22-1358
  • Legacy Issue Number: 7562
  • Status: closed  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    ReadSelfAction has the contraint: "The action must be contained in an activity that has a host classifier." On the other hand the semantic section describes: "For activities that have no other context object, the activity itself is the context object." A ReadSelfAction within an activity without a host classifier object returns the activity object. So the constraint is superfluous.
  • Reported: UML 2.0 — Mon, 5 Jul 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    This was fixed as part of 7319.
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Attribute scope is of type StructuredActivityNode instead of StructuredActi

  • Key: UML22-1357
  • Legacy Issue Number: 7554
  • Status: closed  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    Attribute scope is of type StructuredActivityNode instead of StructuredActivityGroup
  • Reported: UML 2.0 — Thu, 1 Jul 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 22:55 GMT

Section: 12.3.16

  • Key: UML22-1356
  • Legacy Issue Number: 7440
  • Status: closed  
  • Source: Silogic ( Yves BERNARD)
  • Summary:

    It's explicitly stated that all tokens within the protected node terminate if an exception isn't caught but nothing is written about how the tokens are managed when the exception is caught, except that the handler will provide the output pins of the protected node. It could implicitly indicate that tokens in the protected nodes are terminated in this case also. Is it right ? Is a semantic variation point?
  • Reported: UML 2.0 — Mon, 7 Jun 2004 04:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    see above