Comparison of Rational Rose, powerdesign, and Visio

For the current modeling software, Rational Rose, powerdesign, and Visio are commonly used series. Here we will compare them, I have used powerdesign, Visio, and staruml, a free tool similar to Rose. Some of the following content comes from the network, and I cannot find the source, so I am too lazy to mark where it comes from, it is from the network.

Rose is a design tool born directly from the Development of UML. It was designed to support UML modeling. Rose did not support database modeling at the beginning, however, the database modeling function has been added to the current version. Rose is mainly used to describe various semantics, modules, objects, processes, and states in the development process. It is mainly reflected in the ability to analyze and design from various aspects and perspectives, make the software development blueprint clearer and the internal structure clearer (but its structure is only for developers who have mastered UML, that is to say, it is not necessarily effective to understand the functions and processes of the system. However, the development and management of databases and database iteration are not very good.

Powerdesigner was originally a database modeling tool developed for database modeling. It was not until version 7.0 that it began to support object-oriented development, and later introduced support for UML. However, because powerdesigner focuses on different aspects, it supports database modeling well and supports about 90% of the databases that can be seen. The support for various diagrams used in UML modeling lags behind. However, it has been strengthened recently. So there are not many developers who use it for UML development. Many people use it for database modeling. If you use UML for analysis, it has good support for Sybase product PowerBuilder when generating code (Other UML modeling tools do not have or need some plug-ins ), other object-oriented languages such as C ++, Java, and VB, C # and other support is also good. However, it seems that it inherits the consistent tradition of Sybase and is not very good at the Chinese market. Therefore, Chinese support always has one or another problem.

In the past, Visio was just a drawing tool that could be used to describe various graphics (from circuit diagram to housing structure diagram). It was also the first time that visio2000 began to introduce software analysis and design functions 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 (UML support for software development is only a small part ). It is compatible with Microsoft Office products. The ability to directly copy or embed images into Word documents. However, for code generation, Microsoft products such as VB are supported., VC ++, MSSQLServer and so on (this is also the tradition of Microsoft), so it can be said that it is more convenient to describe the graphic semantics, but it is a little far-fetched for iterative development in the software development process.

Each product has its own focus and advantages and disadvantages. It mainly depends on your choice and your development method and environment.
I also want to talk about it from my own experience.
I am talking about it from the perspective of purpose and support.
First, let's talk about a purpose. Now we are focusing on Object-Oriented Analysis and Design. Let's start with OO. The version is rational suite 2002 vs powerdesigner 9.5 vs Visio 2002.
First, a basic function of CASE software is plotting.
In software engineering, we have made the following diagrams: system diagram/tree diagram; UML diagram; erdiagram; Gantt diagram; Any flowchart; and other arbitrary charts.
The system diagram/tree chart is used when you are relatively casual and have not formed a specific document. In this stage, it is best for Visio, which is not supported by Rose. powerdesigner is not easy to support.
In the UML diagram, all three are supported. Rose supports a full range of features, such as iteration and case-driven. It has the best relevance. Its disadvantage is poor graphic 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. 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. Compared with Visio, the image quality is the best, but the cohesion and relevance are also the worst. Logical check and control can barely do a little bit.
Needless to say, the best job is powerdesigner, Rose, and Visio.
The Gantt diagram is used for project planning, which can be done by visio, but not by others. However, we recommend that you do not use Visio or project.
Any flow chart is not supported by Rose. Rose only supports business-oriented activity diagrams and use-case-oriented activity diagrams. There are many restrictions. Powerdesigner 9.5 is supported and can be used. Visio is the best because it has the best graphic quality and has the most predefined elements.
Rose does not support any other charts. Powerdesigner 9.5 supports many predefined elements. It is best to say this in Visio.

Second, good case software supports two-way conversion between case documents and code, case documents and databases.
The rose document can be bidirectional conversion with codes and databases through intermediate plug-ins. Powerdesigner is best for big integration and supports bidirectional conversion between code and database without plug-ins. Visio uses VBAAnd macro implementation, it is a little troublesome to use, although this technology is not difficult, but now it does not seem to understand this too much.

Next, let's talk about support and collaboration.
Rose has the latest and most complete UML support, while powerdesigner and Visio are slightly behind each other. Rose has the support of the RUP system and a series of software and Rose collaboration supporting the RUP, which is beyond the reach of powerdesigner and Visio. However, powerdesigner has an advantage of "one-stop" analysis design. It can be converted in two-way with code and database without any plug-ins. In this regard, Rose needs the corresponding plug-ins provided by rational (databases are not required, only client code). This winter's money is really expensive! In this regard, powerdesigner is really good :). Visio does not feel like a stream.

There may be other aspects. I will not list them one by one. You can choose between them based on your own environment. My suggestion is: 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 is a little inferior to the business and English language and the system analyst can understand the RUP well, we recommend that you use powerdesigner. Of course, 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.

Provide two-way conversion support and collaboration between case documents and codes, case documents and databases
System diagram/tree diagram UML diagram erdiagram Gantt diagram arbitrary flowchart other arbitrary charts
The purpose of Rose (rational suite 2002 vs) was to support UML modeling. At the beginning, there was no support for database modeling and good support for system code framework generation. However, the development and management of databases and database iteration are not very good. Rose does not support a full range of products. It is easy to reflect iteration, case-driven, and other features. It has 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. In my spare time, It is not supported. Rose, which does not support intermediate plug-ins, has the latest and most complete UML support.
Powerdesigner 9.5 is a database modeling tool developed for database modeling. It was not until version 7.0 began to support object-oriented development, and later 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. Powerdesigner 9.5 is not easy to support. The advantage is that the image quality is good, the generated documents are easy to customize, and the logic check and control are good, dictionaries with design objects can be quickly searched and quickly located in graphs. The disadvantage is that the connection between them is a little more troublesome. They are used by people who are not proficient in UML and RUP, it does not reflect iteration and case-driven. It is better for skilled users to solve the problem. The best is not supported and can be supported, but the predefined elements are not much better. Plug-ins do not need to support the latest and most complete UML, and the support of the RUP system is not supported.
Visio (vs Visio 2002) is only a drawing 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 (UML support for software development is only a small part) iterative development for the software development process is a little far-fetched. The best picture quality of Visio is the best, but the cohesion and relevance are also the worst. Logical inspection and control can barely do a little bit. In my spare time, Visio can still be used as a project. It is best for Visio to useAnd the. Visio implemented by the macro feel that the support for the latest and most complete UML is a little lagging behind; no support for the RUP System
Each product has its own focus and advantages and disadvantages. It mainly depends on your choice and your development method and environment.
If your team is familiar with business and English, but is not familiar with RUP, we recommend that you use rose because it has complete theoretical support and is highly relevant;
If your team is a little inferior to the business and English language and the system analyst can understand the RUP well, we recommend that you use powerdesigner;
Powerdesigner is the best if you are not prepared to fully adopt the RUP development process. Visio is required, but it is only used as a supplement to Rose or powerdesigner.
 
 

Comparison of Rational Rose, powerdesign, and Visio
Two-way conversion support and collaboration between case documents and code, case documents and databases
System diagram/tree diagram UML diagram erdiagram Gantt diagram arbitrary flowchart other arbitrary charts
The purpose of Rose (rational suite 2002 vs) was to support UML modeling. At the beginning, there was no support for database modeling and good support for system code framework generation. However, the development and management of databases and database iteration are not very good. Rose does not support a full range of products. It is easy to reflect iteration, case-driven, and other features. It has 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. In my spare time, It is not supported. Rose, which does not support intermediate plug-ins, has the latest and most complete UML support.
Powerdesigner 9.5 is a database modeling tool developed for database modeling. It was not until version 7.0 began to support object-oriented development, and later 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. Powerdesigner 9.5 is not easy to support. The advantage is that the image quality is good, the generated documents are easy to customize, and the logic check and control are good, dictionaries with design objects can be quickly searched and quickly located in graphs. The disadvantage is that the connection between them is a little more troublesome. They are used by people who are not proficient in UML and RUP, it does not reflect iteration and case-driven. It is better for skilled users to solve the problem. The best is not supported and can be supported, but the predefined elements are not much better. Plug-ins do not need to support the latest and most complete UML, and the support of the RUP system is not supported.
Visio (vs Visio 2002) is only a drawing 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 (UML support for software development is only a small part) iterative development for the software development process is a little far-fetched. The best picture quality of Visio is the best, but the cohesion and relevance are also the worst. Logical inspection and control can barely do a little bit. In my spare time, Visio can still be used as a project. It is best for Visio to useAnd the. Visio implemented by the macro feel that the support for the latest and most complete UML is a little lagging behind; no support for the RUP System
Each product has its own focus and advantages and disadvantages. It mainly depends on your choice and your development method and environment.
If your team is familiar with business and English, but is not familiar with RUP, we recommend that you use rose because it has complete theoretical support and is highly relevant;
If your team is a little inferior to the business and English language and the system analyst can understand the RUP well, we recommend that you use powerdesigner;
Powerdesigner is the best if you are not prepared to fully adopt the RUP development process. Visio is required, but it is only used as a supplement to Rose or powerdesigner.

 

Comparison of various tools:
 

	Birth	Graph Creation						Bidirectional conversion between case documents and codes, 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 uses VBAAnd the. Visio implemented by macros do not feel like they are in the stream.	The support for the latest and most complete UML is a little lagging behind; no support for the RUP System
Each product has its own focus and advantages and disadvantages. It mainly depends on your choice and your development method and environment. If your team is familiar with business and English, but is not familiar with RUP, we recommend that you use rose because it has complete theoretical support and is highly relevant; If your team is a little inferior to the business and English language and the system analyst can understand the RUP well, we recommend that you use powerdesigner; Powerdesigner is the best if you are not prepared to fully adopt the RUP development process; Visio is required, but only

Comparison of Rational Rose, powerdesign, and Visio