Summary of UML-1 for Agile Development

how UML is used
Draft
Blueprint
Development language

In agile development, we often use UML in a draft manner.
Figure
The graphs we commonly use in agile development are class diagrams and sequence diagrams. We use these two graphs to analyze the domain model of recognition. The concepts identified in these graphs will form a set of languages that we describe in the relevant fields.

1. Class Diagram (Diagram)

The type used to describe the object, which is a description of the static information. These static information includes the relationship and limitations of the class's attributes (Features) with the class.

-related concepts

-Attention Point
When we identify generalization relationships, we pay attention to the concept of differentiated Classification (classification). The reason is that generalization is transitive, and classification is not transitive, it is the relationship between the object and the type. For example, monkeys are primates, primates are animals. Primates are animals classified by purpose. We try to apply a transitive relationship to organize it. We can say that monkeys are animals, but we can't say that monkeys are animals classified by purpose. Note here that "primate is an animal classified by purpose" is classification. So note that the "yes" relationship here is not all generalization.

2. Sequence diagram (Sequence Diagram)
Sequence diagrams are one of the interaction diagrams (Interaction Diagram). Interaction diagrams describe certain behaviors between objects (note that between objects, not classes. It is also possible that there is more than just a collaborative relationship between the objects of the class and possibly other participants. Sequence diagrams are used to help us capture the behavior of a scene. When you draw a sequence diagram, we often use a use case to identify the instance objects and the information that they interact with to illustrate the diagram.

-Role
This diagram does not clearly describe the algorithm, but it can clearly describe the invocation relationship. This is in line with our agile development needs. As a sketch we don't need to focus too much on algorithmic detail.
This diagram can clearly distinguish the responsibilities of each object. As an entry point or novice user of OO development, it is often easy to write code that centrally controls (centralized control) because it is more closely aligned with procedural thinking habits. And we advocate distributed logical control (distributed), that is, the data and behavior tightly to the object of a single responsibility.

This article is from the "Torrent Blog" blog, make sure to keep this source http://simonwzing.blog.51cto.com/3896700/1632197

Summary of UML-1 for Agile Development