UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — the default for a Property should not be inconsistent with its type

  • Key: UML22-206
  • Legacy Issue Number: 9622
  • Status: closed  
  • Source: UK Ltd ( Pete Rivett)
  • Summary:

    There should be a constraint on Property that the ValueSpecification used for its default should not conflict with its type.
    In some cases, for example if an OpaqueExpression is used, then the type of the value cannot be determined. However if it can then it should not be inconsistent.
    This would, for example require the default for a Integer-typed Property to be an instance of LiteralInteger and not LiteralString or any other LiteralX.

  • Reported: UML 2.0 — Tue, 2 May 2006 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:


  • Updated: Fri, 6 Mar 2015 20:58 GMT