Rose is a design tool that is born directly from UML. It appears to support UML modeling, and Rose has no support to the database end model, but the functionality of the database modeling has been added in the current version. Rose is mainly better in various semantics, modules, objects, and processes, states, etc. in the development process, mainly reflected in the analysis and design of all aspects and angles, making the software development blueprints clearer, and the internal structure is more clear. (However, its structure is only a good support for those developers and processes of UML, which means that the functions and processes of the system are not necessarily valid), and have good support for the system's code framework. But the development management of the database and the iteration of the database end is not very good. PowerDesigner is originally a database modeling tool developed to model database modeling. Until the 7.0 version began support for the development of the object, it introduced support for UML. However, because PowerDesigner focuses on, it supports the support of the database, supports about 90% of the database that can be seen, and the support of the various graphs used in the UML model lags. But it is recently strengthened. So use it to make UML development, many people use it as the modeling of the database. If you use UML analysis, its advantage is that the support of Sybase's product PowerBuilder is very good when generating code (other UML modeling tools do not or requires a certain plugin), other object-oriented languages such as C , Java, VB, C #, etc. Not bad. But it seems to inherit Sybase's consistent tradition. It is not very optimistic about China's market, so there is always such a problem with Chinese support. Visio is just a picture tool, which can be used to describe a variety of graphics (from circuit diagrams to housing structural maps), but also to Visio2000 began to introduce software analysis design functions to all functions generated by the code generation, it can be said to be the most used. The graphical mode is used to express various commercial graphics purposes (the UML support in software development is just some of them). It is very compatible with Microsoft's Office products. Ability to copy graphics or embedded into Word documents. However, for the generation of code, more products that support Microsoft products such as VB, VC , MS SQL Server et al. (This is also a tradition of Microsoft), so it can be said to be more convenient for graphical semantics, but it is used for software development processes. Development is a bit awkward. All three products have side focus, each has advantages and disadvantages, mainly to see your choices and your development methods and environments.
Talking from your own experience, I am talking about the perspective of purpose and support. First talk about a purpose issue. It is now paying attention to object-oriented analysis and design, and you will be based on oo. The version is Rational Suite 2002 VS PowerDesigner 9.5 VS Visio 2002.
First, a basic function of the CASE software is a mapping. In the software engineering, we do the figure below: System block diagram / tree map; uml map; ER map; Gantt, any flow chart; other charts. The system block diagram / tree diagram is used in the next time, and there is not a specific document, on this link, Visio is best, ROSE does not support, PowerDesigner supports a little bit is not easy.
In the UML diagram, the three support, Rose supports the full range, and it is easy to reflect the characteristics of iteration, the use case drive, the best correlation is the difference between pattern quality, logic check and control, no NAME and CODE distinction ( PowerDesigner's characteristics) Not suitable for Chinese, generating documents is not suitable for custom, and no dictionary for design objects can be quickly found. PowerDesigner 9.5 full support, the advantage is that the graphics quality, the generated document is easy to customize, the logic check and control, the dictionary with design objects can quickly find and quickly locate the graphics, the disadvantage is a little bit a little more troubles between each other. The people who are unskilled with UML and RUP are used, and they are reflected in iterative and use case drivers, and those skilled people have used it to be better resolved. Compared to Visio's graphics quality is the best, but the connection and correlation is also the worst, logical checks and control can be done. The ER picture is not said, and the best is PowerDesigner, Rose and Visio compare amateur. Gantt map is used for project plans, Visio can do, and other do not support. But I suggest you do it with Visio, or do it with Project. Any flowchart is not supported by ROSE, Rose only supports business-oriented activity maps and an active map for useful activities, which are more limit. PowerDesigner 9.5 support, it is also available. Visio is best because of its best quality, and the predefined element is also the most. Rose does not support other charts. PowerDesigner 9.5 support, but a predefined element is not much. This point Visio is best, don't say more. Second, good case software supports the two-way conversion between the Case document and the code, the CASE document and the database. Rose documents can be converted with code, database bidirectional, is implemented by intermediate plugins. PowerDesigner is best, big integration, supports two-way conversions between code and database, and does not need plugins. Visio is achieved through VBA and macro, which is used for a little trouble, although this technology is not difficult, but now I don't seem to be much. Secondly talk about a support and collaborative issue. Rose has relatively up-to-date and most complete UML support, PowerDesigner and Visio are slightly lag. Rose has the support of the RUP system and a series of software supported by RUP and Rose collaboration, this is PowerDesigner and Visio lingering. However, PowerDesigner has an advantage that "one-stop" analysis design, no need for any plug-in, two-way conversion with code and database, Rose needs the corresponding plug-in provided by Rational Company (not, just client code), this Winter winter money is really fucking! This aspect PowerDesigner is really good :). Visio feels no flow. There may be other aspects, I am not one, everyone can pay according to their own environment. My suggestion is that if your team is more familiar with business and English, it is not familiar with RUP. It is recommended that you use Rose because it has a complete RUP theory and is very dependent; if your team is slightly Xun and system analysts can understand RUP well, then it is recommended that you use PowerDesigner; of course, if you are not prepared to fully adopt RUP development processes, PowerDesigner is the best; Visio is required, but just as Rose or PowerDesigner supplements.
