best books on design principles

Article Description: The designer's creativity is infinite, but the user's navigation demand is fixed, any style, as long as can meet the navigation principle several requirements, can complete the user's navigation task. The easier way is to find the page path in the page element, which is equivalent to satisfying the navigation principle. Such principles and methods can be used to test whether our design

absolutely necessary for the documentation of SQL expressions; 5 Define the standard object naming conventions. 2, table and field design　　 1) Table Design principles (1) standardization and normalization; The standardization of data helps to eliminate data redundancy in the database. There are several forms of standardization, but third normal Form (3NF) is of

The open-closed principle was mentioned in the previous blog post, not in detail. This time, let's summarize some of the principles of design patterns.1 Open-closed principle: refers to the software entities (classes, modules, functions, etc.) should be able to expand, but can not be changed.The principle of understanding: the opening and closing principle is the most idealistic color of a principle, it is

Design principles include: 1. Single responsibility principle, 2. Lee's replacement principle, 3. Dependency inversion principle, 4. Interface isolation principle, 5. The dimit law, 6. Open and Close principles. 1. Single Responsibility PrincipleSingle Responsibility Principle, SRP ): There shoshould never be more than one reason for a class to change. For a cl

In all the revolutions that have taken place in the software industry, two factions were once so widely rooted in the hearts of the people, structured programming and object-oriented programming. All mainstream modernProgramming LanguageBoth of them are under intense influence. In fact, if you don't want to write it like structured and object-oriented programmingProgramIt is a hard task. None of our mainstream programming languages are Goto, so they are subject to the most important prohibitions

no difference, but the problems will be exposed in the development stage. Let's look at two basic design principles. [Simplified aggregation] The design principle of streamlining aggregation is undoubtedly the most important. Some Software Engineering Methodology books often guide us in UML business modeling,"No techn

reconstruction, etc.), according to the plan to do the relevant product research work, because the prophase products do not have related documents, to the work brought a lot of inconvenience. But also to the system to maximize the idea of open, in the process, seriously feel "experience" important. If you have ever used or participated in the construction of a similar system platform, that would be much better. For a time do not know how to start, a period of very distressed. But now that it's

submodule or business logic;Through the business logic compression interface in the public method, the interface often to review, as far as possible to get the interface to "flesh", rather than "fat doodle" a lot of methods;has been contaminated with the interface, as far as possible to modify, if the risk of a large change, the use of adapter mode for conversion processing;Understand the environment and refuse to follow blindly. Each project or product has specific environmental factors, don't

I. Principles of text design 1. Text readability:The main function of text is to convey the author's intention and various information to the public in visual communication. To achieve this goal, we must consider the overall appeal of the text and give a clear visual impression. Therefore, the text in the design should be easy to recognize and understand, and

I read "big talk Design Patterns" and extract the principles of the design patterns mentioned in this book for future use. I. Single Responsibility Principle For a class, there should be only one reason for its change. If a class has too many responsibilities, it is equivalent to coupling these responsibilities. A change in responsibilities may weaken or suppress

Six Design Principles Single Responsibility Principle Rys replacement principle Dependency inversion principle Interface isolation principle Dimit Law Principle of opening/closing 1. Single Responsibility Principle) Single responsibility, SRP for short. The definition of a single responsibility is: there should be only one reason for class changes. The most difficult part

Translator's words : For designers, poster design can be said to be the most exciting thing, because the poster form a variety of forms, broad themes, less restrictive, emphasizing creativity and visual language, point line, picture and text can be flexibly combined application, but also pay attention to the composition of the plane and color composition. It can be said that poster design is a synthesizer o

Design principle one : single principle of responsibility Definition: There should be only one reason for a class to cause it to change. Advantages: Reduce the complexity of the class, improve the readability of the class, improve the maintainability of the system. Example: Super Human public class Superman {public void Maintains world peace () {//Superman maintains world Peace}} Extension: public class Animal {Public void Breathe (String animal) {Sys

. Dependency inversion principle: high-level modules do not depend on low-layer modules, both of which are dependent on abstraction. Or just the example: Duck is a high-rise module, Fly is a low-level module. Duck does not depend on fly, the high-rise module changes slowly, while the lower-level modules change slowly.Abstractions should not be dependent on implementation details, and implementation details should be dependent on abstraction. Fly is an abstraction, it does not depend on how to fl

1. Overview Dr. Roy Fielding (see Personal homepage) is the main designer of the HTTP and URI protocol issued by the IETF. HTTP and Uri are the two most important web infrastructure protocols, so Dr. Fielding is one of the founders of the Web architecture. In addition to academic excellence, Dr. Fielding has been involved in the design and development of many Open-source software. He was the developer of Libwww-perl, one of the world's earliest HTTP

Tags: efficiency file Cap File System Runtime design principles Description Program implementation recommendations1. Relationship between the original document and the entityCan be a pair of one or one-to-many, many-to-many relationships. In general, they are one-to-one relationships: a single original document corresponds to and corresponds to only an entity.In special cases, they may be one-to-many or man

attribute Name: type [= default value] Visibility method Name (parameter list) [: Return value type] Examples are as follows: (3) The relationship between classes ① Association Relationship 1) bidirectional correlation. Examples are as follows: 2) One-way association. Examples are as follows: 3) Self-correlating. Examples are as follows: 4) Multiple sexual associations. Examples are as follows: 5) Aggregation relationship. Examples are as follows: 6) combined relationship. Simi

The so-called No recruit wins a recruit, practice a kung fu divides into internal strength and drilling.Drilling is like the moves, is the so-called 23 kinds of design patterns. But the internal strength, is the heart, that is the 6 kinds of laws. Light will drilling that is huaquanxiutui, the internal strength is the situation.So many design patterns, learned 2 times. 3 times you'll probably forget just th

Design principles applicable to all regions (1) One design is suitable for one project but not necessarily for another project. It is unrealistic to grasp the various designs applicable to each project. Experience tells us that using rules can help our brain take control of more things. Similarly, with the help of design