Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Eve

Pages: [1] 2 3 ... 481
I'm afraid I'm not sure how the multiplicity is handled on the expansion nodes. The examples I've seen it's not specified. I think that would mean that each occurrence of the region will take one object from the node.

Yes, it's not a construct I've seen used frequently. I did check though and it is one of the UML constructs that are directly imported to SysML. I misread it, the list it appears in is the UML types excluded from SysML not included. I still think it's the clearest way to express what is going on.

The ExpansionNode, drawn as 3 joined boxes, is available in the context menu for your Region. It's also available on our UML (but not SysML) Activity toolbox.

As for how to display the type on those nodes, that requires going into my first disagreement with that diagram... It doesn't make any sense to describe a type as an array in an Activity diagram. You will have the type of all relevant object nodes set as the type of the array, then set a multiplicity on the node. So in that diagram all Pins and Expansion nodes should be showing the same type, whatever is stored in the array.

My second disagreement with that diagram is that it needs Pins on the inner actions. Being inside an expansion region doesn't have that.

If you want to look into the LoopNode, it's available when you drop a 'Structured Activity' from the toolbox. My tip is that it's even more complex, and will probably obscure that you are processing multiple items in a collection.

General Board / Re: Conditional Looping in SysML Activity Diagrams
« on: July 09, 2020, 03:31:34 pm »
What you are looking for is an ExpansionRegion.

An ExpansionRegion is a StructuredActivityNode that executes its content multiple times corresponding to elements of
input collection(s).

Effectively, you create the region with any inputs and outputs involved and the contents of that region will be performed for each set of inputs.

General Board / Re: Changing [default] directions in associations
« on: July 09, 2020, 08:41:28 am »
Unfortunately the ribbon search only detects items directly within the ribbon.

The user preferences, which is where this option is found can be accessed from:

Start > Desktop > Preferences

Once there, the option is at:

Links > Association default = source -> target

General Board / Re: How to change the language
« on: July 08, 2020, 10:14:13 am »
No, only one language is included in the install.

Search the help for executable state machines. This allows multiple instances of state machines.

Do either of the stereotypes have the _strictness property? That will mean that the two stereotypes can't both be applied and therefore you only get the option to remove one and add the new one.

No. As suggested by the name, it only hides UML link types.

Assuming you're wanting to specialize block for reasons other than the link rules, you can override the relationships that it does expose or rely on the toolbox filters to hide SysML elements.

- Why is EA-Matic complaining (not seeing the scripts) if I start using typed variables instead of just object?
For example: dim element as EA.Element
This would be helpful to use the suggestions in the editor.
As I understand it, because that's not actually part of the language and EA-Matic is passing the scripts directly through to the windows interpreter.

Learn something new every day!
Or the same thing once every couple of years.  ;)

The colours set by a shape script are only overridable if you call drawnativeshape.

You probably didn't see this one. It was before auto colored legends were introduced though, they would be somewhere near the top.
This is to my knowledge, the complete list of overrides for the drawing style of elements.

  • Print in Color - User option for black and white only during printing.
  • Whiteboard mode - Suppresses fill colours and gradients. Set for a diagram
  • Shape Script Rendering - Any drawing properties explicitly set in a shape script before explicit draw commands.
  • Local Appearance - The user configured appearance of the object on this particular diagram. Set on the toolbar.
  • Shape Script Defaults - Any drawing properties explicitly set in a shape script before drawing the native shape.
  • Default Appearance - The user configured default appearance for this object on any diagram.
  • Stereotype Appearance - The appearance for any objects created with this stereotype as configured by the profile order.
  • Element Group Colours - (Optional) Fill colours for different element types configured by Sparx. Enabled in local diagram theme or user settings
  • Local Diagram Theme - Theme override set by a user for an individual diagram.
  • User Style Settings - Defaults set for appearance of all elements for a user. Can be set via a theme.
  • Global Defaults - Defaults for the user settings defined by Sparx.

Thank you.

It will work if you add
+    EAUML::Trace(UML::Abstraction) = Trace

ie. Specify what is actually created rather than the historical anomaly. I'll make sure we update to support both versions.

General Board / Re: EA REST API
« on: July 03, 2020, 08:59:35 am »
There is no REST API on the EA Client, on the pro-cloud server (PCS)
I'm pretty sure you know this, but just to be clear. The OSLC interface provided by PCS is a REST api.

If you want to set a fixed appearance that cannot be changed by the user, you can use the shapescript.
The color set by shape scripts before calling DrawDefaultShape can still be overridden with a local diagram color.

Colors set before explicit draw commands can't be overridden.

What you are wanting to do is the same thing as SysML does with Unit and QuantityKind.

It's not quite as easy (for you or your users) as a simple stereotype, but it can be done.

You need:
  • A model wizard pattern for the actual classes that you want included in the user model.
  • A pattern for an instance of one of those classes
  • Add <technologyname>::<patternname>(UMLPatternSilent) to your toolbox. (You can also use UMLPattern so the dialog shows)
  • Users will need to import the model pattern and then they should be able to use the toolbox item.

At the moment the only way to get that behavior is to inherit it from SysML.

Pages: [1] 2 3 ... 481