More and more organizations are focusing on the use of an architecture repository. An architecture repository contributes to a more mature approach to introducing architecture into an organization. In the current working method, based on office automation, organizations encounter limitations when producing architectural documents.

Introducing an architecture repository is then one of the options and a logical scenario. There are multiple platforms and tools available for architecture repositories. In this book we use Sparx Enterprise Architect as a tool for setting up a repository.

Experience shows that the tool can provide the right support from a functional perspective. However, introducing an architecture repository comes with a number of challenges. The transition from a document-driven to a repository-based working method should be seen as a change process that can have a significant impact. Impact on the architecture team, but also on the stakeholders of architecture within and outside your own organization.

Reason for developing this book in this way. We will therefore discuss the advantages and disadvantages of an architecture repository compared to the document-driven approach. We then develop a solution architecture for an introduction to an architecture repository. Actually an “Eat your own dog food” approach, the model itself has been developed in a repository! Subsequently, a number of step-by-step plans are described which scenarios can be followed when introducing an architecture repository. The last part is a number of tools that will support the change in working methods.