Architecture governance / maintain repository consistency

[Greg_PL]

Hello Community!

I'm pleased to join this forum and I come with question to discuss here right away .

How to maintain repository and keep it always up to date within architecture team working on it on daily basis?

While taking care of ArchiMate elements / components by aproovig them and moving to production repository instead of keeping in local packages, I'm struggling with.... Relations. How to make sure that all conceptional work / solution variations that are using production components is just temporary and will not impact traceability in production repository?.. If only relations/connectors had 'status', but they don't.

I'd appreciate any suggestions.

All the best to you!

[qwerty]

There's no easy answer and it requires a consultant to collect requirements in order to come up with a good solution. That may be a central database with locking or a manual distribution via XML. (Stay away from the Mickeysoft replication feature whih brings more grief than it will support).

q.