Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: junior on April 16, 2007, 05:22:54 am
-
Hi,
We are using EA with RaQuest for specifying system and software requirements. We are working on different packages, ex, Client, Server,... that version controlled. We didn't had any problem until now when we needed to correct a relation between two requirements. We decide that the relation was the other way around. So, we went to the matrix view and changed the relation direction.
The problem was that only the person that did the change saw the relation in the correct way. All the others anded up with a cyclic relation.
We tried deleting the existing relation and relate it to a different requirement, but what we only managed for the other users when they check-out, is a relation with the old requirement and the new one.
Bottom line there seems to be a problem when deleting or changing a requirement when the project is under version control. Only additions are sent to CVS the deletions are only local.
This is a serious problem, is there any work around.
-
Are the requirements in separate controlled packages?
If so, then you'll need make sure both packages are committed.
Arte you using source control direct from EA or externally via XMI export?
Paolo
-
Yes, the requirements are in separate controlled packages. But even in side the same package this happens.
For instance you have a packaged checked out that has requirements A,B and C. You make a relation between A and B and then you commit. Everybody gets this new relation if they check-out this package. Later on you decide to delete the relation between A and B and do a relation between A and C and you commit. When others check-out they have the relation A to B and A to C.
-
I've found that this problem occurs only when using the requirement matrix for inverting the relantionship. If you invert the relation in the matrix the previous one is not erased and the new one is added creating a ciclyc relation.
If after you right click the requirement and do "Delete Relationship..." and you select one of the repeated relations they both are deleted!
I think this is a bug.
-
Yes, it looks that way.
Since this is (primarily) a User Support board,remember to formally report it to the Sparx support email address:
[email protected], or use the support link at the top of this page.
You can reference the post in your report and then Sparx can view any additional commentary.
It would also be good if you could report any Sparx response into the Topic.
Paolo
-
Just submitted the bug report.
-
Sorry to trouble you.
About bugs, requests and questions of RaQuest, please
send email to [email protected] .
If possible, please resend your report to the email address.
--
t-kouno
-
I've found that this only happens to users that already have the packages configured locally. If a new user arrives and configures everything from scratch what is imported from CVS is correct.
I'm not so sure that this is a bug anymore. This is probably related with the fact that when you update your packages you must always use the option "Always Import" instead of "Import Changes Only" that appears when you do a checkout on some package.
This action never erases the previous relations from the local EAP and adds the new ones created that are on CVS, making the local Project have more relations than there are.
-
Hi Junior,
If you are saying that if you select the Import Changes Only you see the bug, but if you use Always Import it's OK, then it IS a bug...
Report this as a bug to Sparx. You can use the [size=13]Report a Bug[/size] (http://www.sparxsystems.com.au/support/bug_report.html) link via the Support link at the top of the page.
Place a reference back to this topic in the bug report. That way, the Sparxians can see any ongoing discussion.
If you get a response, please add it to the topic.
Paolo