Shulou(Shulou.com)06/02 Report--

This article will explain in detail why we need UML modeling CASE tools, the editor thinks it is very practical, so share it for you to do a reference, I hope you can get something after reading this article.

Why do we need UML modeling CASE tools

The construction of the system is becoming more and more complex, and UML modeling CASE tools provide many benefits to project stakeholders (such as project managers, analysts, designers, architects, developers, etc.). UML modeling CASE tool allows us to apply standard methods and theories of object-oriented analysis and design, away from the entangled source code, to achieve the level that construction and design become more intuitive, easier to understand and modify. In large projects, it is more important to use CASE tools. By using the CASE tool:

◆ uses the use case model to capture business / system requirements for business / system analysis.

The design model made by ◆ designers / architects can clearly express the interaction between objects or subsystems in the same layer at different levels (typical UML diagrams such as class diagrams and interaction diagrams).

◆ developers can quickly turn a model into a runnable application, find a subset of classes and methods, and understand how they interact.

The model is seen as the final manual for blueprints and building systems. Similarly, modeling is the ability to consider the presentation of a design and understand how it works at a high level and in an appropriate form.

For these reasons, UMLCASE tools and corresponding methodologies provide us with a way to describe systems that are too complex to understand the underlying source code, while allowing us to develop the right software solutions faster and cheaply.

Of course, CASE tools should be considered in terms of UML modeling capabilities, project lifecycle support, two-way engineering, data modeling, performance, price, supportability, ease of use, and so on. This article will explore the similarities and differences between Rose and EA in the areas of UML modeling, project life cycle support, and two-way engineering, hoping to help you choose the right tools in your project.

UML modeling characteristics

The UML standard in RoseUML modeling tool consists of three parts, namely: building blocks (such as objects, classes, messages), relationships between building blocks (such as association, generalization) and diagrams (such as activity diagrams). UMLprofile uses the UML extensibility mechanism to extend standard UML symbols, that is, stereotypes, dimension values, and constraints. EA Professional Edition V.3.51 and RationalRoseV.2002.05 both support eight standard UML diagrams of UML1.4 nine diagrams-use case diagram, class diagram, sequence diagram, collaboration diagram, activity diagram, state diagram, implementation diagram (component) diagram, deployment diagram, and several UMLProfiles. If necessary, object diagrams can be created using collaboration diagrams. The differences only exist in the features supported when creating UML diagrams (Table 1) and extending UMLprofiles.

EnterpriseArchitect has a general UMLprofile mechanism for loading and running different Profiles. EnterpriseArchitect specifies a XML file in a specific format for UMLprofiles. In RationalRose, however, you need to generate an additional item.

Two-way engineering

Two-way engineering in RoseUML modeling tools includes forward engineering-from model to code and reverse engineering-from code to model. Once the design is complete, DDL scripts for a specific programming language or database can be generated using model (design model and data model) information. When developers add / change code or database implementations, the design and data model can synchronize code or DDL scripts through two-way engineering to keep them consistent.

The source code files that EA generates for the class are in the same package. RationalRose is more related to specific projects in VC++ or VB. RationalRose can also create classes through wizards and providing code templates, which can greatly increase the amount of source code generated. In addition, both EA and Rose can apply design patterns. When using EA, users must create their own patterns, while Rose provides 20 GOF design patterns for Java.

Project lifecycle support

The CASE tool should provide support for all members of the team to complete their tasks. With regard to project lifecycle support, EA combines a large number of functions, while Rose is primarily a modeling tool that can be integrated with other Rational or third-party tools, such as RequisitePro,TestManager,Soda,MSWord,MSProject, to achieve the same goal. Table 4 compares the functional support of EA and Rose in different subjects.

Conclusion

In general, EA and RoseUML modeling tools have similar functions in modeling capabilities. Both EA and RationalRose support eight of the nine UML diagrams. You can see from Table 1 that EA is superior to Rose in user-friendly flexibility, especially sequence diagrams. In two-way engineering, Rose supports more languages than EA, except for C # and VB.NET (in fact, Rational has developed another tool-RationalXDEfor.NET is for the .NET environment). Table 4 illustrates that EA is a better choice than Rose in terms of project lifecycle support. Although you can buy other Rational tools to assist it, most companies do not think this is an acceptable solution when considering cost. Of course, this is also an important factor to consider when you need other specific features that are not available in the tool or are not supported by third-party tools. RationalRose has broader support for this.

* is the cost different after a series of comparisons of the same type? Yes-very different! Rose alone costs 28 times as much as EA. If you want to compare project lifecycle support, suppose you are a Rose user, you will have to buy a complete set of products bundled with Rational, such as RequisitePro,SoDA,TestManager, etc. Although the additional tools provide richer functionality than comparable EA, the basic functionality of EA is sufficient most of the time. At the time of this writing, EA Enterprise Edition (* version supports SQL background) costs $179.00 (£111.58), RationalRose Enterprise Edition costs $5024 (£3140), and a complete set of development kits (RationalDeveloperSuite) costs $8976 (£5610) for one day.

On "Why do we need UML modeling CASE tools" this article is shared here, I hope the above content can be of some help to you, so that you can learn more knowledge, if you think the article is good, please share it out for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.