The relationship between the behavior and the behavior of the function is mainly used to describe the use case model system /. Generalization, extend relationship, relationship comprising: the relationship between the three use cases. Generalization refers to a plurality of common use cases for a similar structure and behavior of their common parent abstract use cases, other embodiments use a sub-embodiment (indicated by solid line arrows CSA). Expanded relationship is beginning to develop a complex system with cases from one group, and can not be changed under the premise of the use case to the base embodiment expand more behavior (by a broken line plus open arrows, and add a << extend in the dotted line with> >). It contains the relationship is more with the same period of behavior example of abstract into a single use case, then let the other use cases to include this use case (plus open with dashed arrows, and add a << include >> in dashed line). Wherein the containment relationship is unconditional, conditional relationship expansion.
Object Name three expressions: (1) object name; (2) object name: Class Name; (3): Class Name
FIG sequence for sequential operation between the object capture system interaction, to emphasize that the time sequence of message exchange.
FIG sequence (Sequence Diagram) = Lifeline (Lifeline) + message (Message)
Lifeline shows the lifespan of an object in the interactive process, indicating the presence of an object times the performance of a function in the system.
In object-oriented analysis and design, the behavior of an object is also called a message (Message).
Attribute name = signal or message (parameter: Parameter Type): Return value
Message into simple message, synchronous and asynchronous message message. Simple message does not contain the details of control. Synchronous message means blocking and waiting. Asynchronous message means a non-blocking. If the object A sends a message to the object B, the object A and the process B must wait for completion of the operation command message is performed after the blocking call may perform their operations.
<< create >> represents an object to create a message, << destroy >> object that represents the destruction of a message.
No trigger object message (found message) indicates the sender of the message is not specified in detail; no message receiving object (lost message) indicates that describes the message recipient is not specified in detail, or a known recipient, the message or a time not received.
Control Message: conditions, iterative
The return value added message-Open arrows indicated by broken lines.