Issue 7738: Locally Managed Capacity Indicator (deployment-rtf)
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity: 
Summary: The capability is lacking to indicate if the capacity model for a capacity
is managed by the node/device or not. The Deployment and Configuration
specification should not constraint System Architecture/Developers from
architecting/implementing the system but be flexible. The OMG SWRadio spec
allows for this flexibility. One Example use case of this is multiple
domains trying to reserve capacity from the same device.


Recommendation
At a locallyManaged boolean attribute to the RequirementSatisfier.
Add a new interface called CapacityManager or CapacityAllocator. This
allows a node/device to realize this type of interface. A node/device would
only have to support this interface if it had capacities that are locally
managed. Recommendation for the interface definition is based upon the
SWRadio DeviceComponent allocateCapacity and deallocateCapacity operations


Resolution: 
Revised Text: 
Actions taken:
September 10, 2004: received issue
Discussion: 
During the RTF meetings and telephone conferences the RTF agreed that this issue needs to be further investigated. Thus, 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 5: Locally Managed Capacity Indicator
The capability is lacking to indicate if the capacity model for a capacity
is managed by the node/device or not. The Deployment and Configuration
specification should not constraint System Architecture/Developers from
architecting/implementing the system but be flexible. The OMG SWRadio spec
allows for this flexibility. One Example use case of this is multiple
domains trying to reserve capacity from the same device.


Recommendation
At a locallyManaged boolean attribute to the RequirementSatisfier.
Add a new interface called CapacityManager or CapacityAllocator. This
allows a node/device to realize this type of interface. A node/device would
only have to support this interface if it had capacities that are locally
managed. Recommendation for the interface definition is based upon the
SWRadio DeviceComponent allocateCapacity and deallocateCapacity operations


Jerry Bickle
Engineering Fellow
Network Centric Systems
1010 Production Rd
Fort Wayne, IN 46808-4711
260-429-6280
260-429-5060 Fax