Messages

1

General Board / Re: EA vs Altova UModel + other CASE tools evaluat

« on: June 20, 2007, 04:20:37 am »

Feature mandatory: Support to version control...
Altova UModel ignore this feature...  

2

General Board / BUG: Relationship between package elements and XMI

« on: March 06, 2007, 10:13:29 am »

Hi folks,

There's a critical issue since build version 804 (I’m not sure if previous builds maybe affected too).

Our environment is based in version control (SCC) and individuals EAP files.

The bug: Packages in check-in (locked) have been changed due the load (get latest or check-out) of other packages that, in some moment, have relationship between elements.

This bug is not critical. It's catastrophic!
See steps to reproduction below.

1 - Create a new model EAP.

2 - Select Use Case model.

3 - Create package 'A' in use case model view.

4 - Create package 'B' in use case model view.

5 - In package A, create a use case diagram.

6 - Create one use case in this diagram with the name 'Use Case1A'.

7 - Repeat the steps 5 and 6 to package B using the name 'Use Case1B' to the use case.

8 - Drag and drop a simple link of 'Use Case1A' to diagram in package B.

9 - Create a extends link from 'Use Case1B' to 'Use Case1A'.

10 - Export packages A and B to XMI files A1.xmi and B1.xmi respectively.

11 - In diagram from package B, delete from model the link between use cases and the simple link of 'Use Case1A'. Only the 'Use Case1B' will continue in diagram. Save changes. (In this step, we expect that no changes was applied in the package A)

12 - Export packages A and B to XMI files A2.xmi and B2.xmi respectively.

13 - Import package A from A1.xml file overwriting the actual package A.

14 - Deliberately, package B was changed with the last import. Now, imagine these steps considering the use of version control feature. This is a hell.

15 - To finish, take a look in the xml files exported with a diff tool. In any moment the package A was changed intentionally.

I hope that Sparx fix this issue quickly.

Regards,
Edvan

3

General Board / Re: XMI Round Trip - Data Loss?  Your help ne

« on: January 24, 2007, 09:18:02 am »

The issue wasn't corrected in new build 803  :-/  .....

4

General Board / Re: XMI Round Trip - Data Loss?  Your help ne

« on: January 18, 2007, 05:35:49 am »

Hi Folks,

For me, the following bug is the most critical in EA. This is a show stopper for my company because we work on a distributed model development. Similar topic: http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=suggestions;action=display;num=1160532884

We already have been reported this to Sparx.

Steps to reproduce:

1 - Create 2 packages A and B;
2 - Create 2 element, one (X) into package A and other (Y) into package B;
3 - Create a new diagram into package B;
4 - Create a simple link of element X from package A into diagram on package B.
5 - Create a simple link of element Y from package B into diagram on package B;
6 - Create a link, a dependency for example, from element Y to element X;
7 - Save diagram;
8 - Export packages A and B to xmi files;
9 - Delete both packages A and B from model;
10 - Import xmi file thats represents the package B;
11 - After open the diagram on package B, the link between elements Y and X and the element X is missing from diagram without any information about a dependency over package A that contains the element X. This is a serious bug because if you export the package B again to update the respective xmi file, the relationship will be lost definitively when both packages will be loaded in the model.

Best regards,
Edvan

5

General Board / Re: XMI Import Data Corruption/Loss in EA 6.5 (802

« on: January 24, 2007, 09:11:08 am »

Please,

The issue 4 refers to this topic: http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=display;num=1163383934 ??

This is a critical issue. I hope that will be fixed in next build...  :-/

6

General Board / Re: EA and TeamWork

« on: January 18, 2007, 08:20:21 am »

I use the EAP files since most of the time I work as soldier of fortune, meaning I do not have to share the model. When doing teamwork, it's definitely better to work with a DB.

Work with a DB in a corporate large model is limited by simple security implemented in EA. Unfortunately...