I wonder, if it SysML already provides most features to model the AUTOSAR.
I know, there have been UML-profiles for AUTOSAR, I think EA even put their
.eap in AUTOSAR specs, but then it stopped.
I'm refereing here to this AUTOSAR UML Profile article
I'm currently trying out Topcased and Eclipse/MDT/Papyrus, but both lack a
profile for it.
There were also already other approaches to Automotive engineering/modeling
facts, like EAST-ADL/ADL2, which also had interesting ideas like feature
modeling (think about base projects, which are adapted to (OEM-specific)
customer projects and within a customer project again different
platform-depedent and country coding dependent feature
application/configuration. Some of these projects (like EAST-ADL2) seem to
be stalling, which is just so depressing. :(
Some AUTOSAR to SysML mappings could be e.g.
- Sender/Receiver Interfaces and ports could be already modeled by
flowports, and Client/Server by normal ports. On the other side, some icons
would have to be adapted .
- I guess, the AUTOSAR SWCs types can also be specialized from UML
"Component" or is it better to apply a stereotype to UML-"Component"? There
should also be components in SysML, since it only extends UML?
- ECUconfiguration (as stated in the linked profile article) could be
done by parametric diagrams?
- Considering parametric diagrams, can they be used like, you have your
software (deployed as e.g. an application.mot-file), which is the same over
and handles all platforms/country-codings, but the coding itself is packed
into a separate deployment unit (a separate parameter.mot file, e.g.
flashed in a separate flash area than the application.mot file), which
could bundle 0..* such configs, which the application would search/load at
runtime, depending on some central config parameters pprovided by the car
over CAN? Can this be modeled by SysML and generated out of it?