QVT 1.1 RTF Avatar
  1. OMG Issue

QVT11 — Section: 8/2 page 70

Open Closed All
  • Key: QVT11-95
  • Legacy Issue Number: 9428
  • Status: closed  
  • Source: Universidad Politécnica de Madrid ( Jorge Enrique Pérez-Martínez)
  • Summary:

    Association result of the ImperativeOperation class should be (see figure 8.2) result: VarParameter [*]

    {composes, ordered}

    Association body of the ImperativeOperation class should be (see figure 8.2) body: OperationBody [0..1]

    {composes}
  • Reported: QVT 1.0 — Tue, 14 Mar 2006 05:00 GMT
  • Disposition: Resolved — QVT 1.1
  • Disposition Summary:

    In Section 8.2.1.10 (ImperativeOperation), replace
    "result: VarParameter [*]

    {composes}"
    by "result: VarParameter [*] {composes, ordered}"
    and replace "body: OperationBody [0..1] {composes, ordered}"
    by "body: OperationBody [0..1] {composes}

    "

    NOTE (FIXES after AB Review)
    Additional omissions concerning the

    {composes} and {ordered} indications in property definitions where detected (when comparing to diagrams). The following resolutions should also be applied
    - Add the missing {composes}

    indication for the following defined properties (within the class descriptions):
    ImperativeOperation::context , Constructor::/body, ResolveExp::condition, BlockExp::body, WhileExp::condition, WhileExp::body, ImperativeLoopExp::condition, ForExp::/condition, ForExp::body, ForExp::source, ImperativeIterateExp::/condition, ImperativeIterateExp::/body, ImperativeIterateExp::/iterator, ImperativeIterateExp::/source, SwitchExp::elsePart, AltExp::condition, AltExp::body, VariableInitExp::referredVariable, UnpackExp::source

    • Add the missing {ordered}

      indication for the following defined properties (within the class descriptions):
      MappingOperation::inherited, MappingOperation::merged, MappingOperation::disjunct, BlockExp::body,ImperativeIterateExp::iterator, ComputeExp::returnedElement
  • Updated: Fri, 6 Mar 2015 22:55 GMT