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

Pages: 1 [2] 3 4 ... 7
16
Yep - it's working!

17
Thanks everyone.
I've had a support ticket in with eaDocX about this and the good souls there have an approach that goes like this:
- import into some temporary elements with tagged values holding the GUIDs of the things that need hooking up, together with the type of connector and it's stereotype;
- run a script on the temp elements to connect up the elements referred to in the temp elements' tagged values.

Simples. 25,000 elements in play, it's still processing (doing it over VPN), but I will report back.

18
Hello
We're still no further with this - i.e. being able to import relationships into EA from Excel.
Reminder: the elements already exist in EA so we want first to push the elements out to Excel with GUIDs (can do this part), then transpose them with the target elements and relationship type (available in a second file) so that we have an Excel table thus:

Source_GUID, {other source fields}, Target_GUID, {other target fields}, Relationship type

Lastly, to import this back into EA such that the existing elements remain unaltered but that they gain the new relationship type.

Are we hoping for too much?
Namaste
YM

19
General Board / Re: Glossary in Version 13
« on: March 12, 2017, 04:38:51 am »
Thanks everyone for your kindness, humour, and help.
What a community!
I'm back into the Glossary. Happy!

20
General Board / Re: Glossary in Version 13
« on: March 11, 2017, 03:30:12 am »
Now I feel really stupid  :-[
What is the EA icon menu? (I have looked, honestly).

21
General Board / Glossary in Version 13
« on: March 11, 2017, 12:57:29 am »
I just can't find it! Help doesn't help! Can one of you kind souls?
Namaste
YogaMatt

22
Automation Interface, Add-Ins and Tools / Archimate 3 model exchange format
« on: February 16, 2017, 01:09:26 am »
Does V13 support ArchiMateŽ Model Exchange File Format for the ArchiMate 3.0 Modeling Language?

http://www.opengroup.org/xsd/archimate/3.0/

Many thanks,

M

23
Bugs and Issues / Re: Windows 10 issues
« on: February 03, 2017, 07:34:03 pm »
Thanks everyone - false alarm - IT support desk determined it was an access rights issue.

24
Bugs and Issues / Re: Windows 10 issues
« on: February 02, 2017, 09:40:29 pm »
Hi
We've had a problem with installing 1308 in Windows 10. Compatibility mode OK? Or should we avoid the upgrade?
Cheers
M

25
Many thanks Geert. That's brilliant.

26
Having model elements to represent TFS stories, features etc in Sparx EA will support traceability and agile modelling.
We want to avoid rekeying and dual maintenance of the stories, etc in TFS and EA.
So, does Sparx EA integrate with TFS in such a way that TFS stories, etc are synchronised with model elements in Sparx EA? That is, model elements which are the stories and features, etc.


For anyone else reading this post later, and for completeness, does Sparx EA integrate with TFS for:
  • For versioning the code generated from the model?
  • For versioning of the model elements?

27
General Board / Re: Changing Stereotypes
« on: December 06, 2016, 04:04:26 am »
Thank you Qwerty
I understand the caution.
Your suggestion is to use side scripting on the Sparx client?
I've not done anything with that yet.
I looked into it on the help files but was put off by apparent complexity.
Please can you point me at some clear examples / pointers to get started?
Namaste
YM

28
General Board / Changing Stereotypes
« on: December 06, 2016, 03:31:03 am »
Several hundred model elements were stereotyped "PhysicalDataComponent" (PDC) when they should be "PhysicalApplicationComponent". (PAC)
Manually changing them is one option  ;D

Updating the value in Stereotype field in the SQL t_object table gets you some of the way there. But there seems to be some 'hangover' where the old PDC stereotype still exists as a second stereotype in the browser. It will switch off if I manually go to the element properties and disable that PDC stereotype. Again, manually changing them is one option  ;D

Back to SQL I found that the t_objectproperties table held entries for each element, which were for the tags that came with the PDC stereotype. Deleting these entries cleared the PDC stereotype from about half of my elements. But not all. And now I'm wondering if anyone out there knows the underlying schema well enough to suggest where this ghost is hiding, please?

29
Suggestions and Requests / Re: TOGAF 9 support
« on: September 17, 2016, 12:51:29 am »
Yes, and in Extensions->TOGAF->About, we see "tool certification pending"  ;)

30
General Board / Re: TOGAF and Archimate technologies
« on: September 17, 2016, 12:48:50 am »
Hello Stig

Did anybody reply to you?
We're working it from the other way around, whereby we'd like to move over from the TOGAF content model to using Archimate constructs in order to leverage BEASI. But we'd keep aspects of TOGAF content model (and extensions), and certainly keep our model structuring/process alignment with the ADM.
How did you get on? Did you know that The Open Group are working on "Project Harmony" to harmomise Archimate and TOGAF?

Namaste
YogaMatt

Pages: 1 [2] 3 4 ... 7