UML Re-summary

Start the machine room reconstruction immediately, master let me draw drawing, clarify the idea, UML study for a period of time, the first two days of professional courses just finished, on the strike, and then some important concepts summed up, let their brains clearer.

1. A message is a single communication between two objects, from the sender to the receiver's control flow, the message can be used to pass parameters between objects, which are method calls in object-oriented.
1. When modeling a system using a time series diagram, you can follow the following strategies: Set the interaction context, identify the role that the object plays in the interaction, place it in a left-to-right direction in the sequence diagram according to the importance of the object, and draw the subsequent message from top to bottom in the sequence between lifelines. You can attach the appropriate time and space constraints to each message, and attach a pre-or post-condition to each message for a control flow.
1. Collaboration diagrams model only the interactions between objects and the relationships between those objects.
1. collaboration diagrams and time series diagrams all represent interactions between objects, but their focus is different. Time series diagrams describe the chronological order of the interaction, but there is no explicit relationship between the objects, and the collaboration diagram describes the relationship between the objects, but the chronological order is obtained from the serial number.
1. 5 part. The transformation is composed of the source state, the target State, the triggering event, the action of the Guardianship event, 5 part.
1. component diagrams typically contain 3 Types of elements: components, interfaces, and dependencies.
1. A component is a physical implementation unit that defines a good interface, which is a replaceable physical part of a system that wraps implementations that implement and follow and agree to provide a set of interfaces.
1. Nodes: You need to consider both the ability (such as compute power, memory size, and so on) and physical location (which requires that the system be accessible in all geographic locations where the system needs to be used).
1. Three elements of software engineering: methods, tools, processes.
1. UML ( Unified Modelding Language , Unified Modeling Language)
1. UML is an object-oriented modeling language. Its main role is to help users to the software system for object-oriented description and modeling, it can describe the software from the requirements analysis until the implementation and testing of the development process.
1. View is composed of graphs, uml Span lang= "ZH-CN" style= "font-family: Arial" > provides 9
1. uml
1. from uml uml uml
1. use case diagrams include the following 3 aspects: Use case diagrams, participants, relationships between participants and use cases, generalization relationships, inclusive relationships, extended relationships, and so on.
1. Use case diagram Modeling steps: Identify participants based on system boundaries, determine the use cases associated with them based on each participant, optimize the relationship between participants and use cases, and optimize the relationship between use cases.
1. uml uml
1. uml + - # "expression.
1. The relationship between the use cases is the most commonly used four kinds: dependency between classes, general and special relationship between classes, the relationship between objects in relation to structure, and the relation between the specification and implementation in class.
1. in the UML , an object graph represents a set of objects at a certain time and a graph of the relationships between them. An object graph can be seen as an instance of a class diagram at some point in the system.
1. The role of a package: to group elements.
2. timing diagrams include 4 elements, respectively, are objects, lifelines, activations, and messages.
1. Interaction diagrams are dynamic diagrams, including time series and collaboration diagrams, time series diagrams and activity diagrams that express concurrency.

(Five views of UML)

UML Re-summary