SoaML 1.1 RTF Avatar
  1. OMG Issue

SOAML11 — Figure 96: Specification

  • Key: SOAML11-40
  • Legacy Issue Number: 15354
  • Status: open  
  • Source: SINTEF ( Brian Elvesæter)
  • Summary:

    Same as issue 15333: Here <<specification>> is introduced and <<Participant>> is used on the implementation (realization). The relationship between <<specification>> and <<Participant>> is not clear to me in the specification. I would argue that a <<Participant>> can be seen as a logical system component that represents a specification, which can be further decomposed into a set of Participants (in the case you want to specify lower-level/participant-level services architectures) or components (design of software components).

  • Reported: SoaML 1.0 — Thu, 1 Jul 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT