1
General Board / EA Repository Structure
« on: August 15, 2024, 01:06:29 am »
I am sure there are as many ways to organise an Enterprise Architecture repository in Sparx as there are Sparx customers, but I would be keen to see some examples that organisations have found helpful and why.
We started with the TOGAF 10 Repository Structure but I am not sure this is really that practical with most elements and drawings end up in sub packages in the Architecture Landscape.
We were thinking of adding a top level Projects package in which all elements, be they proposed changes to current state, or an interim state or a final state would be created. Once deployed, they would be moved into the Architecture Landscape and the earlier states removed.
Just wondering what is considered best practice in Sparx
We started with the TOGAF 10 Repository Structure but I am not sure this is really that practical with most elements and drawings end up in sub packages in the Architecture Landscape.
We were thinking of adding a top level Projects package in which all elements, be they proposed changes to current state, or an interim state or a final state would be created. Once deployed, they would be moved into the Architecture Landscape and the earlier states removed.
Just wondering what is considered best practice in Sparx