Issue 13346: SoaML: The distinction between participant and ParticipantArchitecture Participants is unclear (soaml-ftf)
Click here
for this issue's archive.
Source: International
Business Machines (Mr. Jim Amsden, [email protected])
Nature:
Uncategorized Issue
Severity:
Summary:
In UML2, a <<specification>> Component (or EncapsulatedClassifier) is a specification of the overall structure and behavior that realizing Components are required to implement. This is similar to the distinction between Interface and realizing Classes in UML and Java, but allows the specification to also define ports, parts and behaviors as well as operations.
<<ParticipantArchitecture>> in SoaML appears to support the same separation of specification from realizing participants. SoaML should clarify the similarities or differences between these two concepts.
Resolution:
ParticipantArchitecture
has been removed as a stereotype. Services Architecture as a diagram
type will be used for the architectural view of a participant.
The services architecture diagram type is restricted to showing the parts of a structured classifier (E.G. collaboration, class or component) that are participants or uses of service contracts.
<<specification>> may be used on a participant to indicate that it is restricted to specifying the external contract of that participant without any internal structure. Therefore a services architecture diagram would not be used for a <<specification>> participant.
Example services architecture diagram of a participant:
:
Revised
Text:
FIRST PRESBYTERIAN CHURCH A SYNOPSIS OF ISSUES
IN THIS ISSUE KEY STORY 1 JOURNALISTS SENTENCED
ISSUE 4 DEAR PATIENT WELCOME TO
Tags: issue, participantarchitecture, between, soaml, distinction, participant, 13346