Deployment and Configuration of component-based Distributed Applications Avatar
  1. OMG Specification

Deployment and Configuration of component-based Distributed Applications — Open Issues

  • Acronym: DEPL
  • Issues Count: 9
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Ambiguous mulitplicity of Target::CommunicationPath::connectedNode

  • Key: DEPL4-18
  • Legacy Issue Number: 17032
  • Status: open  
  • Source: Fraunhofer FOKUS ( Max Bureck)
  • Summary:

    The multiplicity of stereotype-property Target::CommunicationPath::connectedNode is [1..*] in the overview picture, in textual description it is [*]. The multiplicity of [1..*] makes more sense, since the source for the derived property is
    self.interconnect.connectedNode, where CommunicationPath::interconnect has multiplicity [1..*] and Interconnect::connectedNode has multiplicity [1..*], so there should be at least one connectedNode.

  • Reported: DEPL 4.0 — Mon, 23 Jan 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Stereotype-property Components::Port::UID ambiguous

  • Key: DEPL4-17
  • Legacy Issue Number: 17031
  • Status: open  
  • Source: Fraunhofer FOKUS ( Max Bureck)
  • Summary:

    The name and description of stereotype-property Components::Port::UID seems odd. Other stereotypes have a UUID property, providing a unique identifier. The description "The primary type of the port." does not seem to fit.

  • Reported: DEPL 4.0 — Mon, 23 Jan 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Type of Components::ExternalReference::location does not exist

  • Key: DEPL4-16
  • Legacy Issue Number: 17030
  • Status: open  
  • Source: Fraunhofer FOKUS ( Max Bureck)
  • Summary:

    The property Components::ExternalReference::location is of type URL. This type is neither defined in the UML meta-model, nor in the DEPL profile. The type should be String and maybe a constraint or regular expression should be defined to restrict the value to a URL.

  • Reported: DEPL 4.0 — Mon, 23 Jan 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Multiplicity of Target::SharedResource::resourceUser ambiguous

  • Key: DEPL4-19
  • Legacy Issue Number: 17033
  • Status: open  
  • Source: Fraunhofer FOKUS ( Max Bureck)
  • Summary:

    The multiplicity of the stereotype-property Target::SharedResource::resourceUser is [0..*] in the overview picture, but [1..*] in the textual description. There seems to be no reason why there should be at least one user for a shared resource.

  • Reported: DEPL 4.0 — Mon, 23 Jan 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 7.6.1.1-7.6.1.2; 9.10

  • Key: DEPL4-12
  • Legacy Issue Number: 9884
  • Status: open  
  • Source: AGH - University of Science and Technology ( Jacek Cala)
  • Summary:

    On page 51 (section 7.6.1) there is inconsistency between TargetManager interface depicted in figure in subsection 7.6.1.1 and operations' description in subsection 7.6.1.2. In the figure there is 'commitResources' operation whereas in the description there is 'createResourceCommitment' operation. Which one is correct? Just to mention that on page 121 (section 9.10) in figure 9.1 - Executor in Action there is invocation of commitResources operation.

  • Reported: DEPL 4.0 — Thu, 6 Jul 2006 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add startLaunch also to DomainApplication/NodeApplication

  • Key: DEPL4-13
  • Legacy Issue Number: 14088
  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    Only the DomainApplicationManager and NodeApplicationManager have a startLaunch, on both classes this leads to a call to a DomainApplication/NodeApplication but this has no name in figure 9.1. We propose to seperate construction with the real functionality. Add startLaunch also to DomainApplication/NodeApplication which means adding it also to the application interface

  • Reported: DEPL 4.0 — Tue, 21 Jul 2009 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Multiplicity of Components::Component::ownedPort ambiguous overview diagram

  • Key: DEPL4-14
  • Legacy Issue Number: 17028
  • Status: open  
  • Source: Fraunhofer FOKUS ( Max Bureck)
  • Summary:

    In the overview diagram the property Components::Component::ownedPort has the multiplicity [1..*] in textual description, however, the multiplicity is [*]. There seems to be no reason why a component should have at least one port.

  • Reported: DEPL 4.0 — Mon, 23 Jan 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Multiplicity of Components::Component::ownedPort ambiguous

  • Key: DEPL4-15
  • Legacy Issue Number: 17029
  • Status: open  
  • Source: Fraunhofer FOKUS ( Max Bureck)
  • Summary:

    The property Components::ComponentImplementation::capacity is of type Sequence(Capacity). The type Capacity is not existent, neither in the UML meta-model nor in the DEPL specification. It is most likely (also judging from the stand-alone PIM meta-model) that the type Capability was meant here. So the property should be exchanged by the property:
    Components::ComponentImplementation::capability(Capability)

  • Reported: DEPL 4.0 — Mon, 23 Jan 2012 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Supports For Many Applications

  • Key: DEPL4-11
  • Legacy Issue Number: 9178
  • Status: open  
  • Source: Anonymous
  • Summary:

    Supports For Many Applications: The current specification is more and more consummate for deploying an application.In the case of actual distributed environments such as embedded system,several applications running at the same time may be more hopeful.Although deploying several applications involves more things to consider,firstly we can add an ApplicationController component.The application controller is the component that coordinates and communicates with each application. Recommendation: The application controller component can be considered an assembly-based component in which each assembly component represents an application.Add an optional ApplicationControllerComponent Elment to the assemblyComponent description which contains an attribute that identifies the component is the application controller component.The corresponding PSM XML should be updated for assemblyComponent description.In implementation,an ApplicationFactory should be added which is reponsible for creating applications.

  • Reported: DEPL 4.0 — Wed, 23 Nov 2005 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT