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 ... 432
Just tested 1420.

The only quicklinks that I get between Device and System Software are the base UML links. (1421 added the capability to suppress these)
Looks like it's not running any validation at all, which would be the big difference.

In my opinion, 1427 would be more useful for modeling ArchiMate. Even if you have to disable the strict connector syntax.

The ArchiMate technology was converted to use a metamodel during the 14.0 beta period. (1414 to be precise)

Are you sure you haven't done something like replace the MDG technology with an older version?

We don't generally publish the source of our MDG technologies, even the ones that are in plain text in the installer.

The relationships in the ArchiMate3 specification where completely reworked. Instead of defining a quicklinker table with one row for every letter in the relationship tables (manually) , we have a metamodel that defines available relationships as defined by the metamodel figures in Chapters 3 through 13. (And the corresponding textual descriptions)

General Board / Re: Attribute descrption in v14
« on: November 13, 2018, 09:58:00 am »
The notes for attributes can be edited in the docked notes window.

System Eng. Edition ordered with EA13 == Unified Edition


I'm not saying you are wrong, I'm not a fan of the Archimate specification either, but in this particular case that can't be an excuse.
Figure 77 of the ArchiMate metamodel clearly shows the relation between device and system software.

You're right. I remember a report about that particular issue and adding it in to our metamodel now. If you don't want to wait for a release, add the text in bold to your ArchiMate3 technology file. (The rest is for context)

          <Stereotype name="ArchiMate_Device" metatype="Device" notes="" bgcolor="12648384" fontcolor="-1" bordercolor="-1" borderwidth="1" hideicon="0" generalizes="Node" baseStereotypes="Node" strictness="profile">
              <stereotypedrelationship stereotype="ArchiMate3::ArchiMate_Assignment" constraint="ArchiMate3::ArchiMate_SystemSoftware;ArchiMate3::Event;ArchiMate3::Internal Behavior"/>

            <Icon type="bitmap" xmlns:dt="urn:schemas-microsoft-com:datatypes" dt:dt="bin.base64">

System software was previously inheriting the stereotyped relationship to Event and Internal Behavior. Because the stereotyped relationship overrides any existing relationships of that type we need to add them too.

General Board / Re: Aggregates connector is shown the wrong way around
« on: November 12, 2018, 03:22:33 pm »
The option you are talking about is:
Start | View | Preferences | Links | Draw Aggregations Reversed.

This option is still used when dragging an aggregation or composition from the toolbox.

That option doesn't have any effect when using the quicklinker because that generally shows 'to whole' or 'to part' in the menu.

Regardless of which option you pick or how you create it, the source end of the aggregation has/will always be the the part unless you explicitly swap it via the UI.

From a UML perspective, associations don't have a source and target. They have two1 equal ends.

The real question, is why is this causing you a problem? Perhaps we can solve that problem.

1 When aggregation is set it's limited to two, with only one specifying aggregation. Otherwise it's two or more.

Matthew, it's a little more complicated than that.

In addition to the metamodel, there is a textual description of how derived relationships work. This is where the "ambiguous" comes in to my comments. However, even taking that into account there are some connectors allowed by the table that I can't see how they fit into the metamodel. EA currently doesn't have those derived relationships added. Most issues reported come down to that.

There's also a comment somewhere about something not happening between layers. Going from memory here, so I don't have the specifics. But the effect of that comment is excluding relationships in the table that the metamodel would otherwise allow.

EA 14.1 uses a metamodel approach to build quicklinkers for UML, UAF, ArchiMate and user technologies if they choose. It works well when the metamodel is well defined. Unfortunately, it doesn't necessarily meet user expectations when the specification writers have ignored the metamodel and defined a table showing what the available relationships are.

General Board / Re: Shape script control by external switch
« on: November 12, 2018, 11:31:59 am »
If you're wanting to change that notation for all elements on the diagram, I would be creating customized diagram types, then checking diagram.mdgtype within your shape scripts. This means the modeler has the choice of whether the extra notation is shown or not.

From what I can see, the dictionaries are located in the registered users section. When you purchase EA you will receive a username and password that will allow access to that section for a year.

General Board / Re: Unapply profile in XMI export
« on: November 12, 2018, 09:34:13 am »
I'd look at running an XSLT transform on the exported XMI. There's built-in support to do that, to the extent that you can use it as a new export format.

Archimate 3 MDG seems to be broken in build 1427.

In my opinion, it's the ArchiMate 3 specification that's broken. It's self-contradictory and ambiguous.

EA has implemented the relationships as defined the the metamodel described by the specification. We are aware that it's different than the appendix, which attempts to provide an interpreted view of that metamodel.

PCS General Board / Re: André
« on: November 12, 2018, 09:24:00 am »
I'm not aware of any existing translations of WebEA (or Prolaborate) into Portugese.

However, my understanding is that the English strings used for display in the UI are all declared in a single PHP file to allow for translation. (Sorry, I don't know exactly where that is)

Profile Metatype (bad) Component, (good) ArchiMate3::ArchiMate_ApplicationComponent.

This sounds like when you exported, the definition was type, now it's profile metatype. Changing it back to Type may get you going.

Bugs and Issues / Re: Can't order Responsibilities
« on: November 05, 2018, 11:20:16 am »
Element Responsibilities (aka - Internal Requirements) can't be ordered.  The ONLY order available is alphabetic.

Please rectify.

Every collection in EA should be able to be ordered.
While I appreciate what you are saying that "every" collection could have an order applied, there are other factors at play here.

UML itself has several "unordered" collections. My interpretation of this is that there is no meaning in the order, and it can be validly be presented in any order.

For an EA specific issue, there's nowhere for EA to store a user specified order on these. That alone means you're probably better off adapting.

Pages: [1] 2 3 ... 432