Introduce structured configuration parameters
Source: THALES ( Thomas Vergnaud)
It is currently not possible to gather several configuration parameters together.
For example, let us suppose we want to design a message connector that handles channels with different FIFO priorities.
Such a connector would allow the specification of a channel number for each emission port.
It would also allow the specification of a FIFO priority for each channel number in each reception port.
See the following example of what would be needed:
Sets made of several channels and one priority can be specified for each port “receiver”.
Such a connector could be used as follows:
Composite component 'C_appli' contains 5 subcomponents: c1, c2 and c3 send messages to c4 and c5.
Subcomponent c1 sends on channel 1, c2 sends on channel 2, c3 sends on channel 3.
Subcomponents c4 and c5 receive all messages, with different priorities.
Thus, c4 receives data from c1 (channel 1) with priority 2, data from c2 and c3 (channels 2 and 3) with priority 9.
And c5 receives data from c1 (channel 1) with priority 5, data from c2 (channel 2) with priority 2, data from c3 (channels 3) with priority 1.
Reported: UCM 1.2 — Thu, 15 Oct 2020 13:16 GMT
Disposition: Resolved — UCM 1.3
create structured configuration parameters
Add two new concepts in the meta-model: StructuredConfigurationParameter and StructuredConfigurationParameterValue.
Update the XML schema and DTD accordingly.
Updated: Mon, 4 Oct 2021 17:10 GMT