Issue 18659: primitive types in SysML Activities (sysml-rtf) Source: No Magic, Inc. (Mr. Nerijus Jankevicius, nerijus(at)nomagic.com) Nature: Uncategorized Issue Severity: Summary: In SysML, value property types are restricted to be a ValueType. I see the problem with incompatible and inconsistent types in customer models, as Activities have no restrictions and still use UML primitive types as pin and parameter types. Did I miss something in the spec, or types used in Activity are not restricted to be ValueTypes? Also, did we fix VerdictKind to be a ValueType? I don't remember. Resolution: Revised Text: Actions taken: April 12, 2013: received issue Discussion: End of Annotations:===== ted-NM: yes From: Nerijus Jankevicius Subject: primitive types in SysML Activities Date: Fri, 12 Apr 2013 14:13:27 +0300 To: "sysml-rtf@omg.org (sysml-rtf@omg.org)" X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r3CBDaMJ002048 X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== In SysML, value property types are restricted to be a ValueType. I see the problem with incompatible and inconsistent types in customer models, as Activities have no restrictions and still use UML primitive types as pin and parameter types. Did I miss something in the spec, or types used in Activity are not restricted to be ValueTypes? Also, did we fix VerdictKind to be a ValueType? I don't remember. Thanks, Nerijus DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=Wf4OxdPg6LMZgbQ9ny6C+1osmY7gVyRiveGv5E1Bawc=; b=TSDyHBFeBH78A4VTUOrus3wE4VOL3lP67wH+B0i5USSuWY4PA6UNb3x6VgtSC6DwIo npOiHAFkikj87pINF8a5DgcONOnWl3lL3u3e6lXXJH9aJ/yBevY9m3+izcODK465tc0A 4kfluYuWsyayhvaxXh7+tZdf5Mp8uu4zj+GbQmo0OoqOzLZ/FPbgZiSCa1ovZpQXwnc1 lSJ8HOsM76Lg+YZ5xHMDwWQHnY4hExz5UWfJHKtTgjAmSS/lNToYOuZyFm6WS9hdzRsp 8vn1CoktDVq40HCEsGfku1ZwsppbHTZhy7ypyZ5Nim8Piy8n2AIH23pcaB1UxVsT4Zjn zIiQ== X-Received: by 10.224.134.199 with SMTP id k7mr11254934qat.51.1365767424383; Fri, 12 Apr 2013 04:50:24 -0700 (PDT) From: "Sanford Friedenthal" To: "'Nerijus Jankevicius'" , Subject: RE: primitive types in SysML Activities Date: Fri, 12 Apr 2013 07:49:58 -0400 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac43btUD9mbNM/UPTFS5s+ghGT5ZmAABI98A X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAQzCY6M= X-Brightmail-Tracker: AAAAAA== Nerijus I don't recall seeing an issue to change verdictKind to verdictType. What is the issue? Is the intent to not restrict the verdict to an enumerated value? Also, your observation regarding activities seems like an issue. What would be the impact on our use of fUML. I assume we would require an extension in both fUML. Regards, Sandy -----Original Message----- From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] Sent: Friday, April 12, 2013 7:13 AM To: sysml-rtf@omg.org (sysml-rtf@omg.org) Subject: primitive types in SysML Activities In SysML, value property types are restricted to be a ValueType. I see the problem with incompatible and inconsistent types in customer models, as Activities have no restrictions and still use UML primitive types as pin and parameter types. Did I miss something in the spec, or types used in Activity are not restricted to be ValueTypes? Also, did we fix VerdictKind to be a ValueType? I don't remember. Thanks, Nerijus X-Trusted-NM: yes Subject: Re: primitive types in SysML Activities From: Nerijus Jankevicius Date: Fri, 12 Apr 2013 14:58:51 +0300 Cc: To: Sanford Friedenthal X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r3CBwuaI006950 X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== Sandy, Back in December both you and Nicolas agreed that it is an issue (see December 13 emails) and resolution could be included into nearest ballots. The problem is that any Activity execution result, including VerdictKind for testcases, can't be used/assigned as SysML block property value, as UML types are not allowed. All these must have ValueType stereotype applied (including VerdictKind enumeration). Nerijus On Apr 12, 2013, at 2:49 PM, Sanford Friedenthal wrote: > Nerijus > I don't recall seeing an issue to change verdictKind to verdictType. What is > the issue? Is the intent to not restrict the verdict to an enumerated value? > > Also, your observation regarding activities seems like an issue. What would > be the impact on our use of fUML. I assume we would require an extension in > both fUML. > > Regards, > Sandy > > -----Original Message----- > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > Sent: Friday, April 12, 2013 7:13 AM > To: sysml-rtf@omg.org (sysml-rtf@omg.org) > Subject: primitive types in SysML Activities > > In SysML, value property types are restricted to be a ValueType. > I see the problem with incompatible and inconsistent types in customer > models, as Activities have no restrictions and still use UML primitive types > as pin and parameter types. > > Did I miss something in the spec, or types used in Activity are not > restricted to be ValueTypes? > > Also, did we fix VerdictKind to be a ValueType? I don't remember. > > Thanks, > > Nerijus > X-Trusted-NM: yes Subject: Re: VerdictKind From: Nerijus Jankevicius Date: Fri, 12 Apr 2013 15:13:31 +0300 Cc: "'Rouquette, Nicolas F \(313K\)'" , , To: Sanford Friedenthal X-Mailer: Apple Mail (2.1085) X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id r3CCDhvB008749 X-Brightmail-Tracker: AAAAAA== X-Brightmail-Tracker: AAAAAA== just for the reference. On Dec 13, 2012, at 11:19 PM, Sanford Friedenthal wrote: > Nerijus > Please propose resolution as indicated below, and this should be > straightforward to put on next ballot. > Sandy > > -----Original Message----- > From: Rouquette, Nicolas F (313K) [mailto:nicolas.f.rouquette@jpl.nasa.gov] > Sent: Thursday, December 13, 2012 4:12 PM > To: Nerijus Jankevicius; sysml-rtf@omg.org (sysml-rtf@omg.org) > Cc: issues@omg.org > Subject: Re: VerdictKind > > Indeed, this is an issue with the SysML 1.3 XMI: > > VerdictKind should have the ValueType stereotype applied. > > > - Nicolas. > > > On 12/12/12 2:10 PM, "Nerijus Jankevicius" wrote: > >> I just realized that Requirements::VerdictKind enumeration in SysML >> profile is NOT a ValueType, so I can't use it in SysML model to type my >> values. >> >> Does everyone agree that it shall have ValueType stereotype applied? >> >> We should make sure all datatypes we provide are ValueTypes. >> >> >> -- >> Nerijus Jankevicius >> SysML Product Manager >> OMG-Certified UML Professional >> No Magic Europe >> Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, >> Kaunas >> Phone: +370-37-324032 Fax: +370-37-320670 >> e-mail: nerijus@magicdraw.com >> WWW: http://www.magicdraw.com >> -- >> MagicDraw - UML made simple! >> > >