SDRP — Flexibility to Perform Allocation, Load and Execute Behavior

Flexibility to Perform Allocation, Load and Execute Behavior at
Component as well as Device Level

Problem: For software radio deployment, the ability to perform capacity
allocation/deallocation, object module load/unload, and process/thread
execution/termination should not be restricted to devices. Flexibility
should be provided such that for an application component, it would be
possible for such behavior to be managed by the ApplicationFactory at
the component level, without the constraint of having to use a device.

Proposed Solution: Operations load () and unload (), execute () and
terminate (), and allocate () and deallocate () in addition to all
related types and behavior should be broken out of the Device,
LoadableDevice and ExecutableDevice interfaces, each put into their own
separate interfaces (e.g. LoadableInterface, ExecutableInterface,
AllocableInterface), used (not inherited) from the Device,
LoadableDevice and ExecutableDevice interfaces, and then used optionally
by the ApplicationFactory for deployment of components that have load,
execute or capacity behavior and do not need a device for deployment.

Rationale: Need for flexibility in the SWRADIO UML Profile to
accommodate deployment of an application component with or without a
device.

No Data Available