Why does Java development require UML?

 

YesWhat is the big chaos caused by UML? Do you know what types of functions are available in UML but not in JAVA? Do you know why we need another computer language besides JAVA? UML is not just a substitute for JAVA or other languages. UML is an annotation of object-oriented analysis and design. UML is a language independent of traditional design languages. Because UML is not attached to a language and is used as a basic tool to communicate with Java, C ++, Smalltalk, and other languages. By using UML, you can plan the entire system before coding, and developers can clearly understand the role of the modules they are responsible for in the entire system.

More importantly, UML can help you record errors that have occurred since the design. You need to know that poor design can cause a series of troubles. Imagine that when the source code is half compiled, you suddenly find that the information you need is exhausted, but you cannot obtain the information again because you didn't reference the OBject, even if you reference an object, the information is not public. Obviously, you will spend several days identifying code changes.

UML helps you get rid of the following dilemmas: the code accumulates with the increase of details, so you can find out which are the basic elements of the system, it is difficult to understand the relationships between objects and how they are connected. When a large amount of code is generated, it is also difficult to make some changes. Therefore, it is a major task to determine whether the function of an object is assigned to the settings in collaboration. Sometimes it is just as simple as changing the name of a method, it may also lead to a long edit-compile-error loop.

Prior to coding, a high level of design is to conduct correct requirement analysis and accurate definition. automation tools of UML are important, but UML is more useful in design discussions.

OOA, OOD, and OOP

What Is OO analysis and design? What are their differences from OO programming? To understand this, observe the loop process of a program.

Step 1: Collect requirements: first, plan the system and implement the system. Usually, people extract requirements through discussion, record them in detail, discuss with key users or consumers, and let them agree that you have mastered the problems that the system is solving.

OOA (Object oriented analysis) is a process that describes the combination of system implementation and system planning. The analysis expands the targets in the problem center, analyzes their important roles, and analyzes the relationships between the targets and the targets. In addition, resolution also determines which target belongs to the public category.

In particular, the resolution should be similar to the problems in real life, and there is no need to create any new complicated problems. You can even share the analysis with someone who doesn't understand the technology but understands the problems. They can point out what you missed in the analysis, and ignore what or where something went wrong.

At the design stage, you have to zoom in on specific issues for analysis. Then you have to determine the independent variables of the method and their return type. You may find that the new class will help you with the design. You can abstract common functions into interfaces or base classes. A single analysis class can be divided into several cooperative classes. All in all, you are still in the planning phase, not the implementation phase ..

After you build a framework, the next step is to implement the Code. After a proper design, you can perform the following steps:

1. Use a Hasse table or a binary tree.

2. Does RMI or CORBA be used for communication between customers and servers?

3. What language is used?

To provide a more practical experience on how UML plays a helping role in the parsing and design phases, we need to solve a problem.

Once you code everything and execute it, you can use it cyclically. As the delivery date of the system approaches, we will find out where the system is insufficient and what parts need to be improved in the next step. By using interactive parsing, design, improvement, and operation, you can quickly and stably repeat and improve the system without worrying about code loss.