SQL repository with version control

[SimonDMU]

I am have briefed my self and tested setting up an SQL repository and find this is fine but I was able to have two people edit the same project and submit changes at the same time.

I have not been able to find how you can provide some form of identity lock with a repository. For example when a business analyst opens the repository record project it is checked out and so no body else can edit this until it has been checked back in. Can this be done?

Also is there away of incorporating version control with this as well so that we are able to roll back to previous versions if we so choose?

I think part of my query comes from understanding how to set up a version control repository and an SQL repository but not how the advantages of both can be combined...

[Geert Bellekens]

Yes,

You can use both the security option as an integration with a VC to (or combine both) get exclusive access to a certain part of the model.
The type of backend (eap or dbms) doesn't really mattern.

Geert

[SimonDMU]

Geert

I understand what you mean:

You can use both the security option as an integration with a VC to (or combine both) get exclusive access to a certain part of the model.

But I am trying to find how to have version control with a DBMS in place as the repository.

My understanding of Tortoise SVN is that it operates as a repository itselt. I don't understand how the structure would work with having a DBMS as a central repository with a version control repository controlling the check in check out status of information. Can this be done? or even should this be done?

I am attempting to put a structured method of developing architectures within a large organisation that has issues with first of all providing corporate wide access, SQL repository, and also managing the editing of data with regards to multiple developers, architects and analysts checking in and out the same packages simultaneously, Toroise SVN.  I need to manage package versions and lockign of packages if required.

So my question is am i looking at the correct solution or am I trying to be too complicated? I appreciate any feedback and advice you are anyone else can supply.

Cheers,

Simon

[Geert Bellekens]

Simon,

As I said the integration with VC is possible regardless of the persistence backend (eap or dbms) you use.

VC work on xmi exports from packages within a model.
If check in a package EA will export an xmi file with the contents of this package and check that file in. The package then gets locked so nobody can change it.
When checking out a package the (latest version of the) xmi is retrieved from the VC server and imported in the model. This package is now made unlocked for the person that checked it out. Only this person can now change something in the package.
After the changes are done this person has to check-in the package again. EA then creates an xmi file... etc...

Hope this clears up something...

Geert

[SimonDMU]

Geert,

I beleive I understand.

I think maybe producing a process model in EA will help me better understand this  

I will try and set this up within the organisation and see how it goes. I think the issue will be around getting users to adopt this method of control.

Thank you

Simon

[pH]

Hi,

One limitation of using Version control is that when package is exported to xmi it will ignore some information. These are typically project specific information. For example if you have some physical view or deployment diagram in your architecture using some nice images, exporting to xmi ignores those images. Similarly if you have done some UI modeling and if UI elements like screens are captured as images, such images will be missing from xmi. Author will be still seeing them but others will not see those images. Also when tried through image library I have found images getting misplaced for other user!!. VC will be helpful only for history and otherwise using Security for access control might be the preferred approach as it allows at element level as against package level with VC.

Thanks.
pH