A system with a high coupling degree is a negative example. There are many reasons for the high coupling of the system, one of which is what I encountered:Confuse System Process Analysis with System Structure Analysis.
In fact, this sentence has been mentioned in any system analysis book, so why is this mistake easy to make.
Take the system I designed as an example:
In the "Project Planning" module, there is a class uiysgq (yangshui irrigation area), which inherits from windows. Forms. Control, that is, this class must respond to user operations. In my initial design, I put all the data processing in the "yangshui irrigation area" in uiysgq. In the initial design, the data in the "yangshui Irrigation Area" can only be processed here. Therefore, put the processing code in uiysgq as follows:Take it as a matter of course.
When the system is finished, the customer proposes another operation mode, that is, to put the "yangshui Irrigation Area" data as a subset in another user response interface, the problem arises. Because the data in the "yangshui irrigation area" is not encapsulated, it is necessary to rewrite the data in the "yangshui Irrigation Area" on that new interface.
In fact, this problem is clearly described in the basic object-oriented programming idea, but why is it still ignored by me?
The reason is that I directly analyzed the "System Process" as the basis of "system architecture design.
"System flow" is a form class that is easy to think of. If we design it based on it, it is easy to bind Data Processing and interfaces together, this error occurs. This gave me a deep taste of the pain of the process-based design wizard.
Where can I solve this problem? I am afraid to raise my mind. I just want to talk about my own opinions.
After obtaining the system flow, you need to analyze the objects (classes) in the system and determine the relationships (methods, events, and attributes) between objects ), the analysis results are then used for system design. I am too simple here, because my research in this area is not very in-depth, but I think this is a correct direction.
There are many methods to analyze the system. Here we just remind you: do not fall into"Confuse System Process Analysis with system structure analysis".