Autosar does not only define the basic software and the templates to exchange system information, it also defines blueprints for data types and software components in the vehicle. It provides software components etc. for body, power train, chassis etc. Although there is a number of pdfs, an Excel sheet and the Autosar XML, it is sometimes quite hard to find your way around the models without a graphical overview.
In the research project IMES, we are building a number of automotive related editors based on the Eclipse Graphiti framework to demonstrate an integrated tool chain and I have been using these to find my way around the application interfaces lately.
The editor is based on the Artop framework, which is available to members of Autosar and provides the basic infrastructure framework to build Autosar tooling upon. The application interfaces are imported by just copying the files that are provided at autosar.org to the workspace
Required ports are per default on the left, provided on the right. But they can be dragged on any side and will always point in the right direction (i.e. provided will alway point outside, even if on the top or bottom border).
Right now it seems that Artop faces a problems with the connectors that are specified in the provided .arxml. As soon as that is clarified, we will have automatically drawn connections, too.