Book a Demo

Author Topic: SysML Activities composite association source stereotype <<AdjunctProperty>>  (Read 5994 times)

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
From my understanding of the sysml specification the stereotype should be <<adjunct>> rather than <<AdjunctProperty>>. Further on I would expect, when calling “Synchronize Structural Elements” on the owning activity that the created Activity properties are stereotyped by <<AdjunctProperty>> or maybe by <<adjunct>> (specification not absolutely clear to me).
But the properties are without a stereotype.
Best regards,

Peter Heintz

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Hi Peter,

I also think the stereotype should be <<adjunct>>. Also, the association should have the stereotype <<adjunct>>.

An explanation you find:
http://model-based-systems-engineering.com/tag/sysml/
and of course in the SysML 1.4 specification.

As far as I know, EA doesn't support an activity tree. It would be nice, but I think I could do it by other means.

Currently, I don't see the need to constraint a call behavior by an <<adjunct>> composition. Maybe I have missed something.

Kind regards,

Helmut
Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
According to the SysML specification: The stereotype is AdjunctProperty, the keyword to indicate it is applied is «adjunct».

From SysML 1.4 section 8.3.2.1 - AdjunctProperty
Quote
The keyword «adjunct» before a property name indicates the property is stereotyped by AdjunctProperty.

But that probably just shifts your request to be that it's displaying the wrong keyword.