Activity for Tim Weilkiens
-
Tim Weilkiens posted a comment on ticket #12
Good point. Thanks for the information. I will fix it and publish a new version soon.
-
Hi, I only tested it a bit with the demo version. Unfortunately, I don't have a full license of the newest Cameo version yet. But I heard from others that it should work. Actually, the stereotypes should not be a problem, but probably, the toolbar customizations does not work as they should. Kind regards, Tim Christian Richter jonathanarcher@users.sourceforge.net schrieb am Mi., 23. März 2022, 17:31: Hi, I wonder if the SYSMOD plugin is compatible with the newer versions of Cameo Systems Modeler...
-
Hi, Unfortunately, the FAS plugin is not compatible with Cameo 2021x. We work on a solution. However, this is an open source, non-commercial project and we have limited resources. It may take a while. Any help is appreciated. We will release a new version as soon as we have fixed it. Kind regards, Tim
-
The "Region of Interest" pin is intentionally not connected. Actually, according to SysML, it should show an incoming arrow in the rectangle, so that you can see that it is an InputPin. However, it is not shown in Cameo. The value is not a parameter of the activity, but should be read from a system configuration. This kind of modeling occurs very often. You are right that it is not very clear if you just use an unconnected pin. As a pragmatic modeling pattern, I modeled OpaqueActions that read the...
-
Found it :-) Thanks! In the past, the extendedStakeholder was based on Actor, but is now based on Class. The Stakeholder element in the template dates back to when it was based on Actor. Oddly enough, changing the stereotype from Actor to Class was possible in the background. I've fixed the template. If you would like to do it manually: remove the stereotypes, use refactor to change the element from actor to class, and apply the stereotypes user and extendedStakeholder. Cheers, Tim
-
Hi, The extendedStakeholder stereotype is an extension of a Class not an Actor. It specializes the SysML stereotype Stakeholder which extends Classifier. Where did you find the application to an actor? Cheers, Tim
-
Fixed as proposed.
-
VariantConfiguration::selectedVariants multiplicity is undefined
-
REQUIRES on wrong toolbar group
-
Could move the REQUIRES to the XOR group. However, it seems that both - REQUIRES and XOR - don't work as model elements in the toolbar. You must apply them as stereotypes to a constraint for example in the specification dialog. I have removed XOR and REQUIRES from the toolbar. Please let me know if you know how to use stereotyped constraints in a toolbar and I will change it.
-
Validation rule ValidVariantConfigurationMaxVariants has not error message
-
Fixed as proposed.
-
Validation rule ValidVariantConfigurationMaxVariants has not error message
-
REQUIRES on wrong toolbar group
-
VariantConfiguration::selectedVariants multiplicity is undefined
-
Customized Toolbars do not Work
-
Defined concrete metaclasses or special stereotypes for the toolbar like txtExtendedRequirement et. al
-
Customized Toolbars do not Work
-
The problem is that the stereotype extends an abstract metatype. To create a model element the tool needs the information about a concrete metatype. I am in contact with NoMagic to get the information how to define a default concrete metatype. For example Block respectively Class for UserSystem or Requirement respectively Class for the ExtendedRequirement taxonomy.
-
Customized Toolbars do not Work
-
SYSMOD Diagram Toolbox
-
SYSMOD Diagram Toolbox
-
Minor updates for next edition of the SYSMOD book
-
Update from NoMagic plugin to new plugin version
-
Need a build system
-
Provide project template
-
SYSMOD Diagram Toolbox
-
Thanks for your contribution. Customized toolbars, smart manipulators, or special...
-
MD does not provide the most recent version of the plugin. The current version is...
-
Provide project template
-
Update from NoMagic plugin to new plugin version
-
Minor updates for next edition of the SYSMOD book
-
Strange that the tool allows packages with same name. I thought it is a strict built-in...
1
