1. Static diagram: In the class diagram, the category is represented by the rectangle box, its attributes and operations are listed in the division. If you don't need to express more information, the tissue can be omitted. A class may appear in several figures. The attributes and operations of the same class can be listed in one figure, in other figures, can be omitted. The connection between the relationship class box is represented, and different relationships are different from the modifiers at the connection and connecting ends.
2. Using an example view: Model diagram of system functions that can be observed by external users called participants. The use case is a functional unit in the system that can be described as a interaction between the participant and the system. The use of an example model is to list the use cases and participants in the system, and which participant is displayed which use case is performed.
3. Interaction View: Interaction View describes the order relationship between each role that performs system functions. The class is a description of an object that serves a particular role in the interaction between the system, which distinguishes it to other objects of the same class. The interaction view shows the system control flow across multiple objects. The interaction view can be represented by two diagrams: sequential diagrams and collaboration diagrams, which have different focuses.
4. Sequence diagram: The sequence diagram represents the time order of the transfer message between the objects. Each type element role is represented by a lifeline - that is, the vertical line represents the life of the object in the entire interaction process. The arrow connection between the lifeline represents the message. The sequence diagram can be used to perform a scene description - the historical process of a transaction. 5. Collaborative drawing: It is used to represent each role in the interaction (Figure 3 - 4). Arrows attached to the class dollar representative message. The order of the message is described in the number of messages at the message arrow. One purpose of the collaboration map is to represent a class operation. Collaboration drawings can explain the parameters and local variables used in class operations and permanent chains in operation. When a behavior is implemented, the message number corresponds to the nesting structure and signal transfer process in the program. 6. State chart: It is a model diagram of all the journeys that may experience the class object. The state machine consists of various states of the object and the conversion of the connection these states. Each state gives an object to a time period construction model for a certain condition in its lifetime. When an event occurs, it triggers the transition between states, causing an object to be converted from one state to another. When executed with the conversion-related activity, the conversion also occurs at the same time. The state machine is expressed. 7. Active map: It is a variant of the state machine to describe the activities involved in the workflow of the algorithm. The active status represents an activity: a workflow step or an operation. The activity diagram describes a set of sequential or concurrent activities. The activity view is reflected in the activity map. The purpose of the map is the workflow modeling of the real world of human tissue. Such views provide mechanisms that map classes in the system into physical components and nodes. 9. Deployment View: Describe the arrangement of the running component instance on the node instance. The node is a set of running resources such as computers, devices, or memory. This view allows evaluation of allocation results and resource allocation. 10. Model management view: Modeling model itself. A range of packets composed of model elements (such as classes, state machines, and use cases). Packs may contain other packages, so the entire model can actually see a root package, which indirectly contains all the contents in the model. The package is the basic unit of operating model content, access control, and configuration control. Each model element is included in the package or in other model elements. (The model is a complete description of the system from a certain point of view with a certain exact degree.)
