access & version control best practices

[meduri]

Hello, Our project with multiple teams planned to use Sparx Enterprise Architect 7.0. And EA setup is to use share filesystem for repository and use MKS for version control. Each worksteam team will have specific packages in EA and need version control and access control at worksteam level. Does Sparx has any best practices or recomendations on creating and maintaing the version control at package levels. Also looking for similar documentation on how to setup and maintain security access levels on the packages for internal worksteam team members and external teams.

Thanks in advance

[«Midnight»]

This is highly dependent on your corporate practices.

That said, there's a wealth of information and suggestions, including some information on tricks and traps, to be found.

Sparx has several articles on this. Rather than hunt around for them, I suggest you search the forum - all sections - for information about this.

There are several benefits of doing so. Among these are: you'll get experience in searching the forum (the search engine is a bit arcane, but once you get the hang of it you'll learn a lot), the resources on the Sparx site are all identified (and critiqued to some extent) in the various threads, and you'll learn a lot about what works and doesn't in various situations.

HTH, David