The choice of design tool (UML)

A few months ago I was assigned to choose a tool for designing and documenting systems. In the company where I work, all this was done in Word and other office programs, and the products that the company produces became more and more complex, more and more people participated in the development, and so on. Therefore, it became necessary to use some more suitable tool for the work of analysts, designers and developers. I will share the findings.

After a brief acquaintance with such tools, 5 were highlighted, which were evaluated in more detail. When evaluating, my colleague and I identified about 30 criteria for objectivity of the assessment. We have grouped these criteria as follows:
- System design - does the tool provide enough functionality for documentation of requirements, us-cases, OO design and other UML diagrams. Does it have the functionality to create dependencies between objects of different types, the ability to track changes. This is a mandatory criterion for the tool.
- Export - the tool should support convenient export of artifacts produced in it. Different export formats should be available - at least html and doc. Document templates should be easily modified. This is also a mandatory criterion.
- Convenience of use. The tool should be convenient, intuitive, with a simple interface for frequently used functions.
- Minimize routine . It would be nice if the tool did some things on its own - for example, it generated test cases, object design from a database, maybe pieces of code.

So, 5 tools and their evaluation.
1. Case Complete - a tool for recording requirements, creating us-cases and connections between them. Convenient interface, export, but one serious drawback - this thing doesn’t go further than us-cases. In general, it is not clear how she got on our list. 2 of 5.
2. Artiso Visual Case - the first thing that catches your eye when using this tool is a wildly awkward user interface. To create an elementary class, it took me 5 minutes. In addition, the tool does not have the ability to link objects (like a us-case <-> class), etc. 1 of 5.
3. Magic Draw - the tool has a very strong side for UML, but this makes it a bit uncomfortable. Also, there is no connection between different objects (like a class and activity, etc.). 3 out of 5.
4. Sparx Enterprise Architect - meets almost all the criteria put forward, just that some frequently used functions are hidden somewhere. Probably, if you get used to - well. Also, I didn’t find in it how to connect requirements with design objects. Maybe she was looking bad. 4 out of 5.
5. Sybase PowerDesigner - the first impression after opening the program is a completely different level. All functions are exactly where you expect to find them, and this tool has satisfied all 30 criteria from the groups described. In addition, PowerDesigner has a bunch of very useful features that are not included in the list of criteria - such as change assessment (impact), model validation, Repository, and more. 5 out of 5.

Here I posted a complete comparison, if anyone is interested.
')
Although PowerDesigner is several times more expensive than others, we chose it. Today, I use it for 2 months - if anyone is interested, I can write about it - not everything in it is perfect (but close!).

Probably just ask why the list did not include Rational Rose. I do not like him! He's not handsome. And yet, I could not find where to download it legally. But basically he is good. But PowerDesigner is better.