When all the veterans of the total work program can not only write it, account of the above might be planning a new system task, then the old bird advantage in terms of experience it is easy to show it, especially thinking system depth architecture.
When planning the system, in addition to the user's needs, appropriate design software architecture (architecture) will let programmers in the future under the more relaxed when composing or maintenance procedures, and software architecture is like the system as a house, every systems have their own architecture, and architecture will become the future development direction of the guidance and the same specification and method of blueprint, and it is a bit like Framework sense, but in essence it is different.
The so-called software architecture (Software Architecture) is a blueprint for a piece of software that tells you the software structure, function, interface, usage, and other system configurations, and even data exchange specifications and so on , but it does not tell you to use What practical way, the software architecture typically produce documents, drawings, prototypes and specifications, the program is not available, because it is not a software architecture should have something like the house was built is to give you a blueprint, not a cover good house. In contrast, software framework (Framework) is the English name of the original intent of the skeleton, break it is "Frame" - "work", is expressed in an established framework can do the job , that is to say, this is already shaping a method, and a program instances (such as steel construction method is to have the steel to do), and will tell you how to use it (ie a perfect example Framework Documentation, MSDN Library that is), but how to use it is the programmer (that is, overseer) work, regardless of the Framework.
Therefore, the need for software architecture design is one of many working knowledge and experience, previously shared are part of the object-oriented thinking and thinking and so on which the construction of large systems, there are some like interface-oriented programming, the ability to abstract , hierarchical thinking, the idea of adapting the environment, or the network system integration and so on, almost always touches on some of the architectural design software, so the more knowledge accumulated in the architectural design will be more helpful. In the past, the school will read how many things come in handy, work will use the domain knowledge, design pattern, enterprise pattern and experience will play a significant role.
There are also many books have to tell the software architecture, there are a lot of sample solutions, will indirectly show direct architecture of a system design approach on the network may be more to touch these things, will help software architecture evolutionary thinking.
Reference: http://www.dotblogs.com.tw/regionbbs/category/2520.aspx
Original: Large column [Sui Suinian] program development areas by the rookie to the veterans of the growth process (27) - veterans stage - thinking architecture.