Messages

1

Bugs and Issues / Re: SysML actions on an activity diagram to not add pins to an action on the diagram

« on: October 27, 2025, 09:40:30 pm »

Just tried it in build 17.1.1710 and it works like a charm. Which build are you using?

2

Bugs and Issues / Re: An issue with the CSV import

« on: October 27, 2025, 09:34:03 pm »

The import only adds or changes elements by design.

When you want to delete elements based on an import file, you should use scripting to figure out which elements are obsolete and can be removed or modify the status, which is better for requirements management.

3

Automation Interface, Add-Ins and Tools / Re: Integration Requirements Tools - EA

« on: August 23, 2023, 04:54:36 pm »

Hi Michele,

The beauty of EA is that it's open and therefor easy to make an own interface. We have to work with a specific dutch tool for requirements management (Relatics) and we build our own import/export interface. The importer makes sure it only imports the changed requirements.

Cheers,
Rob

4

General Board / Re: Diagram images rather small when published in Word doc

« on: August 23, 2023, 04:42:22 pm »

In your diagram properties, make sure the Hide Page Border is not set. Than you are able to see the page boundaries. Adjust your diagram so that it fits the page.

5

General Board / Re: Difference between Properties and Attributes and Values in EA SysML

« on: December 02, 2020, 08:03:25 pm »

In this example Light is not a data type as it represent a flow. It states that the light flows into the camera, so light is modeled as an item and therefor should be a block.

6

General Board / Re: Difference between Properties and Attributes and Values in EA SysML

« on: December 01, 2020, 06:28:09 pm »

1. the above answer is the most practical. There are reasons not to use parts for everything: for example when you want to generate code for a software block. For the code generation, only attributes can be used (as they are basically UML structures).

2. A value type is a data type, see the definition in the standard: "A ValueType defines types of values that may be used to express information about a system, but cannot be identified as the target of any reference. Since a value cannot be identified except by means of the value itself, each such value within a model is independent of any other, unless other forms of constraints are imposed."
Simply put, a value type cannot be instantiated whereas a block should have an instance to be useful.

7

General Board / Re: Proxy ports versus full ports in SysML, there has to be a better explanation

« on: November 30, 2020, 11:29:14 pm »

All standards are based on consensus of several stakeholders. You do not have to use the complete standard in your project. Best thing to do when you start a project, is to document which modelling language constructs you should use and which constructs are not used by the project.

As Weilkiens states in his mbse blog, he recommends only to use proxy ports. I agree to this as we also only use proxy ports in our projects. But if you have a project where you buy a component as a connector between other components and you are not interested in the internal behavior of the COTS component, you can model it as a full port. This is the trade-off you have to make!

8

General Board / Re: Display a number in a circle next to elements on a diagram ?

« on: September 17, 2020, 04:34:07 pm »

How to Bookmark Diagram Elements in Enterprise Architect 15:
https://www.youtube.com/watch?v=kv-pI_vBd_I

9

Suggestions and Requests / Re: Executable SysML FlashLight

« on: May 22, 2020, 06:39:03 pm »

Check https://sparxsystems.com/enterprise_architect_user_guide/15.0/model_simulation/executable_statemachines_main.html

10

General Board / Re: Default to not show connectors in other diagra

« on: May 25, 2018, 04:42:38 pm »

I agree with what Helmut writes. To say it in other words: there is a difference between a model (containing concepts) and the representation of the model (references to concepts).  A diagram is a representation.

For example I have three concepts: role A, role B and role C (guess you use ArchiMate). All those three roles have relations with each other (let's say flows).

Now I create a diagram in which I want to focus on role A. So I have roles A, B and C, and only the relations in which A is a party.

And now the awkward thing occurs: whenever I add a relation between B and C, it's added to my diagram that has A as focus.

Grrrrrr.....

A modelling tool should offer good support to this. (Visio is not a modelling tool, but a drawing tool.)

The tool offers support for this, via automation. We use scripts to 'tidy-up' context diagrams, so they show only the associations of the system of focus. I admit, it's something you have to build yourself but it is possible and not difficult!

11

General Board / Re: Naming standard for Tagged Values, so different scripts works

« on: May 17, 2018, 10:13:54 pm »

The use of special characters is mainly defined by the underlying database. If you use a database/driver that supports unicode, EA works fine with special characters.

12

General Board / Re: Create relationship matrix in RTF report

« on: November 11, 2015, 10:15:50 pm »

This is also a feature I want...but as far as I know it is not (yet) possible to have a table with a variable number of columns.

13

General Board / Re: RTF Generator and Automatic Fields

« on: April 12, 2013, 10:13:18 pm »

You can put those fields in tagged values of a package. In the template you can use "valueOf" to access those fields.

cheers,
Rob

14

General Board / Re: version control vs EA Security

« on: March 27, 2013, 10:20:30 pm »

I support the post of qwerty. We started out with version control (SVN) but had to move to EA security/locking because of frequently damaged models. Since the transition we do not have any problems anymore.

The one thing that I miss since the transition, is commit comments. The reason of change, was previously noted as commit comment, is now unknown. With auditing on, you can see who made the change but the why is not recorded anymore.

cheers,
Rob

15

General Board / Re: Sequence Diagram Not Allowing for Component Re

« on: January 04, 2013, 09:30:46 pm »

This 'new' behaviour looks like a bugfix. In a sequence diagram you should work with instances and not with classes. The colon prefix indicates that an instance of the class is created.