Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: mse on September 19, 2020, 08:07:30 pm

Title: How would model an AUTOSAR NONQUEUED-RECEIVER-COM-SPEC in UML?
Post by: mse on September 19, 2020, 08:07:30 pm

I hope there are some automotive folks out there who can answer this one. Basically I would like to model AUTOSAR communication specifications on ports in UML. I am thinking it might have to go the way of tagged values, but I am open to other suggestions if anyone knows of a more 1:1 mapping. In XML, it looks like this (see figure 4.30 for a picture of the meta-model version of the following AUTOSAR specification https://www.autosar.org/fileadmin/user_upload/standards/classic/4-1/AUTOSAR_TPS_SoftwareComponentTemplate.pdf (https://www.autosar.org/fileadmin/user_upload/standards/classic/4-1/AUTOSAR_TPS_SoftwareComponentTemplate.pdf)):

Code: [Select]

                <R-PORT-PROTOTYPE UUID="9270A340-6B39-43FC-BCBB-88410F58A834">
                  <SHORT-NAME>SpeedPort</SHORT-NAME>
                  <REQUIRED-COM-SPECS>
                    <NONQUEUED-RECEIVER-COM-SPEC>
                      <DATA-ELEMENT-REF DEST="VARIABLE-DATA-PROTOTYPE">/PortInterfaces/Speed_IF/speedValue</DATA-ELEMENT-REF>
                      <TRANSFORMATION-COM-SPEC-PROPSS>
                        <END-TO-END-TRANSFORMATION-COM-SPEC-PROPS>
                          <DISABLE-END-TO-END-CHECK>false</DISABLE-END-TO-END-CHECK>
                          <MAX-DELTA-COUNTER>3</MAX-DELTA-COUNTER>
                          <MAX-ERROR-STATE-INIT>0</MAX-ERROR-STATE-INIT>
                          <MAX-ERROR-STATE-INVALID>0</MAX-ERROR-STATE-INVALID>
                          <MAX-ERROR-STATE-VALID>0</MAX-ERROR-STATE-VALID>
                          <MIN-OK-STATE-INIT>1</MIN-OK-STATE-INIT>
                          <MIN-OK-STATE-INVALID>1</MIN-OK-STATE-INVALID>
                          <MIN-OK-STATE-VALID>1</MIN-OK-STATE-VALID>
                          <WINDOW-SIZE>10</WINDOW-SIZE>
                        </END-TO-END-TRANSFORMATION-COM-SPEC-PROPS>
                      </TRANSFORMATION-COM-SPEC-PROPSS>
                      <ALIVE-TIMEOUT>2</ALIVE-TIMEOUT>
                      <ENABLE-UPDATE>false</ENABLE-UPDATE>
                      <HANDLE-NEVER-RECEIVED>false</HANDLE-NEVER-RECEIVED>
                      <INIT-VALUE>
                        <CONSTANT-REFERENCE>
                          <CONSTANT-REF DEST="CONSTANT-SPECIFICATION">/Constants/SpeedConstant</CONSTANT-REF>
                        </CONSTANT-REFERENCE>
                      </INIT-VALUE>
                    </NONQUEUED-RECEIVER-COM-SPEC>
                  </REQUIRED-COM-SPECS>
                  <REQUIRED-INTERFACE-TREF DEST="SENDER-RECEIVER-INTERFACE">/PortInterfaces/Speed_IF</REQUIRED-INTERFACE-TREF>
                </R-PORT-PROTOTYPE>
               

Title: Re: How would model an AUTOSAR NONQUEUED-RECEIVER-COM-SPEC in UML?
Post by: mse on September 19, 2020, 08:09:47 pm

Here is my mapping so far:

R-PORT-PROTOTYPE is a uml:Port
SHORT-NAME is the name of the uml:Port
REQUIRED-INTERFACE-TREF corresponds to an exposed required interface which references an interface in the model