It would be a very nice Feature to create a custom or edit the default Nameconvention, so that you could use your company naming convention and generate correct named code.

I really like the MonoDevelop implementationin : http://www11.pic-upload.de/04.12.14/e8s7xyv5cur.jpg

Add the interface connector for subsystems in the toolbar: the direct connector to interface ( --O ) and connector that is anchored to an interface ( --(O ). It would be nice to be easy to apply, such as associations in the class diagram.

When it doing reverse code from Java, all the imports are ignored. This results in replicated classes without package in root.

Would be great if you could implement polymorphic associations for models.
Example here: http://guides.rubyonrails.org/association_basics.html#polymorphic-associations

For me it is very important to hide elements. In my case I use a State Chart Diagram and there are many overlapping transitions. The description of these Elements will make it very confusing.
Also the auto-align ability is not that good. It squeezes the Diagram too much.

we see lot of javascript code on web and it is very difficult to understand it but it is easy to understand and visualize the code via uml diagrams.
This way we can save lot of amount of time.
Perticularly useful who came from C/C++ background to understand the javascript code in fast.
I would like to know why nobody thinks in this way?
Please do update me if any such tool or procedure already exists?
Even I am happy to contribute for the same, if required.

Thanks,
RajaA

If you're behind a proxy server it is not possible to load Extensions.
Other solution: Manually installable packages.

Currently, if one object is "in front" of other, smaller one, you are not able to select it.
My suggestion is to allow selection (hit-testing) "through" objects that are empty (that is, have no fill, only outline). That way, for example, I can select a message insede a "loop" fragment in a sequence diagram

With a HTML link per class that is exported with SVG one could navigate easily to a class within a doxygen HTML documentation.
This feature would be very easy to implement.

A state diagram in UML support the notion of nested states, or submachines. In such a case a substate may transition to its superstate and vice versa. The transition is then drawn from the border of the substate to the border of the superstate (and vice versa...). Currently all transitions are drawn center to center, also between nested states...

add support for color UML

There is a little bug in there. I created a do activity in a node. And in ther a new StateChart Diagram. I opened it, but I am not able to create anything in there. At this time it is useless but not that worse :)

As previous version of StarUML you can assign a pattern to a class... So if your project works on a specific pattern. just when you create a class, you assigned whic pattern will this class use.. like Singleton.

It ist possible to add user defined constraints to classes and to attributes. It would pay off if those constraint could be displayed in the same way as predefined constraints such as "isUnique", "isID" etc.

It would be even better, if displaying constraints could be enable and disabled: "Show Constraints" (like "Show Type") or "Supress Constraints" (like "Suppress Attributes").

Sequence diagram Lifeline : more icons to represent different actors
Message : could see only 10 character while editing the text
Note tool : text wraps according to the size of the text area
Rich Text formatting for part of the text with in note tool

If you select something in the model view, then it should be selected in the explorer.
If you select in explorer then it should be selected in the model view.

Use case to use case document mapping will help a lot to elaborate use case inside tool. Documentation textbox is not enough for that. If any attachment, like doc, pdf, etc., can be added with use case, it will be great. Otherwise documentation textbox can be rich textbox with expand option, where we can draw some table, format text, etc.