|
Birth |
Graph Creation |
Case document andCodeBidirectional conversion between case documents and databases |
Support and collaboration |
System diagram/tree chart |
UML diagram |
ERTU |
Gantt diagram |
Any Flowchart |
Any other chart |
|
|
Rose (rational suite 2002) |
The purpose was to support UML modeling. At the beginning, database modeling was not supported, and the system code framework generation was well supported. However, the development and management of databases and database iteration are not very good. |
Not Supported |
Rose supports a full range of features, such as iteration and case-driven, with the best relevance. Its disadvantage is poor image quality and poor logic check and control, without distinction between name and code (the feature of powerdesigner), it is not suitable for Chinese people, it is not good to generate documents, it is not suitable for customization, and there is no dictionary of design objects for quick search. |
Amateur |
Not Supported |
Not Supported |
Not Supported |
Implemented by the Intermediate plug-in |
Rose has the latest and most complete UML support; the support of the RUP System |
Powerdesigner (powerdesigner 9.5) |
A database modeling tool developed for database modeling. It was not until version 7.0 that it began to support object-oriented development. Later, it introduced support for UML. It supports around 90% of the databases that can be seen, and the support for various diagrams used in UML modeling is lagging behind. However, it has been strengthened recently. I am not very familiar with the Chinese market, so there is always a problem with Chinese support. |
Poor Support |
Powerdesigner 9.5 is fully supported. The advantage is that the image quality is good, the generated documents are easy to customize, the logic check and control are good, and the dictionary with design objects can be quickly searched and located in the graph, the disadvantage is that the interconnection between them is a little more troublesome. It is not suitable for the use of UML and RUP, but it cannot be reflected by iteration and case-driven. It is better for skilled users to use it. |
Best |
Not Supported |
It can also be used. |
Yes, but there are not many predefined elements. |
Best, no plug-ins required |
The support for the latest and most complete UML is a little lagging behind; no support for the RUP System |
Visio (vs Visio 2002) |
It turns out to be just a painting tool. the software analysis design function was introduced only in visio2000 to all the functions of code generation, it can be said that it is currently the most graphical tool to express the use of a variety of commercial graphics (only a few of the UML support in software development) for iterative development of software development process is a little far-fetched |
Best |
The graphical quality of Visio is the best, but the cohesion and relevance are also the worst. The logic check and control can barely do a little bit. |
Amateur |
Visio can be used or used as a project. |
Best Visio |
This is best for Visio. |
Visio is implemented through VBA and macros. Visio does not feel like it is streaming. |
The support for the latest and most complete UML is a little lagging behind; no support for the RUP System |
the three products have their respective focuses, each has its own advantages and disadvantages. It mainly depends on your choice and your development mode and environment. if your team is familiar with business and English, but not familiar with RUP, we recommend that you use rose because it has complete theoretical support and is highly relevant; if your team has a poor understanding of the business and English language and the system analyst is able to understand the RUP, we recommend that you use powerdesigner. if you are not prepared to fully adopt the RUP development process, powerdesigner is the best. Visio is required, but it is only used as a supplement to Rose or powerdesigner. |