Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - orcus

Pages: [1]
1
Suggestions and Requests / Re: EA in Team Environment
« on: July 29, 2003, 09:01:06 am »
Mikkel-

Thanks again for the quick response.

Interestingly, as User B, I did try opening a diagram (and tried opening package) in build 613 and I am not sure if it updated the diagram.

I just got the new build 618 and will try with that.

regards,
Orcus

2
Suggestions and Requests / Re: EA in Team Environment
« on: July 29, 2003, 08:02:28 am »
Mikkel-

Thanks for the response.

In the two cases you mentioned, I was looking for a solution to the first one where User B already has the model file open.

I am not sure if the "Reload current Model" is just to update the project browser, coz it does have the added benefit of refreshing any open models with the most recent changes including any changes to elements.

In anyway, I think it would be a great new feature - if everytime I expand a package, EA could pop up a box notifying me if the package elements have been altered. This way I can force a reload. (...this however will not fix the issue if I am exploring a package that is being modified at that particular instant by another user.)

I hope Geoffrey is reading this thread....  :)


Orcus



3
Suggestions and Requests / EA in Team Environment
« on: July 28, 2003, 02:56:06 pm »
I have already posted this in the "General forum" so my apologies for the crosspost but I think this message is more appropriate here.

In a large team environment, I am wondering how teams using EA are handling concurrent changes.  

I am using the security, locking and package control in EA with my team (about 10 members to grow to a 25 member team) with most of them using EA in various phases of the project.

My questions is - Is there any way to improve "Reload current Model"?  

Here is a typical scenario:  
If user A locked an existing package and  changed an element (e.g. added a new method to the Employee class), and user B is exploring the same package (in a readonly view) and wants to print the diagram with the employee class out, he will probably print the older version unless he reloads the model. I think this method is very error-prone.

Can a new feature be  added to prompt the user with a message if he is trying to enter a package that has been modified by another user?  

I'd like to know how other EA teams are handling this.  

Thanks in advance for your time...


regards,
orcus


4
General Board / EA in Team environment
« on: July 28, 2003, 01:02:40 pm »
Hi-

In a large team environment, I am wondering how teams using EA are handling concurrent changes.

I am using the security, locking and package control in EA with my team (about 10 members to grow to a 25 member team) with most of them using EA in various phases of the project.

My questions is - Is there any way to improve "Reload current Model"?

Here is a typical scenario:
If user A locked an existing package and  changed an element (e.g. added a new method to the Employee class), and user B is exploring the same package (in a readonly view) and wants to print the diagram with the employee class out, he will probably print the older version unless he reloads the model. I think this method is very error-prone.

Can a new feature be  added to prompt the user with a message if he is trying to enter a package that has been modified by another user?

I'd like to know how other EA teams are handling this.

Thanks in advance for your time...


regards,
orcus

Pages: [1]