UPDM 1.0 NO IDEA Avatar
  1. OMG Issue

UPDM — 7.1.5.2.1 Request

  • Key: UPDM-715
  • Legacy Issue Number: 13765
  • Status: closed  
  • Source: Model Futures Ltd. ( Ian Bailey)
  • Summary:

    7.1.5.2.1 Request: MODAF definition is given as "The mechanism by which a Service communicates." This doesn't exist in MODAF, so no idea where this definition has come from or even what "request" is meant to be. The UPDM definition of "A Request port provides an interaction point for accessing a Resource's capabilities, as defined by the ServiceInterface typing the port. It includes the specification of the work required from another, and the request to perform work by another. The Request is basically a conjugated version of a Service port and as such can use the same ServiceInterface. By adding the Request port to the consumer of the Service, the implementation of a service is kept transparent."…is frankly incomprehensible, which doesn't help.
    Diagram SOV
    Document Issue UPDM (OMG Beta) Jan 2009

    Source Ian BaileyModel Futuresian@modelfutures.com

    Resolution Change the description to match the SOAML description. We should look at changing this to a summary and a reference to the SOAML specification at a later date.

  • Reported: UPDM 1.0b1 — Tue, 17 Mar 2009 04:00 GMT
  • Disposition: Resolved — UPDM 1.0
  • Disposition Summary:

    Change the description to match the SOAML description. We should look at changing this to a summary and a reference to the SOAML specification at a later date.
    Merged with issue OMG 13878

  • Updated: Fri, 6 Mar 2015 20:59 GMT