Hi Bogdan, I announced it here: http://www.argouml-users.net/forum/
Thomas -------- Original-Nachricht -------- > Datum: Fri, 23 May 2008 00:44:43 +0200 > Von: Bogdan Szanto <[EMAIL PROTECTED]> > An: [email protected] > Betreff: [argouml-users] Re: Usability issues of diagrams Survey > Hello all, > Below (and attached) you can find the temporary results from the > usability issues survey. There are 14 responses. The survey is still > opened for another week, until Friday 30th of May. > Please participate in the survey if you have not done so yet. It takes > less than 5 minutes. Visit > http://freeonlinesurveys.com/rendersurvey.asp?sid=4rstjdj52d222e7436241 > > Regards, > > -- > Bogdan SZANTO > ----------------------------------------------- > Impossible is nothing ~ Nothing is impossible ! > ----------------------------------------------- > > > ------------------------------------------------------------------------ > > 1) > > Are you a... ? > > *Percentage* *Responses* > user of ArgoUML > 44.4 > > 8 > developer of ArgoUML > 50.0 > > 9 > Other > 5.6 > > 1 > > ------------------------------------------------------------------------ > > 2) > > Have you participated in GSoC? (This year's paticipation also counts) > > > *Percentage* > > *Responses* > Yes, as a student. > 23.1 > > 3 > Yes, as a mentor. > 38.5 > > 5 > Yes, both student and mentor. > 0.0 > > 0 > No. > 38.5 > > 5 > Not applicable (haven't heard about GSoC). > 0.0 > > 0 > *Total responses:* > *13* > > ------------------------------------------------------------------------ > > 3) > > My GSoC project this year is to tackle some of the usability issues of > ArgoUML. Please list the below wishlist in the order of your preference. > * NA/IDU - you don't understand the description and therefore prefer not > to give a value for it (PLEASE DON'T SELECT ANYTHING) > * 1 - useless and distracting - if implemented, please make it optional > and by default disabled; > * 2 - I don't think I will use it, but, maybe I will try it; > * 3 - might be useful; > * 4 - useful and improves the usability; > * 5 - very useful and it would be a killer feature from a usability > point of view. > > * > 1 > * * > 2 > * * > 3 > * * > 4 > * * > 5 > * * > Responses > * * > Average Score > * > A. A quick "Build new class wizard" allowing to create a class from > scratch and to avoid the same repetitive tasks every time a class is > created: class name, attributes (visibility, type) and operations > (visibility, returned/received parameters) > 0 (0.00%) > > 2 (14.29%) > > *6 (42.86%)* > > 3 (21.43%) > > 3 (21.43%) > > 14 > > 3.50 / 5 (70.00%) > B. Drag an attribute from a class: to the panel in order to create a new > class and a new association; or onto another class to copy/move it. > 2 (14.29%) > > 1 (7.14%) > > *6 (42.86%)* > > 3 (21.43%) > > 2 (14.29%) > > 14 > > 3.14 / 5 (62.80%) > C. Drag & drop reorder of attributes and operations. > 0 (0.00%) > > 0 (0.00%) > > 2 (14.29%) > > *6 (42.86%)* > > *6 (42.86%)* > > 14 > > 4.29 / 5 (85.80%) > D. Integration of classes between diagrams: a class created on a Class > diagram should easily be integrated in other diagrams (as an actor or as > a classifier role for example) and operations from the class should be > available for integration on these diagrams. > 0 (0.00%) > > 0 (0.00%) > > 3 (23.08%) > > *6 (46.15%)* > > 4 (30.77%) > > 13 > > 4.08 / 5 (81.60%) > E. Laser mode: instead of drawing an association all the way from class > X to class Y the user can just start to drag from class X towards class > Y. The edge being drawn will shoot ahead of the user?s mouse position > and attach to the first class in line when the user releases. > 1 (7.14%) > > *5 (35.71%)* > > 4 (28.57%) > > 3 (21.43%) > > 1 (7.14%) > > 14 > > 2.86 / 5 (57.20%) > F. Bird's eye view -- a new panel showing a non editable, reduced size > image of the current diagram. > 3 (21.43%) > > 1 (7.14%) > > 4 (28.57%) > > *5 (35.71%)* > > 1 (7.14%) > > 14 > > 3.00 / 5 (60.00%) > G. Class modification on the panel: possibility to modify visibility of > attribute/methods by clicking an icon in front of the name, or the > current +, -, ~, # signs; possibility to modify type of attribute or of > the received/return type of an operation by using a drop down menu or > the keyboard. > 1 (7.69%) > > *4 (30.77%)* > > 2 (15.38%) > > 3 (23.08%) > > 3 (23.08%) > > 13 > > 3.23 / 5 (64.60%) > H. Rotate through aggregation types by double clicking on association end. > > 3 (21.43%) > > 3 (21.43%) > > *5 (35.71%)* > > 3 (21.43%) > > 0 (0.00%) > > 14 > > 2.57 / 5 (51.40%) > *3.33 / 5 (66.56%)* > > ------------------------------------------------------------------------ > > 4) > > Have you got any other suggestion for features, related to usability > issues, you would like to see implemented in ArgoUML or any other > comment to the above features (Please use letters A,B,C... to identify > features above)? > > - *Drag-move cardinalities on the diagram.* > - *From the Refactoring book, I think the following Refactorings could > be useful: Collapse Hierarchy, Extract Hierarchy, Extract Class, Extract > Interface, Extract Superclass, Pull Up Field, Pull Up Method, Push Down > Field, Push Down Method, Rename Method* > - *mof-editor* > - *In case of problems (e.g. malformed xmi file) user centric error > messages. Instead of Java exceptions with line number of source code, a > message with the xml element or line number of xmi file, wich cause the > problem.* > - *Undo* > - *e) The user will need some way to switch between current mode and > lazer mode maybe by holding down a hotkey in the process and/or a toggle > button in the diagram toolbar. They will still need the current mode if > they want to drop multiple points for an edge. * > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > 1) > > Are you a... ? > > *Percentage* *Responses* > user of ArgoUML > 44.4 > > 8 > developer of ArgoUML > 50.0 > > 9 > Other > 5.6 > > 1 > > ------------------------------------------------------------------------ > > 2) > > Have you participated in GSoC? (This year's paticipation also counts) > > > *Percentage* > > *Responses* > Yes, as a student. > 23.1 > > 3 > Yes, as a mentor. > 38.5 > > 5 > Yes, both student and mentor. > 0.0 > > 0 > No. > 38.5 > > 5 > Not applicable (haven't heard about GSoC). > 0.0 > > 0 > *Total responses:* > *13* > > ------------------------------------------------------------------------ > > 3) > > My GSoC project this year is to tackle some of the usability issues of > ArgoUML. Please list the below wishlist in the order of your preference. > * NA/IDU - you don't understand the description and therefore prefer not > to give a value for it (PLEASE DON'T SELECT ANYTHING) > * 1 - useless and distracting - if implemented, please make it optional > and by default disabled; > * 2 - I don't think I will use it, but, maybe I will try it; > * 3 - might be useful; > * 4 - useful and improves the usability; > * 5 - very useful and it would be a killer feature from a usability > point of view. > > * > 1 > * * > 2 > * * > 3 > * * > 4 > * * > 5 > * * > Responses > * * > Average Score > * > A. A quick "Build new class wizard" allowing to create a class from > scratch and to avoid the same repetitive tasks every time a class is > created: class name, attributes (visibility, type) and operations > (visibility, returned/received parameters) > 0 (0.00%) > > 2 (14.29%) > > *6 (42.86%)* > > 3 (21.43%) > > 3 (21.43%) > > 14 > > 3.50 / 5 (70.00%) > B. Drag an attribute from a class: to the panel in order to create a new > class and a new association; or onto another class to copy/move it. > 2 (14.29%) > > 1 (7.14%) > > *6 (42.86%)* > > 3 (21.43%) > > 2 (14.29%) > > 14 > > 3.14 / 5 (62.80%) > C. Drag & drop reorder of attributes and operations. > 0 (0.00%) > > 0 (0.00%) > > 2 (14.29%) > > *6 (42.86%)* > > *6 (42.86%)* > > 14 > > 4.29 / 5 (85.80%) > D. Integration of classes between diagrams: a class created on a Class > diagram should easily be integrated in other diagrams (as an actor or as > a classifier role for example) and operations from the class should be > available for integration on these diagrams. > 0 (0.00%) > > 0 (0.00%) > > 3 (23.08%) > > *6 (46.15%)* > > 4 (30.77%) > > 13 > > 4.08 / 5 (81.60%) > E. Laser mode: instead of drawing an association all the way from class > X to class Y the user can just start to drag from class X towards class > Y. The edge being drawn will shoot ahead of the user?s mouse position > and attach to the first class in line when the user releases. > 1 (7.14%) > > *5 (35.71%)* > > 4 (28.57%) > > 3 (21.43%) > > 1 (7.14%) > > 14 > > 2.86 / 5 (57.20%) > F. Bird's eye view -- a new panel showing a non editable, reduced size > image of the current diagram. > 3 (21.43%) > > 1 (7.14%) > > 4 (28.57%) > > *5 (35.71%)* > > 1 (7.14%) > > 14 > > 3.00 / 5 (60.00%) > G. Class modification on the panel: possibility to modify visibility of > attribute/methods by clicking an icon in front of the name, or the > current +, -, ~, # signs; possibility to modify type of attribute or of > the received/return type of an operation by using a drop down menu or > the keyboard. > 1 (7.69%) > > *4 (30.77%)* > > 2 (15.38%) > > 3 (23.08%) > > 3 (23.08%) > > 13 > > 3.23 / 5 (64.60%) > H. Rotate through aggregation types by double clicking on association end. > > 3 (21.43%) > > 3 (21.43%) > > *5 (35.71%)* > > 3 (21.43%) > > 0 (0.00%) > > 14 > > 2.57 / 5 (51.40%) > *3.33 / 5 (66.56%)* > > ------------------------------------------------------------------------ > > 4) > > Have you got any other suggestion for features, related to usability > issues, you would like to see implemented in ArgoUML or any other > comment to the above features (Please use letters A,B,C... to identify > features above)? > > - *Drag-move cardinalities on the diagram.* > - *From the Refactoring book, I think the following Refactorings could > be useful: Collapse Hierarchy, Extract Hierarchy, Extract Class, Extract > Interface, Extract Superclass, Pull Up Field, Pull Up Method, Push Down > Field, Push Down Method, Rename Method* > - *mof-editor* > - *In case of problems (e.g. malformed xmi file) user centric error > messages. Instead of Java exceptions with line number of source code, a > message with the xml element or line number of xmi file, wich cause the > problem.* > - *Undo* > - *e) The user will need some way to switch between current mode and > lazer mode maybe by holding down a hotkey in the process and/or a toggle > button in the diagram toolbar. They will still need the current mode if > they want to drop multiple points for an edge. * > -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
