Software design principles and methods popular understanding

Online has a lot of software design principles of the statement, very accurate, very official, but for some beginners may be unintelligible, to the end of their own depressed, learning software should be a pleasant thing.

So what are the principles of software design ?

(1) Reliability

Make a reliable software, and women find a reliable man, women find men, need a man good quality, good character, reliable, trustworthy, can rely on, tall, and so on. Software design is the same, in the design phase of software should pay great attention to the reliability of software, do not wait until the end of the use of software found here can not be there, or in the use of software in the process of the discovery of the problem may be resumed use, not directly crash.

(2) Robustness

This robustness in fact, there is an English called robustness, which is also in the construction industry, civil engineering industry is often used to describe a building fault tolerance, disaster tolerance of a word, mapping to the software inside the same meaning, such as we use Sogou Input method when the chaos of a pass input, or still can remain stable, Another example in some Information system input box input system can not accept the field, the system to give the corresponding hint, and so on, in fact, robustness can not be accurately expressed in language, but a software is robust, very much depends on the soft test development and testing personnel level.

(3) modifiable

This is better understood, meaning is not to write some messy code, no comments, or the interaction between functional modules, logic is unclear, so in the software version upgrade changes when I am afraid even I do not know how to change, let alone others!

(4) Easy to understand

Software has a reliability and can be modified to talk about easy to understand, such as the software itself has a relatively concise structure, designers can be complex business model to abstract into a simple software model implementation, which requires a very deep skill, but also the difference between code farmers and engineers.

(5) Efficiency

The efficiency of the software is generally measured by the execution time of the program and the amount of memory consumed. In the premise of achieving the principle requirement function index, the shorter the program running time and the smaller the storage capacity, the higher the efficiency. In the case of limited resources, the efficiency of software operation is very test of a person's level.

(8) Principles of standardization

The structure of open, based on the industry open standards, in line with the national and Ministry of Information industry norms. To be blunt is not the whole set of interfaces or specifications, or the use of some of the technology or standards of the gate, when the system integration or function expansion of the pain.

(9) Advanced

Meet customer needs, system performance is reliable, easy to maintain.

(10) Scalability

Software design to leave the upgrade interface and upgrade space. Open to extensions, closed for modification, meaning that new functionality can be extended without modifying the original functionality.

This article from "leisurely See Nanshan" blog, please be sure to keep this source http://rudypine.blog.51cto.com/8296651/1782675

Software design principles and methods popular understanding