AS-IS and TO-BE Modelling

[Eamonn John Casey]

Hi!

I am trying to model an existing Version of a system but at the same time trying to model the changes that must be made to the next version.
In Version n+1 I add a new relationship between elements that exist in Version n. I really do not want that new relationship appearing in Version n. Only in Version n+1 models.

Is there some way in EA v12.1 ArchiMate MDG to do this?

Thanks,
Eamonn J.

[qwerty]

Try a Search (button top left) with "AS-IS TO-BE". That gave me 32 results.

q.

[Glassboy]

That's an interesting question.  Given that you're using Archimate and don't have things like  instantiation or v13 new time aware modelling available you're limited in what you're going to be able to do beyond your n and n+1 being completely separate models.

[OpenIT Solutions]

Hi,

Have a look at diagram filters in the help. You can add a version number to a field you can filter on, ie phase, then hide elements as required. However I can't remember of the top of my head if you can filter relationships - I think you can...

[Steven Bos]

the filter option is not helping if you want to see the same component in a state of AS IS and TO BE.
Then you are either stuck to version control and maybe you want to have a look at the versioneer tool from LieberLieber.

https://www.youtube.com/watch?v=PocUexhgW0E

We have chosen for now for two repositories --> the O (development) and the P (production) from OTAP (developement -> test -> acceptance -> production). Maybe later we go for whole OTAP process for EA as well.
Basically we are making an XMI-export as it was code and release an XMI file from the O (development environment) to the P (production environment).

in the end we hope it will result in repositories that represent their related environment in the real world. An advantage will be that we will follow and time the same procedures as the rest of the SCRUM squad so we increase our interaction with them. The other reason is now almost everybody is using EA within the SCRUM team so this release system has our preference. Also the programmers were not too happy about another version control system. It added to much documentation for them to do version control on code and to do version control on their diagrams.