I don't think that this are the right diagrams for my problem.
Its just a view about the system architecture, without any functions oder parameters, just : what modules has the system and which are modules outside the system. Not in detail.
if you evaluate a UML tool for building architectural-like diagram for the automotive domain, I do not understand why you want to not use ports for connecting entities. Ports are part of the AUTOSAR standard as the mean for conecting AR SWC.
Anyway, if you do not want to use ports for connecting components, you can also draw a connector between two parts of a composite directly without going through ports.
About whoch diagram is better suitabe for your case, I do think composite diagram is the right one. It is the most used kind of diagram in any ADL dedicated to Automitive domain.
Finally, if you are working in the domain automotive domain, may be you should have a look on the work done within the EAST-ADL project in defining the EAST-ADL language which is an ADL for Automotuve domain.
If you are interesting in that EAST-ADL language, we have implemented its profile within Papyrus. You may have information on EAST-ADL and may also download this profile following this link: http://www.papyrusuml.org/scripts/home/publigen/content/temp lates/show.asp?P=146&L=EN&ITEMID=14
my firm does not work with autosar. We build our programs in c. They just want a view about the main architecture. Not in Detail. So there are real no ports and so it's snarly when there are in the model ports.
I just have a internship here. So I don't know about the technical backgrounds....
How do i put it into my Eclipse MDT Papyrus ?
Or is it just for the old Papyrus?