Object-Oriented Software Design Principles (I) -- Introduction

The term "Object-Oriented Software Design" and its related topics have become familiar to many developers and even get tired of hearing it. However, to attract attention and attract the attention of the "opposite sex", this topic is still a topic to choose this hot topic as the topic of this blog. Please forgive me. I also hope you can put down the shelf and skip allArticleIf you try again, you can play BS with likes, but do not speak out. After all, you do not want to reduce the Sz of the audience because of the text noise in the seat. You cannot afford to hurt it !!

To get down to the truth, I have been pondering over the question of how to elaborate "Object Oriented Software Design". After all, the proposition is broad, with diverse expressions and levels. In the end, I decided to elaborate on the reading and working experience of this book at a medium level.

The seat was confident in the software architecture (design), data structure andAlgorithmIt is the fundamental core of software and the ultimate standard for measuring the individual's technical level. Therefore, from the very beginning, I paid special attention to the knowledge of software design. The three books I have read here happen to reflect several aspects of software design and development:

• Programming and Development: Design Patterns elements of reusable object-oriented software
• Software Design: Agile Software Development: Principles, patterns, and practices
• System Architecture: Pattern-Oriented Software Architecture

If the software design is not comprehensive at the level of programming and development, it seems that the trees do not see the forest. However, the discussion at the level of system architecture is too professional and the audience is not large, and most readers will be lost. Therefore, this chapter describes the object-oriented software design principles through the notes and experiences of agile software development.

Finally, I want to express an important point of view: the learning process of any knowledge must be "observed" (based on the gourd painting to get the feeling), "broken" (grasp the rules, know how to compare and choose) in the three stages of learning, do not stick to the rules. You need to constantly think about and refine your knowledge based on the actual situation and break through yourself.

• Where does self-confidence come from? It comes from mastering enough knowledge.
• Where does the desire for knowledge come from? It comes from unknown knowledge. Knowledge is like a circle. The more you grasp the knowledge, the larger the circle, the larger the circle.

 

Next chapter: Object-oriented software design principles (II) -- corruption of Software Design

Codeproject