UML hard injury? Application of UML in System Analysis and Design

Three major injuries to UML: A brother attacked UML and said that he had a personal understanding. For the original article, see the link below.

At least the use case diagram, activity diagram, state diagram, class diagram, and time sequence diagram in UML are still very useful (I only use this degree at present ). The use case diagram mainly provides a large view of software functions, and also preliminarily expresses the user's permission range. The activity diagram is easy to understand, which is equivalent to a flowchart, indicating the business process and evenProgramAlgorithmThey are commonly used. The status chart and activity diagram complement each other, and sometimes the state machine conversion is used to express some business flows clearly. class diagrams are useful for expressing the object relationship diagram and expressing the design of classes; A time sequence diagram can be used to express business flows and interface interactions, especially when it is used to express how interfaces (methods) between classes call interactions.

UML can be used in the system analysis phase (use case diagram/activity diagram/State Diagram (Business modeling), Class Diagram (Domain Modeling), and also in the software design phase (Class Diagram (Class/Object Design) activity diagram (Algorithm Description) and use case implementation (Time Sequence diagram and interface interaction )). In addition, through case implementation, the analysis phase is connected with the design phase. The former is OOA, and the latter is Ood. Then, the following brothers can understand and understand the above outputs, basically follow the implementation program, that is, oop. in this way, UML is an expression that helps apply object-oriented technology, and there may be other expressions (such as the"CodeIs design ", implemented through continuous refactoring ?), But at least this method is good. Of course, the final effect depends on the internal strength of the designer.

People are the most critical. UML is just a form of expression and a tool. Many of them feel that UML is useless. Maybe they are not used to it, that is, they are not used to the software analysis and design expressions such as UML. If you are familiar with UML, you will feel that UML is easy to use and can clearly express your meaning. If you are familiar with UML, you will feel that it is easy to understand, knowing what the designer wants to express-that is, the value of UML. If you are not used to using UML, you will feel that UML is useless. It is better to use other expressions. That's all.

Because I am used to Rose, I may have some ideas that I prefer UML to use. But I don't think it is so subtle. Perhaps it depends on the degree of use, and the domestic software environment, for small and medium-sized enterprises, may not allow you to use so deep, can not afford this cost.

The above discussion has not been tested. I would like to try what it will do before, but I have never had this opportunity. In this case, time and energy are not allowed.

Three major damage to UML.