Source: KnowGravity Inc. ( Markus Schacher)
The relationship between "8.7.1 Arbitration Specifications" and "9.3 UTP Arbitration" is not clear. Probably, 9.3 is only the (informal?) semantics of 8.7.1?
Reported: UTP 2.0b1 — Tue, 16 Jan 2018 12:52 GMT
Disposition: Duplicate or Merged — UTP2 2.0
Natural language description of default arbitration specification suffices for the moment
During the meeting on 19th April, the group agreed to do the following:
- Remove complete clause 9.3 UTP Arbitration from the spec for it represents an informative part of the spec. The classes provided by that library were never meant to be implemented by a vendor; they serve the mere purpose to unambiguously define the semantics of the default arbitration specifications.
- Provide a natrual language decscription of the default arbitration specification as normative part of the stereotype descriptions
Removal of clause 9.3 is the easiest way to solve this issue. Having an executable specification is a nice add-on, especially for tool vendors. But this should be a self-contained clause of mere informative nature. It is therefore heavily recommended and indorsed by the FTF to re-incorporate the precise yet executable semantics of the default arbitration specifications back into the document.
Updated: Wed, 3 Oct 2018 14:16 GMT
UMLTP2 — Arbitration Specification Semantics
- Key: UMLTP2-13
- OMG Task Force: UML Testing Profile 2 FTF