The message line wouldn't auto-complete the message name, and the only way to add a new operation from the sequence diagram was to open a class diagram! This is the essence of UML modeling, in my opinion without a shared data model, all you've got is just a structured drawing program with some useful primitives. Although any classes you define are shown in the sidebar, there's no way to reuse those same classes in the sequence diagram. (Repeat if you still haven't scrolled all the way to your destination.) However, you can set the end down, use the scrollbars, and move the end where you need to go. When stretching a sequence line from one end to the other, the view doesn't automatically scroll. It can take a while to expand the document to the dimensions you need. Then you have to use the scrollbars, move it over the edge, and set it down again. I didn't have to play around with page sizes, but the document only resizes when you place something that overlaps the edges. As long as I can get my thoughts across, I'm good.ĭynamic Document Size: Poor. I'm an old geezer (in software reference frame), so there's probably a newer UML specification that I haven't upgraded to. The asynchronous line is represented a little differently than I'm accustomed to, but that's a minor detail. There's no support for orthogonality, so it gets crooked. You have to bend the reflexive line around on your own. Supports Synchronous, Asynchronous, and Reflexive Messages: Poor. Of course, with the poor selection support, you're going to need this feature. Infinite Undo: Perfect! It even separates the undo actions by diagram. When I suddenly realize I've left out the initialization call, I can't move everything down and insert the new call. While this works with classes and their associations, it doesn't work on calls. That's still the ultimate in configurability, but it's not a big help to usability. It doesn't give you a dialog to enter attributes, or auto-complete types that are already in your data model. Unfortunately, you have to do everything by hand. You can also use non-UML labels for your message lines, so that's REALLY configurable. However, it supports UML syntax for everything. ![]() It also wouldn't let me move the labels for the message lines on my sequence diagrams, which means they're going to get crowded or overlap other elements in inconvenient ways. Gaphor didn't allow me to change colors - perhaps that's hidden somewhere, but after the aggregation debacle I wasn't willing to look for too long. but why should I have to add an aggregation diamond?Ĭonfigurable Display: Fair. On its website, Gaphor has a tutorial for adding your own elements. That's right, you can say "is-a" but not "has-a". Rather, it's because there's no aggregation indicator for class diagrams. Mix your classes with your lifelines, go right ahead!īut that's not why I rated Gaphor "Poor" for diagram support. In fact, it makes no restriction about what kind of elements you put on a diagram. Technically, Gaphor "supports" any diagram. Supports Class and Sequence Diagrams: Poor. And the home page looks good!īut Gaphor failed miserably for my purposes. I thought Gaphor would be terrific, since it's a Python/GTK project, and therefore native to my system (Ubuntu/Gnome).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |