SOPES 1.0 FTF Avatar
  1. OMG Issue

SOPES — Annex A - The syntax of the navigation constraint isn’t OCL

Open Closed All
  • Key: SOPES-25
  • Legacy Issue Number: 15196
  • Status: closed  
  • Source: Institute for Defense Analyses ( Steven Wartik)
  • Summary:

    The syntax of the navigation constraint isn’t OCL. For one thing, it uses the “==” operator. For another, it has an “if” without an “else”. I can understand what’s being achieved (sort of – see below) but I don’t know why this syntax was chosen
  • Reported: SOPES 1.0b1 — Wed, 7 Apr 2010 04:00 GMT
  • Disposition: Resolved — SOPES 1.0
  • Disposition Summary:

    The diagram reflects deprecated approach the definition of the data patterns and needs to be updated. Rework Figure A.8.

    Correction: inv self.Wrapper_1.catCode = “domainValue”; where domainValue is a legal value in the catCode domain.
  • Updated: Fri, 6 Mar 2015 20:58 GMT