Agile design is simple and flexible

Agile design is designed to solve complex software and increase and change requirements in the development process. By the way, it seems that every time I say agile, I will improve my changes. Yes, I think this term is one of the important reasons for the software crisis, design principles, design patterns, and agile development.

Agile design requires simplicity and flexibility, which seems to be a conflict.

How is it simple? The so-called simplicity means to use the most common class as much as possible when solving the problem. If you can use a common class to solve the problem, you do not need to use inheritance, polymorphism, and some complex implementation methods. If the current solution can solve the current iteration story, it is enough to solve these iteration stories. There is no need to consider too many extensions, but the following stories and possible extensions based on empirical analysis should be considered a little, but not too much. In the future, when we really expand or implement the following story, we will apply refactoring to bring new functions into the system.

What is flexibility? When there are some special problems or there may be some possible extensions based on experience, some extended interfaces will be left behind. We also observe some design principles and patterns during design. These are called principles and patterns because they are observed by everyone.CodeAfter using these models, everyone can clearly understand their intentions and increase the readability of the system code. However, if these design principles are violated and Some uncommon solutions are used, the system code may be poorly readable and understandable.

In fact, during system development, many rules and regulations are for our reference. As for how simple the system is and how flexible the system structure is, this may have a lot to do with the actual system and the experience of the designer.