Issue 14840: itemFlow stereotype (updm-rtf)
Source:  (, )
Nature: Uncategorized Issue
Severity: Minor
Summary: According to UPDM specification, itemFlow stereotype should be applied to
OperationalExchanges and ResourceInteractions in the UPDM compliance Level
1. According to SysML, itemFlow conveys flowProperties. SysML specification
has constraint defined for a flowProperty "A FlowProperty is typed by a
ValueType, DataType, Block, or Signal." Unfortunately InformationElement,
Energy and DataElement, according to UPDM specification, do not have L1
compliant SysML stereotypes defined. So the result is always failing
constraint. 

Resolution: 
Revised Text: see pages 24 - 26 of OMG document dtc/2010-12-04
Actions taken:
December 8, 2009: received issue
April 25, 2011: closed issue
Discussion: 
From: "Aurelijus Morkevicius" <aurelijus.morkevicius@nomagic.com>

End of Annotations:=====
ted-NM: yes
From: "Aurelijus Morkevicius" <aurelijus.morkevicius@nomagic.com>
To: <juergen@omg.org>
Cc: "Andrius Strazdauskas" <andriuss@nomagic.com>
Subject: UPDM issue
Date: Tue, 8 Dec 2009 08:46:50 +0200
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcpkOm3hczZQKR/NRruHWoi0jQLEkwTlZv6w


Hello Juergen,


There is a UPDM issue that I think should be registered:


According to UPDM specification, itemFlow stereotype should be applied to
OperationalExchanges and ResourceInteractions in the UPDM compliance Level
1. According to SysML, itemFlow conveys flowProperties. SysML specification
has constraint defined for a flowProperty "A FlowProperty is typed by a
ValueType, DataType, Block, or Signal." Unfortunately InformationElement,
Energy and DataElement, according to UPDM specification, do not have L1
compliant SysML stereotypes defined. So the result is always failing
constraint. 
  
Best Regards,


Aurelijus Morkevicius
System Analyst
No Magic Europe
Savanoriu pr. 363, LT 49425 Kaunas, Lithuania 
E-mail aurelijus.morkevicius@nomagic.com