| UML14-1046 |
Type vs. Implementastion class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-1045 |
Compliance ambiguity |
UML 1.3
|
UML 1.4
|
Duplicate or Merged |
closed |
|
| UML14-1044 |
Wording od OCL definition |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-1043 |
Change syntax of certain pre-defined operations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1042 |
Package symbol as a polygon |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1041 |
There is a bug in additional operation 1 of the Namespace element |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-1040 |
How to properly designate exception returned from message sent to Java obje |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-1039 |
In 3.23.1 "Notation" (Internationalization issues) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1038 |
No servant with object . minorcode=0 completed=NO |
UML 1.3
|
UML 1.4
|
Closed; No Change |
closed |
|
| UML14-1037 |
The index shows incorrect section numbering for sections 2.9.4.1 to 2.9.4 |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1036 |
Setting Action as abstract in UML-MetaModel MDL to correspond to Semantics |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1035 |
Who owns an Event? |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1033 |
UML RTF 1.4 editorial comments (Part 9 - Statechart Diagrams) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1034 |
UML 1.4 RTF Issue: Namespace notation too specific |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1032 |
UML RTF 1.4 editorial comments (Part 6 - Use Case Diagrams) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1031 |
UML RTF 1.4 editorial comments (Part 3 - Behavioral Elements) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1030 |
UML RTF 1.4 editorial comments (Part 2 Diagram Elements) |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1029 |
UML 1.4 RTF Issue: Association generalization has notation but no semantics |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1028 |
UML 1.4 RTF Issue: Ordering of attribute values |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1023 |
UML 1.4 RTF issue: OCL: Unary operator "-" missing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1027 |
UML 1.4 RTF Issue: Multiple languages for uninterpreted strings |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1026 |
UML 1.4 RTF Issue: changeability in associations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1025 |
UML 1.4 RTF issue: OCL: grammar is ambigous |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1024 |
UML 1.4 RTF issue: OCL: navigation context in iterate |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1021 |
UML 1.4 RTF issue: OCL: Iterator declarators |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1020 |
OCL: Declarators for iterate |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1022 |
UML 1.4 RTF issue: OCL: Precedence of relational operators |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1019 |
In 2.10.4, semantics of Collaboration, the 1st sentence is confusing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1016 |
Page 2-114, 2nd paragraph. It should be collaboration template |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1015 |
Confusing wording |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1017 |
In 2.10.5, you give pattern a non-standard definition |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1018 |
Ad 3.69.3. In these paragraphs, it should be "Classifier" rather than "Cla |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1010 |
Terminology: Collaboration and Collaboration Template |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1014 |
use of the phrase "In the metamodel..." is unclear |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1013 |
why is AssociationRole is a subtype of Association? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1012 |
2. In 2.10.1, 3rd paragraph, it should be "OOram", not "OOFRam". |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1011 |
Focus is on 2.10 Collaborations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1009 |
Design patterns and collaboration templates. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1008 |
"Unused" data types |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1007 |
Notation for Namespace ownership |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1006 |
UML RTF 1.4 Issue: Typo in state exit |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1005 |
Misleading description of feature inheritance on roles. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1001 |
Incorrect example of constraining elements in collaborations. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1004 |
UML RTF 1.4 Issue: Messages do not have signatures |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1003 |
UML RTF 1.4 Issue: Guard condition in collaborations poorly named. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1002 |
UML RTF 1.4 Issue: Multi-objects in collaborations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-1000 |
UML RTF 1.4 Issue: Duplicate association end names from Constraint. |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-999 |
UML RTF 1.4 Issue: Create action in collaborations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-998 |
UML RTF 1.4 Issue: What does it mean for ReturnAction to be synchronous? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-997 |
UML RTF 1.4 Issue: Action composition meta-modelled improperly: |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-994 |
UML RTF 1.4 Issue: Confusing example of sequence diagram |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-993 |
UML RTF 1.4 Issue: Arrowhead semantics in collaboration unclear |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-992 |
UML RTF 1.4: Description of context role, between state machine and model |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-996 |
UML RTF 1.4 Issue: Flow relationship has the incorrect semantics |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-995 |
UML RTF 1.4 Issue: <> keyword/stereotype |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-989 |
UML RTF 1.4 Issue: Deferred event ambiguity |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-988 |
UML RTF 1.4 Issue: Join in collaboration |
UML 1.2
|
UML 1.4
|
Resolved |
closed |
|
| UML14-987 |
UML RTF 1.4 Issue: State constraint on host object |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-991 |
UML RTF 1.4 Issue: ownerScope and targetScope |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-990 |
UML RTF 1.4 Issue: Guard evaluation for choice points. |
UML 1.2
|
UML 1.4
|
Resolved |
closed |
|
| UML14-986 |
UML RTF 1.4 Issue: Notation for call state |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-985 |
State machine name space |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-984 |
Issue Activity Package |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-983 |
ISSUE FOR UML, SECTION ActivityGraphs |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-982 |
Shouldn't the UML Package be allowed to own/reference UML 'Instances'? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-981 |
Inheritance of Stereotypes |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-980 |
Why is "FinalState" a separate metaclass ? |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-977 |
OCL: Let-expressions |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-979 |
Invalid OCL expression in initial transition |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-978 |
OCL: Samples of invalid typing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-976 |
OCL: class operation has no 'self' |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-975 |
OCL: String literals |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-974 |
OCL: Numeric constants missing |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-973 |
OCL: Literal collections |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-972 |
OCL: Enumeration types inconsistent with UML metamodel |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-971 |
OCL: Enumeration types |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-970 |
OCL: Feature calls on default target |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-967 |
OCL: Are keywords reserved or not |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-966 |
OCL: Consistency in grammar description |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-965 |
"Physical" Metamodel References in Diagrams (uml-rtf) |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-969 |
textual syntax cannot deal with identical class names in different package |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-968 |
OCL: Class context specification grammar incomplete |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-964 |
"Physical" Metamodel References (uml-rtf) |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-963 |
Precise "Physical" Metamodels Missing from Specification (uml-rtf |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-962 |
Language Name (uml-rtf) |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-961 |
OCL Error |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-960 |
Use of interfaces in associations |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-959 |
Generalization should be meta-metamodel element |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-958 |
role concept in UML remains rather vague |
UML 1.2
|
UML 1.3
|
Resolved |
closed |
|
| UML14-957 |
OCL issue |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-956 |
Strange GENERAl USE RESTRICTION |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-955 |
Error in the third postcondition for String::concat on page 6-31 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-954 |
The not-equals operator, "<>", |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-953 |
Divide operator is incorrect |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-952 |
pages 6-28 to 6-29 of OCL documentation |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-951 |
page 6-10 of OCL documentation for 1.3alphaR5 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-948 |
The second postcondition on Integer::div is incorrect |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-950 |
The postcondition seems to be incorrect for sequence::subSequence |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-949 |
The postcondition on set::collect seems to be incorrect |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-947 |
(Minor) Activity diagram change recommendation |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-946 |
OCL Standard package |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-945 |
There is an association between between Constraint and ModelElement |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-944 |
OCL should allow one constraint to reference another |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-941 |
action state symbol/state symbol difficult to distinguish when drawn by ha |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-940 |
UML Semantics, OMG-UML V1.2 Use Cases July 1998, page 2-99 |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
| UML14-943 |
UML has symbol for multiobject, not for multi-instances of other classifie |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-942 |
Dependencies (and other relationships) with role ends |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-939 |
Add Responsibilities as a new metatype |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-935 |
On aggregation. The white diamond name should be "shareable" |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-934 |
Metamodel and semantics for aggregations |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-938 |
Interface issue |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-937 |
Only single stereotyping is supported |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-936 |
Use of black diamond in the metamodel |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-933 |
Some attributes can be expressed in OCL |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
| UML14-932 |
Widen the naming characteristics |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-931 |
BooleanExpression written in OCL or some other language? |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-927 |
Infix operator use should be clarified |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-930 |
Generalized change events |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-929 |
There are issues that make OCL hard to formalize--document ad/98-10-01 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-928 |
Definition of OclAny leads to problems when formalizing OCL |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-924 |
Common operations should be added to collection types in OCL |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-923 |
Add OCL operation to refer to all new instances created during operation |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-922 |
Need well defined way to extend OCL |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-926 |
Set of allInstances should be referrable by the class name |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
| UML14-925 |
Add "Let"-like construct to OCL |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-919 |
Synchronous request |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
| UML14-921 |
Notation says swimlanes are packages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-920 |
ModelElement to Partition multiplicity should be many |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-918 |
Asynchronous action |
UML 1.1
|
UML 1.4
|
Resolved |
closed |
|
| UML14-917 |
Not instantiable |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-916 |
UML RTF Issue: Normative MOF-Compatible version of UML |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-915 |
Core package-backbone diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-912 |
Issue: Missing role names |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-911 |
Issue: Inheritance inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-914 |
MOF does not support association attributes in metamodels. |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-913 |
issue: Missing association names |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-910 |
Issue: Action does not define attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-909 |
Issue: Name attribute inheritance |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-908 |
Issue: abstract class inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-907 |
Figure 2-18 : redundant attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-906 |
UML Semantics (page 109) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-905 |
Association attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-904 |
missing association names |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-903 |
Issue: inheritance inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-902 |
Diagram missing attributes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-900 |
Are subsystems instantiable? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-901 |
Abstract class inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-899 |
Associations as parts of a composite. |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-898 |
Section 5.17 of Notation Guide: No mapping is given |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-896 |
Notation section describing activity states needed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-897 |
Existance of classes in classes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-895 |
States leading to joins in activity models |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-894 |
Activities operate by and on objects |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-893 |
ClassifierInState does not satisfy one of its stated usages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-892 |
Rules 3 and 4 for Transitions in state machines should be limited |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-891 |
UML Semantics, section Common behavior |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-890 |
Notion of "conceptual" or "specification-only" not supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-889 |
OCL should allow the use of "let" expressions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-888 |
Text on page 2-49 section 2.2 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-887 |
Text in Figure 2.13.7.1 ActivityState seems to be incorrect |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-886 |
Need to have relative precedence and, or, xor |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-885 |
Need way to approximate comparisons |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-882 |
Change events issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-881 |
Collection operation size not defined for infinite collections |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-884 |
pre value of object |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-883 |
It"s mistake to automatically flatten collections of collections |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-880 |
States of an object not referenceable from OCL expression |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-879 |
Implicit transitive import between packages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-878 |
Protocol state diagrams issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-877 |
Changes to figure 15 and description of ClassifierRole on page 82 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-876 |
Semantics for dynamic invocation of concurrent activity models are missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-875 |
Collection type within OCL missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-874 |
Operation asSequence Issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-873 |
No discription of the association between Classifier and Parameter is give |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-872 |
Stereotypes on Dependency, page 43 of V 1.1 (figure 7) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-871 |
Reflexive association in section 5.20.2 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-870 |
The class "Subsystem" inherits from "GeneralizedElement" twice |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-869 |
Class "Model" is too prescriptive |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-868 |
Clarify how types of attributes and parameters should be instantiated |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-867 |
Merge "Class" and "Interface" into one class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-866 |
UML 1.1 issue on Associations |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-865 |
Extension Point |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-864 |
Specification for method in a derived class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-863 |
State diagrams: action expressions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-860 |
Responsibilities hardly figure in these documents |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-862 |
Permit multiple stereotyping on relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-861 |
General recommended use of UML |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-858 |
Aggregation is poorly defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-859 |
"Inheritance" connection used is a generalization relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-857 |
Page 98: arrowhead issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-856 |
Page 94 --editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-855 |
Page 82: Add explanation |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-854 |
Page 80: Confusion with headings |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-852 |
Page 72: Example needs rejigging |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-851 |
Page 71: Distinction between Dependency and Association |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-849 |
Page 67: Why is discriminator not discussed in terms of power types? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-850 |
Page 68 overlapping |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-853 |
Page 79: Poor choice of arrowhead |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-846 |
Page 52 figure 20 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-845 |
Typos on pages 24, 40, and 50 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-848 |
Page 58: Add index entry |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-847 |
Page 57: mathematical issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-844 |
Page 35/6: Why are attributes and association not inherited? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-843 |
Page 35/6: Use of word type is confusing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-841 |
Page 30: Class scope attribute underlined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-840 |
Page 29: Protected member |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-842 |
Page 35/6 : Stereotypes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-839 |
Page 26: rename reponsibilities, rules, modification histories etc. |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-838 |
Page 24 Section 5.4.3 para 1: missing compartments |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-837 |
Page 24: add link to Interface |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-835 |
Page 13: Packages are GeneralizableElements |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-834 |
Page 11: Operation-Call |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-836 |
Page 20: Section 4.3.1 could be misleading |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-833 |
Editorials on pages iv, v, 3, and 4 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-832 |
Typos on page 90, 151 plus errors in page numbering |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-831 |
Page 143: "uses" as a stereotype on Generalization |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-830 |
Page 143: uses is a stereotyped dependency |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-829 |
Page 136: Model package relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-828 |
Page 98: Transition is an aggregation of guards |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-827 |
Uses and extends not types of generalization |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-826 |
Page 93: use case |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-824 |
Discussion on Collaborations and Interactions is confusing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-823 |
Typos on pages 55 and 62 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-825 |
Page 93: Is Namespace really aggregeation of use cases? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-822 |
Page 50 Table 3 "refinement" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-818 |
Page 47: Dependency is a unidirectional, client-server |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-817 |
Page 45 dependency lines 2/3 between model elements not instances? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-820 |
Page 50: should stereotypes be defined at the subclass level? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-819 |
Page 50: "instance" should be changed to "instatiate" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-821 |
Page 50: table 3 component |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-814 |
Page 38 para 2 line 3, one of its containers is deleted |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-813 |
Page 35 Diagram (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-812 |
Page 35 -Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-811 |
Class to be defined as an intension |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-816 |
Aggregation of class? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-815 |
Page 40 table 2 Model Element class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-810 |
How to stop an interface realizing a Data Type ? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-809 |
Why does GeneralizableElement inherit from Namespace? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-806 |
Page 16 lost fact that Class realizes an interface |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-808 |
Page 16 ---editorial (Element Ownership) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-807 |
Is name space really a *composite aggregation* of model elements? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-805 |
Interface must also have features |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-804 |
Why is Classifier an Aggregate of Features? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-803 |
Collaboration as a Classifier |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-802 |
Interfaces and support classes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-801 |
UML Semantics, p 81, 145 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-798 |
UseCaseInstance badly defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-800 |
Extension/recommendation needed for inner/outer transitions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-799 |
Notation for state machine inheritance |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-793 |
Collaboration showing instances |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-792 |
Inconsistency between stereotype tables |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-796 |
Multiple transitions from initial states should be allowed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-795 |
Modeling of guards |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-794 |
Collaboration::constrainingElement semantics |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-797 |
Semantics of terminate transitions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-790 |
Stereotypes for superclasses do not apply to superclasses |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-789 |
Inconsistent use of stereotypes, tagged values, and metamodel |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-788 |
Class WFR (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-787 |
Modeling of realization/specification |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-791 |
Stereotype modeled in two ways |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-786 |
GeneralizableElement should not inherit from Namespace |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-785 |
Syntax for Sequence Expressions inconsistently used |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-784 |
Threads of control in Collaboration Diagrams |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-783 |
Control Flow types not modeled |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-782 |
RaiseAction and TimingMark are not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-781 |
Mapping of concurrent subregions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-780 |
"do" action not supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-779 |
Notation for iteration in sequence diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-778 |
"derived" not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-775 |
WFR for bound elements missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-774 |
The meta-type of template parameters |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-773 |
Dependency wrongly mapped |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-777 |
<>, <>, <>, <>, not well supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-776 |
Namespace in case of containment |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-772 |
Package importing transitive |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-771 |
"invoked" not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-770 |
Bad example for LCA, main source, main target |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-769 |
Transition WFR badly written |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-768 |
Entry/Exit actions execution order |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-767 |
CompositeStates with non-composite subregions allowed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-766 |
Message::base undefined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-765 |
AssociationEnd-AssociationEndRole inconsistencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-764 |
Argument::type not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-762 |
WFR for instance links |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-761 |
Well-formedness Rules for Action::actualArguments |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-760 |
CallAction::request |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-759 |
CallAction::isAsynchronous and CallAction::mode |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-763 |
MessageInstance not used |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-754 |
Node and Component parent |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-753 |
Qualifier badly modeled |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-758 |
Action::isAsynchronous and Action::script not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-757 |
Signal::isAsynchronous and Signal::direction not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-756 |
Request"s parents |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-755 |
"implementation" association not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-752 |
Signature conflicts across an inheritance hierarchy |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-751 |
Exotic uses of generalization |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-750 |
Set of inheritable features not defined |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-749 |
Correspondence between operation and method (02) |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-748 |
Correspondence between operation and method |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-744 |
Signature conflicts not well defined (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-743 |
Features and ownedElements (2) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-742 |
"feature" defined twice |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-747 |
Use of language-dependant type expressions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-746 |
Return types for BehavioralFeatures |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-745 |
Package importing not well supported |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-739 |
UML Semantics 1.1, p26, Operation::isPolymorphic |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-741 |
Features and ownedElements (1) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-740 |
Signature conflicts not well defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-738 |
OCL Specification 1.1, section 8 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-737 |
OCL specification 1.1, p. 14, 5.13, example |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-736 |
OCL specification 1.1, p. 15, 5.14, second last paragraph |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-733 |
OCL specification 1.1, p. 32 |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-732 |
OCL specification 1.1, p. 10, 5.4.3, example 3 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-735 |
OCL specification 1.1, p. 24, 7.1.7 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-734 |
OCL specification 1.1, p. 30, 7.2.4 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-731 |
OCL specification 1.1, section 7.2.2 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-730 |
Definition of select and reject operations for Set"s is erranious |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-729 |
Difference between methods, attributes and operations not clear |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-728 |
Editorial issue: OCL spec 1.1, section 6.3, example 2, last row |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-727 |
UML 1.1 Semantics, section 8.2, page 66 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-726 |
Contents of section "Control Icons" is vague |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-723 |
Missing sentence |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-722 |
Editorial error in Semantics |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-725 |
Missing word - editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-724 |
Procedure undefined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-721 |
ActionState implicit deferring of events |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-720 |
internalTransition |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-718 |
Deep History Vertex |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-719 |
deferredEvent mentioned twice in Abstract Syntax |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-713 |
No mapping for send/receive time in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-717 |
Inconsistent definition of extends relationship |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-715 |
No mapping for TimingMark in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-714 |
No mapping for "transition string" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-716 |
No notation for ActivityState |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-709 |
Inconsistent constraint for discriminator |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-708 |
Missing notation for templates |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-712 |
No mapping for swimlanes in Sequence Diagram |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-711 |
Property "derived" not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-710 |
Interface specifier not mapped |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-705 |
Well-formedness rules only expressed in English |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-704 |
Well-formedness rules missing |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-707 |
Confusing text |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-706 |
Missing mapping for directed constraint |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-703 |
Inconsistent definition of stereotype "thread" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-700 |
Stereotypes applied to more than one ModelElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-699 |
English contradicts OCL in rule for CompositeState |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-698 |
Misleading name Link.linkRole |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-697 |
Enumeration OperationDirectionKind obsolete |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-702 |
Inconsistent definition of stereotype " process" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-701 |
Inconsistent definition of enumeration |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-696 |
ordered missing for Constraint.constrainedStereotype |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-695 |
Inconsistent definition of stereotype "friend" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-694 |
Inconsistent definition of stereotype "thread" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-693 |
Wrong aggregation kind for templates |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-689 |
Inconsistent attachment of Activity Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-692 |
Method visibility |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-691 |
Feature.owner must be optional |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-690 |
Extension points of operations not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-688 |
Inconsistent definition of state machine attachment |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-687 |
Inconsistent format of signal/event |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-686 |
More arrow types than message kinds |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-684 |
Attachment of message in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-685 |
Inconsistent mapping of labels in Sequence Diagram |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-682 |
UML 1.0: "role" should be "end" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-681 |
UML 1.0: Template example cannot be representaed in model |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-683 |
UML 1.0: Unknown model element "Qualifier" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-680 |
UML 1.0: Inconsistent name of stereotype "import" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-679 |
UML 1.0: multiplicity "unspecified" not possible |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-676 |
Inconsistent name space rules |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-675 |
UML 1.0: instances |
UML 1.1
|
UML 1.3
|
Resolved |
closed |
|
| UML14-678 |
UML 1.0: Stereotype "uses" applied to more than one class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-677 |
Inconsistent name for stereotype implementationClass |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-673 |
UML 1.0: Tagged value "location" |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-672 |
UML 1.0: Inconsistent mapping of interface circles |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-669 |
UML 1.0: Attachment of messages in Collaboration Diagrams |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-671 |
UML 1.0: Node/Component Instances not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-670 |
UML 1.0: No notation for ModelElement.implementation etc. |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-674 |
UML 1.0: Inconsistent arrow heads for dependencies |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-666 |
UML 1.o: Qualified things in Collaborations |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-665 |
UML 1.0: Collaborations not well defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-668 |
UML 1.0: No notation for ClassifierRole.availableFeature |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-667 |
UML 1.0: Collaborations and Association (role) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-664 |
CallEvent: operation label in figure 18 is not present |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-663 |
Signal label in figure 18 is not present |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-662 |
Figure 15, AssociationRole class issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-659 |
Description of ActionSequence indicates that it is composition of Actions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-658 |
ActionSequence class issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-661 |
Collaboration package: constrainingElement aggregation misdrawn |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-660 |
Collaborations package--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-657 |
Reception class has wrong attribute |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-656 |
Figure 12 shows no attributes for exceptions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-655 |
Behavioral Features called context |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-654 |
Request class is not an abstract class as indicated |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-653 |
Action class is no abstract class as indicated |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-652 |
Description of ViewElement indicates that it is subclass of Element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-647 |
Inconsistency of UML metamodel |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-649 |
Node class shown as subclass of classifier |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-648 |
Node class issue (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-651 |
Comment class shown as subclass of ModelElement class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-650 |
Description of component shown as subclass of class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-645 |
UML Notation Guide, boolean properties |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-644 |
UML Notation Guide, association ends |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-646 |
Association between Method and Operation |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-643 |
UML stereotypes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-642 |
UML potential inconsistency about stereotypes |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-641 |
Inconsistency of UML metamodel |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-640 |
Parameters/Attributes need Specification Classifiers |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-639 |
Predefined LinkEnd constraints issue |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-638 |
Predefined LinkEnd constraints shown as stereotypes in Notation Guide |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-636 |
diagram fragment at start of Model section on page 136 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-635 |
No notation defined in the Notation Guide |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-634 |
ActivityState in Figure 22 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-633 |
well-formedness rules for BehavioralFeature |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-637 |
Figure 8 (Semantics, p. 44) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-630 |
Figure 5 Semantics document (p. 16) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-629 |
Second para, Section 5.16.1: conflict with statement on p 141 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-632 |
Well-formedness rulw [2] for Class (Semantics, p. 27-28) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-631 |
Well-formedness rule [4] for Association |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-628 |
Section 5.16.1--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-627 |
Page 53 UML semantics: base class of TaggedValue not shown |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-624 |
Missing role descriptions |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-623 |
ModelElement Associations (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-626 |
Page 44 UML 1.1 Semantics, figure 8: no base class for ViewElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-625 |
Page 44 UML 1.1 Semantics, figure 8: no component role name |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-622 |
ModelElement Associations (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-621 |
ElementOwnership subclass of ModelElement? |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-619 |
Package dependencies (08) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-618 |
Package dependencies (07) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-620 |
Package dependencies (09) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-617 |
Package dependencies (06) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-616 |
Package dependencies (05) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-613 |
Package dependencies (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-612 |
UML 1.1 bug |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-615 |
Package dependencies (03) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-614 |
Package dependencies (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-609 |
Page 10 UML 1.1 Semantics, duplicate entries listed |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-608 |
Page 98 of UML 1.1 Semantics, figure 18 (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-611 |
UML 1.1 Semantics: Partition (pp.121 123) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-610 |
Page 102 of UML 1.1, StateVertex class misses description |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-607 |
Page 98 of UML 1.1 Semantics, figure 18 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-606 |
Page 98 of UML 1.1 Semantics, figure 17 (04) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-605 |
Page 98 of UML 1.1 Semantics, figure 17 (03) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-604 |
Page 98 of UML 1.1 Semantics, figure 17 (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-603 |
Page 98 of UML 1.1 Semantics, figure 17 (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-598 |
Page 43 of UML Semantics, figure 7 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-597 |
Page 43 UML 1.1 Semantics, figure 7 --editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-600 |
Page 46 of UML 1.1 Semantics, description of associations for ModelElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-599 |
Page 44 UML 1.1 Semantics, figure 8 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-602 |
Page 47 of UML 1.1 Semantics, description of ViewElement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-601 |
Page 47 of UML 1.1 Semantics, description of Refinement |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-596 |
Page 16 of UML Semantics, figure 5 |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-595 |
Page 62---editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-594 |
Page 62 "PseudostateKind"--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-592 |
Page 61: CallConcurrencyKind and EventOriginKind not defined |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-593 |
Page 61 "EnumerationLiteral"--editorial |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-587 |
Page 50 table 3: Dependency Model elements (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-586 |
Page 50 table 3: Dependency model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-591 |
Page 60 figure 10: Data types |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-590 |
Page 9 figure 2: foundation packages |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-589 |
Page 137 table 6: Model management - Standard Elements |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-588 |
Page 50 table 3: Component model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-585 |
Page 50 table 3: Auxiliary Elements-Standard Elements (Component model ele |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-584 |
Page 40 table2: Generalization model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-583 |
page 40 table2: Classifier model element |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-582 |
Page 40 table 2:Constraints Model |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-581 |
Page 40, table 2: Core - Standard Elements |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-580 |
Page 54 - ConstrainedStereotype |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-579 |
Page 39 - ModelElement/Dependency associations |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-578 |
Page 16- The association from parameter to classifier has a 1-1 cardinalit |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-577 |
Page 121 - Partition has no parent class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-576 |
Page 98: ActionSequence has no parent class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-572 |
Page 60 - GraphicMarker |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-574 |
Page 35/37 - AssociationRole |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-573 |
Page 60 - MultiplicityRange |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-575 |
Page 81: message has no parent class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-571 |
Page 60 - visibilityKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-569 |
page 60 - EventOriginKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-568 |
page 60 - CallConcurrencyKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-570 |
Page 60 - PseudostateKind |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-564 |
UML Documentation--Typos (05) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-565 |
UML Documentation--Typos (06) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-566 |
UML Documentation--Typos (07) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-567 |
Error on association owners |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-562 |
UML Documentation--Typos (03) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-561 |
UML Documentation--Typos (02) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-560 |
UML Documentation-Typos (01) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-563 |
UML Documentation--Typos (04) |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
| UML14-559 |
UML 2 issue, Common Behaviors |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-558 |
Components / provided and required interfaces -- derived or subsets |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-557 |
Feature;ModelElement |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-554 |
"Physical" Metamodel Package Structure (uml-rtf) |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-556 |
TaggedValue in TaggedValue |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-555 |
Ambiguous semantics of classifier ownerscope |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-471 |
UML2 super/notation/Keywords |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-470 |
Appendix B/Standard Stereotypes too heavyweight and incompletely defined |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-480 |
UML 2 Super / Interactions / incorrect multiplicity for PartDecomposition |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-479 |
The contents of the Interfaces package is shown in Figure 51 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-482 |
UML 2 Super / Interactions / navigability of enclosingOperation |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-481 |
UML 2 Super / Dependencies / Abstraction should have an optional mapping |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-478 |
UML 2 Super / Templates / subsetting templateParameter |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-477 |
UML 2 Super / General / Idenitfy sections specifying run-time semantics |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-476 |
UML 2 Super / Classes / |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-473 |
importedMember property |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-475 |
UML 2 Super / Interactions / Two typos |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-474 |
missing closing bracket |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-472 |
"• value : InstanceSpecification |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-377 |
Corrections and improvements to glossary definitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-376 |
The name "required interface" is misleading |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-373 |
UML 2.0 significant typo - collaboration diagram |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-372 |
targetScope on StructuralFeature and AssociationEnd |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-375 |
Specification of parametric models |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-374 |
Excessive syntactic and semantic overlap between structured Classifiers |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-371 |
UML Superstructure: 03-08-02 / <> |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-370 |
ad-03-04-01 Chap 3 p. 151 Table 3/Composite structures: ComplexPort |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-369 |
ad-03-04-01 Chap3 p.146/Composite structures: Connected elements constraint |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-368 |
Chap 3 p. 142-143 Figure 3-35 /Composite structures: Port multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-553 |
Issue 6090 correction |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-543 |
UML2 Super / Classes / Operation constraints |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-542 |
UML2 Super / ordering of association ends |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-541 |
Q re Parameter |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-537 |
UML2 super/interactions |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-536 |
UML 2 Super / Templates / invalid multiplicity |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-535 |
UML 2 Super / Profiles / problem with name collisions |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-548 |
XMI schema (02) |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-547 |
Question about Enumeration and EnumerationLiteral |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-540 |
UML 2 Super / missing owners of concepts |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-539 |
UML 2 Super / state machines / state should be a namespace |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-538 |
UML 2 Super/Connector |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-546 |
UML2 Super / Common Behavior / Trigger should be a named element |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-545 |
UML2 Super / Use cases / navigation from subject to use case |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-544 |
UML 2 Super / General / superclass pointers |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-552 |
Issue 6094 correction. |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-551 |
UML 2 Super/Interactions/Need unattached lifelines |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-534 |
transition is simply never enabled |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-533 |
UML Sequence diagram |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-550 |
property strings on association ends |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-549 |
change trigger |
RAS 2.0b1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-405 |
Clarify termination of asynchronous invocations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-404 |
Appendix A Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-403 |
Section 17 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-396 |
Section 8.3.3 Realization |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-395 |
Section 8.3.1 Component |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-401 |
Section 14.4 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-400 |
Section 14.4 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-394 |
Section 8.3.1 Component |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-399 |
Section 14.3.14 Message |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-398 |
Section 10 Deployments |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-393 |
Section 8.1 Overview |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-402 |
Section 14.4 Diagrams (02) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-397 |
Section 9.4 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-450 |
UML2 Super/Ports |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-449 |
UML2 Super/Connector |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-457 |
UML 2 Super / Activities / association end naming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-456 |
UML 2 Super / Activities / inconsistency in representing subsetting |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-454 |
UML 2 Super/Activities/assocition end specialization consistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-452 |
subsettedProperty->forAll(sp | isDerivedUnion) ? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-451 |
UML2 Super/Connector End |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-455 |
UML 2 Super/Activities/invalid multiplicity 0 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-447 |
UML2 Super/Structured Classes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-453 |
UML 2 Super/Activities/end naming consistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-448 |
Page 164 - there are two constraints sections for Connector |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-444 |
UML 2.0 Superstructure Derived Union vs. derivationExpression? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-443 |
UML 2.0 Superstructure reccomendation (derived unions) |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-442 |
UML 2 Super / use cases / incorrect comments in notation section |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-441 |
Error in definition of PackageMergeKind |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-446 |
UML2 Super/parts |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-445 |
UML2 Super/Composite Classes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-437 |
section 9 (State Machines) of 3rd revision |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-436 |
UML 2 Super/Actions/PrimitiveFunction missing properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-434 |
Time trigger notation in state machines |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-433 |
No way to represent "uninterpreted" actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-438 |
UML 2 Super/Actions/non-existent feature "multiplicity" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-435 |
Notation when guards are used in conjunction with triggers in transitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-440 |
UML 2.0 Superstructure 3rd revision - Owner of triggers? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-439 |
UML 2 Super/Action/featuringClassifier misinterpreted |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-493 |
UseCase - Constraint for non-circular include relation |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-492 |
What level of MOF 2.0 is the metamodel for UML 2.0? |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-484 |
UML 2 Super / Realize keyword-stereotype |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-483 |
UML 2 Super / Classes / Properties owned by properties |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-489 |
Inconsistent labeling of tables in Section 12.4, Activities.Diagrams: p 367 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-488 |
Inconsistent labeling of tables in Section 12.4, Activities.Diagrams: p 366 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-487 |
Inconsistent labeling of tables in Section 12.4, Activities.Diagrams p365 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-486 |
UML 2 Super / Deployments / Invalid cross-references |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-495 |
UML 2 Super / use cases / incorrect table title |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-494 |
UseCase - Include - Constraint for irreflexivity |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-485 |
UML 2 Super / Classes / Dependency should not be abstract |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-496 |
UML2 superstructur: actor |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-491 |
UML 2 Super / General / specialization labeling convention |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-490 |
Typo in Collaboration Diagram figure |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-386 |
UML 2 Issue: Connector types |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-385 |
glossary |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-383 |
Abandon the OMGS4LMMA |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-382 |
14.3: StateInvariant and ExecutionOccurrence |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-381 |
UML 2.0 Superstructure FTF issue - Profiles |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-380 |
Removal of gratuitous restrictions to software applications |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-388 |
Section 7.3.1 ElementImport |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-387 |
UML 2 Issue: Include(s) and Extend(s) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-379 |
Diagram Taxonomy corrections |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-378 |
Inconsistent use of terms "implement" and "realize" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-392 |
Section 7.18 Diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-391 |
Section 7.15.3 Interfaces |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-384 |
Change 'Part' to 'Role. |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-390 |
Section 7.13.2 Package Merge |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-389 |
Section 7.3.5 PackageImport |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-412 |
concurrent vs. parallel ExpansionRegions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-411 |
Use Case Metamodel - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-420 |
Operation without - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-419 |
Components and artifacts: Dependency problem - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-416 |
AcitivityEdge: weight=all vs weight=null - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-415 |
Large diamond for binary associations legal? - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-418 |
Guard conditions at fork nodes - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-417 |
Token flow semantics: Implicit fork and join - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-409 |
Multiobject in UML2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-408 |
Outputting constants |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-414 |
Diagrams, Diagrams, Diagrams ... UML 2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-413 |
Binary associations decorated with large diamonds legal? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-407 |
Protocol machines do not subset state invariant |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-406 |
Conditions for parameter sets (02) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-410 |
ActivityFinalNode and running actions - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-518 |
adopt a single notation to specify text strings used in the notation |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-517 |
Appendix A of the superstructure spec |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-516 |
UML 2 Super / Activities / Fig.192 constraint duplicated |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-515 |
Ambiguous semantics of isStatic - resubmission of issue 4446 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-514 |
UML 2 Super / Interactions / Invalid subsetting for enclosingOperand |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-513 |
UML 2 Super / Classes / makesVisible () operation incorrect |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-512 |
Super and Infra / Kernel-Classifiers / incorrect hasVisibilityOf definition |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-526 |
Operations and derived attributes |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-525 |
use of stereotypes |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-524 |
UML 2 Super / Appendix A / Typos |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-523 |
UML 2 Super/Interactions/Alternative with all false guards |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-522 |
UML 2 Super / General / Classes chapter organization |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-521 |
UML 2 Super / State machines / incorrect navigation specifications |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-520 |
UML 2 Super / General / consistent formatting conventions |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-519 |
UML 2 Super / General / Dcoument conventions |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-528 |
Activity Diagrams: Relax Traverse-to-Completion semantics |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-530 |
UML2 super/Deployments/CommunicationPath |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-529 |
State machines / name of transitions association end |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-532 |
UML2 Super/Composite Structure |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-531 |
UML 1 activities |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-527 |
Composite Structures, 03-08-02.pdf |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-431 |
Incorrect usage/definition of "emergence" in Common Behavior Chapter |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-427 |
The node "Order cancel request" that appears in figure 6-86 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-426 |
GeneralizationSet Description clarification - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-429 |
Typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-428 |
Order cancel request |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-423 |
Package Extensibility <> - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-422 |
Dependency notation for interfaces - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-421 |
Inconsistency concerning VisibilityKind - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-424 |
does "is not instantiable" imply "isAbstract"? - UML2 Superstructure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-425 |
Activity nodes and Stereotypes - UML2 Superstructure issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-432 |
Missing actual arguments in submachines states |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-430 |
/pages 485,487,495/mixed names for state machine diagram |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-511 |
Ambiguous example of a local action on a Lifeline in Figures 334, 335 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-510 |
ambiguous definition of the scope of a break CombinedFragment |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-509 |
UML 2 Super/Interactions/inconsistent spelling for InteractionOperator |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-502 |
Ambiguous sentence and typo in description of EventOccurence |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-501 |
graphic nodes for state invariant and continuation are not always distingui |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-498 |
Ambiguous semantics of isStatic |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-497 |
self-activation notation in Sequence diagrams missing |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-505 |
UML 2 Super/Interactions/rationale subsections not informative |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-504 |
UML 2 Super/Interactions/incorrect grammar for |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-507 |
word "execute" in definition of alternative CombinedFragment is ambiguous |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-506 |
UML 2 Super/Interactions/Ambiguous description of state invariants |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-500 |
UML 2 Super/Interactions/incorrect text and table title for Table 19 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-499 |
UML 2 Super/Interactions/incorrect text before Table 14 |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-503 |
UML 2 Super/Interactions/incorrect spelling of EventOccurence |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-508 |
text differs from metamodel for critical region InteractionOperator |
XMI 2.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-466 |
UML 2 Super / state machines / incorrect property redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-465 |
UML 2 Super / state machines / non-existent property reference |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-462 |
Ambuiguity in value pin evaluation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-461 |
page 136, "BasicComponents", |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-468 |
UML 2 Super / state machines / non-existent return type |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-467 |
UML 2 Super / state machines / misplaced operation definition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-458 |
UML 2 Super / Activities / subsetting two properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-460 |
Consistent Naming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-464 |
UML 2 Super / state machines / oclIsKindOf arguments error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-459 |
UML2 Super/Signal |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-463 |
UML 2 Super/State machines/pseudostate name consistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-469 |
UML 2 Super / use cases / invalid subsetting |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-366 |
ad-03-04-01 Chap 3 p. 137/Composite structures: Connector multiplicity >2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-365 |
ad-03-04-01 Chap 2 p. 118 Figure 2-15/Components: Wiring notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-367 |
ad-03-04-01 Chap 3 p. 137-138/Composite structures: Connector semantics |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-364 |
UML 2 Infras./Interactions/ execution occurrence should not be abstract |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-219 |
Typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-225 |
7.4.1 Multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-224 |
7.3.1 ElementImport |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-218 |
Clarify that profiles can contain model libraries |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-217 |
Notation for anonymous instance |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-221 |
UML Superstructure 03-08-02: Loop node notation missing |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-220 |
UML Superstructure: 03-08-02 -- typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-215 |
Notation for attributes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-214 |
Property string undefined |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-226 |
InstanceSpecification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-216 |
Instantiates stereotype |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-223 |
No notation defined for suppressing attributes or operations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-222 |
Notation mismatch for the realization dependency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-177 |
Parameter set corrections 3 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-181 |
Streaming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-180 |
Parameter set corrections 6 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-179 |
Parameter set corrections 5 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-178 |
Parameter set corrections 4 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-332 |
Outgoing edges of initial nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-331 |
Port is a Property in XMI |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-326 |
InformationFlow realization |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-325 |
Dependency multiplicity to CollaborationOccurrence |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-330 |
Ports as properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-329 |
partWithPort without ports |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-323 |
Control pins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-322 |
Profiles in fixed repositories |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-328 |
Association end names and part types |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-327 |
Deployment location |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-333 |
Guards on initial nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-324 |
Control at joins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-228 |
7.11.2 Association |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-227 |
7.10.1 Operation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-234 |
UML 2 Super/Metamodel::IntermediateActivities/redundant merge error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-233 |
BehaviorStateMachines/missing owningState end name |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-238 |
UML 2 Super/Metamodel::Kernel::DataTypes/missing renames |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-237 |
AuxiliaryConstructs::Templates::Operation/extra space |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-232 |
UML 2 Super/Metamodel::BasicBehaviors/package merge issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-231 |
7.15.3 Interface |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-235 |
UML 2 Super/Metamodel::Communications/redundant merge error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-229 |
7.14.1 Abstraction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-236 |
UML 2 Super/Metamodel::Nodes/redundant merge error |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-230 |
7.14.6 Realization |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-195 |
Pins on structured nodes 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-194 |
Pins on structured nodes 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-203 |
Action packaging |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-202 |
BroadcastSignalAction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-196 |
Time spec text |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-200 |
Update actions for isUnique |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-193 |
ExpansionRegion |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-197 |
Partition semantics |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-198 |
Activity frame and parameter nodes 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-201 |
actions on properties that are association ends |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-199 |
Activity frame and parameter nodes 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-347 |
Flows across SAN boundaries |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-346 |
Initial nodes in structured actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-345 |
Parameters in Features and Common Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-342 |
Clarify join specs referencing control flow edges |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-341 |
Combining joined tokens |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-349 |
AcceptCallAction in SAN |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-348 |
Terminating a SAN |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-344 |
Join example |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-343 |
Clarify join rules |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-336 |
Side effects of value specifications |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-335 |
Activity final clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-339 |
ReadSelfAction with no host |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-338 |
Decision behaviors on control tokens |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-340 |
Clarify ReadSelfAction in activity behaviors |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-337 |
Guard evaluation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-334 |
Caption typo |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-291 |
Confusion regarding XMI for use of stereotypes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-290 |
Actors that are outside and inside the system |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-289 |
UML2 super/pgs.17 + 598/"topLevel" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-288 |
Actor |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-287 |
Multiplicity of Regions owning Transitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-286 |
State list |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-285 |
UML 2.0 serious layout problems with activity diagrams |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-284 |
Stereotypes for Actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-283 |
UML Superstructure: 03-08-02 / Typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-282 |
UML 2 Super/Compliance points/confusing and redundant |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-281 |
UML 2 Super/pg.81/semantics of subsetting-specialization-redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-280 |
UML 2 Super/pg.379/anyTrigger clarifications |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-279 |
UML 2 Super/pg. 556/notation for template binding inconsistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-278 |
UML 2 Super/pg. 471/choice pseudostate notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-277 |
UML 2 Super/pg.471/unclear terminate state semantics |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-276 |
UML 2 Super/pg.519/multiplicity semantics of use case associations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-295 |
Question about InterruptibleActivityRegion |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-294 |
fig 141 p205 and 7.13.2 p101 / just what sort of relationship is < |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-293 |
Metamodel for applying a stereotype |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-292 |
Association not affecting ends |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-275 |
UML 2 Super/pg.427/missing notation description for lifelines |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-274 |
UML 2 Super/pg.429/incorrect constraint for Message |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-273 |
UML 2 Super/pg.416/incorrect multiplicities for event occurrence |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-272 |
UML 2 Super/pg.395/multiple meaning of exception |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-271 |
UML 2 Super/pg.235/missing semantics of destroy action |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-270 |
UML 2 Super/pg.130/incorrect stereotype name |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-267 |
UML 2 Super/pg.109/Permission redundant |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-265 |
UML 2 Super/pg.64/Classifier redefinition notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-266 |
UML 2 Super/pg.95/attributes in data types clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-268 |
UML 2 Super/pg.99/misnamed "packageMerge" attribute |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-269 |
UML 2 Super/pg.130/missing notation explanation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-264 |
UML 2 Super/pg.79/underlined operation syntax missing |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-312 |
PackageMerge (from Kernel) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-311 |
Sequence diagram conditions on Message arrows |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-319 |
UML2 Super/Instances |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-318 |
UML2 Super/Ports |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-310 |
Recommendation for InteractionOccurrences |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-309 |
UML 2 Super / Interactions / No way to model reply messages |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-321 |
description of Component on page 137 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-320 |
Figure 61 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-313 |
UML2.super (or infra)/Profiles-Stereotype (18.3.7) |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-317 |
UML 2 Super/Components & Deployment chapters missing OCL constraints |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-316 |
UML2 Super/Profiles |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-314 |
UML2 Super/Composite Structures |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-308 |
UML Superstructur 03-08-02: Notation for ConditionalNode is missing |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-315 |
UML2 Super/Kernel::Classifier |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-263 |
UML 2 Super/pg.78/missing return types syntax |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-262 |
UML 2 Super/pg.78/operation redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-258 |
UML 2 Super/Metamodel::UseCases/Extend and Include are not NamedElements |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-257 |
UML 2 Super/Metamodel/missing namespaces for metaclasses |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-254 |
UML 2 Super/Metamodel/Mis-named Manifestation class |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-253 |
UML 2 Super/Metamodel::Templates/missing return type |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-261 |
UML 2 Super/Spec/completing mandatory sections |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-252 |
UML 2 Super/Metamodel::CommonBehaviors/redundant class? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-256 |
UML 2 Super/Metamodel/missing owners for metaclasses |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-255 |
UML 2 Super/Metamodel/mis-spelled implementingClassifier" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-260 |
UML 2 Super/Metamodel/missing source and target for InformationFlow |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-259 |
ProtocolStateMachines/ProtocolStateMachine not a type of Feature |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-209 |
Protocol state machines are not pre/postconditions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-212 |
Replace "initial value" with "default value". |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-211 |
TimeObservationAction can't return values |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-208 |
Diamond notation for merge junctions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-207 |
Activity attributes on Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-213 |
Kernel::Classifier missing "attribute" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-210 |
Interactions view of state machines/activities |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-206 |
Concrete Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-204 |
Composite structure dependent on Behavior |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-205 |
Complex port |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-307 |
UML 2 Super / Interactions / no create message |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-306 |
UML2 Super / Primitive Types / implementation issue |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-296 |
UML super/Section 2/Compliance points |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-300 |
Defenition of redefines????? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-299 |
UML 2 super/Composite Classes/Connecting parts of parts |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-303 |
UML2 Super / association end naming convention |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-302 |
UML2 Super / Classes/ Incorrect reference to "access" |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-305 |
UML 2 Super / State machines-CommonBehavior / undefined owner of triggers |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-304 |
UML2 Super / SimpleTime package / missing multiplicities |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-298 |
fig236 Datastore example/Datastore should not directly linked with actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-297 |
UML 2 Super/p125 and p126/typos |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-301 |
What does redefines mean in package extensibility? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-356 |
UML 2 Super / Interfaces / Cannot nest classes in interfaces |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-355 |
UML 2 Super / state machines / restriction on redefining transitions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-352 |
Typo on Notation for CombinedFragment? |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-351 |
Visibility of a Package |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-359 |
UML 2 Super / Simple Time / incorrect multiplicities |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-358 |
UML 2 Super / Interface / missing owner of operation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-361 |
UML 2 Super / Package Templates / StringExpression inconsistency |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-360 |
UML 2 Super / Activities / inconsistent naming |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-353 |
Figure 395 requires a lot more explanation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-363 |
UML 2 super / Templates / parameters cannot have names |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-362 |
UML 2 Super / Deployments / node composition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-350 |
Questions about CentralBufferNode semantic |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-354 |
UML 2 super / state machines / entry and exit actions cannot be redefined |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-357 |
UML 2 super / Activities / structured activity node contradiction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-244 |
UML 2 Infra/Section 5.9/missing merge rules |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-243 |
UML 2 Super/Metamodel/package merge and visibility |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-247 |
UML 2 Super/Metamodel::BasicActivities/inGroup problem |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-246 |
UML 2 Super/Metamodel::StructuredClasses/erroneous association |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-245 |
UML 2 Super/Package Merge/redefinition rules and standard OO languages |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-241 |
UML 2 Super/Metamodel::Constructs/inconsistency with Kernel |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-240 |
UML 2 Super/Metamodel::BasicBehaviors/missing redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-250 |
UML 2 Super/Package Merge/missing rule for operations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-249 |
UML 2 Super/Metamodel::Compliance::L3/Missing merges |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-242 |
UML 2 Super/Metamodel/merging of non-redefinable model elements |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-239 |
UML 2 Super/Metamodel::Kernel::Packages/missing redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-248 |
UML 2 Super/Metamodel::StructuredActivities/double redefinition |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-251 |
Profile/inability to attach a stereotype to an element |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-191 |
SendObjectAction |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-190 |
Clarification of insert |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-185 |
Colon notation for pins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-184 |
Local pre/postcondition example |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-182 |
Parameter semantics clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-192 |
ExceptionHandler 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-189 |
No-token activity termination clarification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-187 |
Notation for for global pre/postconditions actions |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-183 |
Behavior execution instances |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-188 |
Notation for isSynchronous |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-186 |
Value Pin notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-171 |
ObjectFlowEffect |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-170 |
Optional parameters |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-176 |
Parameter set corrections 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-174 |
ObjectNode.isUnique |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-173 |
Reentrancy 3 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-169 |
Pin multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-175 |
Parameter set corrections 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-172 |
ExecutableNode, ControlNode should be abstract |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-133 |
UML's use of the word "unique" for multiplicity is ambiguous |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-132 |
UML 2.0 Superstructure: Operation vs. Attribute notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-135 |
The description of DataType is plainly wrong in the specification |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-134 |
notation for shared aggregation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-139 |
Question on Connectors - fig 2-17 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-138 |
There appears to be a typo on page 2-148, in section 2.12.2.13 on StubState |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-137 |
Well-Formedness Rules for Procedure on Common Behavior Package |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-141 |
An error in Figure 464 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-140 |
PackageableElement |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-145 |
Figure 63 missing notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-144 |
Interface Figure 62 uses wrong notation |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-136 |
Description of GeneralizationSet |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-142 |
Section 1.3, ElementImport semantics on page 10 of ad/2003-04-01 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-143 |
Obsolete notation used in state machine - transition examples |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-55 |
Profile Notation |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-54 |
Appendix A, UML Standard Elements |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-58 |
Issue: Conflicting WFRs on Transition |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-57 |
Add Multiplicity to Parameter. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-56 |
Events, signals, stimuli, etc. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-61 |
Predefined datatypes |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-60 |
The definition of Multiplicity in Datatypes does not list the range associa |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-65 |
Component notation: logical compartments |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-64 |
Exceptions do not correspond to common usage |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-53 |
Clarify the origin of an Action in a Collaboration. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-59 |
Ambiguous semantics of classifier targetscope |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-63 |
Event => Event Specification |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-62 |
The text and OCL of rule #5 for Method do not say the same thing. |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-37 |
Another State machine issue |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-36 |
Data Types Misplaced in the "Physical" Metamodel (uml-rtf) |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-30 |
Inheritance violation in "Auxiliary Elements" |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-33 |
class EnumerationLiteral issue |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-35 |
Operations and Constraints Missing from "Physical" Metamodels |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-31 |
Incomplete Inheritance Specification |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-32 |
Datatypes: Expression |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-34 |
Interfaces on Nodes |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-38 |
UML RTF 1.4 Issue: Dynamic concurrency arguments |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-39 |
UML RTF 1.4 Issue: Parallel action iteration |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-168 |
Pin/parameter matching 4 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-167 |
Pin/parameter matching 3 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-158 |
Weight=all |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-157 |
Provide notations for Loop and Conditional |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-163 |
Multiple outputs of object flow transformations |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-162 |
Keywords or properties |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-159 |
Tokens at fork |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-161 |
ExpansionRegions keywords |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-165 |
Pin/parameter matching 1 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-160 |
ActivityFinalNode |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-166 |
Pin/parameter matching 2 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-164 |
Pins owned twice |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-131 |
representation of arrays of values in an action language |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-130 |
2.5.2.29 Node |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-128 |
2.5.2.15 Dependency |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-123 |
2.5.2 Abstract Syntax |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-122 |
Section: 2.5.2.10 Classifier |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-129 |
2.5.2 Abstract Syntax |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-121 |
Designates a Generalization (02) |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-125 |
2.5.2.27 ModelElement |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-126 |
2.5.2.10 Classifier |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-124 |
2.5.2.16 Element |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-127 |
2.5.2 Abstract Syntax |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-82 |
UML 1.4: ClassifierRole contents problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-81 |
UML 1.4: Node, Artifact, Package and Model contents problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-89 |
Suggest that alternate syntax used in section 6.5.5 be adopted thoughout |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-88 |
Invalid XMI.link.atts in UML 1.4 DTD |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-95 |
UML 1.4.1 should use MOF 1.4 |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-94 |
Add action for invoking an activity |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-84 |
UML 1.4: Wrong target for StateMachine.top association |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-83 |
UML 1.4: AttributeLink containment error |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-87 |
Definitions in glossary don't conform to any standard for definitions |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-86 |
Composite relationship between Event and StateMachine |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-92 |
Simplify inputs/outputs of procedures |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-91 |
match/correspond clarfication |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-93 |
StartStateMachine clarification |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-90 |
Namespace.contents |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-85 |
Adding events to the class definition |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-17 |
Parametrizable model elements not shown |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-119 |
Inconsistency regarding guards on forks |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-118 |
spelling of the word Use Case |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-110 |
There is an unnecessary condition in rule 1 of the Namespace element |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-109 |
Rule 6 of the Method element isn't formulated well |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-115 |
There is a misprint in rule 2 of the Object element: “Stimuli” instead of “ |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-114 |
There are misprints with numeration of rules of the Instance element |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-112 |
there is something wrong with rule 3 of the Trace element |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-120 |
The first sentence is not consistent with figure 2-9 on page 2-17 |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-113 |
Wrong alphabetical order: DataValue section should be before DestroyAction |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-111 |
Add rule to Namespace element |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-116 |
There is a misprint in rule 1 of the SubsystemInstance element |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-117 |
font sizes |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-69 |
Using or implementing an interface of a Subsystem |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-68 |
XML attribute "isPolymorphic" does not exist in UML 1.3 or UML 1.4 XMI DTD |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-67 |
Optimize Instance data values |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-66 |
Component notation: showing delegation of messages |
XMI 1.2
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-75 |
UML 1.4: State containment problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-74 |
UML 1.4: Action problem in Collaborations |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-80 |
UML 1.4: Event containment problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-79 |
UML 1.4: Stimulus containment |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-77 |
UML 1.4: Transition containment problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-76 |
UML 1.4: ExtensionPoint containment problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-78 |
UML 1.4: Feature containment problem |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-72 |
Compliance to the UML" pp xxxi -- Editorial? |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-71 |
Nameclash in UML 1.4 |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-70 |
Using OCL at the meta-model level |
UML 1.4
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-73 |
UML 1.4: Action containment error |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-19 |
Guard in current metamodel can be replaced by Constraint with stereotype |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-18 |
Need for notation for dealing with evolution of UML models |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-25 |
Missing OCL |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-24 |
OCL needs to be added |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-26 |
ElementOwnership |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-28 |
extension to the notation for a transition |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-23 |
Page 19 semantic doc. name |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-22 |
UML 1.1.section 4.2:editorial |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-27 |
User-defined symbols for tagged values and properties |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-29 |
Associate a predicate with a state |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-21 |
Figure 7 p. 43 of the UML semantics guide |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-20 |
AssociationEnd needs ownerScope |
XMI 1.0
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-151 |
running a “Check Model” in Rose you get the following errors |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-154 |
Clarify wording on executable activity nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-153 |
Outgoing edges from input pins |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-150 |
UML2 super/pg. 580/Stereotype typo |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-149 |
UML2 super/pg.470/entry and exit points for composite states |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-148 |
Multiplicities diagram in section 7.4 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-156 |
Action should be concrete |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-155 |
Edge constraint for control nodes |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-146 |
Strange notation in Figure |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-152 |
Variable and Pin multiplicity |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-147 |
No Glossary in 03-08-02 |
UML 1.5
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-100 |
Initial state for composite states - OCL example and missing constraint |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-99 |
UML 1.4 - Partition relates to nothing |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-104 |
In v1.4, section 3.84.1 the paragraph on semantics |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-103 |
Section 2.13.4.3 |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-101 |
UML Issue - Inconsistency between UML 1.3 XMI and DTD |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-107 |
Section number duplicated |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-106 |
Section 3.90.2.2 |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-97 |
Well-formedness rules 4 and 6 on 2.12.3.4 PseudoState |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-96 |
A_context_raisedSignal |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-102 |
How does one indicate the target object for a CallState |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-105 |
parameters of object flow states |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-98 |
Well-formedness rules for 2.12.3.8 |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-108 |
Swap rule 2 and rule 3 of the Binding element |
XMI 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-49 |
MOF rules should disallow certain composition relationships |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-48 |
Notation for inherited associations |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-52 |
Conflicting constraint between ActivityGraph and StateMachine. |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-51 |
Attributes obsolete in UML 1.3 |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-50 |
Interface of an object |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-46 |
Why is a StateMachine's top a State instead of a CompositeState? |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-45 |
UML 1.4 RTF Issue: Multiple languages for uninterpreted strings |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-42 |
Efficient diagrammatic notation for Collaboration Specifications |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-41 |
Statemachine/state as Namespace |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-40 |
UML RTF 1.4 Issue: Missing notation mapping for association in composite |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-47 |
Document 99-06-08 - UML Spec |
UML 1.3
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-43 |
ClassifierRoles should be independent of specific underlying base Classifi |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-44 |
UML 1.4 issue: Top state in activity graphs |
XMI 1.1
|
UML 1.4.2
|
Resolved |
closed |
|
| UML14-7 |
issues and bugs on the UML 1.4 Draft |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-6 |
class TaggedValuewill two association-ends with the same name "stereotype" |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-14 |
Figure 2-15 of the uml 1.4 spec |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-13 |
page 2-163, the statemachine semantics escription |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-16 |
isPolymorphic is never in a diagram |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-15 |
well-formedness rule for Package is missing inUML 1.4 |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-10 |
it's => its on page 3-150. |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-9 |
Wf 2 for AssociationEnd |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-8 |
2.9.2 Abstract Syntax |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-12 |
Notation example typo in Fig. 3-99 |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-11 |
The glossary entry "call" should be "call state". |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-3 |
elimination of the Association Class TemplateParameter |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-2 |
2) Page 2-49, additional operation #7 for Classifier |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-5 |
Remove uses of multiple inheritance from UML meta model |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-4 |
Who owns a Comment? |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
| UML14-1 |
Page 2-47, well-formedness rule #2 for Classifier |
UML 1.3
|
UML 1.4
|
Resolved |
closed |
|
) should be available on all namespace elements.
indicates that the association (with the implicit name of parameter)
a
