UML14-1046 |
Type vs. Implementastion class |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
OCL231-38 |
Lack of features commonly used in OCL |
UML 1.1
|
OCL 2.3.1
|
Resolved |
closed |
|
UML14-1044 |
Wording od OCL definition |
UML 1.1
|
UML 1.2
|
Resolved |
closed |
|
UML14-1042 |
Package symbol as a polygon |
UML 1.1
|
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 |
|