Messages

1

General Board / Re: Not being able to type a FlowProperty with a Signal

« on: August 21, 2025, 05:30:55 pm »

In the properties window of the FlowProperty, under Type.

This worked in older EA Versions. I used it through Version 16. And I am pretty sure it worked in the release version of 17.

I was trying to model the signal flow in an IBD. And while creating the InterfaceBlocks I noticed this bug.
Based on the SysML specification: "A FlowProperty shall be typed by a ValueType, Block, or Signal."
Value Type and Block still works though.

Yeah you're doing everything that should work then I think, sounds like a genuine bug!

2

General Board / Re: Not being able to type a FlowProperty with a Signal

« on: August 20, 2025, 05:26:32 pm »

This is of no help to you but I can confirm it does work in 1625 and there's nothing in the release history to suggest that this functionality has been altered in any way since then.
Sorry I don't have 1710 to hand to help you out further.

Out of interest, how are you trying to apply the signal type to the flowproperty?

3

General Board / Re: Extending SysML Requirement

« on: July 28, 2025, 05:48:45 pm »

Good to hear.
Out of curiosity what was the issue and how will it be addressed?

4

Automation Interface, Add-Ins and Tools / Re: how to change default apperance for MDG stereotypes

« on: July 23, 2025, 05:14:07 pm »

I see a lot of views on this topic, could someone of viewer reply to me with a solution  ?

This is normal for this forum I think - usually means that lots of other people have the same question and nobody has worked out how to solve it. Sadly for you, I am one of them! Hopefully one of the Clever Ones will log in soon and help you.

5

General Board / Re: bulk positioning multiple embedded elements (interfaces) of a component?

« on: July 23, 2025, 05:11:43 pm »

As far as I know this is the expected behaviour in all versions of EA to date. I think everyone would agree it would be desirable to be able to move multiple exposed interfaces at once, but for whatever reason this is how the tool behaves.

6

General Board / Re: Posting UML/SysML Diagrams to this Forum

« on: July 18, 2025, 05:20:35 pm »

There is a *model* behind any diagram.

Clearly we have worked with different colleagues

Primarily, a model would have to be embedded into the post, to make it editable.

I wouldn't suggest making it editable, just a simple way to throw a static diagram on the screen to illustrate a point or a query

There are already alternatives worth considering:
...PlantUML - online tool https://www.plantuml.com/ may be used to quickly build sample diagram, if graphical visualization is desired (but not critical nor EA's specific).

Yes there are tools out there to stick together something using UML/SysML notation - even dia or powerpoint can do that for you! It's just fiddly and time consuming that an image has to be created in another tool, uploaded to an external server and then linked here - if the forum engine could handle drawing and hosting simple images they could be embedded in posts with no need for external hosting.


I'm not expecting anything to happen, just dumping some of my brain contents to make space for something actually useful

7

Uml Process / InformationFlow between Actor and UC

« on: July 15, 2025, 07:34:01 pm »

I seem to remember ages ago seeing Something Somewhere that said it is incorrect to link Actors to UCs with InformationFlows that describe the information flowing in/out of that UC (i.e. the Actor is using a system via that UC and the UC diagram also specifies the data flowing in/out of the system's Behaviours).
However, para 20.2.1.5 "InformationFlow > Constraints" of the UML spec states "The sources and targets of the information flow can only be one of the following kind: Actor... UseCase...", which would seem to imply that it is permitted to attach InformationFlows to the Actor-UC Associations on a UC diagram.

Does anyone have any thoughts on this? Is it permitted/forbidden/unrecommended?

If nothing else I guess that maybe it is 'permitted' but only when it is technically correct to do so (i.e. when the Actor is actually the entity that literally sends that InformationItem into the system or receives from it).

8

General Board / Posting UML/SysML Diagrams to this Forum

« on: July 15, 2025, 07:26:49 pm »

I was inspired by the recent discussions on posting SQL snippets to this forum...

I'm sure this has been discussed before but wouldn't it be powerful to have a super-lite diagram editor built into this forum to allow people to quickly throw an individual diagram together to illustrate a point or query in the forum.
So many topics include lengthy worded descriptions of even simple concepts like Class inheritance structures and inevitably end up relying on ASCII character representations of diagrams. I'm taking a leap and imagining something like a super-lite version of WebEA or EALite embedded into the forum toolset.

Anyway, I'll go back to sleep and keep dreaming...

9

General Board / Re: Extending SysML Requirement

« on: June 12, 2025, 05:18:08 pm »

You may have to explicitly specify a Derive Relationship between your new Stereotype and the thing you want to Derive it from in your Profile/MDG

10

General Board / Re: Apply custom stereotype to Class and Connector with different Tagged Values

« on: June 09, 2025, 05:20:07 pm »

Even if it would work, it's sometimes kind of annoying.
ArchiMate does that for a few stereotypes (ArchiMate_Path, and ArchiMate_CommunicationNetwork). They are applied on both Class and Connector
...
I had to completely redefine ArchiMate_Path in our MDG so it would only apply to a Class

Interesting... have to admit I've barely scratched the surface of ArchiMate, is this a case where EA treats the ArchiMate profile differently to others like the SysML profile? Or just something fundamentally different about the 2 altogether?

11

General Board / Re: Apply custom stereotype to Class and Connector with different Tagged Values

« on: June 06, 2025, 05:20:49 pm »

Might be messy (and I'm sure you thought of this) but you could always include the TV on your Connectors too but set it to something like 'N/A'. At least means you can use the stereotypes in the way you want to.

12

Uml Process / Re: SysML Action (accept event)

« on: May 27, 2025, 05:24:24 pm »

If it's just AcceptEventAction that you are looking at, then I don't think you need multiple instances of it anyway.
According to UML 2.5.1 section 16.10.3.1, I see no reason (but happy to be proved wrong!) why the AcceptEventAction cannot be triggered multiple times, and at ANY point during the execution of other Actions within the Activity.
If there are different reasons for triggering it (or if it can be triggered by different incoming signals) then you might need a Decision immediately after the AcceptEventAction to test why it was triggered, what was received and decide what to do about it. But it would seem messy/cluttered to me to have multiple AcceptEventActions within the same Activity which are all receiving basically the same incoming trigger/signal.

As always, I know I don't have the full context and I'm happy to be proved wrong about semantics too - it's how I learn!

13

General Board / Re: Applying custom stereotypes

« on: May 27, 2025, 05:15:57 pm »

Glad you figured it out
(and thanks for sharing the diagnosis/fix!)

14

General Board / Re: Applying custom stereotypes

« on: May 21, 2025, 06:05:49 pm »

Works for me in 1625, sadly don't have a 17.1 installation on this laptop but I'm sure I've had it work before in 17.1.
I created a test stereotype as you described, then when I select a Class Element on a diagram and use the Ellipsis (...) on it's Stereotype property the test stereotype is right there under Perspective='All Perspectives' and Profile='None'.

Are you using custom profiles/MDGs at all? Maybe the stereotype is hidden in a different profile/perspective somehow.

15

General Board / Re: SQL Queries, Connectors, and 'Find in Diagram'

« on: May 21, 2025, 05:54:18 pm »

Such a sad image
In dutch we have a saying feels applicable: "Iemand blij maken met een dooie mus", which translates to "To make someone happy with a dead sparrow"

That's absolutely brilliant! (and slightly monty python ) I'll definitely be using that from now on!