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 - Simon M

Pages: [1] 2 3 ... 424
Suggestions and Requests / Re: Archimate connector stereotype labels
« on: July 13, 2018, 03:12:34 pm »
To be clear - I'm after the Archimate relationship stereotype to be displayed, not anything related to UML types or stereotypes.  For example to have a connector display (optionally, controlled by the existing property) a text label "<<ArchiMate_Access>>", or even better "<<Access>>" to match the toolbox text.

I take your point that Archimate is a new language, although I can't see anything that precludes relationships from being labelled with stereotypes (the Archimate stereotypes). In fact the language explicitly includes the ability to specialize the base (Archimate) element and relationship types and explicitly specifies the use of the UML style guillemet notation for this.
Exactly, those correspond to a UML stereotype on the base UML element representing the connector. It's not something that you would actually want to display on an ArchiMate diagram. If you were using the same notation to describe a specialized form of Access connector, it would make sense to display that like a stereotype.

I don't see how this would impact any users of Archimate negatively - assuming it would be controlled by the existing 'show stereotype labels' diagram property.  With that property turned off the behaviour would be the same as it currently is. However I also take your point that it is unlikely that this will be changed if I raise a feature request (ie I shouldn't waste my time doing that).
Because by default all existing diagrams are set to show stereotypes. That means your change would show those labels on every ArchiMate diagram. Existing users would say that we've broken their diagrams. New users would throw away EA before ever finding the option.

But feel free to submit a request. I'm just one person.

General Board / Re: Need Help TLS1.2
« on: July 13, 2018, 09:49:21 am »
Not yet.

Microsoft has only recently updated the OLE driver for SQL Server databases with support for this, and it's incompatible with the previous driver.

Both EA and the Cloud Server are being updated to allow the new driver. Question though, are you really connecting to your SQL Server database over an insecure network that requires TLS to be used?

Suggestions and Requests / Re: Archimate connector stereotype labels
« on: July 13, 2018, 09:45:07 am »
The ArchiMate technology defines a new language. Yes, it uses stereotypes to define that language, but displaying them would be non-conformant for the target language.

I'm not sure I understand why you want them displayed, but I wouldn't expect any change. Displaying UML stereotypes on ArchiMate connectors based on that option would negatively impact the majority of ArchiMate users.

General Board / Re: Visio import: Element text invisible
« on: July 12, 2018, 09:58:18 am »
We have his YABB here since 2003 (with one update ever since). There are a couple of options YABB seems to  hide.
We stopped using YABB quite some time ago. The forum is SMF (Simple Machine Forum)

If it was previously working, check if you have a perspective that doesn't include your technology.

If your types were never available, add the _metatype property to your stereotypes so that that Matrix view will identify them as distinct types.

General Board / Re: Extend SysML stereotype with a profile
« on: July 06, 2018, 09:32:10 am »
Do you have the SysML technology enabled? You can't extend a technology that isn't available.

What build of EA are you using?

Build 1422 validation reports validation errors in the same situations as strict connector syntax prevents.

The scenario I've seen reported before is that it is showing the https authentication dialog, which is separate from the EA security. Is that your issue?

I think Simon is talking about the strict connector syntax option here.
The same rules that drive Strict Connector Syntax are checked during model validation. So it's both.

Having said that, I know that the rules defined for ArchiMate haven't been refined as much as I would like them to be.

The first one will (silently) add EAUML (the default profile). So I would guess. Any stereotype is only part of a profile.
Not quite true.

If you don't specify a fully qualified name, EA will apply a matching stereotype from any profile. Only if no matching stereotype exists will it create a new stereotype entry.

As a result, you get an insidious bug in your code. It works fine until some other profile including a stereotype with that name loads before yours.

Please... Always fully qualify your stereotypes.

I'm particulary confused with: element.Stereotype, element.StereotypeEx, element.FQStereotype, element.MetaType, element.SynchTaggedValues.
  • Use StereotypeEx for every time you want to write a stereotype.
  • Use HasStereotype() for every time you want to check a stereotype.
  • Edge cases for appending a stereotype to the existing list or checking for any stereotype both use StereotypeEx.
  • FQStereotype is read only. It allows you to see the profile the first stereotype applied comes from.
  • MetaType allows you to get the Metatype defined for an applied stereotype. (It's not read only, but it ignores any assignment)
  • SynchTaggedValues() should be automatic when assigning a stereotype. It's useful if the stereotype definition has been updated or tags accidentally deleted

Define Metamodel Constraints

The relationships you see in the ArchiMate technology are (mostly) the ones that are defined in the metamodel diagrams in the specification. Using this method allows you to define both quicklinkers and model validation using exactly the same information.

General Board / Re: Lock Root Node
« on: June 27, 2018, 12:39:09 pm »
but can you elaborate on the meaning of Security Level.
Okay, okay...

I think the word level is just a hangover from an earlier stage of implementation which used levels.

My understanding is that there are 19 filtered views of the model and one complete view. Each element will be in either 1 filtered view or all of them.

General Board / Re: Lock Root Node
« on: June 27, 2018, 11:22:56 am »

It's not that we have decided that you don't deserve access to any particular solutions.

We have assigned a dollar value. It's up to you to determine how important that solution is to you.

You have the option of charging your clients a value that would allow you to provide that function or to use separate repositories for each client. (Perhaps with controlled packages to provide shared information between them)

Bugs and Issues / Re: Project Menu lost
« on: June 21, 2018, 09:18:42 am »
Can't remember where the Customize option is in 12.1, but if you reset the menu in that dialog it *should* fix it if I've understood your problem properly. Customize would also be the only way I can think of to remove a top-level menu.

Pages: [1] 2 3 ... 424