presentation zen design

Conceptual summary of Design principles Read the design patterns of Zen, the design principles to do a summary of the concept, if you want to better understand, or to see the specific details, this side can only be a rough summary, as a learning note. Principle of single responsibility English Name: Single Responsibili

Preface The Zen of design patterns is tied to this book. When I went to the library to borrow a book in the next semester of my junior year, I saw a new book with a title containing the word "Zen, at that time, he was infatuated with Steve Jobs. Therefore, whatever the messy content it writes, you can use it to get it back to the dormitory. Next, during the summe

Preface "Zen of design patterns" saw 78th pages. Continue to stick to it! As a creation-type design model, the factory method model is frequently used. Therefore, the learning of this model is quite valuable. So what is the definition of this mode? What is the implementation of this mode? What is the role of this model? I will do everything possible for readers t

is metadata? The data used to describe the environment and data, in layman terms, are configuration parameters that can be obtained from a file or from a database.-----> Develop Project Charter(1) Norm-setting, unified style programming-----> Package Changes(1) The package of changes contains two meanings: first, the same change is encapsulated in an interface or abstract class. Second: The different changes are encapsulated in different interfaces or abstract classes, and there should not be t

day good face is also beautiful still need to modify, this time, there is a big kill device appeared-the design is limited, can not indefinitely consider the future change situation, otherwise it will fall into the mire of design can not extricate themselves.Maintain the purity of the interface1, the interface as small as possible, with a single responsibility conflict priority to consider the principle of

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

- Letterprocess.fillenvelope (address); + //Pack Envelopes A Letterprocess.letterinotoenvelope (); at //Send a letter - Letterprocess.sendletter (); - } -}View Code"4" Client test1 PackageCom.yeepay.sxf.template18;2 /**3 * Client Testing4 * @authorSXF5 *6 */7 Public classClienttest {8 9 Public Static voidMain (string[] args) {Ten //Letter of Business class OneIletterprocess letterprocess=NewLetterprocessimpl (); A //Letter of Business class façade c

weigh repeatedly, not only to make the structure clear, but also to achieve high cohesion and low coupling.---> Dimitri Law requires decoupling between classes, but the decoupling is limited, the principle is only for reference, if it violates this principle, the project may not fail, which requires you to use the principle of repeated measures, do not follow is not correct, strict implementation is "too bad."Iv.: Central idea(1) in a scene, the A,b,c class. Complete a goal. A relies on b,b to

type T, and the return value of the same method (overloaded or overridden) of the subclass is S, then the Richter substitution principle requires s to be less than or equal to T. 3. Dependency inversion principle (DIP): The high-level module should not rely on the bottom low-layer module, both should rely on its abstraction; Abstraction should not depend on details; Detail should be dependent on abstraction. The dependency of a PS object is passed in three waysOne, the construct

Preface Today, I started to learn the first mode of 23 design modes-singleton mode. I have read many blog posts about Singleton mode on the Internet. Today, I am going to explain the design patterns in the Zen of design patterns. The author is still very careful. The only pity is that the author explained the singleton

PackageCom.yeepay.sxf.template15;2 /**3 * Collection Interface4 * @authorSXF5 *6 * @param7 */8 Public InterfaceAggregate {9 Public voidAdd (E object);Ten Public voidRemove (E object); One PublicIterator Iterator (); A}View Code"4" Custom collection implementation1 PackageCom.yeepay.sxf.template15;2 /**3 * Custom Collections4 */5 Importjava.util.ArrayList;6 Importjava.util.List;7 8 Public classMyconnectionImplementsAggregate{9 PrivateListNewArraylist();Ten One @O

} - - the}View Code"4" policy wrapper1 PackageCom.yeepay.sxf.template13;2 /**3 * Policy Wrapper4 * High-level module invocation is very simple,5 * know which strategy to use, produce its object, and then put it in the wrapper role to complete the task.6 * @authorSXF7 *8 */9 Public classContext {Ten One PrivateStrategy strategy=NULL; A - PublicContext (Strategy strategy) { - This. strategy=strategy; the } - //Kam SAC Performers - Public voi

Summary No program can run without a user interface. Even if the middle-Layer Code is perfect, users cannot use it. Many architects do not pay much attention to the presentation layer. They only process the presentation layer as a detail after the business layer and data access layer are completed. However, the user interface, business logic, and data access code are equally important in any system. Your at

*/ at Public voidaction () { - This. Command.Execute (); - } -}View Code"6" Client1 PackageCom.yeepay.sxf.template10;2 /**3 * Client Class4 * @authorSXF5 *6 */7 Public classClient {8 9 Public Static voidMain (string[] args) {Ten //first declare the caller Invoker OneInvoker Invoker =NewInvoker (); A //define a recipient -Receiver receiver=NewConcreteReciver1 (); - //defines a command sent to the recipient. theCommand command=NewConcreteC

did something"); - Super. Operate (); -System.out.println ("Concretedecorator1.operate () Decorator 1 did something"); - } + - +}View CodeThe role of "5" Decorator 21 Packagecom.yeepay.sxf.template12;2 /**3 * Decorator 24 * @authorSXF5 *6 */7 Public classConcreteDecorator2extendsDecorator {8 9 PublicConcreteDecorator2 (Component Component) {Ten Super(component); One } A - @Override - Public voidoperate () { theSystem.out.println ("Concretedecora

- order1.addbordinate (bin1); - order1.addbordinate (bin2); - order2.addbordinate (bin3); in order2.addbordinate (BIN4); - leard.addbordinate (order1); to leard.addbordinate (order2); + - //to traverse theListleard.getbordinate (); * for(Componentcorp c:list) { $ Panax Notoginseng if(cinstanceofLeaf) { - //It's soldier . theSystem.out.println ("Clienttest.main (soldier)" +c.getinfo ()); +}Else if(cinstanceofBranch) { A

Some time ago, I finally got my long-awaited book "Zen of design patterns", but for work reasons, there is no time to calm down and savor the Zen words from my work practices. I put this book in front of my bed. Whenever I go to bed, I will flip it over. I have read some books on design patterns before, but I want to g

stories" of the Bible ". This book is the "Zen" of the Bible. It is not as esoteric, obscure, or difficult as the Bible, because of the treasure of words such as gold and character, it is more profound and comprehensive than the "Comments" version of the "Bible", more popular and vivid, closer to the practical scenarios encountered by developers, and more instructive. This book is a milestone in the field of desi