DEPL 4.0 MAILINGLIST Avatar
  1. OMG Issue

DEPL4 — New Requirement Satisfier Type

  • Key: DEPL4-3
  • Legacy Issue Number: 7734
  • Status: open  
  • Source: Raytheon ( Jerry Bickle)
  • 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.

  • Reported: DEPL 1.0 — Fri, 10 Sep 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT