Comparison of EA and Rose UML modeling tools
Author: Unknown Source: Alliance http://www.csai.cn soft test August 8, 2005
Since the official release of UML in 1997, a large number of commercial UML modeling Case tools debut. This provides us with a lot of choices, as well as we need a lot of investigations to better adapt to our business and software applications development needs to better adapt to our business and software applications (ROI). . In this article, we will compare the UML modeling capabilities of two case tools, two-way engineering features and project lifecycle support: Sparx Systems Enterprise Architect (EA) Professional V.3.51 and IBM Rational Rose Enterprise Edition V .2002. Why do we need UML modeling Case tools today, the system builds become more complex, UML modeling case tools are project-related personnel (eg, project managers, analysts, designers, architects, developers, etc.) Many benefits. UML Modeling Case Tool allows us to apply specification-oriented object-oriented analysis and design, away from entangled source code, achieved more intuitive, more easily understood and modified. In large projects, use the CASE tool more important. By using the Case tool: * By the use case model, business / system analysis can capture business / system requirements. * Design models made by the design model can clearly express interactions between objects or subsystems in different levels (typical UML diagrams such as class diagrams and interactions). * Developers can quickly turn the model into a runoff application, find a subset of the class and methods, and understand how they interact. The model is seen as the end manual for blueprints and build systems. Similarly, modeling is a representation of a design and understanding how it operates from the high-level and appropriate form. For these motives, UML Case tools and corresponding methodology provide us with a method of description system that is too complicated and cannot understand the lower source code, while allowing us to develop the correct software solution faster and more cheap. Of course, to consider the Case tool in UML modeling capabilities, project lifecycle support, bidirectional engineering, data modeling, performance, price, supportability, easy usability, etc. This article will explore the same points and differences in UML modeling, project lifecycle support, and two-way engineering, hoping to help you choose the right tool in your project. The UML modeling characteristic UML standard consists of three parts, namely: the relationship between the blocks (such as objects, classes, messages), construction blocks (such as association, generalization) and diagrams (such as active diagrams). UML PROFILE uses the UML scalability mechanism to extend standard UML symbols, ie, constructors, labels, and constraints. EA Professional V.3.51 and Rational Rose V.2002.05 support eight standard UML maps in UML 1.4 nine graphs - use case diagrams, class diagrams, sequence diagrams, collaboration diagrams, active diagrams, state diagrams, implementation maps (components) Figure, deployment diagram, and several UML PROFILES. If necessary, the object map can be created using the collaboration diagram. Different points only exist in some features supported when creating a UML diagram (Table 1) and extending UML PROFILES.
UML graph feature EA ROSE uses an example to establish boundaries of the domain of the field YES NO. However, some work uses text or packages. Sequence collaboration sequence diagram and collaborative diagram Mutual Transformation No Yes Sequence Change Message Range YES NO Sequence Display Message Hierarchy NOS YES NO Sequence Collaboration In the browser Creating objects YES NO sequence management control focus Easy difficult All diagrams of all diagrams YES NO Table 1. Comparison of UML Tunction Models for EA and ROSE
Enterprise Architect has a universal UML Profile mechanism to load and run different Profiles. Enterprise Architect Specifies an XML file in a specific format for UML Profiles. And in Rational Rose, you need an additional item. Table 2 shows the availability of UML PROFILES in EA and ROSE.
UML PROFILES EA ROSE Business Process Modeling Support Eriksson-Penker Business Process Modeling Extended UML Activity Diagram Service Modeling No Yes Data Model YES YES User Experience Model Yes NO Web Model Yes Yes Yes No Yes XML DTD NO
Table 2. Comparison of UML PROFILE EA and ROSE
Bidirectional Engineering Bidirectional Engineering includes forward engineering - from models to code and reverse engineering - from code to model. Once the design is complete, use the model (design model and data model) information to generate a source code or DDL script of a specific programming language. When developers add / change code or database implementation, the design and data models can be consistent with a two-way engineering synchronization code or DDL script. Table 3 shows the characteristics of EA and ROSE bidirectional engineering.
Language EA ROSE ANSI C YES YES VISUAL C No Yes VB6 Yes Yes Java Yes Yes C # Yes No vb.net Yes No Delphi Yes No. Third Party Addition. J2EE / EJB No Yes Corba No Yes ADA83, ADA95 NO YES DATABASE YES. From the data model to the forward project of the DDL script. ODBC Data Source Reverse Engineering Yes.db2, Oracle, SQL 92, SQL Server, Sybase COM NO YES. Just reverse engineering web application NO YES
Table 3. The two-way engineering EA of EA and ROSE EA is placed in the same package for the source code file of the class. Rational Rose more involved in specific items in VC or VB. Rational Rose can also create classes through the wizard and the code template, which greatly increases the number of source code generated. In addition, both EA and ROSE can apply design patterns. When using EA, the user must create a mode itself, and Rose provides 20 GOF design patterns of Java. The project lifecycle supports the Case tool to support their tasks to all players in the team. With regard to the support of the project lifecycle, EA will integrate a large number of functional synthesis, while Rose is mainly modeling tools, which can be integrated with other Rational or third-party tools such as RequisitePro, Test Manager, Soda, MS Word, MS Project. To achieve the same goal. Table 4 compares EA and ROSE functional support in different subjects.
Project subject EA ROSE business modeling yes. Using UML profile to model YES. Use business case model requirements management YES. Function and non-functional requirements; demand tracking matrix merge REQUSITEPRO analysis and design YES; UML class diagram and interactive diagram, If you need some prototype, such as << Layers >>, << Usage Implementation >> YES; UML Class Diagram and Interactive Frame Wizard provide a series of templates to construct a model implementation see Table 3; suitable for C , VB, C # See Table 3 and VB.NET projects; support most languages, except .NET external test Yes No. Quality Architect provides unit testing, it requires other Rational tools, such as Test Manager, Robot version control is not directly supported. Use the control unit to publish a plan for future. Integrated SCC corresponding version control application project management risk management, resource allocation, project budget NOW Web released YES YES generated report Yes No. Use Soda. Multi-user Collaboration YES YES Table 4 EA and ROSE For the project lifecycle support conclusions, EA and ROSE have similar functions on UML modeling capabilities. EA and Rational ROSE support eight of the UML nine diagrams. From Table 1, it can be seen that EA is better than Rose, especially sequence diagrams than Rose. In bidirectional engineering, Rose supports more languages than EA, except C # and VB.NET (in fact, Rational Xde for .NET is for .NET environments). Table 4 illustrates that EA is better for EA relative to ROSE in terms of support of the project life cycle. Although you can purchase other Rational tools to assist it, most companies do not think this is an acceptable solution when considering cost problems. Of course, this is also an important factor to consider when you need some other specific features that don't or on third-party tools. At this point, Rational Rose gains a wider support. Finally, is there a difference in the same type of comparison? Yes - very different! Single is Rose spending 28 times the EA. If you want to compare the support of the project lifecycle, assume you a Rose user, you will have to buy a complete set of products bundled in Rational, such as Requisite Pro, Soda, Test Manager, etc. Although additional tools provide a richer function than the same EA, the basic functions of EA have been sufficient in most time. The cost of the EA Enterprise (the highest version supporting SQL background) is $ 179.00 (£ 111.58) and the cost of Rational Rose Enterprise Edition is $ 5024 (£ 3140), and the cost of the Rational Developer Suite is $ 8976 (£ 5610).
