Thinking about Software (i.)---object-oriented, pattern, framework

Object
What is the software? This is a difficult question to explain. Simply put, it's some logical computer code. But from another point of view, it also has many kinds of meanings and many kinds of puzzles. For example, is software a tool? What is the relationship between it and the human mind? Should he have a personality or even a life? What is the future of software? What is the relationship between software and human future?



Humans have been studying computer software for decades, but it is still in the early stages of software development. The development direction of software is not clear, many problems of software itself have been plagued by developers since its inception. People invented a variety of development languages, but also invented the process-oriented and object-oriented two major types of development methods. These are milestones in the development of software, but not enough. For example, the object-oriented methodology, which accurately describes the mapping relationship between the objective world and the software base code, has a very basic meaning. But this is far from enough, just like we build a house, in addition to have bricks, but also need architectural drawings. Object-oriented methodology is the building of the building with bricks, bricks and mortar, the house, or to see the building drawings, we are missing, is a good architectural drawings. So, the light has object-oriented methodology, or just indulge in its research, hope to have good software, is very short-sighted idea.



Well, if a good software design does not refer to an object-oriented methodology, what is it? Where are the good building drawings coming from? Of course, a good way is to learn from experience. This work has been done in a number of ways, such as patterns and frameworks, these are good things, but there are certain limitations, their attention is mainly concentrated in the local, what is made of some components, such as the building of standard parts. A better approach is to focus on the global, creating standard schemas or frameworks at the software level. But this approach, while creating the benefits of rapid development, has lost its individuality, as if one could not tolerate the use of the same drawing in the entire city's house.



How to solve this problem? One approach is to find a framework with sufficient flexibility. The structure of the framework is robust, and it is easy to personalize. Software that uses this framework has a similar structure, but it can meet different requirements. It is as if a city house has a similar look and structure, but it is different, not only boring, but this embodies the style of the city. We now have a similar framework, such as Java EE,. NET, but there is no good embodiment of the above ideas.