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 ... 433
1
Uml Process / Re: Signals - "Details" tab not displayed
« on: November 20, 2018, 12:24:12 pm »
The details page exists to provide other options that aren't available for other types. It's only an artifact of history that it provides access to the Attributes and Operations. It's never been the primary way to access those windows.

2
Uml Process / Re: Signals - "Details" tab not displayed
« on: November 20, 2018, 09:33:49 am »
I need access to Attributes and Operations...
Design > Element > Features > Attributes
Design > Element > Features > Operations

Alternately, F9 and F10.

3
What build of EA are you using?

The error is the table name is case sensitive, and has been referred to wrong. I think it's already been corrected.

4
General Board / Re: Transfer from SQL Server not possible
« on: November 19, 2018, 10:22:54 am »
As usual I am preparing an .eap file with an empty model as a destination for a transfer. It has ~1.6kByte.
With that size, it's too small to be a valid JET database/eap file.

One recommendation was not to use EA14, so I stepped back to 13.5. What else?
Who gave you that bad advice? With what reason?

5
Uml Process / Re: Parent and child arrow in Insert Related Elements
« on: November 19, 2018, 10:18:17 am »
Then the question becomes why doesn't your code produce the inheritance relationships. That's a question that can't be answered without a sample declaration of the superclass/subclass. Possibly also the imports/includes/file paths. We don't even know at this stage what language you are using.

6
Bugs and Issues / Re: How use tagged-value in SQL-script for Chart diagram
« on: November 19, 2018, 10:14:15 am »
It's a synonym. A shortcut for "AS o".  "t_object ON t_object.Object_ID"  would be the same. But sometimes you need a table more than once. In that case you'd use e.g. "t_object AS o1" in one place and "t_object AS o2" in the other.

q.
The interesting thing is, at least one of the databases EA connects to will give an error if you use "as" with a table alias. If you're writing cross platform sql, it's better not to include the as here. In contrast aliases on column names are the reverse. You need to include the "as" or at least one database type doesn't handle it.

7
Automation Interface, Add-Ins and Tools / Re: Insert Related Elements - Q
« on: November 16, 2018, 10:19:17 am »
1. Insert Related Elements: (accessible via right click on a class): When I use this to insert all related elements, even at Level 1 depth, in addition to adding the related elements to the diagram, EA is automatically adding relationships between the 'related' elements also which is causing a cesspool of connectors on the resulting diagram. We have around 600 classes which is compounding the issue. Is there a way to make EA show only the related elements on the diagram, using this feature, and not all the relationships between the related elements ? Any add - ins that can achieve this ?
To show only the relationships directly to/from your desired element(s):
Open the relationships window.
Select everything on the diagram
(Possibly optional - Type 'Visible' into the filter bar for the last? column)
Right click on any row, and select hide.
Select the elements that you want to see the relationships for.
(Possibly optional - Type 'Hidden' into the filter bar for the last? column)
Right click on any row, and select show.

My apologies if any of that doesn't use exactly the right term. It's from memory.

8
Bugs and Issues / Re: Unsafe form when searching Help
« on: November 16, 2018, 10:09:26 am »
I don't have much to do with maintaining the website. I don't know how hard it would be to update the old versions of the help, but the 14.0 version of the help no longer references http as the handler for the form.

9
But Im not sure how to secure the common part (Master & reference object) of the repository, mostly for error or mistakes by novice users
A user can be part of more than one group. So if it helps you can add groups for master and reference editors.

The normal lock just leads to situations that people take locks and go on vacation, leaving a dead locked system behind.
Not sure that "lock to edit" solves that.


10
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.


11
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.

12
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)

13
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.

14
System Eng. Edition ordered with EA13 == Unified Edition

15
Simon,

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.

Geert
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">
            <stereotypedrelationships>
              <stereotypedrelationship stereotype="ArchiMate3::ArchiMate_Assignment" constraint="ArchiMate3::ArchiMate_SystemSoftware;ArchiMate3::Event;ArchiMate3::Internal Behavior"/>
            </stereotypedrelationships>

            <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.

Pages: [1] 2 3 ... 433