Sparx Enterprise Architect as a repository for teams

About this course

More and more organizations are focusing on the use of a modeling repository. A repository contributes to a more mature approach to introducing models like architectures into an organization. In the current working method, based on office automation, organizations encounter limitations when producing modeling documents. With a modeling repository reuse, cooperation in the modeling teams and a more agile approach are enablers for a modeling and architecture team.Introducing a repository is then one of the options and a promising and logical scenario. There are several platforms and tools available for modeling repositories. In this training we use Sparx Enterprise Architect as a tool for setting up a repository as a demo. The reason for choosing Sparx Enterprise Architect is the favorable price-functionality ratio compared to other products available in this segment of modeling tooling. Experience shows that the tool can provide the right support from a functional perspective. However, introducing a 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 modeling and architecture within and outside your own organization.Reason for developing this training course and book in this way. We will therefore discuss the advantages and disadvantages of a modeling repository compared to the document-driven approach. We then develop a solution architecture for an introduction to a 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  repository. The last part is a number of tools that will support the change in working methods.

Course objectives

• evaluate the advantages and disadvantages of modeling repositories
• support teams in adapting to a new working method
• foster better cooperation in modeling teams