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 |
|
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-1380 |
Section: 7.3.10/Associations |
UML 2.1.2
|
UML 2.2
|
Duplicate or Merged |
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 |
|
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 |
|
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-1142 |
Output tokens |
UML 2.1
|
UML 2.1.1
|
Duplicate or Merged |
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-630 |
UML 2.3: Transitions outgoing junction vertexes should be allowed to have triggers |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-675 |
Modeling sent messages in State Machines |
UML 2.3b1
|
UML 2.5
|
Resolved |
closed |
|
UML25-674 |
TestIdentityAction for datatypes |
FUML 1.0b2
|
UML 2.5
|
Resolved |
closed |
|
UML25-660 |
Behavior should be derived from Classifier, not Class |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-659 |
Package merge on Class metatype causes semantic issues - particularly with state machine context |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-648 |
Error in UML diagrams? |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-647 |
Suggestions for editorial changes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-654 |
how to instantiate associations between stereotypes |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-653 |
Core package caption wrong |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-658 |
Add an example for the lifeline head shape |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-657 |
color of the notation is specified |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-656 |
The property packagedElement: PackageableElement [*] is not a derived property and should not be prefixed with "/" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-655 |
Opposite ends of derived unions should be derived unions |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-651 |
Use of term "locus of control" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-650 |
V2.4.1 from 11-08-05 on page 14 in Figure 7.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-646 |
default is wrong |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-645 |
V2.4.1 from 11-08-05 on page 14 in Figure 7.3 |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-649 |
Reference in index to item that does not exist in contents |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-652 |
incorrect upper value of coveredBy of Lifeline |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-632 |
ChangeEvent association mismatch |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-631 |
EnumerationLiterals in the XMI |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-635 |
"A_realization_abstraction_component" is useless |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-634 |
Subpart I and II are missing in Bookmarks |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-644 |
default value of ClassifierTemplateParameter#allowSubstitutable is "..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-643 |
Figure 15.2 does not include TransitionKind |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-640 |
role "interval" appears "interva" |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-639 |
OpaqueBehavior#body attributes "nonunique" truncated as "nonuni..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-642 |
misspelling: io-oargument |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-641 |
OpaqueBehavior#body attributes "nonunique" truncated as "nonuni..." |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-636 |
RedefinableElement (from Kernel) is preferable |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-633 |
UML Superstructure Specification |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-637 |
poor figure resolution and a misspelling: fal...( false ) |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
UML25-638 |
{ordered} is rather far from +bodyOutput |
UML 2.4.1
|
UML 2.5
|
Resolved |
closed |
|
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-33 |
Expansion nodes using all the tokens in them as a single collection |
FUML 1.0b2
|
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 |
|
UML23-144 |
Section: Classes |
RAS 2.2
|
UML 2.3
|
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-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 |
|
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-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-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-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 |
|
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 |
|
UML22-1 |
Semantics of firing compound transitions still appears to be circular |
UML 1.3
|
UML 2.2
|
Resolved |
closed |
|