I am writing this just so as to document some of the problems I have faced with Star UML. I do not know if it is just me but I think it should be out here.
I have less than a month on my part2/3 deadline and right now I am at Sequence Diagrams. When I started with Star UML, the first mistake I did was that I worked on the newer Star UML 2 Beta version (link here). This was a big mistake. 2 days ago, while working on my models, the file got corrupted with all my sequence diagram gone. It just vanished. I subscribed to the google group of the software and the developer got in touch with me. He asked me for the corrupted file and I am thankful to him that in 4 hours, he restored the file.
Then I installed Star UML (old version) and since there is no way to migrate the models from the newer version to the older one, I spent one day doing that manually. I had to redo all my stuff. Last night, when I had finished my first sequence diagram I went back to the class diagram and tried to add a new class connecting to an interface for the "required interface notation" - it is that socket notation. There isn't a way to do this via the drag-and-drop and the only way I think it can be done is by using the keyboard shortcut (double click on the class and then type "-(InterfaceName"). Then I got an address violation error. There is no way I can go past this now. I googled a little and found this:
Alright, I just got a note from the developer saying that they are not maintaining the old Star UML anymore and the issue I have mentioned would require code changes, testing etc. I think we all know that - however he added that, this issue (Address violation) comes because of using the keyboard ways of creating elements. He told me to use "Iconic" as the stereotype for an interface that will have the lollipop notation and it worked (so the keyboard way of "-(interfacename" can be avoided). I am just putting it here so that anyone stuck in a similar situation has a way out.
Sorry to hear that. I used old version of Star UML about 6 years ago when I did my SCEA 5 assignment (yes, Sun Microsystems was alive that time), and Star UML worked perfectly for me. Just well balanced interface/features tool.
Exam 1Z0-817: Upgrade OCP Java 6, 7 and 8 to Java SE 11 Developer Study Guide and Quiz
I do not want to give an impression that Star UML can't be used here. I am still using it and I know many others have already used it.
The address violation issue in the old version is rare as it is evident that not many people have faced it. Maybe mine was a one-off case, I do not know. But however, I certainly want to tell people to not use the Star UML Beta at this time if they have a deadline as it is not stable yet (Though I am very impressed by talking to their developer and that they are constantly working on it. Going by their release patterns, soon, it will be stable enough, I am sure.)