UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — GeneralizationSet description conf. about meaning of "specific" + "general

  • Key: UML22-1231
  • Legacy Issue Number: 7071
  • Status: closed  
  • Source: PostFinance ( Karl Guggisberg)
  • Summary:

    GeneralizationSet - description is confused about the meaning of "specific" and "general"

    In the description on page 121, classifieres are called "specific" when they should be called "generic", and vice versa.

    Here is the respecitive paragraph with some editorial notes:

    . i(aaaaa) means insert aaaaa at the position of i . r-------aaaaa means replace everything above ----- with aaaaa

    Each Generalization is a binary relationship that relates a specific Classifier to a more general Classifier (i.e., a subclass). Each i(i.e. a subclass) r------superclass GeneralizationSet defines a particular set of Generalization relationships that describe the way in which a specific Classifier r-----generic (or superclass) may be partitioned. For example, a GeneralizationSet could define a partitioning of the class Person into two subclasses: Male Person and Female Person. Here, the GeneralizationSet would associate two instances of Generalization. Both instances would have Person as the specific classifier, however one Generalization would involve Male Person as the r-----generic general Classifier and the other would involve Female Person as the general classifier. In other words, the class Person can r----specific here be said to be partitioned into two subclasses: Male Person and Female Person. Person could also be partitioned into North American Person, Asian Person, European Person, or something else. This partitioning would define a different GeneralizationSet that would associate with three other Generalization relationships. All three would have Person as the specific Classifier; only the general classifiers would differ: i.e., North AmericanPerson, Asian Person, and European Person. r-----generic r-----specific

  • Reported: UML 2.0 — Thu, 4 Mar 2004 05:00 GMT
  • Disposition: Resolved — UML 2.1
  • Disposition Summary:

    Was resolved as part of Issue No. 5980 (item 4).

  • Updated: Fri, 6 Mar 2015 22:54 GMT