Feature Request
532 results found
-
Rust code generation and reverse engineering
StarUML lacks any extension for the up-and-coming Rust programming language. There are several large scale corporations (many StarUML costumers) that are migrating Java and C++ to Rust.
6 votes -
Activity Diagram Enhancements
Activity Diagram Ideas for better alignment with the UML Specification:
- Swimlanes should have the ability to be typed by either a Classifier or an Instance
- Once the Swimlane has been typed by a Classifier, I should be able to drag an Operation defined for that Classifier onto the Swimlane directly. Pins should be automatically adorned on that Classifier and represent the parameters of the Operation. If a parameter is added to the Operation, the diagram should automatically be updated to show this.
6 votes -
Improve actors in Use Case Diagram
It would be nice to add eyes and a smile to actors, because smiles spread smiles.
6 votes -
Correction of agregation and composition
Currently, when drawing an aggregation relation from one class (expected to contain the aggregation) to another class (which is supposed to be referenced), the aggregation diamond is placed at the wrong end. The standard says that it should be place at the class that contains the referenced element. In StarUML this would be the start of the aggregation line.
In the properties of the aggregation, one can change the end arrows and the type of relation ship. Doing this for all drawn aggregations makes no fun, so please change the default behavior of aggregation drawing to have the diamond at…6 votes -
Context Menu Issue
When you right click on the class to add property or operation the context menu disappear quickly... it should be popover.
5 votes -
Synchronize selection between explorer and model
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.5 votes -
Add polymorphic associations
Would be great if you could implement polymorphic associations for models.
Example here: http://guides.rubyonrails.org/association_basics.html#polymorphic-associations5 votes -
Intersecting lines always cause me an issue
I want to suggest two features; First feature is that when multiple classes inherit one class, the generalization lines should join in a single line:
http://service-architecture.static-barryandassociates.com/images/database/class-inheritance.jpgThe second feature is that when two lines intersect, there should be a distinction between them:
http://www.mindscriptact.com/blogFiles/away3d/Away3dObjectTreeV4_0_beta.pngI hope I was clear enough.
5 votes -
customize the toolbox
I'd like to be able to add items to the toolboxes that don't come there by default.. like a component to the use case diagram toolbox or something like that
5 votes -
Support for better layout algorithms using https://github.com/OpenKieler/klayjs
The layout algorithm for the diagrams do not layout the labels and are somewhat bad. Perhaps the use of this library would help the quality of the diagrams.
5 votes -
Allow hyphens for naming subystems and swimlane
In German we use hyphens for combining words coming from different languages, like "Bürger-Client" or "Compliance-Manager".
When entering names like that in the diagram area, the StarUML does not allow it. Workaround for this is writing the name directly in the element's properties area.5 votes -
More verbose error message
When drawing connections / relations StarUML sometimes just complains with a too simple error message, leaving the user unknown what the underlying problem really is and how it could be solved. E.g. draw "interface realization" just gives "Invalid connection" error popup but it does not explain why it is invalid !?!?
5 votes -
Default attribute, parameter and method return type
Create options in preference window to allow us to define the default type for new elements into a class, namely: attributes, method parameters and method return.
5 votes -
Maintaining containment relationship between components
Placing a component inside another component should create a durable containment relationship.
5 votes -
5 votes
-
Duplicated names should be forbidden
The application should not accept two different elements inside the same package with the same name. The concept of namespace discards that possibility. I regret to say that StarUML version 1 didn’t allow the user to do that. Sorry if this obvious suggestion was already made but I was not able to find it.
5 votes -
support of Cross functional flowcharts
Flowchart is a basic connectors for representing the call flow. However i see the existing flowchart template is missing the concept of swim lanes.
Cross functional flowcharts use swim lanes to provide an extra dimension by assigning each process step to a category. Most often the category is a stakeholder (person, role, or department).
5 votes -
Transparent background when copying diagram to the clipboard
Thank you very much for adding in V3 the capability to copy diagram as an image to the clipboard!
Would it be possible to set transparent background on the copied image (or not, selected eventually in the user preferences)?
Thanks!
5 votes -
Visual Studio extension
Would be great if there was an extension for visual studio
5 votes -
where is communication diagram(collaboration diagram)?
how to convert a sequence diagram into a communication diagram (collaboration diagram)?
5 votes
- Don't see your idea?