Outline and principle of structured design -- modularization

---

The technology is average   No mapping   Forgive !!!

How to do a good job of modularization in the process of software development is a problem worth thinking .

Before thinking about it , I have done some refactoring of the project code in my current work , The refactoring principle I set for myself is , Divide the modules according to the single responsibility . In function splitting, the code lines with independent function structures are split into a function and encapsulated into an interface .

Before I see the picture above , I don't think I'm wrong , But the picture above triggered my thinking , Is there a problem with my split principle , According to written knowledge, it seems to be flawless , One of the principles of object-oriented design is the principle of single responsibility . But affairs always bring negative effects where they bring benefits , Excessive splitting leads to more interfaces in the process of module calling . Interface costs also increase . That's a problem , So how do we split modules .

There are also some suggestions without nutrition , I feel sick of myself ：

1 Resolution principle , Or according to the knowledge in books -- Principle of single responsibility .

2 Specific implementation , Divide and merge functions according to business scenarios , And then split it .

3 Some business independent tool modules can be split as fine as possible , These things accumulate into wealth , The thinner it is, the easier it is to be reused .

... Follow up to add