| Re: [mdt-papyrus.dev] User Experience with papyrus |
Hi
Thank you. Constructive feedback is always helpful. A repro is
even better, but obviously you cannot recall everything you did in
the preceding hours.
Could you clarify whether your observations apply exclusively to
Sequence Diagrams or whether Use Cases or Class Diagrams also
froze? I'm not really a Papyrus user, but my subjective
observation is that Eclipse goes off into la-la land far more
often than it used to, but only enough to irritate rather than
seriously disrupt as you have found. When you describe a freeze do
you mean have a coffee-break freeze, a restart-Eclipse freeze, or
a restart-OS freeze?
It would be helpful if you can raise a Bugzilla with
- the configuration.log from Help->About
Eclipse->Installation Details->Configuration
- the ZIP that you sent to your team
- specific observations about inadequacies demonstrated by the ZIP
Regards
Ed Willink
Dear Sir/Madam,My name is Ina and I am writing to you to share my experience using papyrus.
I am a student at Kings College London and for a coursework project we were required to use papyrus to create use case diagrams, class diagrams, state machines and sequence diagram. My course has 3-4 hundred students and each one of us had constantly issues with the software receiving errors saying "Your file is corrupted" and diagrams being deleted for no apparent reason, the software freezing and modifying the diagrams on its own. I do not feel like Papyrus is a proper tool for project management as it constantly ruins projects and does not in any way assist the work.
I have had to re-do one sequence diagram 5 times because papyrus froze and didn't allow me to create, change or delete anything, and if it did allow it, it wouldn't display it on the diagram. When I actually managed to created the aforementioned diagram on the 5th attempt, 9 hours later, AND MIND YOU IT WASN'T A COMPLEX OR LONG ONE, I zipped the file and send it to my team.Now imagine my surprise when I looked at the report, containing screenshots of the diagram, and saw that the ONE diagram which had been tormenting me for 9 HOURS STRAIGHT HAD CHANGED WITHOUT ME DOING ANYTHING TO IT. This wouldn't have been a problem had my original file not changed as well after the zipping, nor if papyrus had allowed us to change it back to how it was originally. The software wouldn't allow us to select anything inside the fragments, move or rename elements. And it was not only so for one device.One of my team mates had three of her diagrams deleted because papyrus decided out of no where that the files are corrupted. And what exactly does it mean corrupted!?
This project is worth 20% of the final mark for the module for 6 people in my team and another 60 teams of 5 to 6 people.Finishing this project has been a torment because of every issue with Papyrus and trying over and over again to create something just to watch your effort go down the drain is emotionally and physically tiring. I am not in the slightest satisfied with your software and if was given the choiceI would have immediately transferred to "Visual Paradigm" which is a tool that my team and I used to create our sequence diagrams and didn't have one single issue with. But the coursework requires us to use Papyrus so transferring our not at all complex or long 9 diagrams manually to papyrus has taken us longer than actually creating them and has exhausted us twice as much.I really hope you take this rather harsh feedback and improve the software because I do suppose that we will be using it again next year and I do not want to write the same email again.Thank you for reading my feedback and for your time and patience to finish this email.Kind regards,Ina on behalf of all 3-4 hundred students in Kings College London.
_______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev