Author Topic: How to represent an AUTOSAR construct in UML  (Read 94 times)

mse

  • EA User
  • **
  • Posts: 168
  • Karma: +1/-0
    • View Profile
How to represent an AUTOSAR construct in UML
« on: August 05, 2020, 09:31:17 pm »
Take a look at the following document, page 119 of 566, figure 4.29.

https://www.autosar.org/fileadmin/user_upload/standards/classic/4-0/AUTOSAR_TPS_SoftwareComponentTemplate.pdf

While it is easy to model a port in UML to represent an RPortPrototype, and this is even mapped in the AUTOSAR UML profile, nothing is said about RPortComSpec and its derivatives. Looking at that meta-model diagram I suppose I could just model it as a class. However, how would one attach such information to the port itself? I suppose I could go with Tagged Values, perhaps some profile, but does anyone see some direct mapping to a UML construct before I go creating a special profile type?

Modesto Vega

  • EA User
  • **
  • Posts: 528
  • Karma: +14/-7
    • View Profile
Re: How to represent an AUTOSAR construct in UML
« Reply #1 on: August 05, 2020, 10:08:39 pm »
I m not an AUTOSAR expert but it looks quick straightforward.

RpPortPrototype is a class, Port PortPrototype is also a class and RPortComSpec is also a class.

None of the elements in that diagram with the word 'Port' in them are ports as described in this help page https://sparxsystems.com/enterprise_architect_user_guide/15.1/model_domains/port.html