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

Pages: [1]
1
General Board / Re: use heatmap for existing diagrams of elements
« on: December 04, 2015, 12:06:04 am »
Great, thanks
(wish I had found it before writing custom SQL for a heatmap :)

ta

Jason

2
General Board / use heatmap for existing diagrams of elements
« on: December 02, 2015, 06:54:28 pm »
Hi,

Is it possible to use the heatmap functionality in 12.1 to colour-code an existing diagram of elements?
I'd like to colour-code a diagram of elements based on a specific tagged-value.

I could write a script to do this, but I wonder if its possible to do with the new heatmap functionality

thanks

3
General Board / Re: best practice for baseline and target arch mod
« on: November 04, 2015, 08:30:25 pm »
Thanks for the reply.
That is what we ended up doing.
I found one other suggestion on a linkedin forum which recommends a 3rd party MDG tech that creates a profile with built-in time concepts.
E.g: you can then show that certain elements and connectors become relevant after certain projects are finished, etc

It was too much overhead for our use case so we just keep baseline and target models separate and update each manually

(the alternative I mentioned is on a closed linkedin group, but if you google "Best Practices for Baseline and Target architectures" and open the cached version of the linkedin result then you can read the thread - this forum sw barfs if I post the webcache link...)


Jason

4
General Board / best practice for baseline and target arch models
« on: October 31, 2015, 12:12:45 am »
What are the best techniques for modelling baseline and target architectures?
We're modelling a legacy migration in archimate and want to show how the app landscape will change over time.

Most the elements will remain the same but the connectors will change as new components replace the legacy box. E.g., in this simple example new components E and F will replace parts of D and the relevant clients (B, C) will change connectors accordingly:



If we have everything in the same model then we need many connectors to represent different time periods. If we have the baseline and target in different models then we need to copy all the elements from baseline to target and then manually update the baseline as the target gets implemented.

Are there any other alternatives?

thanks
Jason

5
General Board / Re: set feature visibility for non-uml entities
« on: February 23, 2015, 07:51:55 pm »
Thanks.
Its an MDG provided by sparx. I see that they have extended the UML Activity stereotype for the entities I use (archimate businessfunction).
It should inherit the compartments from UML Activity, but its not being displayed - so I guess I'm stuck...

J

6
General Board / set feature visibility for non-uml entities
« on: February 21, 2015, 01:52:28 am »
Hi,

Can I add feature visibility for non-UML entities?
I'd like to show features (e.g., tagged values) for Archimate entities (MDG plugin) but nothing displays when using the various checkboxes.
Entities are displayed with rectangle notation
EA = v11.1

Is there something else that needs to be done for entities from MDG plugins?

thanks
Jason

7
General Board / Re: Multiple relationship matrices
« on: December 10, 2014, 10:21:05 pm »
Thanks.
Using overlays is throwing an Oracle exception when I try to apply it and set the value for the relationship
(ORA-01400: cannot insert NULL into ("EAS"."T_CONNECTORTAG"."PROPERTYID")

But I guess thats an issue for another forum...

J

8
General Board / Multiple relationship matrices
« on: December 09, 2014, 11:11:46 pm »
Hi,

Is it possible to have multiple relationship matrices with the source, target and link type?
I'm using the matrix to capture BusinessFunction to ApplicationComponent realisation relationships (archimate). And I would like to capture both AS-IS and TO-BE.
i.e., I'm after the same source, target, and link type but the relationships will look different in each matrix.

I guess I could work around the issue by either using different link types for AS-IS and TO-BE or to replicate the ApplicationComponent (targets) in another package for TO-BE. But I would prefer not to.

thanks
Jason

9
great, thanks

10
anyone know where this link has gone?
Can't find it in google's cache either...

thanks
Jason

Pages: [1]