Shulou(Shulou.com)06/03 Report--

There are a lot of opinions about software design principles on the Internet, which are very accurate and official, but for some beginners, they may not know what to say. In the end, they are depressed, and it should be a pleasure to learn software.

So what are the principles of software design?

(1) Reliability

To make a reliable software, just like a woman looking for a reliable man, a woman needs a man with good quality, good character, reliable, tall, and so on. The same is true of software design, in the design stage of the software, we should pay great attention to the reliability of the software, do not wait until the final use of the software here and there, or in the process of using the software can be restored once a problem is found, can not just crash.

(2) robustness

In fact, this robustness is called robustness in English, which is also a word commonly used in the construction industry and civil engineering industry to describe the fault tolerance and disaster tolerance of a building. It also means the same when it is mapped into the software. For example, when we use Sogou Input, we can still keep it stable. For example, enter fields that the system cannot accept in the input box of some information systems. The system can give corresponding hints, and so on, in fact, robustness can not be accurately expressed in language, but whether a software is robust or not depends very much on the level of soft test developers and testers.

(3) can be modified.

This is easy to understand, which means don't write some messy code without comments, or the interaction between functional modules is complicated and illogical, so I'm afraid I don't even know how to change it when the software version is upgraded and changed, let alone someone else!

(4) easy to understand

Only when the software is reliable and modifiable can it be easily understood. For example, the software itself has a relatively concise structure, and designers can abstract complex business models into simple software models. This requires a lot of skill, and it is also the difference between programmers and engineers.

(5) efficiency

The efficiency of software is generally measured by the execution time and memory capacity of the program. On the premise of meeting the functional specifications required by the principle, the shorter the time required for the program to run and the smaller the storage capacity, the higher the efficiency. In the case of limited resources, the efficiency of software operation is a great test of a person's level.

(8) Standardization principle

To achieve openness in structure, based on open industry standards, in line with the norms of the state and the Ministry of Information Industry. To put it bluntly, do not use your own whole set of interfaces or specifications, or use some partial technologies or standards, which will be painful when system integration or function expansion occurs.

(9) Advanced nature

Meet the needs of customers, the system performance is reliable, easy to maintain.

(10) scalability

After the software design, there should be upgrade interface and upgrade space. Open for extensions and closed for modifications, which means that new features can be extended without modifying the original functionality.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.