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

Pages: [1] 2 3 ... 8
1
General Board / Re: How to retrieve the name of the last modifier
« on: August 16, 2019, 12:24:05 am »
There are only two ways. Either you turn on auditing or you dare to write a trigger for that purpose.

q.

I looked and saw a lot of audit information, with names and timestamps etc. but not easy to interpret. How can I access the audit information in a script or report template so that I can find out for a particular element who has changed it when?

2
General Board / Re: How to retrieve the name of the last modifier
« on: August 15, 2019, 07:30:46 pm »
There are only two ways. Either you turn on auditing or you dare to write a trigger for that purpose.

q.

Allright, but neither of these methods give me the modifier from a time when I had neither of these mechanisms in place, right? Doesn't the SQL Server database store this information?

3
General Board / Re: Ignoring invalid ArchiMate 2 element
« on: August 15, 2019, 06:06:07 pm »
It sounds to me that you are trying to export an model with ArchiMate 3 elements to ArchiMate 2 and you could be having a backward compatibility problem.

I am not too familiar with the Generate Model Exchange extension but your original post clearly states
(context->extensions->Archimate2->Generate Model Exchange file.
and your last post states
Actually I use Archimate 3 but my models historically still contain some Archimate 2 elements

Have you consider that your Archimate 3 elements are not backward compatible? Have you considered upgrading all elements to Archimate 3 stereotypes and exporting an Archimate 3 exchange file? Alternatively, you could downgrade all elements to Archimate 2.

I would not recommend mixing Archimate 2 and 3 elements, it is likely to give you a headache.

An issue is that Sparx EA version 13 only allows exports in an Archimate 2 exchange file, not Archimate 3. So one option would be to downgrade everything to ArchiMate 2, but I don't know how. Manually, element by element, is no option.  I am sure it is possible to create a script for this but I have no idea what exactly must be done by this script. Also of course, this might break a thing or two.....

4
General Board / How to retrieve the name of the last modifier
« on: August 15, 2019, 05:56:50 pm »
Elements and diagrams contain the name of the Author, set to the user at creation time. But the name of the person who did the last modification to an element or diagram is not so easy to find. Is this information permanently lost or is there some way to retrieve it? As a related question, I would also like to know who created or modified a connector.
I am using Sparx EA version 13 with a shared SQL Server database.

5
I've seen some relationships end up with stereotypes from multiple ArchiMate versions.
Indeed, multiple boxes in multiple pulldowns may be checked. I find the assignment of stereotypes to elements a messy business.

6
I've just tested it in 13.0.1310 and it works.  Have you checked you do have an ArchiMate 2 flow stereotype on the relationship you're trying to export?

Yes it is a perfect Archimate 2 flow. All other relationships in the same diagram are exported correctly.

It is a strange problem because I just created a new Archimate2 diagram and then it worked. Doing the same in another model, also with an Archimate 2 diagram, does not work. This erratic behaviour only occurs with Flow relations, not with other.


7
When I export my Archimate 2 model using Sparx EA version 13, FLOW relations are NOT exported and do not appear in the generated XML file! All other relations are present. This of course is a serious bug and hampering my work.

Has this been resolved in a newer version?

8
I need to export my Archimate model in Archimate Exchange format from Sparx EA version 13.0.1308.
For some strange reason, versie 13 supports Archimate 3 but can only export Archimate 2 models....

So there are two solutions: (1) convert my model(s) to Archimate 2  or (2) modify the export script (where can I find that??) to support Archimate 3.

Does anyone have a script for the conversion 3-->2?

Thanks!

9
Bugs and Issues / V14 Serious Bugs in Archimate3 implementation
« on: August 01, 2019, 01:27:56 am »
 I have a number of issues with the Archimate 3 implementation in V14:
  • The Quick Link does not allow me to draw a Flow relation between two application components while this is perfectly allowed in the standard
  • The Quick Link does not allow me to draw a Serving relation between two application components while this is perfectly allowed in the standard
  • The Model Export (Generate Model Exchange File) refuses to include any flow relations (not only betwee application components but also between application functions - the latter I can create via the Quick Link)
  • If I create a Composition relation via Quick Link, it is graphically incorrect: it is shown like a Serving relation

10
General Board / Archimate FLOW relationships do not export!
« on: August 01, 2019, 01:02:20 am »
Thanks for all the help and suggestions so far. I have the practical situation that it is hard to avoid having some old Archimate 2 elements in my Archimate 3 models.

But currently there is another pressing issue:  Archimate Flow relationships do not export at all via Model Export facility. Neiter flows between application components neither flows between application functions! They just do not show up in the model exchange file (Archimate 3 nor Archimate 2). This seems a bug.....


11
General Board / Re: Ignoring invalid ArchiMate 2 element
« on: July 30, 2019, 11:21:56 pm »
I've had similar problems and I found that EA was getting confused between multiple versions of the Archimate MDG.  Try this:  just move the other Archimate MDGs  from the MDG file under program files and have only Archimate 2 (I'm assuming that is the one you want).   Restart EA and sure that your EA has only Archimate2 MDG selected as a technology.   Then try it again.  It's worth a shot.  In general, I model with Archimate 3 only and found that if I had Archimate 2 available, it would sometimes create an element as the wrong MDG type.  Removing the other technologies fixed that, but your results may vary.

Actually I use Archimate 3 but my models historically still contain some Archimate 2 elements. So I want elements of all versions of Archimate to be exported. For some strange and annoying reason, the export process only exports the Archimate 2 elements. Very user unfriendly and very unnecessary since the differences between the two versions are minimal.

Regarding the switching off of some MDG's, that seems like a good idea but I cannot do this by moving files because I work on a shared SQL Server repository. I suppose there is no way to do this then?

And finally, is the Archimate Exchange process executed by a script that I can perhaps edit? Any idea?

12
General Board / Re: Ignoring invalid ArchiMate 2 element
« on: July 23, 2019, 11:31:29 pm »
I have tried to change the stereotype of these elements but I have not yet found a reliable way to have these ignored elements included in the export.

Has anyone suggestions?


How are you changing the stereotype? Try removing the old stereotype from the element then drop the new stereotype from the correct toolbox onto the element on the diagram.

Actually, the situation is even worse (and weird!). When I create a new Archimate element in Sparx 13, the "Generate Model Exchange File" process refuses the new element because it apparently is an Archimate 3 element while the Exchange file process supports ONLY version 2, very strange indeed. And it is completely unnecessary to differentiate between two versions of the standard that are very similar.

13
General Board / Ignoring invalid ArchiMate 2 element
« on: July 22, 2019, 11:44:48 pm »
I am trying to export an Archimate model into the Archimate exchange format in Sparx EA version 13. (context->extensions->Archimate2->Generate Model Exchange file.
But the result is missing many elements and the export log contains many lines like
  * Ignoring invalid ArchiMate 2 element : <name of element>
I have tried to change the stereotype of these elements but I have not yet found a reliable way to have these ignored elements included in the export.

Has anyone suggestions?   



14
General Board / Re: Import of large model from an external source
« on: April 12, 2019, 01:03:49 am »
I wouldn't try to go through xmi. That really isn't the most easy format to use.

There are a few options:

- Use the excel importer to import classes and attributes. (Excel scales pretty good and goes up to 1M of rows)  You might want to write additional code to import datatypes (and link them to the attributes) and relations.

- Write a custom import program that reads your source database and creates the corresponding model in EA.

I can't image it being more than a few days of work to get it all done.

If you want to hire me as qwerty suggested (thanks qwerty ;)) you can email me at geert@bellekens.com. But please take into account that I have a pretty full calendar already. Next available days at the moment are in July.

Geert

Thanks for these suggestions. This does not sound as a very easy job.

We are in fact investigating the use of EA for the maintenance of a complex model instead of the current text-based interface. The advantage of EA is its graphical representation of the data but getting the data in EA and creating useful diagrams is then a new challenge.

But is EA in itself capable of handling a model with say 200.000 elements and relations?
Not "very easy" but not that difficult either.
Yes, EA scales pretty well up to hundreds of thousands of elements. (thanks to the database backend)

Geert

Ok, so this might be doable with the XLS-importer? I obtained it from your website but I did not see how it can also import relationships.

15
General Board / Re: Import of large model from an external source
« on: April 11, 2019, 10:56:47 pm »
I wouldn't try to go through xmi. That really isn't the most easy format to use.

There are a few options:

- Use the excel importer to import classes and attributes. (Excel scales pretty good and goes up to 1M of rows)  You might want to write additional code to import datatypes (and link them to the attributes) and relations.

- Write a custom import program that reads your source database and creates the corresponding model in EA.

I can't image it being more than a few days of work to get it all done.

If you want to hire me as qwerty suggested (thanks qwerty ;)) you can email me at geert@bellekens.com. But please take into account that I have a pretty full calendar already. Next available days at the moment are in July.

Geert

Thanks for these suggestions. This does not sound as a very easy job.

We are in fact investigating the use of EA for the maintenance of a complex model instead of the current text-based interface. The advantage of EA is its graphical representation of the data but getting the data in EA and creating useful diagrams is then a new challenge.

But is EA in itself capable of handling a model with say 200.000 elements and relations?

Pages: [1] 2 3 ... 8