Issue 18842: There needs to be a distinction between Operational View IEs and Systems View Exchange elements (updm-2-0-rtf) Source: MITRE (Dr. Fatma Dandashi, dandashi(at)mitre.org) Nature: Uncategorized Issue Severity: Summary: Information Exchange (IEs) item or element: Currently all IEs are defined as elements of package AllView. This should not be the case. There needs to be a distinction between Operational View IEs and Systems View Exchange elements. Discussed Resolution: Currently in MODEM, only InformationElement flows are allowed in OVs (see below). MODEM will use FlowedElement instead. Will consider changing its current type from abstract to make it a typed generic flow defined in OVs. An abstract ResourceType is defined for SVs. It will have as subtypes: human, non-human etc. as shown below. In addition, subtype InformationElement will be moved from current location to be a NonHumanResourceType defined in SVs. Allow any of the SV ResourceType leaf level elements (e.g. NaturalResourceType) to trace back to OV flows. Resolution: Revised Text: Actions taken: July 31, 2013: received issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 31 Jul 2013 13:50:52 -0400 To: issues@omg.org, updm-2-0-rtf@omg.org From: Juergen Boldt Subject: issue 18842 -- UPDM 2.2 RTF issue X-Virus-Scanned: amavisd-new at omg.org This is issue # 18842 There needs to be a distinction between Operational View IEs and Systems View Exchange elements Information Exchange (IEs) item or element: Currently all IEs are defined as elements of package AllView. This should not be the case. There needs to be a distinction between Operational View IEs and Systems View Exchange elements. Discussed Resolution: Currently in MODEM, only InformationElement flows are allowed in OVs (see below). MODEM will use FlowedElement instead. Will consider changing its current type from abstract to make it a typed generic flow defined in OVs. An abstract ResourceType is defined for SVs. It will have as subtypes: human, non-human etc. as shown below. In addition, subtype InformationElement will be moved from current location to be a NonHumanResourceType defined in SVs. Allow any of the SV ResourceType leaf level elements (e.g. NaturalResourceType) to trace back to OV flows. see attachment also 18842.doc 18842.doc Juergen Boldt Director, Member Services 109 Highland Ave Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org [] From: "Levine, Leonard Frederick (Len Levine @ DISA) CIV DISA EE (US)" To: Juergen Boldt , "issues@omg.org" , "updm-2-0-rtf@omg.org" Subject: RE: issue 18842 -- UPDM 2.2 RTF issue Thread-Topic: issue 18842 -- UPDM 2.2 RTF issue Thread-Index: AQHOjhbkBsN80g4uiEeKByADu+/W0Zl/Gq9w Date: Wed, 31 Jul 2013 18:27:08 +0000 Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [214.21.83.188] X-Virus-Scanned: amavisd-new at omg.org Content-Transfer-Encoding: 7bit IMHO, MODEM questions should be tracked but deferred and in response to UPDM 3.0 RFP. Len -----Original Message----- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Wednesday, July 31, 2013 1:51 PM To: issues@omg.org; updm-2-0-rtf@omg.org Subject: issue 18842 -- UPDM 2.2 RTF issue This is issue # 18842 There needs to be a distinction between Operational View IEs and Systems View Exchange elements Information Exchange (IEs) item or element: Currently all IEs are defined as elements of package AllView. This should not be the case. There needs to be a distinction between Operational View IEs and Systems View Exchange elements. Discussed Resolution: Currently in MODEM, only InformationElement flows are allowed in OVs (see below). MODEM will use FlowedElement instead. Will consider changing its current type from abstract to make it a typed generic flow defined in OVs. An abstract ResourceType is defined for SVs. It will have as subtypes: human, non-human etc. as shown below. In addition, subtype InformationElement will be moved from current location to be a NonHumanResourceType defined in SVs. Allow any of the SV ResourceType leaf level elements (e.g. NaturalResourceType) to trace back to OV flows. see attachment also smime10.p7s smime10.p7s From: "Dandashi, Fatma" To: "Levine, Leonard Frederick (Len Levine @ DISA) CIV DISA EE (US)" , Juergen Boldt , "issues@omg.org" , "updm-2-0-rtf@omg.org" Subject: RE: issue 18842 -- UPDM 2.2 RTF issue Thread-Topic: issue 18842 -- UPDM 2.2 RTF issue Thread-Index: AQHOjhaqeJl6rQKnLUqYPiWVq3iFnZl/XgEA//+96PA= Date: Wed, 31 Jul 2013 18:32:08 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.83.31.51] X-Virus-Scanned: amavisd-new at omg.org X-MIME-Autoconverted: from base64 to 8bit by amethyst.omg.org id r6VIWEqt012546 Content-Transfer-Encoding: 8bit Len, The set of issues (except one perhaps) being emailed today were issues that we discussed in Berlin and have decided to "resolve" by deferring to UPDM 3.0. I just wanted to document them so we do not lose track of the discussion we had. Best Regards, Fatma Dandashi >-----Original Message----- >From: Levine, Leonard Frederick (Len Levine @ DISA) CIV DISA EE (US) >[mailto:leonard.f.levine.civ@mail.mil] >Sent: Wednesday, July 31, 2013 2:27 PM >To: Juergen Boldt; issues@omg.org; updm-2-0-rtf@omg.org >Subject: RE: issue 18842 -- UPDM 2.2 RTF issue > >IMHO, MODEM questions should be tracked but deferred and in response to >UPDM 3.0 RFP. Len > >-----Original Message----- >From: Juergen Boldt [mailto:juergen@omg.org] >Sent: Wednesday, July 31, 2013 1:51 PM >To: issues@omg.org; updm-2-0-rtf@omg.org >Subject: issue 18842 -- UPDM 2.2 RTF issue > >This is issue # 18842 > >There needs to be a distinction between Operational View IEs and >Systems View Exchange elements > >Information Exchange (IEs) item or element: Currently all IEs are >defined as elements of package AllView. This should not be the >case. There needs to be a distinction between Operational View IEs >and Systems View Exchange elements. >Discussed Resolution: Currently in MODEM, only InformationElement >flows are allowed in OVs (see below). MODEM will use FlowedElement >instead. Will consider changing its current type from abstract to >make it a typed generic flow defined in OVs. An abstract ResourceType >is defined for SVs. It will have as subtypes: human, non-human etc. >as shown below. In addition, subtype InformationElement will be >moved from current location to be a NonHumanResourceType defined in >SVs. Allow any of the SV ResourceType leaf level elements (e.g. >NaturalResourceType) to trace back to OV flows. > > >see attachment also