Category: Plugin Directory / UML / UML Tool for Eclipse
| | | |
Version: 3.2
Support Eclipse Version: 3.x
License: Free for non-commercial use
Development Status: Production/Stable
Company: Visual Paradigm
| |  | Home Page |  | Plugin Support |  | Discussion Forum |  |
|
SDE for Eclipse (SDE-EC) is a full-featured visual analysis, modeling extension for Eclipse. SDE-EC supports all UML diagrams and model elements which allow you to model any sophisticated systems. With the unique textual analysis and use case modelling facility, you can perform the requirement capturing and analysis tasks easily. Also, SDE-EC supports Java code generation, reverse engineer Java code to class diagram, and more.
Added on: 05-Feb-2004 | Updated: 06-Apr-2006
|
Last 10 Comments
| User: Anonymous | Rating: 1 | 2007-11-07 13:26:13 | | | No Class diagram diagram generation from code (version 4.1 Community ed).
Useless.
| | User: Anonymous | Rating: 1 | 2006-05-19 03:33:03 | | | | I'll rate this plugin for it's function fit for me and attract me.
| | User: Anonymous | Rating: 1 | 2005-10-13 13:59:06 | | | SDE for Eclipse has several critical errors in it. I dont know how the company approved such buggy program for release. It gave lot of out of memory errors, will not save UML model, best of all it will delete previously saved models and modify your code without your knowledge. With a bonus that the modified code wont even compile. If you have lot of time and want to trash your project, please try this product. Good for a laugh ;)
| | User: Anonymous | Rating: 1 | 2005-08-05 01:09:32 | | | Yet another ugly UML editor
| | User: Anonymous | Rating: 4 | 2004-12-28 00:27:14 | | | goods
| | User: Anonymous | Rating: 1 | 2004-09-08 10:18:01 | | | Worst eclipse plugin I have ever used. It hanged for 3times just after I started using it, killed eclipse process 3 times . I got freaked out and removed it.
I dont know what's wrong with it.
| | User: Anonymous | Rating: 1 | 2004-09-03 03:52:17 | | | Where is Linux version???
| | User: Anonymous | Rating: 9 | 2004-07-31 12:38:34 | | | It now supports Eclipse 3.0. It seems that it is improved a lot. In this new version, it supports teamwork features.
| | User: Anonymous | Rating: 1 | 2004-07-02 10:51:24 | | | It just doesn\'t work on Linux
| | User: Anonymous | Rating: 3 | 2004-04-29 23:17:49 | | | | Summary
This product is promising, but is \"not ready for prime time\" yet. (But with
some serious attention to bug fixing and usability improvements, this product
has the potential to be excellent.)
Details:
I spent between 4 to 6 hours evaluating the product and have come to the following
conclusions:
First, the pluses:
1. I was impressed by the quality of the documentation.
2. I was impressed by the integration into Eclipse.
3. I was impressed by the feature list presented on the product's web page.
Now the negatives:
1. A large portion of the functionality did not work.
2. The software hung (stopped responding) several times, causing me to have
to kill Eclipse in order to recover.
3. Many configuration settings did not function (for example hiding initialization
code).
4. Auto-arrange sort of worked but still required manual manipulation.
5. Code generation for a very simple class caused the Java virtual machine to
run out of memory.
6. Export functionality failed.
7. Defining new attributes was cumbersome (you have to right-click to create
each one). The product doesn't allow these to easily be added to the class'
properties table.
8. Creating class diagrams from an existing package created these \"nested\"
diagrams that included a non-standard view of the class hiearchy, by default,
and I had to search the docs to find out how to disable it. (E.g., com was a
package, mycompany was a package, mycode was a package, main was a package,
mypackage was a package -- when the classes we in the com.mycompany.mycode.main.mypackage
package).
9. Closing the editor view of a class diagram caused all of the existing code
in the package to be deleted!
10. Minor readjusting of the layout of a class diagram (I didn't change any
attributes or methods) caused the class' code to be modified for no apparent
reason.
11. There was no way to specify the desired formatting of the generated
code, and the product's style is different from our company's coding standards.
12.
Configuration settings did not persist across different sessions. For example,
I unchecked the flag that causes the code and model to remain synchronized,
I saved the SDE project, closed Eclipse, re-opened Eclipse and the flag was
checked again.
13.... There's many more problems, but you get the idea ...
So, my impression is that this product is \"not ready for prime time\" yet.
I believe that this product does not have the required level of quality and
functionality to be a valuable tool for us at this time.
|
|
|
