Issue 7734: New Requirement Satisfier Type (deployment-rtf)
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity: 
Summary: Issue 1: New Requirement Satisfier Type
Unable to express a node/device characteristic as a set where each item is
an instance of the same characteristic class. For example, node/device may
have many runtimes, libraries, communication paths/QoS. One needs to be
able to express a characteristic such as runtime or library as one
characteristic with multiple instances, where each instance contains the
same requirement satisfier definition. For example, for runtime or library
characteristic each instance in the set would contain name and its value
and version and its value, as a set of instances of a characteristic that
contains name and version in this case. This would allow one to state the
set of libraries or runtimes in a consistent manner all belonging to the
runtime or library characteristic.


Right now for the D & C, I would have to define a RequirementSatisfier as
RunTime1 and RunTime2 instead of RunTime. I am able to express a
requirement as RunTime but this will not be matched against RunTime1 and
RunTime2.


Potential Recommendation
Add definition for RequirementSetSatisfier that contains 1 one to many
RequirementSatisfier. The constraint being the RequirementSatisfier
definition has to be the same except for the values.


Appears that an abstract definition is needed for the
RequirementSetSatisfier and RequirementSatisfier since a node or device can
have either or both of them, and they have common attributes (name,
resourceType).


This added capability would also cause changes to the update operation to
support this information.

Resolution: 
Revised Text: 
Actions taken:
September 10, 2004: received issue
Discussion: 
During the RTF meetings and telephone conferences the RTF agreed that a concrete use case is needed in order to specify an appropriate resolution for this issue. Since such use case is not yet available this issue is deferred to the next Deployment RTF
End of Annotations:=====
ubject: Deployment & Configuration Spec 
To: issues@omg.org 
Cc: deployment-rtf@omg.org 
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001 
From: Gerald_L_Bickle@raytheon.com 
Date: Fri, 10 Sep 2004 13:56:29 -0500 
X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.13a  |April 8, 2004) at 
 09/10/2004 01:56:29 PM 
X-SPAM: 0.00 


Issues for Deployment & Configuration Spec


Issue 1: New Requirement Satisfier Type
Unable to express a node/device characteristic as a set where each item is
an instance of the same characteristic class. For example, node/device may
have many runtimes, libraries, communication paths/QoS. One needs to be
able to express a characteristic such as runtime or library as one
characteristic with multiple instances, where each instance contains the
same requirement satisfier definition. For example, for runtime or library
characteristic each instance in the set would contain name and its value
and version and its value, as a set of instances of a characteristic that
contains name and version in this case. This would allow one to state the
set of libraries or runtimes in a consistent manner all belonging to the
runtime or library characteristic.


Right now for the D & C, I would have to define a RequirementSatisfier as
RunTime1 and RunTime2 instead of RunTime. I am able to express a
requirement as RunTime but this will not be matched against RunTime1 and
RunTime2.


Potential Recommendation
Add definition for RequirementSetSatisfier that contains 1 one to many
RequirementSatisfier. The constraint being the RequirementSatisfier
definition has to be the same except for the values.


Appears that an abstract definition is needed for the
RequirementSetSatisfier and RequirementSatisfier since a node or device can
have either or both of them, and they have common attributes (name,
resourceType).


This added capability would also cause changes to the update operation to
support this information.