| UMLR-804 |
Link incorrect |
UML 2.5.1
|
|
|
open |
|
| UMLR-802 |
Owner has to do with Namespaces |
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 |
|
| UML22-21 |
UML 2 Issue: isUnique |
UML 1.5
|
UML 2.2
|
Resolved |
closed |
|
| UMLR-757 |
Make AssociationClasses unique again |
UML 2.5
|
|
|
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-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 |
|
| 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-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-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-234 |
UML Interactions: Misleading suggestion of relationship between Interactions and Activities modeling |
UML 2.5
|
|
|
open |
|
| UMLR-740 |
DecisionNode is missing a constraint on incoming edges |
UML 2.5
|
|
|
open |
|
| UMLR-306 |
How to access a token value in a guard? |
UML 2.5
|
|
|
open |
|
| UMLR-711 |
Conflicting constraints |
UML 2.5
|
|
|
open |
|
| UMLR-243 |
Restrictions on decision nodes |
UML 2.5
|
|
|
open |
|
| UMLR-668 |
Unspecified and inconsistent notation for Observations |
UML 2.5
|
|
|
open |
|
| UML22-319 |
Explanation of Observation notation |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| 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-685 |
UML 2.5: StateMachine Vertex needs to be made a kind of RedefinableElement instead of State |
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-696 |
The behavior of an OpaqueExpression should be allowed to have input parameters |
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-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-673 |
Spec refers to TypeElement twice. Should be TypedElement |
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-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-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-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 |
|
| UML22-307 |
Repr. of applied stereotypes and their properties insufficiently described |
UML 2.1
|
UML 2.2
|
Resolved |
closed |
|
| UMLR-619 |
Class.isAbstract attribute is not necessary |
UML 2.5
|
|
|
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 |
|
| UML25-684 |
Typo in Interaction Example |
UML 2.5b1
|
UML 2.5
|
Duplicate or Merged |
closed |
|
| 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 |
|
| 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-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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
<