Learn about object oriented analysis and design book, we have the largest and most updated object oriented analysis and design book information on alibabacloud.com
Pattern (analysis pattern, Architecture Pattern and design pattern) is a topic that we discuss extensively. It is researched to improve software reuse (CodeReuse and design reuse. Model development andOoLanguage development,OOADDevelopment of methodology andUMLDevelopment is closely related. In 20 Century 60 ~ 70 Age, the initial development period of
The object-oriented paradigm is a new and radically different way of thinking about programming, and many people begin to frown on how to construct a project. In fact, we can make a "good" design that leverages all the benefits that OOP offers.Most of the books on OOP analysis and
1. Object-Oriented Analysis The object of object-oriented analysis is the objective world of knowledge and modeling. In fact, in the object
61 military rules of PHP object-oriented analysis design. (1) all data should be hidden inside the class. (2) a class user must depend on the common interfaces of the class, but the class cannot depend on its users. (3) minimize the elimination in the class protocol (1) all data should be hidden inside the class. (2) a
mechanisms of subproblems. Ai-Password analysis-large-scale reuse of blackboard architecture instances Artificial Intelligence generally requires the knowledge base of human beings to approach different AI fields. Data collection-meteorological monitoring station-small systems will also learn from the object-oriented architecture and reveal some basic prin
A summary of 61 PHP object-oriented analysis designs. (1) all data should be hidden inside the class. (2) a class user must depend on the common interfaces of the class, but the class cannot depend on its users. (3) minimize messages in the class protocol (1) all data should be hidden inside the class. (2) a class user must depend on the common interfaces of the
Arthur J.riel once said that you do not have to strictly abide by these principles and will not be sentenced to religious punishment for violating them. But you should think of these principles as alarms, and if you violate one of them, the alarm will ring. So, whatever we do, we have to have a principle. Programming is no exception, the following describes PHPThe principle of object-oriented
From http://www.cnblogs.com/kid-li/ I have been working for three years. To tell the truth, I have never studied Object-Oriented Programming well. I just learned some perceptual knowledge and some so-called theories. I am reading a book "head first object-oriented
human a (" Man "); Yes, he's denatured, so A.setsex (" woman "); Imagine what it would be like if you didn't use the attributes, but what you did with the type? So, when we are building a type system, we need to be clear when we refine it, whether it is a property or a subtype. Variable, is the attribute. Immutable, is the type. Three may not be possibleHere, we analyze the behavior of the object. When we design
number of access methods in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner. (15) Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is that many get and set functions are created in the public interfaces of classes in your application. (16) In an application composed of an object-
frameworks rather than reusable components when creating an inheritance hierarchy. (55) If you use multiple inheritance in the design, first assume that you have made a mistake. If you do not make a mistake, try to prove it. (56) as long as inheritance is used in object-oriented design, I have two questions: (1) i
the design. (13) do not create all-powerful classes/objects in your system. Be especially careful about the classes whose names include driver, Manager, system, and susystem. Plan an interface instead of implementing an interface. (14) Be careful with classes that define a large number of access methods in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner. (15) Be c
of access methods in the public interface. A large number of access methods means that the relevant data and behavior are not centrally stored. (15) Be more careful with classes that contain too much communication behavior. Another manifestation of this problem is the creation of many get and set functions in the public interface of the classes in your application. (16) In an application composed of an object-ori
of access methods in the public interface. A large number of access methods means that the relevant data and behavior are not centrally stored. (15) Be more careful with classes that contain too much communication behavior. Another manifestation of this problem is the creation of many get and set functions in the public interface of the classes in your application. (16) In an application composed of an object-ori
not change operations into classes. Question any class whose name is a verb or a derived Automatic Word, especially a class with only one meaningful action. Consider whether the meaningful behavior should be migrated to an existing or undiscovered class.(21) We often introduce a proxy class when creating an analysis model for an application. In the design phase, we often find that many agents are useless a
system domain.(20) Do not turn the operation into a class. Question any class whose name is a verb or a derived automatic word, especially one that has only a meaningful behavior. Consider whether the meaningful behavior should be migrated to a class that already exists or has not yet been discovered.(21) We often introduce proxy classes when creating an application's analysis model. In the design phase, w
Today, I read the second chapter object model of object-oriented analysis and design, from the first generation of computer to the evolution of object-oriented programming, has undergon
inheritance in the design, first assume that you have made a mistake. If you do not make a mistake, try to prove it. (56) as long as inheritance is used in object-oriented design, I have two questions: (1) is the derived class a special type of the thing it inherits? (2) is the base class part of the derived class? (5
in public interfaces. A large number of access methods mean that related data and behaviors are not stored in a centralized manner. (15) Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is in your application. Program Many get and set functions are created in the public interface of the class. (16) In an application composed of an object-oriented
inheritance in the design, first assume that you have made a mistake. If you do not make a mistake, try to prove it. (56) as long as inheritance is used in object-oriented design, I have two questions: (1) is the derived class a special type of the thing it inherits? (2) is the base class part of the derived class? (5
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
