Problems encountered in Software Design

Some pure software problems encountered during the recent development of a project;
1. The functional division of the entire software is clear at the beginning, but ProgramAs well as some structural adjustments, the relationship between various modules is getting closer and closer, especially the Event-related logic, map analysis, real-time event alerts, historical event queries, event playback, etc, all events are used, and all events must be read. This results in strong coupling between these modules.
2. Some classes have clear functions at the beginning, but with the later modification of the program and the addition and deletion of functions, there are too many class responsibilities, some classes have less responsibilities. The functions of many classes gradually do not match their names.
3. the naming of classes, functions, and member variables is also a bit messy. The main reasons are as follows: Sometimes, in order to complete a function as soon as possible, it is too late to come up with a good name, it may have been intended to be modified after writing, but I don't want to change it because of the inertia. For a type of name, a convention is used at the beginning, later, I felt that another kind of convention was better, and another kind of convention was adopted. However, the previous one was not modified, which resulted in inconsistent naming rules.
4. Sometimes I just find a class stinks and wants to reconstruct it by intuition. But if I really want to do it, I often feel that I have no idea how to do it, this may be due to the lack of principles in my personal thoughts, and I do not know how to deal with a certain type of things. I used to think that learning to use some models is almost the same, but now it seems that these models are far from enough, so one is to master more models, in addition, we should add something else, so nothing can be said for the time being.