One: Time series Diagrams---> Timing diagrams are used to describe the interaction patterns between objects in chronological order. ---> It displays these objects according to the "Lifeline" of the object that participates in the interaction and the messages they send to each other. ---> Time series diagrams contain objects and lead instances, and messages that explain how they interact. ---> Time series diagrams describe the events that occur in the objects that participate in the interaction (explained from the point of activation), and how these objects communicate by sending messages to each other. ---> Timing diagrams and collaboration diagrams can be converted to each other, and unlike collaboration diagrams, time series diagrams emphasize the order in which message events occur, making it easier to articulate the process of the flow. But time series diagrams are difficult to express the relationship between objects. ---> Timing diagram is divided into: business model timing Diagram and conceptual model timing diagram. II: Business model time series Diagram---> Business model Time series diagrams are used to model business entity interactions in a domain model---> The goal is to implement business use cases. ---> Before plotting the business entity sequence diagram, you should have drawn the activity diagram in the business use case implementation process. Activity diagrams can help us discover business entities. In fact, if you have an activity diagram before you can draw a sequence diagram of a business entity, you will find that there are traces that are easy to follow. ---> Draw attention to the business model timing diagram: First, the timing diagram is the guideline for achieving business objectives. Second: This phase is in the business phase, and the descriptive language used should use business terminology. Third: The content of the time series diagram will be helpful to the future analysis design, but it is not able to be relied on because of the coarse state relative to the coding implementation. Three: The conceptual model sequence diagram---> Concept phase of the sequence diagram using the Analysis class to draw. ---> Goals are also implementations of business use cases. The---> Analysis class itself represents a system prototype, so the timing diagram for this phase is already with computer understanding.
< 17 timing diagram of the >UML core view Dynamic View
