hi I'm Mazen a software engineer at mathw works when authoring software architectures using modelbased design we need the ability to Define interfaces and data types and share their definitions across components in the architecture I will show you how to use the interface dictionary in autosort Block set to create and manage definitions like interfaces and data types use them in the model for simulation code generation and finally R XML export here we have an autosar architecture model which def
ines a throttle position control composition we've not yet defined any interfaces for these ports so let's get started and create an interface dictionary which will contain the definitions for the port interfaces we will use the Standalone interface dictionary editor this is an intuitive editor that can also be used independently from the model context with these tabs we can clearly see the different types of data this dictionary commands let's start by adding a data interface for this bottle po
sition sensor output we can also set the autosar properties for example the interface kind now let's define the elements for my interface in this case we'll have one data element called value we can also Define the design data for example the implementation data type and also the osar information for my element this ensures that the design data and the platform information is always in sync and contained in the same dictionary now let's define the data types required for the inter by the interfa
ce elements now since I have few sensor inputs and outputs that are reading and writing data to the hardware IO I will Define a common data type that will be shared by them this data type will have an implementation type unsigned in 16 and a specific Min and max value you can go back to the interface element and set this data type that we just created and we can clearly see that the data type specification is no longer owned by this element now let's add the software address method which will De
fine a memory section in the autosar platform we can now use this software address method on the data elements we will now create the rest of the interfaces and data types required by the design the interface editor also allows me to link the interfaces and data types to requirements using the traceability Matrix here I'm linking the interfaces to requirements that I've already authored the interface dictionary also allows me to Define platform specific workflows like defining XML options in a c
entralized location that can be used by the dictionary elements and any model linked to the dictionary I can also export the contents of the dictionary to R XML independently from the model context now let's go back to the architecture model and use these interfaces to assign them to Ports we can view and edit the content of the dictionary in the model editor here we're using the property inspector to assign the interface to the selected port or we can right click on the interface Editor to do s
o the bidirectional traceability helps us navigate from Port to interface and vice versa let's now compile the model to make sure we've not made any mistakes with Port interface compatibility and indeed here looks like I've made a mistake with assigning the wrong interface let's fix that and try again now we're ready to create Behavior models for my components we can see that the POR and implementation model are assigned to the expected interface and linked to the same dictionary we can now cont
inue to implement the models apply simulation and finally we can generate code in rxm L for the whole composition the output of this process is a ZIP file that contains both the rxm L and the source code for the components in this video I showed you how to create an interface dictionary from the architecture model use a standalone interface Editor to author interfaces and data types then assign those interfaces to ports in the architecture model and then finally simulate generate code on R XML t
hanks for listening
Comments