| UMLR-845 |
The XMI for the little *Home" example is not well-formed |
UML 2.5.1
|
|
|
open |
|
| UMLR-841 |
Multiplicity of Operation::returnResult() should be [0..1], i.e. not multivalued |
UML 2.5.1
|
|
|
open |
|
| UMLR-842 |
UMLR-673, reported for UML 2.5, still isn't fixed in 2.5.1 |
UML 2.5.1
|
|
|
open |
|
| UMLR-673 |
Spec refers to TypeElement twice. Should be TypedElement |
UML 2.5
|
|
|
open |
|
| UMLR-844 |
Constraint "input" of ParameterSet assumes owner is always a BehavioralFeature |
UML 2.5.1
|
|
|
open |
|
| UMLR-843 |
PropertyTemplateParameter in description of constraint "binding_to_attribute" |
UML 2.5.1
|
|
|
open |
|
| UMLR-840 |
Parameters of a ParameterSet should be ordered |
UML 2.5.1
|
|
|
open |
|
| UMLR-837 |
Suggested improvement to description of "BehavioralFeature::isDistinguishableFrom()" |
UML 2.5.1
|
|
|
open |
|
| UMLR-839 |
Suggestion for improved wording of description for attribute "isDisjoint" |
UML 2.5.1
|
|
|
open |
|
| UMLR-838 |
Allow method bodies for abstract BehavioralFeatures |
UML 2.5.1
|
|
|
open |
|
| UMLR-696 |
The behavior of an OpaqueExpression should be allowed to have input parameters |
UML 2.5
|
|
|
open |
|
| UMLR-836 |
Behavior and ordering of Parameters in OpaqueExpression |
UML 2.5.1
|
|
|
open |
|
| UMLR-835 |
InformationItem specified as a concrete Class, but it is abstract according to its constraint "not_instantiable" |
UML 2.5.1
|
|
|
open |
|
| UMLR-834 |
Grammatical improvement is needed in the descriptions (p. 342) |
UML 2.5.1
|
|
|
open |
|
| UMLR-833 |
Simplification of Stereotypes Usage<--Create and Usage<--Instantiate |
UML 2.5.1
|
|
|
open |
|
| UMLR-832 |
Missing extends arrow in diagram |
UML 2.5.1
|
|
|
open |
|
| UMLR-831 |
Unclear wording about Stereotypes and ownership of their Properties |
UML 2.5.1
|
|
|
open |
|
| UMLR-830 |
Typo in the hyperlink for "Normative URL" |
UML 2.5.1
|
|
|
open |
|
| UMLR-829 |
Missing constraints for class Interval |
UML 2.5.1
|
|
|
open |
|
| UMLR-828 |
TemplateParameter placeholder names? |
UML 2.5.1
|
|
|
open |
|
| UMLR-827 |
UMLR-826 is a non-issue |
UML 2.5.1
|
|
|
open |
|
| UMLR-826 |
Stereotype must be owned by a Profile, but shows composition relationship to Package |
UML 2.5.1
|
|
|
open |
|
| UMLR-825 |
ConnectableElement is not defined until section 11, but Parameter (defined in section 9) inherits ConnectableElement and needs to see its definition |
UML 2.5.1
|
|
|
open |
|
| UMLR-824 |
Suggestion: Generalization::isSubstitutable() should return "Boolean = false" and not "Boolean [0..1]" |
UML 2.5.1
|
|
|
open |
|
| UMLR-823 |
Redundant association from Classifier to NamedElement at bottom of diagram |
UML 2.5.1
|
|
|
open |
|
| UMLR-822 |
Ambiguity of operation "Classifier::general()" and association end "/general" |
UML 2.5.1
|
|
|
open |
|
| UMLR-821 |
Multiplicity of composition/aggregation end for many different elements with {subsets owner} should be 1 and not 0..1 |
UML 2.5.1
|
|
|
open |
|
| UMLR-820 |
Multiplicity of Comment's "owningElement" (composition/aggregation end next to Element) in UML diagram for Root should be 1 and not 0..1 |
UML 2.5.1
|
|
|
open |
|
| UMLR-819 |
missing async Operation call |
UML 2.5.1
|
|
|
open |
|
| UMLR-818 |
wrong definition of partial order |
UML 2.5.1
|
|
|
open |
|
| UMLR-817 |
Misleading sentence about the default history transition |
UML 2.5.1
|
|
|
open |
|
| UMLR-816 |
History Pseudostates should be allowed for top-level regions |
UML 2.5.1
|
|
|
open |
|
| UMLR-815 |
Derived union property values cannot change after initialization |
UML 2.5.1
|
|
|
open |
|
| UMLR-814 |
need to add DataType |
UML 2.5.1
|
|
|
open |
|
| UMLR-811 |
No formal mapping between VisibilityKind and Visibility Symbols |
UML 2.5.1
|
|
|
open |
|
| UMLR-813 |
Inconsistent document structure descriptions in section 6.4 |
UML 2.5.1
|
|
|
open |
|
| UMLR-812 |
Missing dot notation in Abstract Syntax diagrams in Clause 16 Actions |
UML 2.5.1
|
|
|
open |
|
| UMLR-808 |
Wrong cross-reference for RedefinableElement specialisation |
UML 2.5.1
|
|
|
open |
|
| UMLR-685 |
UML 2.5: StateMachine Vertex needs to be made a kind of RedefinableElement instead of State |
UML 2.5
|
|
|
open |
|
| UMLR-810 |
Mis-spelling of redefined property modelElement becomes modeElement |
UML 2.5.1
|
|
|
open |
|
| UMLR-809 |
Many diagram hyperlinks in the Diagrams sections of Classifier Descriptions sections are wrong |
UML 2.5.1
|
|
|
open |
|
| UMLR-807 |
BehavioredClassifier is not shown as a specialisation of Classifier anywhere in the Abstract Syntax |
UML 2.5.1
|
|
|
open |
|
| UMLR-804 |
Link incorrect |
UML 2.5.1
|
|
|
open |
|
| UMLR-802 |
Owner has to do with Namespaces |
UML 2.5.1
|
|
|
open |
|
| UMLR-806 |
Specification inconsistent |
UML 2.5
|
|
|
open |
|
| UMLR-805 |
Possible missing ActivityEdge guard notation example on Figure 15.5; Duplicate ActivityEdge weight on Figure 15.5 and Figure 15.7 |
UML 2.5.1
|
|
|
open |
|
| UMLR-803 |
StateMachine initial transition inconsistency |
UML 2.5.1
|
|
|
open |
|
| UMLR-704 |
Figure 14.44 ProtocolStateMachine example error |
UML 2.5
|
|
|
open |
|
| UMLR-705 |
Meaning of Event on Initial Transition unclear |
UML 2.5
|
|
|
open |
|
| UMLR-801 |
Figure 9.1: duplicate graphical element "NamedElement" |
UML 2.5.1
|
|
|
open |
|
| UMLR-800 |
Typo in caption for figure 14.14 |
UML 2.5.1
|
|
|
open |
|
| UMLR-799 |
Behavioral Classification |
UML 2.5.1
|
|
|
open |
|
| UMLR-757 |
Make AssociationClasses unique again |
UML 2.5
|
|
|
open |
|
| UMLR-443 |
UML 2.5 issue. AssociationClasses should have isUnique property |
UML 2.5b1
|
|
|
open |
|
| UMLR-798 |
Unclear how StateInvariants on a Lifeline identify the next OccurranceSpecification |
UML 2.5.1
|
|
|
open |
|
| UMLR-797 |
unclear whether imported elements are merged by package merge |
UML 2.5.1
|
|
|
open |
|
| UMLR-796 |
MultiplicityElement.isOrdered: Abstract Syntax Metamodel does not match the specification document |
UML 2.5.1
|
|
|
open |
|
| UMLR-795 |
Inheritance of extension not explicitly stated |
UML 2.5.1
|
|
|
open |
|
| UMLR-794 |
Association wrong here |
UML 2.5.1
|
|
|
open |
|
| UMLR-793 |
The last link on the page about Diagram Definition is dead |
UML 2.5.1
|
|
|
open |
|
| UMLR-792 |
Dead URL link for XMI |
UML 2.5.1
|
|
|
open |
|
| UMLR-791 |
https/www.omg.org/spec/UML/ URL is not valid (typo) |
UML 2.5.1
|
|
|
open |
|
| UMLR-790 |
UML::Property.defaultValue has upper multiplicity of 1 even though Property is a MultiplicityElement |
UML 2.5.1
|
|
|
open |
|
| UMLR-789 |
Receptions should be redefinable elements as operations are. |
UML 2.5.1
|
|
|
open |
|
| UMLR-788 |
Inconsistent use of unspecified and unlimited for the multiplicity notation |
UML 2.5.1
|
|
|
open |
|
| UMLR-787 |
There is not a way to do this... |
UML 2.5.1
|
|
|
open |
|
| UMLR-786 |
removeAt_and_value wrong |
UML 2.5.1
|
|
|
open |
|
| UMLR-785 |
Misleading Link |
UML 2.5.1
|
|
|
open |
|
| UMLR-784 |
Include ordering |
UML 2.5.1
|
|
|
open |
|
| UMLR-783 |
need to include setup |
UML 2.5.1
|
|
|
open |
|
| UMLR-782 |
switch LoopNode for ConditionalNode |
UML 2.5.1
|
|
|
open |
|
| UMLR-781 |
" in state name |
UML 2.5.1
|
|
|
open |
|
| UMLR-780 |
Local Transitions conflict |
UML 2.5.1
|
|
|
open |
|
| UMLR-779 |
OCL and Text Mismatch |
UML 2.5.1
|
|
|
open |
|
| UMLR-777 |
Lambda's,Traits and Generics |
UML 2.5.1
|
|
|
open |
|
| UMLR-778 |
Textual "Markdown" visualization |
UML 2.5.1
|
|
|
open |
|
| UMLR-776 |
OCL for excludeCollisions in Namespace element seems incorrect |
UML 2.5.1
|
|
|
open |
|
| UMLR-775 |
An Activity Edge cannot connect to Activities |
UML 2.5.1
|
|
|
open |
|
| UMLR-774 |
Needs to be a constraint between AggregationKind and subsetting |
UML 2.5.1
|
|
|
open |
|
| UMLR-773 |
Please make it clear what is being modeled behind the scenes for figures |
UML 2.5.1
|
|
|
open |
|
| UMLR-759 |
UML Specification "Normative References" uses non-secure links |
UML 2.5
|
|
|
open |
|
| UMLR-772 |
Please provide more detail on redefinition |
UML 2.5.1
|
|
|
open |
|
| UMLR-771 |
UML.xmi is not well-formed |
UML 2.5.1
|
|
|
open |
|
| UMLR-480 |
Can passive classes have ClassifierBehaviors? |
UML 2.4.1
|
|
|
open |
|
| UMLR-770 |
PackageImport Missing for Type Generalization |
UML 2.5.1
|
|
|
open |
|
| UMLR-769 |
Nested Port not supported on Sequence Diagram |
UML 2.5.1
|
|
|
open |
|
| UMLR-768 |
InteractionUse can not reference a CollaborationUse (as shown in Figure 17.24) |
UML 2.5.1
|
|
|
open |
|
| UMLR-767 |
Error in Loop fragment deffinition |
UML 2.5.1
|
|
|
open |
|
| UMLR-766 |
Duplicate section titles |
UML 2.5.1
|
|
|
open |
|
| UMLR-761 |
Property.Association is not a union |
UML 2.5.1
|
|
|
open |
|
| UMLR-765 |
Comments not annotating anything should annotate their owner |
UML 2.5
|
|
|
open |
|
| UMLR-89 |
No way of specifying element documentation |
UML 2.5
|
|
|
open |
|
| UMLR-764 |
Specializations of an Association Class |
UML 2.5.1
|
|
|
open |
|
| UMLR-219 |
UML has no way of distinguishing Notes from Comments |
UML 2.5
|
|
|
open |
|
| UMLR-185 |
Association class notation with just class or association |
UML 2.1.2
|
|
|
open |
|
| UMLR-763 |
Clarify that AcceptEventActions in InterruptibleActivityRegions are disabled when token leaves |
UML 2.5
|
|
|
open |
|
| UMLR-750 |
Description of Generalization of Enumerations is contradictory |
UML 2.5
|
|
|
open |
|
| UMLR-758 |
Duplicated xmi:id values in UML.xmi |
UML 2.5.1
|
|
|
open |
|
| UMLR-756 |
Behavior::behavioredClassifier bodycondition is serialized as a precondition |
UML 2.5.1
|
|
|
open |
|
| UMLR-755 |
Unclear whether current State during Transition is the target State |
UML 2.5.1
|
|
|
open |
|
| UMLR-754 |
Figure 9.11 misses attribute name |
UML 2.5.1
|
|
|
open |
|
| UMLR-753 |
I believe ptc/08-05-12 and ptc/08-05-06 got mixed up on the UML 2.2 specification page |
UML 2.2
|
|
|
open |
|
| UMLR-751 |
The definition of relative Time Events is ambigious |
UML 2.5.1
|
|
|
open |
|
| UMLR-292 |
About behavior ports |
UML 2.5
|
|
|
open |
|
| UMLR-54 |
Operation calls on behavior ports |
UML 2.0
|
|
|
open |
|
| UMLR-107 |
Behavioral port |
UML 2.5
|
|
|
open |
|
| UMLR-749 |
Are null NamedElement::name values names? |
UML 2.5
|
|
|
open |
|
| UMLR-748 |
Thing |
UML 2.5
|
$issue.fixedSpecification.name
|
Deferred |
closed |
|
| UMLR-747 |
Typo |
UML 2.5.1
|
|
|
open |
|
| UMLR-746 |
Figure 7.17 has some trucated labels |
UML 2.5
|
|
|
open |
|
| UMLR-745 |
Typo in last syntax example |
UML 2.5
|
|
|
open |
|
| UMLR-744 |
Attachment point of connectors not specified |
UML 2.5
|
|
|
open |
|
| UMLR-743 |
Implied Multiplicity of the association-like notation should be displayable |
UML 2.5
|
|
|
open |
|
| UMLR-742 |
Lifeline "same_classifier" constraint has an inconsistent specification |
UML 2.5
|
|
|
open |
|
| UMLR-741 |
Are two identical bound templates the same? |
UML 2.5
|
|
|
open |
|
| UMLR-738 |
Incorrect use of multiplicity element. |
UML 2.5
|
|
|
open |
|
| UMLR-620 |
Complete and Covering are Synonyms and used confusinginly |
UML 2.5
|
|
|
open |
|
| UMLR-730 |
Does the abort of an Do/Activity by an incoming event count as a Completion Event |
UML 2.5
|
|
|
open |
|
| UMLR-542 |
Figure 12-15 (MOF Model Equivalent
) p.284 - MOF Model Equivalent navigation and ownership incorrect |
UML 2.4.1
|
|
|
open |
|
| UMLR-234 |
UML Interactions: Misleading suggestion of relationship between Interactions and Activities modeling |
UML 2.5
|
|
|
open |
|
| UMLR-582 |
What is a DurationInterval |
UML 2.4.1
|
|
|
open |
|
| UMLR-584 |
What is a DurationInterval |
UML 2.4.1
|
|
|
open |
|
| UMLR-438 |
Observations in TimeExpressions |
UML 2.5b1
|
|
|
open |
|
| UMLR-450 |
UML 2.5: Time Observation and Duration Observation problem |
UML 2.5b1
|
|
|
open |
|
| UMLR-740 |
DecisionNode is missing a constraint on incoming edges |
UML 2.5
|
|
|
open |
|
| UMLR-437 |
What is the abstract syntax for Figure 17.27? |
UML 2.5b1
|
|
|
open |
|
| UMLR-433 |
What is a UML diagram? is it restricted to showing elements that are instances of the M2 UML metamodel and nothing else? |
UML 2.5b1
|
|
|
open |
|
| UMLR-306 |
How to access a token value in a guard? |
UML 2.5
|
|
|
open |
|
| UMLR-428 |
Guard evaluation with decision input |
UML 2.5b1
|
|
|
open |
|
| UMLR-711 |
Conflicting constraints |
UML 2.5
|
|
|
open |
|
| UMLR-471 |
Allow a notation to allow for a default assignment of a decision to the owner of the activity |
UML 2.5b1
|
|
|
open |
|
| UMLR-528 |
Location: Figure 15-43 ActivityFinalNode example - Balancing Decision / Merge |
UML 2.4.1
|
|
|
open |
|
| UMLR-530 |
Location: Page 413, 15.3.2 Abstract Syntax Control Nodes Figure 15-26 |
UML 2.4.1
|
|
|
open |
|
| UMLR-243 |
Restrictions on decision nodes |
UML 2.5
|
|
|
open |
|
| UMLR-668 |
Unspecified and inconsistent notation for Observations |
UML 2.5
|
|
|
open |
|
| UMLR-737 |
ReturnValueRecipient missing in Metamodel Diagram of InteractionUse |
UML 2.5
|
|
|
open |
|
| UMLR-736 |
Figure 17.20 "InteractionUse with value return" shows incorrect notation |
UML 2.5
|
|
|
open |
|
| UMLR-735 |
Undefined notation for ownedBehaviors in Figures 17.23 and 17.24 |
UML 2.5
|
|
|
open |
|
| UMLR-734 |
Instances are linked to other instances, not associated |
UML 2.5
|
|
|
open |
|
| UMLR-732 |
Odd restriction on state machine redefinition context |
UML 2.5
|
|
|
open |
|
| UMLR-729 |
Clarify diagram notation for collection parameters in operation |
UML 2.5
|
|
|
open |
|
| UMLR-728 |
Transistion selection algorithm is incomplete |
UML 2.5
|
|
|
open |
|
| UMLR-727 |
UML: Missing property subset for StateMachine::extendedStateMachine |
UML 2.5
|
|
|
open |
|
| UMLR-725 |
Nested activities in activity diagrams |
UML 2.5
|
|
|
open |
|
| UMLR-726 |
Template binding relationship incorrect notation |
UML 2.5
|
|
|
open |
|
| UMLR-724 |
bad example for weight in Figure 15.21 |
UML 2.5
|
|
|
open |
|
| UMLR-404 |
ActivityEdge weight examples |
UML 2.5
|
|
|
open |
|
| UMLR-723 |
Implication of weight of ActivityEdge is unclear |
UML 2.5
|
|
|
open |
|
| UMLR-722 |
Conjugated port properties shown on association ends and in compartments |
UML 2.5
|
|
|
open |
|
| UMLR-721 |
Actor Relationships |
UML 2.5
|
|
|
open |
|
| UMLR-720 |
Incorrect arrow heads for object flows |
UML 2.5
|
|
|
open |
|
| UMLR-718 |
Ambiguous meaning of word "composed" |
UML 2.5
|
|
|
open |
|
| UMLR-119 |
Section: Annex A: Diagrams |
UML 2.1.1
|
|
|
open |
|
| UMLR-681 |
ClassB::height missing from diagram |
UML 2.5
|
|
|
open |
|
| UMLR-680 |
Missing interface name in Figure 10.10 ISensor is a required Interface of TheftAlarm |
UML 2.5
|
|
|
open |
|
| UMLR-691 |
Section 14.2.4.4 is not a real section |
UML 2.5
|
|
|
open |
|
| UMLR-677 |
Why is Association.memberEnd ordered? |
UML 2.5b1
|
|
|
open |
|
| UMLR-684 |
Figure 11.23 (and 11.22) should use one brand of tire but show two instead |
UML 2.5
|
|
|
open |
|
| UMLR-690 |
Transition guards should be its own section. |
UML 2.5
|
|
|
open |
|
| UMLR-697 |
UML 2.5: StateMachine Vertex needs to be made a kind of |
UML 2.5
|
|
|
open |
|
| UMLR-702 |
Clarify that deep history uses the same default transition strategy as shallow history |
UML 2.5
|
|
|
open |
|
| UMLR-354 |
State machine semantics for transition between regions of an orthogonal state |
UML 2.4.1
|
|
|
open |
|
| UMLR-717 |
Invalid XMI elements containing both xmi:type and href |
UML 2.5
|
|
|
open |
|
| UMLR-710 |
Missing visibility definition |
UML 2.5
|
|
|
open |
|
| UMLR-716 |
What is a "compound state"? |
UML 2.5
|
|
|
open |
|
| UMLR-715 |
All actions should be able to own control pins |
UML 2.5
|
|
|
open |
|
| UMLR-714 |
Missing Constraint: Associations cannot type StructuralFeatures |
UML 2.5
|
|
|
open |
|
| UMLR-348 |
Actor association constraint makes UseCase subclass of Class |
UML 2.5
|
|
|
open |
|
| UMLR-713 |
On page 290 of UML 2.5 formal/2015-03-01, |
UML 2.5
|
|
|
open |
|
| UMLR-712 |
New Issue on UML 2.5 formal/2015-03-01 re signalbroadcastaction vs. broadcastsignalaction |
UML 2.5
|
|
|
open |
|
| UMLR-92 |
UML/OCL spec mismatch-Constraint.context vs Constraint.constrainedElement |
UML 2.5
|
|
|
open |
|
| UMLR-706 |
What is "a separate InteractionConstraint"? |
UML 2.5
|
|
|
open |
|
| UMLR-703 |
XOR Constraint modeling |
UML 2.5
|
|
|
open |
|
| UMLR-701 |
Inconsistent constraints about several kinds of UML Diagrams |
UML 2.5
|
|
|
open |
|
| UMLR-699 |
Notation of a reception: Keyword <> is superfluous |
UML 2.5
|
$issue.fixedSpecification.name
|
Deferred |
closed |
|
| UMLR-698 |
OpaqueExpression should own Behavior |
UML 2.5
|
|
|
open |
|
| UMLR-627 |
Semantics of Lifeline.selector not clear |
UML 2.5
|
|
|
open |
|
| UMLR-640 |
Notation is depreciated for inherited interface |
UML 2.5
|
|
|
open |
|
| UMLR-692 |
Comment is misleading |
UML 2.5
|
|
|
open |
|
| UMLR-689 |
Mixed plural/singular |
UML 2.5
|
|
|
open |
|
| UMLR-688 |
Plural vs Singulr? |
UML 2.5
|
|
|
open |
|
| UMLR-687 |
Unclear sentence |
UML 2.5
|
|
|
open |
|
| UMLR-686 |
Missing words in sentence |
UML 2.5
|
|
|
open |
|
| UMLR-68 |
reply messages in interactions |
UML 2.5
|
|
|
open |
|
| UMLR-101 |
Subclasses of InstanceSpecification |
UML 2.5
|
|
|
open |
|
| UMLR-112 |
ValueSpecification that refers to some Element shall be defined |
UML 2.5
|
|
|
open |
|
| UMLR-113 |
Ability to define "context specific" default values for Part |
UML 2.5
|
|
|
open |
|
| UMLR-431 |
problems with BehavioralFeature::method |
UML 2.5b1
|
|
|
open |
|
| UMLR-488 |
Interaction parameters. |
UML 2.4.1
|
|
|
open |
|
| UMLR-489 |
How should context be represented? |
UML 2.4.1
|
|
|
open |
|
| UMLR-683 |
Order of example information should be diagram first, then explanation. |
UML 2.5
|
|
|
open |
|
| UMLR-682 |
Link to "see" sections missing |
UML 2.5
|
|
|
open |
|
| UMLR-679 |
AssociationEnd/Attribute redefintion consistency |
UML 2.5
|
|
|
open |
|
| UMLR-678 |
Why is a qualified association qualifier composed by a Property? |
UML 2.5
|
|
|
open |
|
| UMLR-355 |
UML should support proxies for linking models |
UML 2.5
|
|
|
open |
|
| UMLR-676 |
No UML approach to create an infix operator |
UML 2.5
|
|
|
open |
|
| UMLR-674 |
Parameter types required for operation parameters |
UML 2.5
|
|
|
open |
|
| UMLR-329 |
TypeElement / TypedElement typo |
UML 2.5
|
|
|
open |
|
| UMLR-672 |
Constraint TemplateSignature::own_elements too constraining |
UML 2.5
|
|
|
open |
|
| UMLR-671 |
Need example of derived qualifier. |
UML 2.5
|
|
|
open |
|
| UMLR-670 |
The Kind field from frame names should be bold |
UML 2.5
|
|
|
open |
|
| UMLR-659 |
Need BNF for Protocol State Machines Transitions |
UML 2.5
|
|
|
open |
|
| UMLR-669 |
DI refers to putting the Diagram Kind in bold... |
UML 2.5
|
|
|
open |
|
| UMLR-667 |
Package names in wrong location. |
UML 2.5
|
|
|
open |
|
| UMLR-666 |
Sequence Diagram Message Numbers |
UML 2.5
|
|
|
open |
|
| UMLR-35 |
Disjointness should be independent of generalization |
UML 2.0
|
|
|
open |
|
| UMLR-41 |
section 7.3.17 /EnumerationLiteral should not be an InstanceSpecification |
UML 2.5
|
|
|
open |
|
| UMLR-665 |
Impossiblity to specify links for connected roles. |
UML 2.5
|
|
|
open |
|
| UMLR-664 |
Delegation Connector should not be typed |
UML 2.5
|
|
|
open |
|
| UMLR-663 |
Decide whether the document divisions are "sub clauses" or "subclauses" |
UML 2.5
|
|
|
open |
|
| UMLR-662 |
What are the type/classifiers of an InstanceValue |
UML 2.5
|
|
|
open |
|
| UMLR-660 |
Unexpected trigger reception has contradictory results in Protocol State Machines |
UML 2.5
|
|
|
open |
|
| UMLR-661 |
What does calling an "operation for a state" mean in PSM. |
UML 2.5
|
|
|
open |
|
| UMLR-658 |
No notation for associations defined for abstract classes |
UML 2.5
|
|
|
open |
|
| UMLR-202 |
UML:Notational option to display inherited features in a subclass |
UML 2.5
|
|
|
open |
|
| UMLR-657 |
Deploying a «deployment spec» has no explicit interpretation |
UML 2.5
|
|
|
open |
|
| UMLR-656 |
Shoppin->Shopping |
UML 2.5
|
|
|
open |
|
| UMLR-655 |
UML 2.5 refers to EBNF, but the spec uses a variant BNF, not EBNF |
UML 2.5
|
|
|
open |
|
| UMLR-384 |
Classifiers can contain Packages, but they can't have appropriate visibility |
UML 2.5
|
|
|
open |
|
| UMLR-654 |
Pin rectangles in examples should not overlap the action border |
UML 2.5
|
|
|
open |
|
| UMLR-653 |
Activity Generalization is underspecified |
UML 2.5
|
|
|
open |
|
| UMLR-315 |
Rename Specialization/Generalization between abstract classes |
UML 2.5
|
|
|
open |
|
| UMLR-449 |
Contradiction between the abstract syntax and semantics of an Interval |
UML 2.5b1
|
|
|
open |
|
| UMLR-652 |
In Sequence diagrams, the duration constraint shown as a vertical two-headed is ambiguous |
UML 2.5
|
|
|
open |
|
| UMLR-651 |
In the time-related syntax for Sequence diagrams, there are used two terms (now, duration). Are there more? Are these defined? |
UML 2.5
|
|
|
open |
|
| UMLR-650 |
It doesn't seem possible to use a time-based trigger in the alternate format transition-focused state machine. |
UML 2.5
|
|
|
open |
|
| UMLR-649 |
Use of decomposition indicator |
UML 2.5
|
|
|
open |
|
| UMLR-648 |
InstanceSpecification for a qualified Property |
UML 2.5
|
|
|
open |
|
| UMLR-646 |
Recursive use of Interaction Use |
UML 2.5
|
|
|
open |
|
| UMLR-647 |
Limitation on isDimension Partition to be uncontained appears unwarranted |
UML 2.5
|
|
|
open |
|
| UMLR-645 |
Classifier.allSlottableFeatures shall incorporate redefinition |
UML 2.5
|
|
|
open |
|
| UMLR-643 |
Location of owning fully qualifed name not specified. |
UML 2.5
|
|
|
open |
|
| UMLR-642 |
Clarify the difference between «create» and «instantiate» |
UML 2.5
|
|
|
open |
|
| UMLR-641 |
Missing parameter properties of stream and exception in BNF |
UML 2.5
|
|
|
open |
|
| UMLR-637 |
What is the order for EnumerationLiterals? |
UML 2.5
|
|
|
open |
|
| UMLR-639 |
Wrong expression for dipicting package merge process? |
UML 2.5
|
|
|
open |
|
| UMLR-638 |
Inconsistency in constraints and rules for property merge |
UML 2.5
|
|
|
open |
|
| UMLR-636 |
How to deal with guard in Transition redefinition? |
UML 2.5
|
|
|
open |
|
| UMLR-635 |
Typing error in figure 9.11 |
UML 2.5
|
|
|
open |
|
| UMLR-634 |
Wrong figure referrence in text |
UML 2.5
|
|
|
open |
|
| UMLR-633 |
Computation error for the example of ReduceAction |
UML 2.5
|
|
|
open |
|
| UMLR-631 |
UML 2: Lifeline should be made a TemplateableElement |
UML 2.5
|
|
|
open |
|
| UMLR-630 |
Semantics of UnlimitedNatural in notation section. |
UML 2.5
|
|
|
open |
|
| UMLR-629 |
Matching between '+-#~' in Property's and "public-private-protected-package" is not described |
UML 2.5
|
|
|
open |
|
| UMLR-628 |
Constraint wording implies aggregation is only for associations |
UML 2.5
|
|
|
open |
|
| UMLR-626 |
Need to constrain where triggers can be put in state machines |
UML 2.5
|
|
|
open |
|
| UMLR-625 |
Missing: how +-#~ symbols map to VisibilityKind |
UML 2.5
|
|
|
open |
|
| UMLR-624 |
Example for association-like notation for attribute contradicts description. |
UML 2.5
|
|
|
open |
|
| UMLR-623 |
In OCL, the use of ::_'in' appears unwarranted |
UML 2.5
|
|
|
open |
|
| UMLR-622 |
Define well-formed/ill-formed |
UML 2.5
|
|
|
open |
|
| UMLR-621 |
Clarify Property Qualifiers with a full Example |
UML 2.5
|
|
|
open |
|
| UMLR-619 |
Class.isAbstract attribute is not necessary |
UML 2.5
|
|
|
open |
|
| UMLR-429 |
Missing glossary |
UML 2.5b1
|
|
|
open |
|
| UMLR-420 |
Multiplicity of opposite end of a number of associations from various action metaclasses |
UML 2.5
|
|
|
open |
|
| UMLR-618 |
isDirectlyInstantiated is defined in reverse |
UML 2.5
|
|
|
open |
|
| UMLR-427 |
7.2.3, last sentence 2nd paragraph the revised text |
UML 2.5b1
|
|
|
open |
|
| UMLR-328 |
NamedElement::allNamespaces is invalid at model root |
UML 2.5
|
|
|
open |
|
| UMLR-351 |
Section 15.5.3: a missed word |
UML 2.5
|
|
|
open |
|
| UMLR-617 |
Location: 18.1.5 Examples Figure 18-2. 689 - Explain about Navigation |
UML 2.4.1
|
|
|
open |
|
| UMLR-616 |
UML 2.5: UML redefinition mechanism insufficiently granular |
UML 2.5
|
|
|
open |
|
| UMLR-505 |
Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - Need stricter limit on associations |
UML 2.1.2
|
|
|
open |
|
| UMLR-504 |
Location: 18.2 Classifier Descriptions Extend Constraints. 695 - Constraint is overly restrictive |
UML 2.4.1
|
|
|
open |
|
| UMLR-502 |
Location: 18.1.4 Notation P. 688 - Can Use Cases have attributes and operations? |
UML 2.4.1
|
|
|
open |
|
| UMLR-503 |
Location: 18.2 Classifier Descriptions Use Case Constraints. 697 - Need stricter limit on associations (02) |
UML 2.1.2
|
|
|
open |
|
| UMLR-496 |
Location: Figure A.5 P. 734 - Use Cases are not behavior diagrams |
UML 2.4.1
|
|
|
open |
|
| UMLR-497 |
Location: Appendix A, list of frame names, p 734 - List of Namespaces suitable for diagram headers is overly restrictive |
UML 2.4.1
|
|
|
open |
|
| UMLR-500 |
Location: 18.1.1 Summary p 685 - Bases of specialized stereotypes |
UML 2.4.1
|
|
|
open |
|
| UMLR-501 |
Location: 19.5 Classifier Descriptions Deployment Specification Attributes P. 711 - Why a multiplicity of [0..1] |
UML 2.4.1
|
|
|
open |
|
| UMLR-498 |
Location: 22.3 Standard Stereotypes «Metamodel» p. 731 - «Subsystem» should be allowed for more classifiers |
UML 2.4.1
|
|
|
open |
|
| UMLR-499 |
Location: 19.5 Node Association Ends Node P. 714 - Shared ownership of nodes |
UML 2.4.1
|
|
|
open |
|
| UMLR-506 |
Location: 18.2 Classifier Descriptions Extend Constraints. 695 - Extensions must be a DAG |
UML 2.4.1
|
|
|
open |
|
| UMLR-495 |
Location: Figure B.3. 737 - A diagram is a PackageableElement |
UML 2.4.1
|
|
|
open |
|
| UMLR-568 |
Reword isComputable |
UML 2.4.1
|
|
|
open |
|
| UMLR-569 |
Location: 8.6 p 98 TimeObservation ...simplify |
UML 2.4.1
|
|
|
open |
|
| UMLR-576 |
Too many alls |
UML 2.4.1
|
|
|
open |
|
| UMLR-575 |
Intended to Produce |
UML 2.4.1
|
|
|
open |
|
| UMLR-577 |
Bad Description, observation has no value |
UML 2.4.1
|
|
|
open |
|
| UMLR-580 |
Like to overridden definition |
UML 2.4.1
|
|
|
open |
|
| UMLR-573 |
Why cant the operand be a stringExpression |
UML 2.4.1
|
|
|
open |
|
| UMLR-578 |
Range Confusion |
UML 2.4.1
|
|
|
open |
|
| UMLR-570 |
Simplify (Location: 8.6 p 97 TimeExpression) |
UML 2.4.1
|
|
|
open |
|
| UMLR-574 |
Bad Description |
UML 2.4.1
|
|
|
open |
|
| UMLR-571 |
Simplify |
UML 2.4.1
|
|
|
open |
|
| UMLR-572 |
What incompatible about sub-expressions and operands |
UML 2.4.1
|
|
|
open |
|
| UMLR-434 |
PrimitiveTypes::Real is inconsistently specified relative to its mapping to xsd:double |
UML 2.5b1
|
|
|
open |
|
| UMLR-436 |
No explanation of how to deal with conflicting transitions of equal priority |
UML 2.5b1
|
|
|
open |
|
| UMLR-435 |
Definition of allOwningPackages() |
UML 2.5b1
|
|
|
open |
|
| UMLR-430 |
Several UMLDI redefining associations are invalid |
UML 2.5b1
|
|
|
open |
|
| UMLR-442 |
UseCases: Explanation of words fragment and increment |
UML 2.5b1
|
|
|
open |
|
| UMLR-445 |
Behavior does not override NamedElement::isDistinguishableFrom() like BehavioralFeature does |
UML 2.5b1
|
|
|
open |
|
| UMLR-426 |
Uml2.5 issue - constraints of Behavior incorrectly assume context is always non-null |
UML 2.5b1
|
|
|
open |
|
| UMLR-432 |
Add condition : Constraint[0..1] to the include relationship |
UML 2.4.1
|
|
|
open |
|
| UMLR-439 |
Timing Events Question / Issue |
UML 2.5b1
|
|
|
open |
|
| UMLR-441 |
The notation for ExtensionPoint provides for an explanation, but the metamodel provides nowhere to store it. |
UML 2.5b1
|
|
|
open |
|
| UMLR-440 |
UseCases: no way for an Extend to pick out individual ownedBehaviors of the extending UseCase |
UML 2.5b1
|
|
|
open |
|
| UMLR-595 |
Definition of invariant condition |
UML 2.4.1
|
|
|
open |
|
| UMLR-597 |
Section Unbalanced |
UML 2.4.1
|
|
|
open |
|
| UMLR-592 |
Need table correlating Literals with symbols (+,-,#,~) |
UML 2.4.1
|
|
|
open |
|
| UMLR-593 |
Inconsistent use of (s) |
UML 2.4.1
|
|
|
open |
|
| UMLR-601 |
Section 11.7 has no content or notation for template Collaborations Clause - 11: Structured Classifiers |
UML 2.4.1
|
|
|
open |
|
| UMLR-603 |
Section 11.3.4 isService clarification - Clause 11: Structured Classifiers |
UML 2.4.1
|
|
|
open |
|
| UMLR-596 |
Descendants rather than specializations |
UML 2.4.1
|
|
|
open |
|
| UMLR-602 |
Section 11.2.4 clarification - Clause 11: Structured Classifiers |
UML 2.4.1
|
|
|
open |
|
| UMLR-600 |
List attributes whose ordered property has change in UML 2.5 |
UML 2.4.1
|
|
|
open |
|
| UMLR-598 |
Bound Element Semantics overly specific |
UML 2.4.1
|
|
|
open |
|
| UMLR-599 |
UML 2.5 FTF issues for Clause 18: UseCases |
UML 2.4.1
|
|
|
open |
|
| UMLR-594 |
Template Notation example |
UML 2.4.1
|
|
|
open |
|
| UMLR-615 |
Clarification on the semantics of CommunicationPath |
UML 2.4.1
|
|
|
open |
|
| UMLR-614 |
isIntegral() |
UML 2.4.1
|
|
|
open |
|
| UMLR-613 |
Capitalization of dependency |
UML 2.4.1
|
|
|
open |
|
| UMLR-470 |
Profile: can a stereotype extend fewer metaclasses than another stereotype it specializes? |
UML 2.5b1
|
|
|
open |
|
| UMLR-469 |
Clarification re MOF Equivalent Semantics about defining/applying a stereotype to a slot of ininstance of a stereotype |
UML 2.5b1
|
|
|
open |
|
| UMLR-476 |
Node::nestedNode should subset Class::nestedClassifier, not Namespace::ownedMember. |
UML 2.4.1
|
|
|
open |
|
| UMLR-477 |
Meaning of State in ProtocolStateMachines |
UML 2.4.1
|
|
|
open |
|
| UMLR-479 |
Should completion event be an explicit event type? |
UML 2.4.1
|
|
|
open |
|
| UMLR-481 |
Not clear if else keyword is defined for State Machines |
UML 2.4.1
|
|
|
open |
|
| UMLR-482 |
State of the substates of the history state |
UML 2.4.1
|
|
|
open |
|
| UMLR-475 |
UML: No restrictions on what seem to be meaningless associations |
UML 2.5b1
|
|
|
open |
|
| UMLR-473 |
It is a pity that UML does not provide the ability for Messages to correspond directly to property accesses and updates |
UML 2.4.1
|
|
|
open |
|
| UMLR-472 |
Need packages overview diagram and explicit depiction of package dependencies |
UML 2.5b1
|
|
|
open |
|
| UMLR-474 |
Meaning of absent multiplicity notation |
UML 2.4.1
|
|
|
open |
|
| UMLR-478 |
Figure 14.39 missing superclass |
UML 2.4.1
|
|
|
open |
|
| UMLR-517 |
Not clear when to use ExecutionOccurrenceSpecification with ExecutionSpecification |
UML 2.4.1
|
|
|
open |
|
| UMLR-518 |
Location: Pg. 617, Figure 17.4.4: Notation, Sub-clause: Message |
UML 2.4.1
|
|
|
open |
|
| UMLR-508 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - No Alternative Path |
UML 2.4.1
|
|
|
open |
|
| UMLR-509 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - First ExtensionPoint |
UML 2.4.1
|
|
|
open |
|
| UMLR-513 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - What classifiers can be a subject? |
UML 2.4.1
|
|
|
open |
|
| UMLR-516 |
Location: 18. Global - No discussion of use case instances |
UML 2.4.1
|
|
|
open |
|
| UMLR-511 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Multiplicity at Use Case end |
UML 2.4.1
|
|
|
open |
|
| UMLR-510 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Show name of extension |
UML 2.4.1
|
|
|
open |
|
| UMLR-514 |
Location:Page #640, 17.8.2 Example Sequence Diagram |
UML 2.4.1
|
|
|
open |
|
| UMLR-512 |
Location: 18.1.3 Semantics Use Cases and Actors P. 686 - Multiple subjects require the same actors |
UML 2.4.1
|
|
|
open |
|
| UMLR-507 |
18.1.3 Semantics Use Case and Actors Extends P. 687 - Single Location |
UML 2.4.1
|
|
|
open |
|
| UMLR-515 |
Location: weak sequencing p. 622 |
UML 2.4.1
|
|
|
open |
|
| UMLR-585 |
What is a DurationConstaint |
UML 2.4.1
|
|
|
open |
|
| UMLR-586 |
Time constant |
UML 2.4.1
|
|
|
open |
|
| UMLR-579 |
More detail on Express |
UML 2.4.1
|
|
|
open |
|
| UMLR-590 |
Expression examples unclear |
UML 2.4.1
|
|
|
open |
|
| UMLR-588 |
OCL not indexed |
UML 2.4.1
|
|
|
open |
|
| UMLR-591 |
Semantics Clarification |
UML 2.4.1
|
|
|
open |
|
| UMLR-587 |
Event |
UML 2.4.1
|
|
|
open |
|
| UMLR-581 |
incompatible multiplicities |
UML 2.4.1
|
|
|
open |
|
| UMLR-583 |
one -- > first |
UML 2.4.1
|
|
|
open |
|
| UMLR-589 |
Orphan Title |
UML 2.4.1
|
|
|
open |
|
| UMLR-425 |
typo in 12.2.3 Model |
UML 2.5b1
|
|
|
open |
|
| UMLR-521 |
Location: Pg. 613, Figure 17.6 - : Incorrect multiplicities in the metamodel in Figure 17.6 |
UML 2.4.1
|
|
|
open |
|
| UMLR-522 |
Location: p 611 |
UML 2.4.1
|
|
|
open |
|
| UMLR-524 |
Not clear when to use ExecutionOccurrenceSpecification with ExecutionSpecification |
UML 2.4.1
|
|
|
open |
|
| UMLR-529 |
Location p413 Final Node - Rollback behavior |
UML 2.4.1
|
|
|
open |
|
| UMLR-532 |
Location p413 Final Node - Atomic behavior |
UML 2.4.1
|
|
|
open |
|
| UMLR-519 |
Location: 17.3.4 Notation Lifeline p 613 - Specification of color |
UML 2.4.1
|
|
|
open |
|
| UMLR-520 |
Location: Pg. 613, Figure 17.6 - Incorrect multiplicities in the metamodel in Figure 17.6 |
UML 2.4.1
|
|
|
open |
|
| UMLR-525 |
Interactions p 607 |
UML 2.4.1
|
|
|
open |
|
| UMLR-523 |
Location: 16.2.3 Semantics / Opaque Actions |
UML 2.4.1
|
|
|
open |
|
| UMLR-527 |
Location: Figure 15.67 page 436 |
UML 2.4.1
|
|
|
open |
|
| UMLR-526 |
Location: p 504 - Marshall Actions |
UML 2.4.1
|
|
|
open |
|
| UMLR-606 |
Inconsistent approach to type conformance |
UML 2.5b1
|
|
|
open |
|
| UMLR-608 |
Issue for UML 2.5 FTF against Clause 9: Classifiers |
UML 2.4.1
|
|
|
open |
|
| UMLR-604 |
"Object identity" undefined |
UML 2.5b1
|
|
|
open |
|
| UMLR-605 |
Consistent use of "conforms to" vs. "is a subtype of" |
UML 2.5b1
|
|
|
open |
|
| UMLR-455 |
Notation for Variables and Variable Actions is very vague and incomplete |
UML 2.5b1
|
|
|
open |
|
| UMLR-452 |
Rg. Realization and InterfaceRealization |
UML 2.5b1
|
|
|
open |
|
| UMLR-444 |
Clarification needed about the semantics of stereotype specialization and stereotype application |
UML 2.5b1
|
|
|
open |
|
| UMLR-451 |
Issue for Figure 17.18 |
UML 2.5b1
|
|
|
open |
|
| UMLR-448 |
Clarification about Interactions owning Actions and about the semantics of Actions owned by Interactions |
UML 2.5b1
|
|
|
open |
|
| UMLR-453 |
[UML 2.5] Redundancy in the definition of use case extensions |
UML 2.5b1
|
|
|
open |
|
| UMLR-456 |
Issue with Reply message in interactions (UML 2.5 Beta) |
UML 2.5b1
|
|
|
open |
|
| UMLR-447 |
Incorrect notation in figure 14.37 |
UML 2.5b1
|
|
|
open |
|
| UMLR-446 |
Shouldn't Gate and InteractionFragment be redefinable to support Interaction specialization? |
UML 2.5b1
|
|
|
open |
|
| UMLR-454 |
UML 2.5 - figures 14.37 and 14.38 use incorrect notation for keyword |
UML 2.5b1
|
|
|
open |
|
| UMLR-557 |
Location: Page 265, 12.2.3 Semantics - Unchanged URIs |
UML 2.4.1
|
|
|
open |
|
| UMLR-555 |
Location: 12.2.3 Semantics Package p 265 - Reference to unknown section heading |
UML 2.4.1
|
|
|
open |
|
| UMLR-566 |
Location: 9.6.4 Notation p 127 Missing Infix operation syntax / discussion |
UML 2.4.1
|
|
|
open |
|
| UMLR-567 |
ParameterSet Notation |
UML 2.4.1
|
|
|
open |
|
| UMLR-561 |
Location: constraints class_behavior p.190 |
UML 2.4.1
|
|
|
open |
|
| UMLR-562 |
Location 10.3.3 Receptions p.186 - exceptions for receptions? |
UML 2.4.1
|
|
|
open |
|
| UMLR-563 |
p 118: isException and other outputs |
UML 2.4.1
|
|
|
open |
|
| UMLR-560 |
Location: Constraints p 193 - All feturs must be public? |
UML 2.4.1
|
|
|
open |
|
| UMLR-564 |
Location p 162 ParameterSet associationends: Exceptions and parametersets |
UML 2.4.1
|
|
|
open |
|
| UMLR-558 |
Location: 12.1 Packages Summary p 264 |
UML 2.4.1
|
|
|
open |
|
| UMLR-559 |
Location: Figure 11-5 (ii) p 204 |
UML 2.4.1
|
|
|
open |
|
| UMLR-565 |
Query of alternative scopes? |
UML 2.4.1
|
|
|
open |
|
| UMLR-486 |
Problems with XMI IDs in the UML 2.5 UML.xmi file |
UML 2.4.1
|
|
|
open |
|
| UMLR-487 |
17 Semantics of interactions |
UML 2.4.1
|
|
|
open |
|
| UMLR-490 |
UML Interactions do not provide the ability for Messages to correspond directly to property accesses and updates |
UML 2.4.1
|
|
|
open |
|
| UMLR-493 |
Location: B.6 UML ProfileDiagrams . 768 - Profile Diagram Elements |
UML 2.4.1
|
|
|
open |
|
| UMLR-492 |
Location: B.6 UMLClass Diagram P. 757 - Class namespace diagrams? |
UML 2.4.1
|
|
|
open |
|
| UMLR-483 |
Overriding deferred events |
UML 2.4.1
|
|
|
open |
|
| UMLR-484 |
Stable state not needed |
UML 2.4.1
|
|
|
open |
|
| UMLR-491 |
Location: Annex C Keywords P. 778 - Inconsistent metaclass keywords |
UML 2.4.1
|
|
|
open |
|
| UMLR-485 |
Default entry if default history transition missing |
UML 2.4.1
|
|
|
open |
|
| UMLR-494 |
Location: B.2.2 P. 738 - What ISO document |
UML 2.4.1
|
|
|
open |
|
| UMLR-549 |
Location: Page 270/271, 12.2.3 Semantics - Model description confusing |
UML 2.4.1
|
|
|
open |
|
| UMLR-550 |
Location: Page 269, 12.2.3 Semantics - Association merge aggregation constraint is property rule |
UML 2.4.1
|
|
|
open |
|
| UMLR-545 |
Location: Page 286, 12.3.3 Semantics - Incorrect if statement |
UML 2.4.1
|
|
|
open |
|
| UMLR-544 |
Location: Page 285, 12.3.3 Semantics - Old behavior unnecessarily preserved |
UML 2.4.1
|
|
|
open |
|
| UMLR-552 |
Page 269, 12.2.3 Semantics - Property merge transformation conflicts with constrain |
UML 2.4.1
|
|
|
open |
|
| UMLR-553 |
Location: Page 267, 12.2.3 Semantics - Type and TypedElement confusion |
UML 2.4.1
|
|
|
open |
|
| UMLR-556 |
Location: Page 265, 12.2.3 Semantics PackageMerge - Long-winded package merge description |
UML 2.4.1
|
|
|
open |
|
| UMLR-546 |
Location: Page 281, 12.3.3 Semantics - Duplicated text |
UML 2.4.1
|
|
|
open |
|
| UMLR-554 |
Page 266, 12.2.3 Semantics - Un-matched resulting elements aren't always the same |
UML 2.4.1
|
|
|
open |
|
| UMLR-548 |
Location: Page 280, 12.3.3 Semantics - Note should be main text |
UML 2.4.1
|
|
|
open |
|
| UMLR-551 |
Location: Page 269, 12.2.3 Semantics - Property merge rule pointless |
UML 2.4.1
|
|
|
open |
|
| UMLR-547 |
Location: Page 280, 12.3.3 Semantics - Poorly indented XMI |
UML 2.4.1
|
|
|
open |
|
| UMLR-460 |
UML2.5: Clarification about UML profiles |
UML 2.5b1
|
|
|
open |
|
| UMLR-458 |
Serilaization of required stereotypes |
UML 2.5b1
|
|
|
open |
|
| UMLR-459 |
Reply messages now mandatory? |
UML 2.5b1
|
|
|
open |
|
| UMLR-466 |
Semantics of TimeConstraints and DurationConstraints |
UML 2.5b1
|
|
|
open |
|
| UMLR-461 |
Notation for DurationObservation with two event elements |
UML 2.5b1
|
|
|
open |
|
| UMLR-464 |
Semantics of Namespaces |
UML 2.5b1
|
|
|
open |
|
| UMLR-467 |
Stereotype for extended bound element realization |
UML 2.5b1
|
|
|
open |
|
| UMLR-462 |
Interactions and parameter assignments |
UML 2.5b1
|
|
|
open |
|
| UMLR-468 |
Please provide running footers or headers indicating the section/subsection of a page |
UML 2.5b1
|
|
|
open |
|
| UMLR-463 |
Semantics of Message argument mapping in Interactions |
UML 2.5b1
|
|
|
open |
|
| UMLR-457 |
UML2.5 issue: constraints needed in model of Standard Profile |
UML 2.5b1
|
|
|
open |
|
| UMLR-465 |
Meaning of access to constrainedElements |
UML 2.5b1
|
|
|
open |
|
| UMLR-543 |
Location: Page 286, 12.3.3 Semantics - Nonsensical alternative to stereotype name |
UML 2.4.1
|
|
|
open |
|
| UMLR-531 |
Location: p 410 |
UML 2.4.1
|
|
|
open |
|
| UMLR-537 |
Location: Page 328, 14.2.3 - UseCase cannot be the context of a StateMachine |
UML 2.4.1
|
|
|
open |
|
| UMLR-536 |
Location: Signal Receipt symbol |
UML 2.4.1
|
|
|
open |
|
| UMLR-534 |
Location: Page 346, State List Notations - Why must state lists be effect free? |
UML 2.4.1
|
|
|
open |
|
| UMLR-538 |
Location: 13.3.5 Examples p 314 |
UML 2.4.1
|
|
|
open |
|
| UMLR-540 |
Location: Opaque and Function Behaviors p 308 |
UML 2.4.1
|
|
|
open |
|
| UMLR-533 |
Location: p. 336 Compound transitions - Run-to-completion Paradigm |
UML 2.4.1
|
|
|
open |
|
| UMLR-539 |
Location: Page 316 redefinedBehavior - Extends |
UML 2.4.1
|
|
|
open |
|
| UMLR-535 |
Location: Page 331 deep history entry - Default deep history entry |
UML 2.4.1
|
|
|
open |
|
| UMLR-541 |
Location: Figure 12-13 p.281 - Incorrect use of << for «. |
UML 2.4.1
|
|
|
open |
|
| UMLR-347 |
UML 2.5 Beta 2 XMI invalid |
UML 2.5
|
|
|
open |
|
| UMLR-610 |
How to model a transition to history pseudostates in two orthogonal regions? |
UML 2.4.1
|
|
|
open |
|
| UMLR-612 |
Clarification on the semantics of inheritance between use cases |
UML 2.4.1
|
|
|
open |
|
| UMLR-607 |
Clarify aliasing in Namespaces |
UML 2.5b1
|
|
|
open |
|
| UMLR-609 |
Clarify ownership vs. membership for NamedElements |
UML 2.5b1
|
|
|
open |
|
| UMLR-611 |
Fuzzy diagrams |
UML 2.5b1
|
|
|
open |
|
| UMLR-421 |
Missing Example of TemplateBinding with model element "Class" |
UML 2.5b1
|
|
|
open |
|
| UMLR-415 |
Object Flow arrow heads are inconsistent: V-shaped vs triangular |
UML 2.5
|
|
|
open |
|
| UMLR-410 |
More on SateMachines |
UML 2.5
|
|
|
open |
|
| UMLR-409 |
Figure 14.5 State with Compartments does not show all the compartments that it should |
UML 2.5
|
|
|
open |
|
| UMLR-408 |
BNF notation as given and used is unclear about italics |
UML 2.5
|
|
|
open |
|
| UMLR-407 |
Figure 14.14 includes a "Submachine Sate" |
UML 2.5
|
|
|
open |
|
| UMLR-418 |
InformatonFlows are constrained to be Classes or Classifiers -- which one? |
UML 2.5
|
|
|
open |
|
| UMLR-417 |
Are DeploymentSpecification execution-time input to components -- meaning they are somehow read by the component while they are running/executng? |
UML 2.5
|
|
|
open |
|
| UMLR-416 |
Can be performed their instances --> missing "by" |
UML 2.5
|
|
|
open |
|
| UMLR-413 |
A State can only have one Do/ behavior, but example shows more than one. |
UML 2.5
|
|
|
open |
|
| UMLR-412 |
Some hyperlinks are underlined and some are not. This is inconsistent |
UML 2.5
|
|
|
open |
|
| UMLR-424 |
UML 2.5: Property::isConsistentWith() error |
UML 2.5
|
|
|
open |
|
| UMLR-423 |
UML 2.5 beta issue - Operation notation is wrong |
UML 2.5b1
|
|
|
open |
|
| UMLR-422 |
UML2::Constraint |
UML 2.2
|
|
|
open |
|
| UMLR-411 |
These are typographical errors |
UML 2.5
|
|
|
open |
|
| UMLR-403 |
Shouldn't it be possible to make the state of an object be private to support encapsulation/information hiding?. |
UML 2.5
|
|
|
open |
|
| UMLR-402 |
States of Reachable objects may be used in guard constraints, but reachable is not defined |
UML 2.5
|
|
|
open |
|
| UMLR-414 |
Any Activity parameter is steaming. It must be too hot to handle |
UML 2.5
|
|
|
open |
|
| UMLR-405 |
adding error |
UML 2.5
|
|
|
open |
|
| UMLR-401 |
orthogonal State missing on bullet point list |
UML 2.5
|
|
|
open |
|
| UMLR-391 |
Use of Qualifier and Qualified in same section of UML 2.5 spec should be more clearly disambiguated |
UML 2.5
|
|
|
open |
|
| UMLR-386 |
UML needs standardized default package (or Model) |
UML 2.5
|
|
|
open |
|
| UMLR-387 |
shoes-->shows |
UML 2.5
|
|
|
open |
|
| UMLR-380 |
In Sequence diagrams it is unclear if the name of the Gate can be different from the name of the message |
UML 2.5
|
|
|
open |
|
| UMLR-361 |
Inconsistent use of Oxford comma in "Behavior, Event, and Trigger" |
UML 2.5
|
|
|
open |
|
| UMLR-358 |
AcceptEventActions where the triggers are all for ChangeEvents or CallEvents should allow output ControlPins |
UML 2.5
|
|
|
open |
|
| UMLR-360 |
Minor error in ptc-13-09-05 |
UML 2.5
|
|
|
open |
|
| UMLR-352 |
Pin multiplicity and token upper bound |
UML 2.5
|
|
|
open |
|
| UMLR-346 |
Classifier::ownedTemplateSignature needs to subset Element::ownedElement |
UML 2.5
|
|
|
open |
|
| UMLR-345 |
Issue against UML: implementation of OCL constraint containingProfile |
UML 2.5
|
|
|
open |
|
| UMLR-344 |
No specification of which visibility marking corresponds to which VisibilityKind value |
UML 2.5
|
|
|
open |
|
| UMLR-340 |
ExpansionNodes owned by ExpansionRegions? |
UML 2.5
|
|
|
open |
|
| UMLR-339 |
Incorrect sentence |
UML 2.5b1
|
|
|
open |
|
| UMLR-342 |
BehavioralParameter should be BehavioralFeature |
UML 2.5
|
|
|
open |
|
| UMLR-341 |
UML wording in Superstructure 2.4.1 |
UML 2.5
|
|
|
open |
|
| UMLR-337 |
Message should extend Namespace |
UML 2.5
|
|
|
open |
|
| UMLR-343 |
Semantics of static features |
UML 2.5
|
|
|
open |
|
| UMLR-338 |
Incomplete sentence |
UML 2.5b1
|
|
|
open |
|
| UMLR-305 |
Rg. Reception.ownedParameter |
UML 2.5
|
|
|
open |
|
| UMLR-308 |
Generalization should be limited to relate similar UML-elements |
UML 2.5
|
|
|
open |
|
| UMLR-307 |
Type conformance for classifiers |
UML 2.5
|
|
|
open |
|
| UMLR-300 |
Notation for PrimitiveTypes |
UML 2.5
|
|
|
open |
|
| UMLR-299 |
Problems with normative UML 2.5 Beta 2 Standard profile |
UML 2.5
|
|
|
open |
|
| UMLR-304 |
Descriptions missing for PseudostateKind literals |
UML 2.5
|
|
|
open |
|
| UMLR-303 |
Clause 21 Primitive Types is misnamed |
UML 2.5
|
|
|
open |
|
| UMLR-298 |
Problem with NamedElement::clientDependency subsets in UML 2.5 Beta 2 |
UML 2.5
|
|
|
open |
|
| UMLR-301 |
Can PrimitiveTypes be user-defined and where? |
UML 2.5
|
|
|
open |
|
| UMLR-302 |
A PrimitiveType can/cannot have owned attributes. |
UML 2.5
|
|
|
open |
|
| UMLR-310 |
InstanceSpecification validity is not modelable |
UML 2.5
|
|
|
open |
|
| UMLR-309 |
Missing OpaqueXXX body constraint |
UML 2.5
|
|
|
open |
|
| UMLR-259 |
UML Appendix A: After Figure A.4 |
UML 2.5
|
|
|
open |
|
| UMLR-258 |
UML: unification of OCL declarations |
UML 2.5
|
|
|
open |
|
| UMLR-260 |
Clarification about serializing the application of SysML 1.3 to a UML2.4.1 model |
UML 2.5
|
|
|
open |
|
| UMLR-264 |
OccurrenceSpecification should have at least an optional notation |
UML 2.4
|
|
|
open |
|
| UMLR-262 |
Message arguments for a Signal signature too restrictive |
UML 2.4
|
|
|
open |
|
| UMLR-261 |
Relation of message arguments to signature parameters ambiguous |
UML 2.4
|
|
|
open |
|
| UMLR-265 |
The included use case is always required for the including use case to execute correctly |
UML 2.4.1
|
|
|
open |
|
| UMLR-268 |
Concerning Transition and its owned elements |
UML 2.5
|
|
|
open |
|
| UMLR-266 |
Abstraction::mapping should be of type ValueSpecification or OpaqueExpression |
UML 2.4
|
|
|
open |
|
| UMLR-263 |
Message arguments should not be contained in a message |
UML 2.4
|
|
|
open |
|
| UMLR-267 |
UML 2.4/2.5 Aliases |
UML 2.5
|
|
|
open |
|
| UMLR-236 |
Under-specified associations in UML2.4 & the need for clarifying the semantic directionality for all UML associations |
UML 2.5
|
|
|
open |
|
| UMLR-235 |
Issue on UML 2.4 - notation for Component::provided |
UML 2.5
|
|
|
open |
|
| UMLR-233 |
Nasty UML 2.x Issue - /qualifiedName is not unambiguous |
UML 2.5
|
|
|
open |
|
| UMLR-242 |
Creation of an expansion node under an activity is allowed by UML and SysML specifications |
UML 2.3
|
|
|
open |
|
| UMLR-241 |
Part document structures in Superstructure need to conform to ISO standard Document Template Conventions |
UML 2.5
|
|
|
open |
|
| UMLR-230 |
How to specify actual parameters to pass to parameterized submachine StateMachine |
UML 2.5
|
|
|
open |
|
| UMLR-229 |
Ports |
UML 2.5
|
|
|
open |
|
| UMLR-228 |
Initialization of complex fields |
UML 2.5
|
|
|
open |
|
| UMLR-238 |
UML 2 issue: connectors typed by Association Class |
UML 2.5
|
|
|
open |
|
| UMLR-237 |
Clarifying the support for and semantics of subsetting/redefinition for a pair of properties defined in different contex |
UML 2.5
|
|
|
open |
|
| UMLR-240 |
UML 2.3 Infra 12 Incomplete conformance for infinity |
UML 2.5
|
|
|
open |
|
| UMLR-239 |
No Constraint for multiple associations |
UML 2.3b1
|
|
|
open |
|
| UMLR-232 |
Aggregation missing from Property string syntax |
UML 2.5
|
|
|
open |
|
| UMLR-231 |
Issue on UML 2.3 - Use of isAbstract for Interfaces |
UML 2.5
|
|
|
open |
|
| UMLR-244 |
Retationships and composite structures |
UML 2.5
|
|
|
open |
|
| UMLR-394 |
How is an attribute that is not a part, a role? |
UML 2.5
|
|
|
open |
|
| UMLR-393 |
Lack of clarify of attribute vs attribute value. |
UML 2.5
|
|
|
open |
|
| UMLR-392 |
Generalizations should allow enumeration types as PowerTypes. |
UML 2.5
|
|
|
open |
|
| UMLR-396 |
Caption for Table 9.1 on wrong page |
UML 2.5
|
|
|
open |
|
| UMLR-395 |
Making the default for Generalization isDisjoint=False is contrary to modelers' expectations. |
UML 2.5
|
|
|
open |
|
| UMLR-390 |
Continuation examples are missing InteractionConstraints for the Alternative CombinedFragment |
UML 2.5
|
|
|
open |
|
| UMLR-389 |
Extraneous " (double quote) in 17.6.3 Semantics |
UML 2.5
|
|
|
open |
|
| UMLR-388 |
As no UML operators are defined, it is not possible to write a UML Expression |
UML 2.5
|
|
|
open |
|
| UMLR-364 |
As Events are Packageable Elements, how is their Package known? |
UML 2.5
|
|
|
open |
|
| UMLR-365 |
Use Cases both can and cannot have BehavioralFeatures |
UML 2.5
|
|
|
open |
|
| UMLR-363 |
Semantics of Executable Nodes does not cover Control Flows on Control Pins |
UML 2.5
|
|
|
open |
|
| UMLR-362 |
A type defines a set member (not a set) |
UML 2.5
|
|
|
open |
|
| UMLR-353 |
2 Conformance: Missing Oxford comma in Item #2. |
UML 2.5
|
|
|
open |
|
| UMLR-333 |
UML 2.5 Mandatory but suppressible compartments |
UML 2.5
|
|
|
open |
|
| UMLR-332 |
UML 2.6 Issue --- SignalEvent Triggers |
UML 2.5
|
|
|
open |
|
| UMLR-327 |
Incorrectly drawn ParameterableElement.owningTemplateParameterSubstitution multiplicity |
UML 2.5
|
|
|
open |
|
| UMLR-326 |
Incorrect drawing of non-navigable redefined opposites |
UML 2.5
|
|
|
open |
|
| UMLR-330 |
Incorrect OrderedSet returns |
UML 2.5
|
|
|
open |
|
| UMLR-335 |
Figures 15.45 and 15.46 in the spec are bad examples as they are of malformed activity diagrams |
UML 2.5
|
|
|
open |
|
| UMLR-336 |
meaning is not clear |
UML 2.5b1
|
|
|
open |
|
| UMLR-334 |
Incorrect Result in ReduceAction Example |
UML 2.5
|
|
|
open |
|
| UMLR-331 |
Specification should not contain any methodology |
UML 2.5
|
|
|
open |
|
| UMLR-290 |
Improving the association direction notation |
UML 2.5
|
|
|
open |
|
| UMLR-291 |
Sequence Diagram: Message limitation |
UML 2.5
|
|
|
open |
|
| UMLR-287 |
Use cases and use of arrows |
UML 2.5
|
|
|
open |
|
| UMLR-286 |
Even if Use Cases need not have an actor, there is some ambiguity when there is an «include»d or «extension» use case |
UML 2.5
|
|
|
open |
|
| UMLR-295 |
Information flow instantiation |
UML 2.5
|
|
|
open |
|
| UMLR-294 |
Cannot set an activity as the source or target of an information flow |
UML 2.4.1
|
|
|
open |
|
| UMLR-289 |
Description of the OCL on Actor does not match OCL and both are obsolete. |
UML 2.5
|
|
|
open |
|
| UMLR-293 |
About prescribed port implementation |
UML 2.5
|
|
|
open |
|
| UMLR-297 |
Problem with MultiplicityELement::lower redefinition in UML 2.5 Beta 2 |
UML 2.5
|
|
|
open |
|
| UMLR-296 |
BehavioredClassifier should redefine Classifier::conformsTo to include interfaceRealization |
UML 2.5
|
|
|
open |
|
| UMLR-288 |
No rules on Extension Pts governing differences between Use Case definitions & «extend» relationships usage |
UML 2.5
|
|
|
open |
|
| UMLR-285 |
Abstract Syntax diagram for Use Cases |
UML 2.5
|
|
|
open |
|
| UMLR-257 |
Navigability orthogonal to end ownership or not? |
UML 2.3
|
|
|
open |
|
| UMLR-256 |
Ambiguous stereotype notation |
UML 2.5
|
|
|
open |
|
| UMLR-248 |
Notation of Lifelines |
UML 2.5
|
|
|
open |
|
| UMLR-247 |
Tags typed by classes/blocks |
UML 2.5
|
|
|
open |
|
| UMLR-246 |
XMI representation of stereotype application |
UML 2.5
|
|
|
open |
|
| UMLR-245 |
New notation for attribute |
UML 2.5
|
|
|
open |
|
| UMLR-254 |
Use cases specifying the same subject cannot be associated: exception |
UML 2.4
|
|
|
open |
|
| UMLR-252 |
Metaclass stereotype notion (02) |
UML 2.4
|
|
|
open |
|
| UMLR-251 |
Metaclass stereotype notion |
UML 2.4
|
|
|
open |
|
| UMLR-250 |
Profile URI Attribute - Mingled URI Definition and Use in XMI |
UML 2.4
|
|
|
open |
|
| UMLR-253 |
State::stateInvariant multiplicity too restrictive |
UML 2.5
|
|
|
open |
|
| UMLR-249 |
Package URI Attribute Uses Obsolete RFC 2396 |
UML 2.4
|
|
|
open |
|
| UMLR-255 |
A deferrable trigger may have a guard |
UML 2.4
|
|
|
open |
|
| UMLR-227 |
Owning of interaction fragments is ambiguous when InteractionOperands are present |
UML 2.5
|
|
|
open |
|
| UMLR-226 |
Chapter 14 is ambiguous and contradictory about how to link up messages and execution specifications |
UML 2.5
|
|
|
open |
|
| UMLR-225 |
issue10087 and association-like notation |
UML 2.5
|
|
|
open |
|
| UMLR-224 |
not sure it is possible to define a constraint without a context |
UML 2.5
|
|
|
open |
|
| UMLR-223 |
Timing Diagram and interchange |
UML 2.5
|
|
|
open |
|
| UMLR-400 |
Missing constraints preventing contradictory GeneralizationSets. |
UML 2.5
|
|
|
open |
|
| UMLR-399 |
What is the default setting for disjoint/overlapping and complete/incomplete for generalizations that are not part of a GeneralizationSet |
UML 2.5
|
|
|
open |
|
| UMLR-398 |
How can a GeneralizationSet not have any Generalizations? |
UML 2.5
|
|
|
open |
|
| UMLR-397 |
Ambiguity in description of TransitionKind |
UML 2.5
|
|
|
open |
|
| UMLR-385 |
Two classes can share attributes by use of element import |
UML 2.5
|
|
|
open |
|
| UMLR-383 |
History pseudo states in protocol state machines |
UML 2.5
|
|
|
open |
|
| UMLR-381 |
Message lines can cross without the first being asynchronous |
UML 2.5
|
|
|
open |
|
| UMLR-382 |
Justification for messages on differnent sides of a gate being identical is not clear. |
UML 2.5
|
|
|
open |
|
| UMLR-369 |
Tables 17.1, 17.3, 17.5, 17.6 Header Formats |
UML 2.5
|
|
|
open |
|
| UMLR-379 |
Need clarification between exceptionType and the type of the exceptionInput |
UML 2.5
|
|
|
open |
|
| UMLR-378 |
Does not seem possible to have an exception cause an interrupt (leave the region) |
UML 2.5
|
|
|
open |
|
| UMLR-377 |
What exception type is "any" exceptionType |
UML 2.5
|
|
|
open |
|
| UMLR-373 |
Vertical lines do not always describe the time-line for an interaction diagram |
UML 2.5
|
|
|
open |
|
| UMLR-367 |
Spelling error in ActivityGoups |
UML 2.5
|
|
|
open |
|
| UMLR-370 |
Message wildcards appear to ignore operation default values |
UML 2.5
|
|
|
open |
|
| UMLR-372 |
use of ! instead of + or ∪ |
UML 2.5
|
|
|
open |
|
| UMLR-371 |
Extraneous " (double quote) in 17.5.4 BehaviorExecutionSpecification |
UML 2.5
|
|
|
open |
|
| UMLR-376 |
Coloring and shading on Figure 17.10 should be removed |
UML 2.5
|
|
|
open |
|
| UMLR-375 |
Caption for Table 17.5 on wrong page |
UML 2.5
|
|
|
open |
|
| UMLR-368 |
Mismatch of singular/plural Activity Goups are a grouping constructs |
UML 2.5
|
|
|
open |
|
| UMLR-357 |
SignalBroadcastAction used where BroadcastSignalAction should be. |
UML 2.5
|
|
|
open |
|
| UMLR-356 |
Spelling error: i-->is |
UML 2.5
|
|
|
open |
|
| UMLR-350 |
UML 2.5 Section 15.2.3 p392 description for the ActivityEdge weight |
UML 2.5
|
|
|
open |
|
| UMLR-349 |
Another UML 2.5 Beta 2 XMI invalidity |
UML 2.5
|
|
|
open |
|
| UMLR-323 |
Unclear statement regarding Lifeline shape |
UML 2.5
|
|
|
open |
|
| UMLR-322 |
UML 2.5 Overly strict restriction on message slope in seq diagrams |
UML 2.5
|
|
|
open |
|
| UMLR-325 |
Unnamed elements in a namespace |
UML 2.5
|
|
|
open |
|
| UMLR-324 |
Including use case depends on included use case but Include is no subclass of Dependency |
UML 2.5
|
|
|
open |
|
| UMLR-318 |
UML 2.5 Visibility of a packagedElement |
UML 2.5
|
|
|
open |
|
| UMLR-317 |
UML 2.5 Issue on DI for reply arrows |
UML 2.5
|
|
|
open |
|
| UMLR-316 |
Ambiguous Profile::profileApplication |
UML 2.5
|
|
|
open |
|
| UMLR-319 |
UML transition-centric state machine arrows (01) alternative exit pt vs entry pt notation |
UML 2.5
|
|
|
open |
|
| UMLR-321 |
UML 2.5 issue on examples in 17.4.5 |
UML 2.5
|
|
|
open |
|
| UMLR-320 |
UML transition-centric state machine arrows (02) solid vs v-shaped arrow heads |
UML 2.5
|
|
|
open |
|
| UMLR-312 |
UML 2.5 Figure 10.10 Error |
UML 2.5
|
|
|
open |
|
| UMLR-311 |
Name of Package in Figure 7.3 should be "Core" rather than "Constructs" |
UML 2.4.1
|
|
|
open |
|
| UMLR-313 |
Multiple Generalization Sets |
UML 2.5
|
|
|
open |
|
| UMLR-314 |
UML 2.5 Figure 14.25 Choice Pseudostates |
UML 2.5
|
|
|
open |
|
| UMLR-277 |
isReplaceAll=true and lowerBound > 1 |
UML 2.5
|
|
|
open |
|
| UMLR-276 |
test |
UML 2.5
|
|
|
open |
|
| UMLR-275 |
applying and associating stereotypes and explanation of all aspects of their serialization |
UML 2.5
|
|
|
open |
|
| UMLR-279 |
Relax Association::/endType from [1..*] to [0..*] |
UML 2.5
|
|
|
open |
|
| UMLR-278 |
Problems with OCL definition of Package::makesVisible |
UML 2.5
|
|
|
open |
|
| UMLR-274 |
Specifying the multiplicity of a part with an attribute |
UML 2.5
|
|
|
open |
|
| UMLR-273 |
Link notation for stereotype property value |
UML 2.5
|
|
|
open |
|
| UMLR-272 |
Generalization should be allowed to be cyclic and should no be restricted to be owned by the specialized classifier |
UML 2.5
|
|
|
open |
|
| UMLR-270 |
Interaction.action should subset ownedMember in lieu of ownedElement |
UML 2.4.1
|
|
|
open |
|
| UMLR-269 |
Message Signature in Interactions and Reception.ownedParameter |
UML 2.5
|
|
|
open |
|
| UMLR-271 |
Migrate UML::Component's ability to own UML::PackageableElements to UML::Class |
UML 2.5
|
|
|
open |
|
| UMLR-282 |
Semantic error in UMLAssociationOrConnectorOrLinkShape::edge_instancespec invariant |
UML 2.5
|
|
|
open |
|
| UMLR-281 |
Semantic error in Lifeline::interaction_uses_share_lifeline |
UML 2.5
|
|
|
open |
|
| UMLR-283 |
XMI.xmi is not merged |
UML 2.5
|
|
|
open |
|
| UMLR-284 |
In the Use Case section, it is unclear whether a use case requires an actor |
UML 2.5
|
|
|
open |
|
| UMLR-280 |
ExtensionEnd upper/lower inconsistent with MultiplicityElement |
UML 2.5
|
|
|
open |
|
| UMLR-159 |
Lack of clarity about meaning of package shapes containing elements with fully qualified names |
UML 2.5
|
|
|
open |
|
| UMLR-158 |
Section 9.3.4 Collaboration Use, 2nd constraint creates unneces |
UML 2.5
|
|
|
open |
|
| UMLR-153 |
UML: Standard Techniques to disambiguate crossing lines needed |
UML 2.5
|
|
|
open |
|
| UMLR-152 |
There is no way to specify the behavior of operations which are members of data types |
UML 2.5
|
|
|
open |
|
| UMLR-161 |
UML 2 - appearance of Association Ends as members of the related classes |
UML 2.5
|
|
|
open |
|
| UMLR-160 |
UML2.2. Contradications in 14.3.10 |
UML 2.5
|
|
|
open |
|
| UMLR-157 |
we can create an invalid active state configuration |
UML 2.2
|
|
|
open |
|
| UMLR-164 |
Concrete specialization of the Relationship meta-class are missing |
UML 2.2
|
|
|
open |
|
| UMLR-163 |
UML 2.2 InteractionOperand abstract syntax |
UML 2.5
|
|
|
open |
|
| UMLR-155 |
UML2: Unclear how to indicate what events a classifier might send |
UML 2.5
|
|
|
open |
|
| UMLR-154 |
UML2.2 RTF: EnumerationLiteral is a DeploymentTarget |
UML 2.5
|
|
|
open |
|
| UMLR-162 |
Section: 9.3.11 Port |
UML 2.5
|
|
|
open |
|
| UMLR-156 |
Section: 7.3.9 Comment should be NamedElement |
UML 2.2
|
|
|
open |
|
| UMLR-151 |
MARTE/section 7.2.1/ "several labels for the same classifiers in the Metamodel" bug |
UML 2.5
|
|
|
open |
|
| UMLR-122 |
Section: 16.3.5 |
UML 2.1.1
|
|
|
open |
|
| UMLR-121 |
Section: 7.3.3 |
UML 2.5
|
|
|
open |
|
| UMLR-126 |
Figure 7.48 and the accompanying discussion under 7.3.21 |
UML 2.1.1
|
|
|
open |
|
| UMLR-125 |
simpleTime package problems |
UML 2.5
|
|
|
open |
|
| UMLR-124 |
Section: 7.3.37 Package (from Kernel) |
UML 2.1.1
|
|
|
open |
|
| UMLR-123 |
UML2 Property collaborationRole should be removed |
UML 2.5
|
|
|
open |
|
| UMLR-128 |
UML2 Issue: notation for Literals does not allow for name |
UML 2.5
|
|
|
open |
|
| UMLR-127 |
Section: 14.4 |
UML 2.5
|
|
|
open |
|
| UMLR-130 |
should be able to show gates on communication diagrams |
UML 2.5
|
|
|
open |
|
| UMLR-129 |
pull semantics are only supported on Action inputs, not outputs |
UML 2.5
|
|
|
open |
|
| UMLR-135 |
new constraint ? |
UML 2.5
|
|
|
open |
|
| UMLR-134 |
Section 7.3.44 |
UML 2.1.2
|
|
|
open |
|
| UMLR-132 |
UML 2 has lost cability to represent operations by collaborations |
UML 2.1.2
|
|
|
open |
|
| UMLR-131 |
UML 2: Need an explicit listing of all semantic variation points |
UML 2.5
|
|
|
open |
|
| UMLR-133 |
Section: 7.3.41 |
UML 2.1.2
|
|
|
open |
|
| UMLR-76 |
No notation for associating Exceptions with Operations |
UML 2.5
|
|
|
open |
|
| UMLR-75 |
Page: 107 |
UML 2.0
|
|
|
open |
|
| UMLR-79 |
Section: 7.3.9 |
UML 2.1
|
|
|
open |
|
| UMLR-78 |
consistent ordering of Association::memberEnd and ownedEnd |
UML 2.5
|
|
|
open |
|
| UMLR-77 |
No ReadParameterAction or WriteParameterAction |
UML 2.5
|
|
|
open |
|
| UMLR-74 |
Need more flexible notation for activity partitions |
UML 2.5
|
|
|
open |
|
| UMLR-69 |
UML2 Super / 14.3.13 Interaction |
UML 2.5
|
|
|
open |
|
| UMLR-70 |
Section: Classes |
UML 2.0
|
|
|
open |
|
| UMLR-67 |
Syntax of Transition |
UML 2.5
|
|
|
open |
|
| UMLR-66 |
OutputPin |
UML 2.5
|
|
|
open |
|
| UMLR-73 |
Page: 492-493 |
UML 2.5
|
|
|
open |
|
| UMLR-72 |
Section: Classes |
UML 2.0
|
|
|
open |
|
| UMLR-71 |
Section: Activities |
UML 2.0
|
|
|
open |
|
| UMLR-40 |
Properties on Association for end objects |
UML 2.0
|
|
|
open |
|
| UMLR-39 |
Notation for classifierBehavior |
UML 2.0
|
|
|
open |
|
| UMLR-38 |
Contextualized attribute values Figures 121 |
UML 2.0
|
|
|
open |
|
| UMLR-42 |
ReadStructuralFeatureAction |
UML 2.0
|
|
|
open |
|
| UMLR-34 |
Section: Classes, Behavior |
UML 2.0
|
|
|
open |
|
| UMLR-37 |
End objects of a link In the semantics of AssociationClass |
UML 2.0
|
|
|
open |
|
| UMLR-36 |
Action for retrieving activity instance |
UML 2.0
|
|
|
open |
|
| UMLR-44 |
Activities section |
UML 2.0
|
|
|
open |
|
| UMLR-43 |
Section: 16.3.1 |
UML 2.0
|
|
|
open |
|
| UMLR-48 |
Add constraints on ConditionalNode |
UML 2.0
|
|
|
open |
|
| UMLR-47 |
ExpansionRegion (behavior in the shorthand notation) |
UML 2.0
|
|
|
open |
|
| UMLR-46 |
Section: Activities : Why is exception type needed? |
UML 2.0
|
|
|
open |
|
| UMLR-45 |
Section: Activities - clarification |
UML 2.0
|
|
|
open |
|
| UMLR-212 |
UML: Cross model dependencies |
UML 2.5
|
|
|
open |
|
| UMLR-211 |
UML: Large Scale Model Support:Federated/Distibuted Models |
UML 2.5
|
|
|
open |
|
| UMLR-214 |
UML: Add abilities to specifiy intent of Assert, Negate, Consider, Ignore fragments |
UML 2.5
|
|
|
open |
|
| UMLR-213 |
UML: Improve Sequence Diagram Semantics (3-issues) |
UML 2.5
|
|
|
open |
|
| UMLR-216 |
UML: Better Profile Capabilitiy |
UML 2.5
|
|
|
open |
|
| UMLR-215 |
UML:Access to standardized ontologies within models |
UML 2.5
|
|
|
open |
|
| UMLR-220 |
NamedElements whose owners do not subset Namespace |
UML 2.5
|
|
|
open |
|
| UMLR-222 |
Sequence diagram and Communication diagrams should support instances as lifelines |
UML 2.5
|
|
|
open |
|
| UMLR-221 |
Parameter |
UML 2.5
|
|
|
open |
|
| UMLR-218 |
UML: Higher-level reusable frameworks |
UML 2.5
|
|
|
open |
|
| UMLR-217 |
UML: Timing semantics for activity diagram |
UML 2.5
|
|
|
open |
|
| UMLR-178 |
Package merge is missing a rule |
UML 2.2
|
|
|
open |
|
| UMLR-177 |
UML 2: notation and concepts for unbound and un-owned template parameters are not clear |
UML 2.5
|
|
|
open |
|
| UMLR-176 |
semantics of associating a use case with another use case, or indeed anything other than an actor, are unclear |
UML 2.2
|
|
|
open |
|
| UMLR-180 |
authorize a reference to an operation in a realized interface. |
UML 2.2
|
|
|
open |
|
| UMLR-179 |
Subsets vs. Redefines |
UML 2.5
|
|
|
open |
|
| UMLR-174 |
Visibility and Import relationships |
UML 2.5
|
|
|
open |
|
| UMLR-173 |
UML2: Need clarification on circle plus notation for containment |
UML 2.5
|
|
|
open |
|
| UMLR-169 |
Section: 18.3.8 |
UML 2.2
|
|
|
open |
|
| UMLR-168 |
The example in Figure 18.11 is badly designed in multiple ways and is strongly misleading |
UML 2.2
|
|
|
open |
|
| UMLR-171 |
Template Binding Question |
UML 2.5
|
|
|
open |
|
| UMLR-170 |
there are numerous places where associations between UML elements have only one, navigable role |
UML 2.1.2
|
|
|
open |
|
| UMLR-172 |
Subsets vs. Redefines |
UML 2.5
|
|
|
open |
|
| UMLR-167 |
Figure 18.9 shows a presentation option for an Interface which has not been introduced before (circle within box) |
UML 2.2
|
|
|
open |
|
| UMLR-166 |
Section: 18.3.6 |
UML 2.2
|
|
|
open |
|
| UMLR-165 |
issue within UPDM with profile diagrams |
UML 2.5
|
|
|
open |
|
| UMLR-175 |
Should there be a constraint for extends equivalent to 16.3.6 [4] |
UML 2.2
|
|
|
open |
|
| UMLR-110 |
clarification on Behavior::specification / meaning of InterfaceRealization |
UML 2.5
|
|
|
open |
|
| UMLR-109 |
Presentation option for return parameter for operation type are incomplete |
UML 2.5
|
|
|
open |
|
| UMLR-108 |
UML 2 Superstructure: Abstractions should be acyclic |
UML 2.5
|
|
|
open |
|
| UMLR-105 |
Constraint.context vs Constraint.constrainedElement |
UML 2.5
|
|
|
open |
|
| UMLR-104 |
Section: Chapter: 7.3.2.4 View |
SysML 1.0
|
|
|
open |
|
| UMLR-103 |
Section: 7 |
UML 2.0
|
|
|
open |
|
| UMLR-106 |
Connector contract is inflexible |
UML 2.5
|
|
|
open |
|
| UMLR-100 |
Section: 13 & 14 |
UML 2.1.1
|
|
|
open |
|
| UMLR-99 |
Optional values and evaluation of defaults |
UML 2.5
|
|
|
open |
|
| UMLR-98 |
OCL Syntax in expressions |
UML 2.5
|
|
|
open |
|
| UMLR-102 |
Association::isDerived should be derived |
UML 2.5
|
|
|
open |
|
| UMLR-111 |
Section: 10.3.4 of formal/2007-02-03 |
UML 2.1.1
|
|
|
open |
|
| UMLR-116 |
UML 2.1.1 - notation for parameter sets |
UML 2.5
|
|
|
open |
|
| UMLR-115 |
Units and types are still problematic |
UML 2.5
|
|
|
open |
|
| UMLR-114 |
names and namespaces |
UML 2.5
|
|
|
open |
|
| UMLR-118 |
Section: 14.4 Timing Diagram: Continuous time axis |
UML 2.1.1
|
|
|
open |
|
| UMLR-117 |
9.3.9 Invocation Action |
UML 2.5
|
|
|
open |
|
| UMLR-120 |
Section: Annex A: Diagrams |
UML 2.1.1
|
|
|
open |
|
| UMLR-53 |
Meaning of relationship between iteration clause and Lifeline.selector clau |
UML 2.5
|
|
|
open |
|
| UMLR-59 |
Section: 14.3.3 Page: 508+ |
UML 2.0
|
|
|
open |
|
| UMLR-58 |
Section: 14.3.3 |
UML 2.0
|
|
|
open |
|
| UMLR-65 |
UML 2.0 Super/Use Cases/Subject of a Use Case |
UML 2.5
|
|
|
open |
|
| UMLR-64 |
Issue 7368 - make Classifier::useCase navigable |
UML 2.5
|
|
|
open |
|
| UMLR-52 |
UML2-rtf issue: communication diagram |
UML 2.5
|
|
|
open |
|
| UMLR-51 |
Section: 10.3.1 |
UML 2.0
|
|
|
open |
|
| UMLR-61 |
Arguments of Message |
UML 2.5
|
|
|
open |
|
| UMLR-60 |
ConditionalNode inputs used by more than one test |
UML 2.0
|
|
|
open |
|
| UMLR-56 |
Association in UseCase diagram |
UML 2.5
|
|
|
open |
|
| UMLR-55 |
Possibility to define a Collection as default Value needed |
UML 2.0
|
|
|
open |
|
| UMLR-63 |
Variables |
UML 2.5
|
|
|
open |
|
| UMLR-62 |
Numbering |
UML 2.5
|
|
|
open |
|
| UMLR-50 |
Add a Constraint |
UML 2.5
|
|
|
open |
|
| UMLR-49 |
SequenceNode should have way to set output pins in CompleteStructured |
UML 2.0
|
|
|
open |
|
| UMLR-57 |
Arguments of Message |
UML 2.5
|
|
|
open |
|
| UMLR-201 |
UML: Include text description field with model element --- additional information added |
UML 2.5
|
|
|
open |
|
| UMLR-200 |
UML: Provide unique URL/URI Reference to/from Model Elements |
UML 2.5
|
|
|
open |
|
| UMLR-207 |
UML: A strong ability to support generating Documents |
UML 2.5
|
|
|
open |
|
| UMLR-206 |
UML Support for multiple library levels |
UML 2.5
|
|
|
open |
|
| UMLR-203 |
Provide notational mechanism to represent any group of model elements based on some criteria w/o stealing ownership |
UML 2.5
|
|
|
open |
|
| UMLR-210 |
UML: Better Definition of Compliance |
UML 2.5
|
|
|
open |
|
| UMLR-209 |
UML: Provide mathematical formalism for UML semantics to provide precise meaning to language constructs |
UML 2.5
|
|
|
open |
|
| UMLR-205 |
UML: Support for maintaining what-if models in repository without massive duplication |
UML 2.5
|
|
|
open |
|
| UMLR-204 |
UML: A strong ability to support reviewing packages |
UML 2.5
|
|
|
open |
|
| UMLR-208 |
UML: Diagrams as Model Elements |
UML 2.5
|
|
|
open |
|
| UMLR-199 |
UML Associate an image/icon with each model element |
UML 2.5
|
|
|
open |
|
| UMLR-184 |
Reconcile the algebra of collections across OCL & UMLs intentional & extensional semantics |
UML 2.5
|
|
|
open |
|
| UMLR-183 |
UML: Issue with stereotype icons in a profile |
UML 2.5
|
|
|
open |
|
| UMLR-182 |
The spec may require some clarification regarding figure 14.16 |
UML 2.5
|
|
|
open |
|
| UMLR-181 |
Need notation option to show type stereotype on typed element |
UML 2.5
|
|
|
open |
|
| UMLR-188 |
Stereotyped Constraints in UML |
UML 2.5
|
|
|
open |
|
| UMLR-187 |
Stereotyped Constraints in UML |
UML 2.5
|
|
|
open |
|
| UMLR-191 |
Property subsets other regular property, non-derived union |
UML 2.5
|
|
|
open |
|
| UMLR-190 |
are Create messages aynch or synch, or doesn't it matter? |
UML 2.5
|
|
|
open |
|
| UMLR-189 |
UML 2 TemplateParameterSubstitution inconsistency about multiplicity of Actual and OwnedActual |
UML 2.5
|
|
|
open |
|
| UMLR-186 |
PrimitiveType has missing constraints |
UML 2.2
|
|
|
open |
|
| UMLR-193 |
UML Issue: Refactor UML to separate SW-Specific Aspects from Foundation Language |
UML 2.5
|
|
|
open |
|
| UMLR-192 |
One association end is derived, another is not |
UML 2.5
|
|
|
open |
|
| UMLR-195 |
Simplify by Making UML More Consistent: Allow States to be model as classes supporting inheritance and composition |
UML 2.5
|
|
|
open |
|
| UMLR-194 |
Simplify by Making UML More Consistent: Apply class and composite structure diagram rules to behavior modeling |
UML 2.5
|
|
|
open |
|
| UMLR-198 |
UML: Include text description field with model element |
UML 2.5
|
|
|
open |
|
| UMLR-197 |
UML: Incorporate SysML Requirements Model into UML |
UML 2.5
|
|
|
open |
|
| UMLR-196 |
UML: Need more robust value model that would enable capture of values vs time |
UML 2.5
|
|
|
open |
|
| UMLR-148 |
InterfaceRealization |
UML 2.5
|
|
|
open |
|
| UMLR-147 |
issue to address how problem 11240 was actually addressed in UML 2.2 spec |
UML 2.5
|
|
|
open |
|
| UMLR-146 |
Figure 7.65 and its explanation, P115 |
UML 2.5
|
|
|
open |
|
| UMLR-138 |
Section: 15.3.7 Constraint [2] |
UML 2.1.2
|
|
|
open |
|
| UMLR-137 |
UML Super 2.1.2: section 18.3.2 |
UML 2.5
|
|
|
open |
|
| UMLR-145 |
UML2 issue regarding Redefinition |
UML 2.5
|
|
|
open |
|
| UMLR-144 |
Section: 14.3.24, 14.3.20 |
UML 2.1.2
|
|
|
open |
|
| UMLR-140 |
Section: Activities |
SysML 1.0
|
|
|
open |
|
| UMLR-139 |
UML 2.1.2 Super: Execution Specification |
UML 2.5
|
|
|
open |
|
| UMLR-136 |
Section: 18.3.3 |
UML 2.1.2
|
|
|
open |
|
| UMLR-142 |
role bindings of a CollaborationUse |
UML 2.1.1
|
|
|
open |
|
| UMLR-141 |
Callout notation for many clients/suppliers |
SysML 1.0
|
|
|
open |
|
| UMLR-149 |
Actors cannot own Operations - a contradiction |
UML 2.5
|
|
|
open |
|
| UMLR-150 |
18.3.8 Generalization of stereotyped model elements |
UML 2.2
|
|
|
open |
|
| UMLR-143 |
3 3.2 Behavior (CommonBehaviors/BasicBehaviors) |
UML 2.1.2
|
|
|
open |
|
| UMLR-82 |
Notation for ordering action input and output pins |
UML 2.5
|
|
|
open |
|
| UMLR-81 |
All associations ends in the UML2 metamodel itself should be navigable |
UML 2.5
|
|
|
open |
|
| UMLR-80 |
Section: Sequence diagrams |
UML 2.0
|
|
|
open |
|
| UMLR-88 |
Unnecessary restriction on aggregations being binary |
UML 2.5
|
|
|
open |
|
| UMLR-87 |
New issue on notation for multiple stereotypes |
UML 2.5
|
|
|
open |
|
| UMLR-86 |
Link notation for instance diagrams does not cope with multiple classifiers |
UML 2.5
|
|
|
open |
|
| UMLR-97 |
Guidance for Representing Enumeration Values |
UML 2.5
|
|
|
open |
|
| UMLR-96 |
Section: 15.3.12, p 588, 589 |
UML 2.1.1
|
|
|
open |
|
| UMLR-95 |
Relationships |
UML 2.5
|
|
|
open |
|
| UMLR-83 |
ControlNodes in ActivityPartitions |
UML 2.5
|
|
|
open |
|
| UMLR-85 |
UML2: No notation for indicating Operation::raisedException |
UML 2.5
|
|
|
open |
|
| UMLR-84 |
Reception has no notation for its signal |
UML 2.5
|
|
|
open |
|
| UMLR-90 |
Unclear usage of LiteralExpression::type |
UML 2.5
|
|
|
open |
|
| UMLR-94 |
Default value types |
UML 2.5
|
|
|
open |
|
| UMLR-93 |
Section: 7.3.33 |
UML 2.1.1
|
|
|
open |
|
| UMLR-91 |
ValueSpecification::isComputable() |
UML 2.5
|
|
|
open |
|
| UMLR-32 |
Alternative entry and exit point notation is ambiguous |
UML 2.0
|
|
|
open |
|
| UMLR-31 |
Coupling between StateMachines and Activities |
UML 2.5
|
|
|
open |
|
| UMLR-33 |
Too much navigability from Generalizations |
UML 2.5
|
|
|
open |
|
| UMLR-14 |
ptc-03-09-15/Need for examples to include instance models |
UML 2.5
|
|
|
open |
|
| UMLR-13 |
Conditions for parameter sets |
UML 2.5
|
|
|
open |
|
| UMLR-11 |
Clarification of use case semantics |
UML 2.5
|
|
|
open |
|
| UMLR-10 |
Integration between behavioral "sublanguages": Interactions and Activities |
UML 2.5
|
|
|
open |
|
| UMLR-15 |
ptc-03-09-15/Explain the new association modeling constructs |
UML 2.5
|
|
|
open |
|
| UMLR-3 |
More explanation needed on Figure 339 |
UML 2.0
|
|
|
open |
|
| UMLR-2 |
More examples |
UML 2.0
|
|
|
open |
|
| UMLR-5 |
Promote local conditions to ExecutableNode |
UML 2.5
|
|
|
open |
|
| UMLR-4 |
Parameterization of lifelines |
UML 2.0
|
|
|
open |
|
| UMLR-9 |
UML 2 Super / State machines / Transition triggers cannot be redefined |
UML 2.5
|
|
|
open |
|
| UMLR-8 |
Join nodes that destroy tokens |
UML 2.5
|
|
|
open |
|
| UMLR-7 |
Deployment a dependency? |
UML 2.5
|
|
|
open |
|
| UMLR-6 |
Notation for method |
UML 2.5
|
|
|
open |
|
| UMLR-1 |
Conditional Node and Loop Node notation missing |
UML 2.5
|
|
|
open |
|
| UMLR-12 |
Section 7.11.2 Association |
UML 2.5
|
|
|
open |
|
| UMLR-23 |
UML2 Super/Deployment/inheritance |
UML 2.5
|
|
|
open |
|
| UMLR-22 |
Questions about DataTypes and generalization |
UML 2.5
|
|
|
open |
|
| UMLR-21 |
missing illustrations of graphical paths for create and destroy messages |
UML 2.5
|
|
|
open |
|
| UMLR-20 |
UML 2 Super / Interactions / Ambiguous diagram tags |
UML 2.5
|
|
|
open |
|
| UMLR-19 |
Redefinitions of OCL constraints must be aligned with MOF2.0/UML2.0 class R |
UML 2.0
|
|
|
open |
|
| UMLR-18 |
UML 2 Infrastructure / rule for redefinition of Property |
UML 2.5
|
|
|
open |
|
| UMLR-27 |
inconsistency in the action model |
UML 2.0
|
|
|
open |
|
| UMLR-26 |
large overlap between structural features and variables |
UML 2.0
|
|
|
open |
|
| UMLR-17 |
UML 2.0 Superstructure Kernal/Packages |
UML 2.5
|
|
|
open |
|
| UMLR-16 |
freeing namespace |
UML 2.5
|
|
|
open |
|
| UMLR-28 |
metaattribute isReadOnly |
UML 2.0
|
|
|
open |
|
| UMLR-25 |
Priority of the joint transition |
UML 2.5
|
|
|
open |
|
| UMLR-29 |
surface notation for state machines |
UML 2.0
|
|
|
open |
|
| UMLR-24 |
UML2 Super/Deployments/Manifestation |
UML 2.5
|
|
|
open |
|
| UMLR-30 |
Provide exception handling for all behaviors. |
UML 2.0
|
|
|
open |
|
)->notEmpty()) implies
of the first 
diagram hyperlinks in the list of diagrams under the Diagrams sections under the Classifier Descriptions have problems. They seem to point to the Classifier section itself. As an example, section 7.8.3.2 lists many diagrams. Clicking Namespaces shows sectiom 7.8.3 and not the diagram in figure 7.5. Clicking Constraints moves correctly to the diagram in figure 7.13. It is interesting to note that the problem seems to only occur for the first diagram reference in the list. Also, note that the problem occurs at MANY places all over the document (in the mentioned "generic" sections). It is especially annoying since the first diagram often is the diagram of main interest (the "definition" diagram).
is used as part of a multiplicity specification to represent an unlimited upper bound. >> nor with the specification of the semantics related to this notation (on top of p.34): << A MultiplicityElement is unlimited if its upperBound has the UnlimitedNatural value of unlimited (“*”) >>. 
