Messages

1

Suggestions and Requests / Re: BUG: Importing of packages from XMI files brok

« on: October 11, 2006, 08:50:51 pm »

It has been confirmed to be a bug and Sparx will have it fixed in the future releases.

I agree with Gary that this bug is a show stopper and hope that this will be fixed quickly.

I thank Sparx for prompt action.

2

Suggestions and Requests / Re: BUG: Importing of packages from XMI files brok

« on: October 10, 2006, 11:30:20 pm »

I do not agree.

At the end of the import process, a message displayed is "Import complete!" on "Import Package from XMI dialog box".

This is in spite of throwing away a part of the information in the import process without letting the user know.

3

Suggestions and Requests / BUG: Importing of packages from XMI files broken

« on: October 10, 2006, 07:14:44 pm »

Two packages A and B were created and exported to XMI files where package A had dependency on package B.
The same XMI files were imported in a new project to reconstruct the original project. XMI file for package A was imported first and then XMI file for package B. The parts of the diagrams for package A dependent on package B were missing.

But if the XMI file for package B was imported first and then XMI file for package A, the reconstruction was OK.

The problem gets worse when both packages have circular dependencies. In this case the project cannot be reconstructed from the XMI files at all even though all required objects were imported albeit in different order.

The order of import should not matter as long as all required referenced objects are available.

This is a bug.  

4

Suggestions and Requests / Option to import XMI using object names

« on: October 26, 2006, 01:25:43 am »

When a package is imported from XMI, it uses the GUIDs already in XML file. There is an option to strip GUIDs, which creates object new GUIDs. There is no other option.

I propose that another option should be provided where object names can be used while importing (overriding GUIDs). That means, if an object with the same name already exists in the model, new object will not be created and use the existing object in the model. All references will be directed to existing object in the model.

It will require another checkbox in the "Import Package from XMI" dialog ( say "Use Object Names") which will allow user to override GUIDs by existing name.

This became apparent when we had an old model and a new model was created from scratch by reverse engineering existing code. Now we needed to import sequence diagrams from the old model into new model. We were not successful as the objects in the sequence diagram could not locate the required objects in our new model because of different GUIDs, even though names were identical. With the proposed functionality, this will be possible.

When matching object names, a fully qualified path name of the object should be tried first, then a partial path name, then just the object name (if a unique name exists). Even after that if there is ambiguity, user may be prompted to select one out of many.

This probably means that an option will need to be provided on "Export Package to XMI" dialog to enable exporting of fully qualified names of objects as well as GUIDs.

Suggestions are welcome.

Voting starts now ....

5

Suggestions and Requests / Diagram Note linking

« on: October 10, 2006, 02:48:17 am »

A sequence diagram A is dropped into another sequence diagram B.   This creates an Interaction Occurrence. A note is linked to the Interaction Occurrence (created by dropping sequence diagram A).

Now the note can be linked to the Interaction Occurrence note but there is no facility where the note can be linked to the Diagram Note of Sequence Diagram A.

This will be helpful as most of the time the note on the sequence diagram can be used by default. If required the it can be overridden by Interaction Occurrence note.