-
Key: UAF11-115
-
Status: closed
-
Source: INCOSE ( Mr. Matthew Hause)
-
Summary:
ServiceMessageHandler looks to have been removed because AsynchronousMessage is no longer being used. However, now that OperationalSignal, etc, have been added, we need Receptions to link the Signals to the Performers that can handle them. Looks like something important has been missed.
-
Reported: UAF 1.0 — Sat, 13 Jan 2018 04:49 GMT
-
Disposition: Closed; No Change — UAF 1.1
-
Disposition Summary:
There is no need to add additional stereotypes
There is no need to create stereotypes for signal receptions. UML signal receptions can be successfully used for this purpose as they can be associated with Operational and Resource Signals.
-
Updated: Tue, 8 Oct 2019 17:49 GMT
UAF11 — Problem with ServiceMessageHandler
- Key: UAF11-115
- OMG Task Force: Unified Architecture Framework (UAF) 1.1 RTF