How to read the summary of the code base group discussion

How to read large applicationsProgramCode base? We talked about it within the project team. To sum up the following:

1. Draw a UML class districh (umlassketch) and a higher-level abstract-level diagram to help you understand and summarize it. The principle is: Just do what makes things work! There is no need to consider the UML standard issue. It is enough to draw a picture to help you and others understand the problem. For example, it is difficult to draw a sequence chart. What's moreCodeThe level is relatively low. Therefore, generally, it is not easy to draw a picture. A graph can be used to express the thought you want to express.

2. The basic idea is: to understand the hierarchical architecture of the entire app + to understand more implementation details from top to bottom with a specific example and to deepen the understanding of the entire architecture.

3. to solve a problem, when you need to understand the code of a certain aspect, do not immediately start to look at the code. Instead, you should first think about it: If I implement it, what will my solution be? It may be the same as the author's idea, so it will be faster to understand. It is really a good idea.