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

Pages: [1] 2
Automation Interface, Add-Ins and Tools / Re: Automate execution of scripts
« on: February 28, 2018, 07:33:33 pm »
Thank you for replying, Geert. Too bad, I hope they will implement this as feature in the future.

Okay, guess I need to work on my searching skills.

Automation Interface, Add-Ins and Tools / Automate execution of scripts
« on: February 28, 2018, 01:28:24 am »
Is there any way to automate execution of scripts?

I've made some scripts which import contents from our cmdb to Sparx EA, and I would like these scripts to automatically run every night.

General Board / Re: Element Text Alignment
« on: December 12, 2017, 06:47:45 pm »
Okay, as expected. I've found a workaround by setting the alias blank and adding a text label which i put inside the element. Not ideal, i hope they will implement a feature which solves this in an easier way.

General Board / Element Text Alignment
« on: December 11, 2017, 08:11:44 pm »

Can anyone tell me if it's possible to set text alignment (name of element) for an element?

I am narrowing down some ArchiMate elements which makes the element name appears partially outside the element. I want it placed back inside the element somehow, hopefully without using shapescripts.

Automation Interface, Add-Ins and Tools / Scripting Layout Diagram
« on: June 08, 2017, 11:38:13 pm »
With the help of you guys I've been able to import elements with their relations from our cmdb to Sparx represented as different ArchiMate elements. I am now in the process (by scripting) of creating a configuration diagram for each application that has been imported. I've been able to add the elements to a new diagram, and all the elements stack upon each other in the upper-left corner of the diagram.

I want the elements to layout as the "diagraph" option (or at least something else) as available in Tools -> Diagram Layout. As far as i can se the project interface package with its diagramLayoutEx method is supposed to do something like this. I have not succeeded in producing any code which executes this method successfully. Can anyone provide me with a good example which I can base my code on?  (for EA 13)  :)

General Board / Re: Time Aware Modelling - Some questions
« on: April 28, 2017, 04:32:19 pm »
I also can't see how you can do without the additional cloned elements.  State Is NOT ONLY indicated by the relationships.  ANY part of the cloned item can change (including its name) so you need to provide the ability to change ANY property or relationship.  The only thing that can't change (and retain the cloning functionality) is the traceback relationship to the master from the clone.  If you change that, you break the cloning functionality.

That's a valid point. We're modelling primarly in ArchiMate, and extend with BPMN, ERD and UML when it's necessary with more details. For ArchiMate the only "property" we could change is name, and perhaps notes/description. Names will rarely change, and if the need for this happen you could add an additonal element representing this, while leaving the other elements alone. Meaning name could be thought of as an unique ID for the element. For the other modeling languages I can see this could be an issue if you're working closer to the solutions continuum, especially in data modeling.

General Board / Re: Time Aware Modelling - Some questions
« on: April 28, 2017, 06:25:44 am »
First question, does the version numbering need to be numerically based?  The implication is that it doesn't but can anybody confirm?
In our case, we use the version field to identify which project the item belongs to - we could extend this to include another part to indicate as-is vs to-be (in that project)

We've done some testing with time aware modeling based one the same idea you suggest. Meaning we use "as-is" and "to-be" in the versioning, which seems to work out fine. Including the project id might be a good idea as it could indicate if it's actually part of a transition architecture.

Consider a cloned V1.1 diagram with a V1 element 'X' that relations to a V1 element 'Y', with a V1(X-Y) relationship.
I don't like the fact that when you clone V1-X, it creates a V1.1(X)-V1(Y) relationship, nor do I like the V1.1(X)-V1(X) relationship.

To Illustrate why I don't like it, consider what happens to a document of your V1 AS-IS that reports on relationships. All of a sudden it is polluted with V1.1 etc version object ends. And also bear in mind it will likely report on the V1.1 'X' through the trace relationship.

I wasn't aware of this, but I see how this could be unfortunate. Could this be solved if there existed a versioning/state for the relations? (indiciating if the relations are as-is or to-be)

My biggest issue with time aware modeling is that you get an ureasonable amount of elements which you have to keep track of across states. Does anyone have any good way to handle this?

I think the most reasonable way to solve this is to have only one element regardless of state, meaning you would clone diagrams rather than elements. State is primarly indicated by the relationsships the element has to other elements, meaning there has to be a way to indicate if a relationsship is as-is or to-be. This would also render the relationsship matrix more useful. In an integration matrix you would for instance be able to sepearte if the integrations (relationship between two elements) are as-is or to-be. As far as I know there's no way to accomplish this in Sparx today.

General Board / Re: best practice for baseline and target arch models
« on: April 26, 2017, 05:26:33 pm »

The TOGAF Content Metamodel says nothing in regards how to structure a repository for the different states for an architecture. The Architecture Landscape chapter does this, but it's a challenge to find a good way to realize this in Sparx EA.

We have partially solved this now by having different states (as-is, to-be, candidate) packages for diagrams/views, and a single package regardless of states for elements (which would be similar to the TOGAF content metamodel). This means the same element can be used in diagrams describing different states, which means we have to find way to describe which state the connectors (relationships) are in. We also have to make sure different people can work with the same element without getting in conflict with each other.

Another option to solve this is to make an element catalog for each state, but this would probably require too much effort to keep updated. Or one might export the elements a project want to use to make sure they're not in conflict with someone else, and then import it back when the architecture has been developed. The GUID of the elements will make sure the exported elements are merged into the existing ones.

General Board / Re: best practice for baseline and target arch models
« on: April 20, 2017, 09:11:39 pm »
We also structure our enterprise model in packages based on the archimate domain which will contain the various catalogue elements, in addition we have a "View" package which primarly contain diagrams. We would like to have the matrices represented as elements in View package as well, but as far as i know this is not possible in Sparx EA.

I've encountered a white paper (W174) from the open group which adresses this issue as well;

One of the most challenging aspects of a well-run repository is managing transitions over time. In most simple terms, every architecture will exist in up to four states. The current state is what exists in the Enterprise today; this baseline provides the reference for all change. The target state is what stakeholders have approved; this state provides the reference for governing all change activity. Transition states are partially realized targets between the current state in the target state. The candidate state is what has been developed by the EA team but has not been approved for a status sufficient to govern change.

I consider this a reasonable way to structure our model, meaning we'll have something like this;

- Clinical Architecture
      - Clinical Candidate
            - Business
               - Business Process
               - Business Role
           - Information
           - Application
           - Technology
           - Views
               - Workflow Diagram
               - Application Commuincation Diagram
     - Clinical Current
           - Business
               - Business Process
               - Business Role
            - Information
            - Application
            - Technology
            - Views
     - Clinical Target
            - Business
               - Business Process
               - Business Role
            - Information
            - Application
            - Technology
            - Views
      - Clinical Transition - Project X
            - Business
               - Business Process
               - Business Role
            - Information
           - Application
           - Technology
           - Views

Do you only consider it neceassy to track different architecture states for views/diagrams?

In my proposed structure mentioned we would have states for the different catalogues (including as elements) as well. The transition relationship which Paolo is mentioning might perhaps eliminate the need to do this?

General Board / Re: best practice for baseline and target arch models
« on: April 20, 2017, 04:23:58 am »
Is there any new best practices regarding this topic?

We're building an architecture repository based on TOGAF, but have some troubles on finding the best way to organize the repository (architecture landscape) in the time dimension (as-is, to-be, transition, etc.). Time-aware modelling might be useful, but I'd really like to hear what you consider is most practical and feasible.

I've been able to import applications and servers as elements into Sparx EA from a CMDB, but now I want to import the relationships as well. What class/method takes care of adding new relationships between two elements?

General Board / Re: Document template - elements of child package
« on: January 30, 2017, 04:57:17 am »
Thank you guys, this was exactly what I needed

General Board / Document template - elements of child package
« on: January 24, 2017, 02:25:07 am »
Is there any way to make a template for documentation that will list the elements of a child package?

This is my code for the template
Code: [Select]
package >
child packages >
< child packages
< package

I want something like {Element.Name} inside child packages

General Board / Hyperlinking related diagrams
« on: January 23, 2017, 10:04:12 pm »
Does there exist a way to hyperlink all of the related diagrams for an element?

I would consider this to be equal to right clicking an element and choosing "Find -> Find in all diagrams...", but i want a hyperlink which does this for me for a specific element.

General Board / Re: Text Label when applying image on element figure
« on: October 17, 2016, 07:47:41 pm »
Thank you Geert. I wasn't aware of the shapescript feature, but it seems to be able to help me a long way :)

Pages: [1] 2