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

Pages: 1 ... 24 25 [26] 27 28 ... 47
When you define Tagged Values for Stereotypes with Profile Helpers and you add e.g. two Tag Groups, you can move the tags to those groups.
After closing and opening the Profile helper, tags defined e.g. under group A are now moved by EA under group B.
This behavior is in V12-V13.

I am not absolutely sure (never searched for that feature), but I belief you cannot do that. What you could do, is to detail your use cases not with the steps included in the use case but creating e.g. sequence or activity diagrams instead.

General Board / Re: Share model components between different projects
« on: August 11, 2016, 05:08:03 pm »
Maybe I do not entirely understand what you do!?

I assumed that you have one common object repository (COR) and 70 projects sharing the common objects in COR). Further on I assumed that the common objects you change in any of your 70 projects and this can cause conflicts and you are using RAS as COR.

In this situation my recommendation was to have one repository to edit your COR one to deploy your COR (RAS) and 70 projects only using but not changing your core.

If your issue is more to update the 70 projects with the new version of your COR automatically, this should be possible with pure imports or version control.

However I would do that automation stuff only in cases, where the elements in COR are really good manageable in a way that people changing that COR, do really know what it means for the 70 projects. Btw. merging stuff is not really possible, so I avoid that whenever possible.

PS.: I am in a big company as well and sometimes things are possible which seem to be impossible. Maybe the git svn bridge satisfies your management.

I assume, you need to be a bit more precise in what you intend to achieve.
In a modelling environment a diagram is nothing/empty without the model behind.
What do you want to do with you extracted xml file?

General Board / Re: EA Repository
« on: August 10, 2016, 04:58:27 pm »
What Paolo describes seems to me, is exactly the same what we are doing.
We also transfer, from time to time, our data from MS-SQL to eap/Access-DB and this EA-File goes for some other reasons in a SVN repository.

I am not an expert in ArchiMate, just a guess.
Maybe running the script mentioned by sunshine helps.

Uml Process / Re: SysML Viewpoints
« on: August 09, 2016, 08:07:12 pm »
I am still using SysML V1.3. For those elements within V1.3 I decided that these do not give me much value, so I do not use those elements. In V1.4 I remember that something has changed, but I did not jet look on that.
However I will follow this thread.

Uml Process / Re: Extending non-UML diagram types
« on: August 09, 2016, 08:01:57 pm »
As I remember it was more a guess, but maybe you find it the way suggested by qwerty.

General Board / Re: EA Repository
« on: August 09, 2016, 07:59:02 pm »
Yes, but in this case you work in a lock/import->change->export/unlock procedure which at least slows down someting.
But could be the right way for you!?

General Board / Re: EA Repository
« on: August 09, 2016, 05:38:31 pm »

Apart from the “Magic Competitor” EA is Magic as well. So one trigger to get a user in the list, is just a login of that user. 

Uml Process / Re: SysML Viewpoints
« on: August 09, 2016, 02:47:22 am »
What do you mean with “Model Views”?
The “Model Views” View you enable in Menu “View” or a Model View element you find in the Toolbox “Documentation”?

Uml Process / Re: Extending non-UML diagram types
« on: August 09, 2016, 02:21:05 am »
Hi Polymorph,
yes, you can do that!

In your diagram meta class under "toolbox"/"Toolbox Profile"(Edit with Profile Helper) you have to insert e.g.:


Thank you!
I will try the DB string functions way. At the end the data will be imported into a "black whole" so newlines is not an issue for me.

General Board / Re: Share model components between different projects
« on: August 08, 2016, 08:13:08 pm »
Another possibility would be to have a own repository for your "common objects" stuff.
This way it is easier to ensure that you "common objects" do not depend on project specific stuff.
This is what we do and it is independent one the way you distribute you common objects" to the projects (import, SVN, RAS).

Pages: 1 ... 24 25 [26] 27 28 ... 47