preventing clashes between multiple users

[yonatan.lehman]

Hi
My team is currently creating an EA model that documents our code base.
Each of us is responsible for a subset of the components and their activities  we're trying to work out how to ensure that when we reference components and activities in diagrams all the links point to the same entities.

We're using EA 14 with a shared SVN repository
We have a Package called External which we are slowly filling up with a tree of components. It looks something like this
External (Package)
   Lib1 (Package)
     comp1 (Package)
        comp1 (Component)
        Interface(Package)
          comp1_activity1 (Activity)
          comp1_activity2 (Activity)
          comp1_activity3 (Activity)
Comp1 represents the c file comp1.c  and comp1_activity1 is a function in comp1
Initially there are no diagrams here - just components and Activities that we drag into Sequence Diagrams and Activity diagrams


Each of us creates our diagrams in out own workspace which is basically a clone of the above structure and when we're done we have to manually drag all our diagrams, once by one, into the package External package

Is there a simper/more efficient/more reliable way of doing this?

[Geert Bellekens]

Is there a simper/more efficient/more reliable way of doing this?

Probably, but it's kind of hard to give any suggestions based on your explanation.

Geert

[yonatan.lehman]

Hi Geert - thanks for replying, not sure what what information is missing. I have my code files and I use Git as a version repository.
I create an EA model based on this code, and I want to be able to detect that an Entity or diagram is out of date with the code.
The only think I can think of is to put the Git Commit code in the Entity/diagram Notes or some other field and then writing a script that compares these to the git commits in the code base.
As a first step I'm hoping there is an established EA way of doing this - it seems pretty basic to me

[Geert Bellekens]

Hi Geert - thanks for replying, not sure what what information is missing. I have my code files and I use Git as a version repository.
I create an EA model based on this code, and I want to be able to detect that an Entity or diagram is out of date with the code.
The only think I can think of is to put the Git Commit code in the Entity/diagram Notes or some other field and then writing a script that compares these to the git commits in the code base.
As a first step I'm hoping there is an established EA way of doing this - it seems pretty basic to me

I don't see anything about GIT or code in the initial post. Did you mix this up with another post?

Geert

[yonatan.lehman]

  oops. Yup thats my other post.
Our problem is that we have 100s of files which we have to document and each of us is taking care  of some of the files. If I create a diagram which references a component someone else is handling I need to create a stub I can use and when he eventually gets to that component he has to know to use my stub as opposed to creating a duplicate. Alternatively I would like a way to switch allmy references to the stubs to the real elements once they are created. The elements we currently use are components and activities.
Hopec that is clearer

[Eve]

The easiest solution is probably using a shared repository with locks instead of trying to share things with version control.

EA will prevent you overlapping work. Instead of having references to a stub you use references to the real thing the other person is working on. EA won't allow you to change it if it's locked, but you can still create relationships to it use it on your diagrams etc.