Based on extensive experience using Sparx Enterprise Architect for Team Modeling on large-scale, mission-critical projects we recommend that your Sparx EA team follow these proven best practices:
- Model sharing: Use a Relational Data Base Management System (RDBMS; e.g., MySQL, Oracle, SQL Server) based model repository instead of a file-based repository (e.g., Subversion), since the former accommodates multiple, fine-grained, concurrent updates better than the latter. (RDBMS model repositories need only update selected table data elements, whereas file-based repositories need to update the entire file each time a model element is updated.) Further note that you must use a Sparx EA Corporate edition or higher to use a RDBMS for a model repository.
- Model version control: Use a dedicated Software Configuration Management (SCM) tool for version control of Sparx EA files in either EAP or XMI file formats. Subversion, which is open source and works well with Sparx EA EAP/XMI file formats, is a popular choice for this.
- Model user permissions: Apply User Permissions to allow/restrict access to various modeling team roles.
You can find generic information about Team Modeling with Sparx Enterprise Architect on the following page: