Why Java Development requires UML

Do you know what the situation in UML is causing chaos? Know what kind of functionality is available in UML but not in Java? Do you know why we need another computer language other than Java? UML is not just a substitute for Java or any other language. UML is not just a substitute for Java or any other language. UML is the annotation of object-oriented analysis and design. UML is a language that is independent of those traditional design languages. Because UML is not attached to a language, it is used as a basic tool for communicating languages such as Java, C + +, and Smalltalk. By using UML, you can plan the entire system before you start coding, and the developer is aware of the role that the module is responsible for throughout the system.

More importantly, UML can help you keep track of errors that start with design, and you know that bad design can cause a series of problems. Imagine that halfway through the source code, you suddenly find that the information you need is exhausted, but you have no way to get information back because you are not referencing object, even if you are referencing object, but the information is not public. Obviously, you'll spend a few days figuring out how the code changes.

UML can help you get rid of some of the difficulties: the code accumulates as the details increase, so it becomes difficult to find out what the basic elements of the system are and how the relationships between objects and how they relate to each other. When a lot of code comes out, it becomes difficult to make some changes. It is therefore a major task to decide that the function of an object is assigned to the settings in collaboration. Even simply changing the name of a method is likely to result in a long edit----compile---error loop.

Before coding a high level of design is the correct requirements analysis and precise definition, UML automation tools are important, but UML in the design discussion is more useful.

OOA, OOD, and OOP

What is OO analysis and design? What is the difference between them and OO programming? To understand this, watch out for the loop process of a program

The first step, demand collection: First of all to plan a good system, planning the implementation of the system steps. Usually people will take a discussion to extract the requirements and make detailed records, then discuss with key users or consumers and let them agree that you have mastered the problems the system is solving.

OOA (Object Oriented analysis) is a process that describes the combination of system implementation and system planning. The analysis magnifies the goals in the central area of the problem, analyzes what their important role is, and what goals are linked to. In addition, parsing determines which targets are subordinate to the common category.

OOA (Object Oriented analysis) is a process that describes the system implementation and the system planning coincide. The analysis amplifies goals in the central area of the problem, analyzes what their important role is, and what goals are associated with them. In addition, parsing determines which targets are subordinate to the common category.

In particular, parsing should be similar to real-life problems without the need for new and complex problems. You can even share these resolutions with someone who doesn't know the technology but understands these issues, and they can point out what you've missed in parsing, what you've overlooked, or where you've gone wrong.

OOD in the design phase, you have to be prepared to magnify specific issues for analysis. Then you have to decide what the method's arguments are and what their return type is. You may find that the new class will help you complete the design. You can abstract common functions into interfaces or base classes. A single analytic class can be decomposed into several cooperative classes. In short, you are still in the planning phase, not the implementation phase.

OOP after you build a framework, the next step is to implement the code. After the appropriate design, you can follow the following steps to implement the details:

1, is the use of Hassi or two fork tree

2, is the use of RMI or CORBA to complete client/server communication?

3, in what language?

For a more realistic experience of how UML works in the parsing and design stages, it needs to be understood by solving a problem.

Once you've coded everything and are in execution, you can use the cycle. As the system delivery date approaches, you will find out what is lacking and which part of the next step you need to refine. By using interactive parsing, design, refinement, and operation, you can run and refine your system quickly and stably without worrying about missing code.