-
Key: DEPL4-31
-
Legacy Issue Number: 8984
-
Status: closed
-
Source: Zuehlke Engineering ( Frank Pilhofer)
-
Summary:
The resolution for issue 6392 introduced the ability
for a monolithic implementation to delegate some of its
ports to a resource.To this effect, the ImplementationRequirement element
has three attributes, "resourceUsage", "resourcePort"
and "componentPort" to identify how the component
instance uses the resource.In the deployment plan, the InstanceResourceDeployment-
Description element captures which resource was chosen
to satisfy the requirement. It has a "resorceUsage",
but neither "resourcePort" and "componentPort"
attributes.This information is necessary in the deployment plan.
Proposed resolution:
Add "resourcePort" and "componentPort" attributes to
the InstanceResourceDeploymentDescription element, to
carry the information from the original implementation
requirement.In section 6.8.12.2, add two attributes:
resourcePort [0..1]: The resource port used by the
component instance. Copied from the original
ImplementationRequirement.componentPort [0..1]: The component port delegated
to or used by the resource. Copied from the
original ImplementationRequirement. -
Reported: DEPL 1.0 — Wed, 31 Aug 2005 04:00 GMT
-
Disposition: Resolved — DEPL 4.0
-
Disposition Summary:
No Data Available
-
Updated: Wed, 11 Mar 2015 01:53 GMT
DEPL4 — Information about Port Delegations Lost In Planning
- Key: DEPL4-31
- OMG Task Force: Deployment RTF