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.

Topics - natvig

Pages: [1]
The new metamodeling features in EA14 is absolutely fantastic. Finally meta constraints and view specifications can be easily implemented into a profile to enable constraints to diagrams and model validation. There are a couple of minor features missing that would improve even furter, such as the possibility to set diagram options in a view specification. Another thing that I have not been able to implement is the inclusion of patterns from a view specification. It works well from a toolbox profile, but not from a view specification. Has anybody made it work? From a view specification I tried to expose an abstract stereotype called MyProfileName::MyPatternName(UMLPatternSilent), but it is not working.

Any ideas?

Automation Interface, Add-Ins and Tools / Achimate, definition vs use
« on: November 06, 2016, 02:25:23 am »
I'm trying to understand how to best use EA for Archimate modeling. Having a solid understanding of SysML, and appreciating the difference between definition and use, I find the Archimate implementation in EA lacks som important features. Say for example that you need to model a business process where one of the business functions appear more the once. This presents a problem in EA since more than one instance of an element on the same diagram is not allowed. This makes perfect sense when modeling SysML since you use call behaviour actions to modell process flows in activity diagrams. However, in the Archimate 3 profile that comes with EA 13 you are supposed to model all diagrams types using "Class diagrams" which is a diagram that is supposed to have elements of definition on them.

My guess is that other Archimate tools allows more than one instance of the same business function on the same diagram. In order to make EA more usable as an Archimate platform should't business processes be modeled in activity diagrams using call behaviour actions?

/Hans (Archimate beginner)

General Board / Copying ports from one element to another
« on: October 13, 2016, 08:20:57 pm »
Is there a way to copy the ports from one element to another element, without having to copy the entire element. Preferably, I'd like to selectively copy any number of ports from the source element to the target element.

I have tried copying the ports by dragging them from the browser and release them over an element in a diagram. (This is what you can do to copy operations between elements.) Not working for ports. I have tried dragging them within the browser, which allows you to MOVE ports from one element to another. But I haven't found a modifier key to invoke copying instead. I have tried the context meny in the browser efter selecting port to find a copy function that works, but cannot find anything that works.

The only workaround I have found is to copy the whole element containing the port that I wish to use. Then MOVE the port as suggested above. Then finally delete what is left from the copied element. Is there a better way?


Suggestions and Requests / Element List improvements
« on: October 26, 2007, 04:39:15 am »
I would suggest two improvements to the element list feature:

1. Possibility to update any field on multiple selected elements, e.g. to change status on several elements at once.

2. Possibility to add additional columns from any given tagged value.

Suggestions and Requests / More RTF Generate Options
« on: October 25, 2007, 08:18:55 pm »
We need to filter out not only Packages but also Elements during RFT output. We therefore suggest that another option should be available in the Generate RTF Documentation -> Generate Options dialog box where the user is allowed to filter by:

Element tag <input tagged value name> <input tag value>

This feature is useful e.g. when the requirements are nested in Packages based on their type (Performance, Functional, etc) but requirements within packages need to be filtered based on other characteristics such as Phase or custom tagged value on element level.

Suggestions and Requests / Requirements Hierarchy
« on: October 16, 2007, 08:33:26 pm »
I would like to see a feature where the requirements hierarchy (or any element hierarchy) optionally could be preserved when doing a model search.

This is useful if you wish to make a selection among requirements based on some attribute (tagged value) but need to keep the hierarchical nesting as well. (The result would be that requirements without match on attribute still should be selected if it owns an element with matching attribute.) Obviously, the resulting selection can then be used to create reports.

This is a feature that is available in other requirements management tools e.g. ReqPro/SoDA.

General Board / Create RTF based on search
« on: June 24, 2015, 03:13:56 am »

I have created an RTF document based on a predefined search. (Instead of dragging packages onto model documents, a search is defined with a search value in tagged values of the model document.) The search looks like this:

Code: [Select]
SELECT Element.ea_guid AS CLASSGUID, Element.Object_Type AS CLASSTYPE
FROM ((t_object AS Element
LEFT JOIN t_connector AS fp ON Element.Object_ID = fp.End_Object_ID AND fp.Connector_Type = 'Dependency')
LEFT JOIN t_object AS product ON product.Object_ID = fp.Start_Object_ID)
Element.Stereotype = 'Function'
AND (fp.Stereotype = 'Performs' OR fp.Stereotype = 'FunctionProvision')
AND product.Object_ID = <Search Term>
ORDER BY Element.Name ASC;

As you can see, only the CLASSGUID and CLASSTYPE are selected. Still EA is capable of reporting on any element attribute as well as any diagram embedded within the element. However, embedded elements are not reported.


1. Is there a way to use the embedded elements Section in your RTF template when using RTF searches as a basis for populating the document?
2. EA ignores/overrides the sorting order in my search. Is it possible to make EA honor the search order?


General Board / Support for Parameter Sets?
« on: February 05, 2013, 10:56:06 pm »
I have tried to find support for parameter sets in EA, but cannot find any information about it or how to accomplish this. In an interview with Geoffrey Sparks some years ago this was planned to go into EA 6. Does anyone know how to make parameter sets?

General Board / Reentrant, a missing property on activities?
« on: February 09, 2012, 08:03:53 pm »
There is a property on UML activities called Reentrant.

If an activity is reentrant, each complete set of inputs arriving at a usage will create a new concurrent execution of the activity. I.e. it tells whether the behavior can be invoked while it is still executing from a previous invocation.

Is this property missing in EA?

General Board / Preserve relationships from imported model element
« on: May 20, 2008, 12:17:21 am »
We are working with multiple models in parallel, using Enterprise Architect. Some which are general (framework) and used as building blocks in more project specific models. The framework model is used by importing it to the project specific model as a root model (from XMI). The model is made read-only to the staff working on a specific project. When an updated version of the framework is released it is imported again into the project specific model. Relationships that originate from elements outside the framework root model are retained during update, also if the relationships have framework elements as target elements. Now, here is my two questions:

1. Relationships may be created from the framework elements even though this model is write protected using the EA-security mechanism. Should EA security mechanism allow this relationship to be created? I think it should not.

2. The relationships created from the framework elements are discarded when framework model is imported again with a new update. How can they be retained?

One typical relationship that we would like to model this way is the SysML <<Satisfy>> relationship. We want to use this relationship from Blocks in the framework to requirements in the project to model that the specific requirements are fulfilled.

Any ideas?

Bugs and Issues / Connectors broken after Import as Model Branch
« on: July 30, 2009, 12:18:28 am »
We are working with very large scale models. The models will consist of hundreds of version controlled packages, some of which are used as framework components (read-only) in multiple models.

Suppose that a general component COMP_A is modeled as a package in model MOD_A and later exported as RELEASE 1.0 (using the XMI import/export). Subsequently, the XMI-file can be imported as a package COMP_A into another model MOD_B (or several other models that will make use of the general component). Later when COMP_A is updated in MOD_A and released as RELEASE 1.1 it is easy to replace the package in MOD_B with the new release by right-clicking on the package that is to be updated and importing the updated XMI file. Any connectors made to elements within COMP_A in MOD_B are preserved. (Obviously connectors from elements in COMP_A are not preserved, and general packages should therefore be made read-only using the Lock-feature, or by using mechanisms available in the used VCS.)

In an environment where 50 developers is contributing to the model and where components need to be configured into multiple platforms, for multiple customers, version control is required. The complex hierarchy of controlled packages is packaged and released using EA's model branch (EAB-file). Also version control branching will be required which is currently not very well supported in EA. We are well aware of the specific replacements that have to be made to the XMI files in order to support branching and handling of version controlled releases that are not residing in main trunk. These shortcomings could be accepted for now, if only the procedure outlined below would work.

Now, to the specific problem:

1. A model branch of package A is initially exported from model A. The model is version controlled and stored in Subversion under trunk.
2. A formal release of A is required and the files (EAB and XMI files) are therefore copied to the subversion release directory (using SVN, not EA).
3. The EAB file and all the XMI files are subsequently edited to reflect their new location within subversion.
4. A model B is subsequently created and a package A is created by importing the model branch. The model will then contain version controlled packages that are stored in the subversion release directory. People working in model B can now work with the initial release of A.
5. An updated release of package A (from model A) is subsequently made available by repeating steps 2 and 3.
6. People working with model B would now want to right-click on the package A and choose "Import as Model Branch..." again, but this is not possible. One way to overcome this problem is to temporarily turn off Version Control on every controlled package within the branch, and then do the "Import as Model Branch..." However, while doing this maneuver all connectors to the package A are removed. This is in contrast to XMI file import as described above, where connectors are preserved.


1. Why is it not possible to redo the "Import as Model Branch..." without turning off Version Control?
2. Why are all connectors broken when doing "Import as Model Branch..." after turning off Version Control?
3. When can we expect support for version control branching in EA?


Is the MDG Technology for SysML still supported? In the SysML Technology menu there is a menu Item called View Allocations. When the item is chosen no allocations are displayed. There are plenty of allocations in the model.

Pages: [1]