Issue 15336: Figure 44: Specification (soaml-rtf) Source: SINTEF (Brian Elvesæter, brian.elvesater(at)sintef.no) Nature: Clarification Severity: Significant Summary: See 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). Resolution: Revised Text: Actions taken: July 1, 2010: received issue Discussion: End of Annotations:===== s is issue # 15336 From: Brian Elvesær Figure 44: Specification See issue 15333: Here <> is introduced and <> is used on the implementation (realization). The relationship between <> and <> is not clear to me in the specification. I would argue that a <> 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).