First impressions of the UML sequence diagram ------- day64

There are a lot of ideas that you can't wait to implement recently, but in fact, there are always problems in the first places that you want to understand and feel OK, which leads to a slight impatience, it should be calm. On the weekend, we will clean up and move things tomorrow. I don't know if broadband can be smoothly moved over. I 'd like to record this week's work in advance.

In general, the initial design of the interface was completed this week, and then the outline design was completed. After the results were integrated, the Word documents had nearly a hundred pages and there were too many sequence diagrams, I am a little dizzy. In fact, in a company a long time ago, the first problem I encountered during the interview was the sequence diagram. As a result, I was very miserable and the result was naturally lost. This time I looked at the sequence chart and understood it for a long time. Just like a lot of things, it's like a piece of window paper. Even if it's thin, I don't know what it means.

This time, I finally made dozens of sequence diagrams. Some of my own little understandings may be biased, but I still keep a record, so I can summarize my work this week.

1. Write tools

This time we useRational Rose 2003(Tried in previous projectsVisolAndPower DesignerIt is better to use power designer now. For the time being)

2. Basic Knowledge

The Sequence Chart, named Sequence digoal, is arranged in chronological order to display the interaction between the participating object and the object.

(My personal experience: taking a web page as an example, a time sequence chart can be created for objects that may be involved in a function and the sequence in which it is executed. In short, I can see the time sequence chart, you can understand the implementation steps and corresponding methods of this function to facilitate code writing)

3. Basic Elements

The Modeling Elements of a time sequence diagram mainly include: Object (actor), lifeline (Lifeline), focus of control, and message (there are too many details on the internet, there are not many records here)

Object status: Activation, running, and destruction

Here I will talk about the significance of activation. For this long square lattice, I have never understood what it actually means. I encountered an open-minded explanation on "Baidu Encyclopedia:You can think of activation as a "{}",From the beginning to the end, it can be understood as a method, an action;

The lifeline is used to describe the time when an object exists. Add the destroy symbol below to delete the object or recycle the object. It is actually a Roman's dragon nest. When it's done, let's leave.

There are four types of messages, but it is necessary to write down

1. Common Message: Common hollow arrow, solid arrow; 2. synchronous Message: solid arrow, solid arrow; 3. asynchronous message: Half Hollow arrow, solid arrow; 4. Return message: Common hollow arrow and dotted arrow

The other one is self-Association.

In fact, the sequence diagram is designed here. For web pages as an example, every participating interface, user, and entity class generated by the user can be an object, after you submit a query request or click Delete, you can mark the message delivery sequence and calling method to view the time sequence diagram and write the code.

4. Several tips on Rational Rose

*CTRL + D to deleteToo many delete operations in edit are too dark;

* When copying data to a word,Click Ctrl + C in the blank area and press Ctrl + V on the word tab.You don't need to paste it first (I am so painful ..)

For the time being, simply record the simple application and write UML in the last week. This is a good summary...

Oh, moving is a tough task. You have to take the time to do two small applications. Come on, let's take the time as a cow. Come on...