Typing attribute and operation parameters

The attributes on receiver or sender interfaces and operation parameters on client or server interfaces must be C types that match the types of AUTOSAR data elements to which they are meant to connect. The exception is for typing attributes with Rational Rhapsody events.

Attributes typed with Rhapsody events

You might type attributes on receiver or sender interfaces by way of Rational Rhapsody events. The event must have either no parameters or exactly one parameter that is typed by a C type that matches the AUTOSAR data element with which to connect. Typing an attribute with an event indicates that the arrival of the incoming or outgoing data is to be interpreted as a Rational Rhapsody event, with the data itself as an optional parameter. Such incoming events might be used to trigger transitions on the statechart for the Rational Rhapsody implementation block (RIMB). Outgoing events might trigger transitions on the statechart of the receiving Rational Rhapsody implementation block in another software component. This in effect provides a “ Rational Rhapsody event communication layer” between AUTOSAR software components on top of the AUTOSAR data layer.

This handling of Rational Rhapsody events is facilitated by the generated receivers, senders, and handlers.


Feedback