Enable support for Requirements
It would be nice if StarUML could support modelling of Requirements and Test. I like the approach taken by Visual Paradigmen 11.2(http://www.visual-paradigm.com/features/uml-and-sysml-modeling/) by supporting "SysML requirement diagram". I tried to emulate it in StarUML 1 with an own model but it isn't quite practicable. If this feature would be voted, please take attention of text-wrapping for the elements and give a possibility to define own values (e.g. for risk). If it's not to much, the fields of the requirement-template should be definable by the user.
Jean-Paul Buu-Sao commented
Support for requirements will be much appreciated, in particular with support for traceability relationships with other artifacts of the model, for example: bidirectional traceability between (user-case, user-story, collaboration diagram, class, etc). Please also consider impact analysis scenarios, whereas one can assess the impact of change of a user-story on the rest of the model, or assess the impact of change of a class up to the user-syyories and use-cases that this class has transitive traceability relationships with.
Venca B commented
Also would be nice to have two way binding between requirements stored in spreadsheet (preferably odt but excel is also fine).
I personally use visual requirements in the use case diagrams to make a concrete link between the use cases and the requirements that support them. In EA it will generate a requirements coverage matrix to make sure that you haven't missed anything and also to get an understanding of how important a given requirement actually is...