Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: FlunkStort on May 18, 2022, 12:04:33 am

Title: Extending SysML with Profile
Post by: FlunkStort on May 18, 2022, 12:04:33 am
I managed to create my own profile, export/import it, and can see/use the results within my new toolbox.

All I did so far was create a stereotype of <<block>> that I named <<function>>. (So I have a diagram with a metaclass object named Class, a stereotype object named "SysML1.4::block", and a stereotype object named "function". There is an extends relationship from function to Class, and a generalization connector from function to the SysML1.4::block object.)

My questions are:

Title: Re: Extending SysML with Profile
Post by: qwerty on May 18, 2022, 07:24:46 am
I'm offline at the moment, but right from my head I seem to remember the answers. There's a _metatype (or was it _metaclass? I always get mixed up with it) which you can assign (IIRC - again - in the stereotype; just consult the help) so you have Function iso. Block. Makes ne aw elemens also with appear with Function<n>.

For the connectors you need to resort to metaconstraints. The old QL matrix should not be touched (and never shoud have been implemented as it was and is). It' a bit of a brain tweezer and needs some time to learn.

q.
Title: Re: Extending SysML with Profile
Post by: kylerbker on May 19, 2022, 11:50:28 pm
Yes, I totally agree with the comment above.
Title: Re: Extending SysML with Profile
Post by: KP on May 20, 2022, 08:04:59 am
By default, the quicklinker filters to only show the elements and connectors in the current toolbox. So you will want to add "UML::Composition" to your custom toolbox.
Title: Re: Extending SysML with Profile
Post by: qwerty on May 20, 2022, 06:08:56 pm
You can turn off that filtering (rather clumsy in the context). Anyway one should do that only for test purpose.

q.