Author Topic: Compare Utility 7.50 build 848 (Read 5977 times)

Henrique Narciso · « **on:** September 05, 2009, 03:21:37 am »

I am having lots of errors in the compare utility.

Vasically all the internal requirements within elements are being presented as changed even thow nothing changed.

My simple experience:
I exported a baseline, into two diferent files a_v1. xml and a_2.xml. These come from a SQL server.
I loaded the first file into a fresh EAP project, and compared it to a_2.xml.
All the elements (internal requirements) are presented as "baseline only" and "Model only".

anyone with this problem?

Henrique Narciso · « **Reply #1 on:** September 08, 2009, 01:58:17 am »

I would like to add that it isn't something linked to the advanced properties.

A internal requirement is just not being well compared with it self.
the dates are the same, everything the same however the tool is saying otherwise.

Geert Bellekens · « **Reply #2 on:** September 08, 2009, 02:49:20 am »

Henrique,

If it say baseline-only/model only for each object that means EA doesn't see those elements as the same.
You have to know that EA uses the GUID stored in the XMI file to couple the model version with the XMI version of the element.
Now I guessing that you imported the first xmi file using the option "strip guids". That option makes EA strip off the guid's in the xmi and create new ones. Which would lead to these symptoms.

Geert

Henrique Narciso · « **Reply #3 on:** September 08, 2009, 07:58:24 am »

Hi Gert,
I thought of that also, so I tried exporting with the GUID's ... same result.
I used winmerge to see the diferences, none appeared.

So I took it a step further;

Imported the XMI into an EAP, Aplied a Baseline, did another baseline without changing anything.
Did the compare and the same result, allinternal use case requirements are presented as model only/baseline only.

Geert Bellekens · « **Reply #4 on:** September 08, 2009, 03:57:49 pm »

Wait, are you saying that ONLY the internal requirements show up as baseline/model only and the other elements show no changes?
In that case this is definitely a bug which you should report asap.

Geert

Paolo F Cantoni · « **Reply #5 on:** September 08, 2009, 04:24:41 pm »

Quote

Wait, are you saying that ONLY the internal requirements show up as baseline/model only and the other elements show no changes?
In that case this is definitely a bug which you should report asap.

Geert

Absolutely! WE have to be able to rely on the comparison function!

FWIW, about 2 years ago, we at Ripple Systems (sadly no longer with us) found a lot of problems with Sparx being able to provide consistent output at the XMI level for RTE.

A number of collections were NOT guaranteed to yield the same output for each emission - though the model was unchanged. (For example, there was no consistent, enforced, ordering - so each emission could generate a different outcome.) This made text comparisons - such as with Beyond Compare - pointless. We worked with Sparx to resolve these. Maybe this is a re-emergence of a similar problem; causing the comparison utility to think they are different...

HTH,
Paolo

«Midnight» · « **Reply #6 on:** September 08, 2009, 09:49:40 pm »

Or maybe it is some variation of the "this behavior is by design" issue.

But I have to look at that possibility as yet another aspect of consistency. And I also have to consider consistency when assessing such a response. IMO a flaw in design is just as much a bug as a flaw in implementation. There, consistency achieved!

Henrique Narciso · « **Reply #7 on:** September 09, 2009, 01:36:54 am »

I reported the bug, its being investigated.

Yes I mean only the internal requirements are presented as model/baseline only.

Henrique

Henrique Narciso · « **Reply #8 on:** September 21, 2009, 07:06:46 pm »

It's a bug

«Midnight» · « **Reply #9 on:** September 21, 2009, 08:23:24 pm »

Do you mean that Sparx has agreed that it is a bug? [Beyond the automated acknowledgment message that is.]

Henrique Narciso · « **Reply #10 on:** October 02, 2009, 08:31:33 pm »

yes.

Hi Henrique,

Thanks for the reply and attached image.

Our developers have confirmed that this behaviour is a bug, and it have been logged to be fixed.

If you have any other questions please let us know.

Best Regards,

Simon Cotching

Geert Bellekens · « **Reply #11 on:** October 02, 2009, 11:06:59 pm »

Henrique,

I have a similar issue.
I've just imported a model branch in an empty model, executed a compare, and to my big surprise I found a lot of "Model Only" elements.
I also have some association on the Baseline Only side, but that I can understand. The model branch was exported as a part of another model. The associations in question are association to elements that are outside of the model branch. (a modelling error from our side).

I'll report it as a bug as well.

Geert

Sparx Systems Forum

News: