-
Key: ALMAS11-6
-
Status: closed
-
Source: BAE SYSTEMS ( Mr. Simon Mettrick)
-
Summary:
The following issues should be discussed in the DDS PSM rationale section to be clear and unambiguous.
- The actual pairing of request and response topics
- The semantics, particularly uniqueness, of request_id values
- UML feature mappings - e.g composition, multiplicities
- Representation of optional attributes
-
Reported: ALMAS 1.0 — Mon, 24 Sep 2018 18:29 GMT
-
Disposition: Resolved — ALMAS 1.1
-
Disposition Summary:
Define uniqueness of request ids and add compositions to mapping description
Request Ids are to be unique across all ALMAS participants.
The general UML mapping for CORBA and DDS PSMs is described in 9.1. It doesn't described composition explicitly, and should do so as per associations
The pairing of requests and responses is no action
The optionality of attributes is a duplicate -
Updated: Wed, 13 May 2020 16:36 GMT
ALMAS11 — DDS PSM Rationale Incomplete
- Key: ALMAS11-6
- OMG Task Force: Alert Management Service (ALMAS) 1.1 RTF