head first object oriented analysis and design

direction as much as possible, that is, the top-level classes should share work in a unified manner according to 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 num

61 empirical principles of Object-Oriented Design Excerpted from the log of OOD, translated by BaO zhiyun, Arthur J. Riel "You do not have to strictly abide by these principles and violate them and are not subject to religious penalties. But you should regard these principles as warning bells. If you violate one of them, the warning bells wi

The maintainability and reusability of softwareRobert C.martin, a well-known software guru, believes that a low-maintainability (maintainability) software design is typically caused by the following 4 reasons: Too stiff (rigidity) Too fragile (fragility) Low reuse rate (immobility) High viscosity (Viscosity) The software engineering and modeling guru Peter Coad believes that a good system

in object-oriented design, ask yourself two questions: (1) is the derived class A special type of the thing it inherits from? (2) is the base class part of a derived class?(57) If you find multiple inheritance relationships in an object-oriented

the outside world.In General , process-oriented development is relatively easy, but it is not easy to deal with changes, object-oriented development is difficult, but it can better deal with the ever-changing world. Therefore, the modern software needs object-oriented devel

horizontal direction, the system functions should be distributed as much as possible. That is, according to the design, the top-level classes should share work in a unified manner. P30 (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. P30 Plan an interface instead of implementing an interface.

, structures and themesClass and object layer: How to build a basic blockAttribute layer: An object's properties and instance joinsService layer: The service of the object, plus the composition of the message communication between the object instancesStructural layer: Describes the general--special structure or generalization--specialization structure, generaliza

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 in your application.ProgramMany get and set functions are created in the public interface of the class. (16) In an application composed of an object-

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 in your application.ProgramMany get and set functions are created in the public interface of the class. (16) In an application composed of an object-

a unified manner according to 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 central

is, the top-level classes should share work in a unified manner according to the design. P30(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. P30Plan 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 re

Content Overview 1. describes the design process of Object-Oriented Analysis Based on UML. 2. What charts and the functions of each diagram are included in the UML object-oriented model? 1. describes the

Just like the location of Newton's three major laws in classical mechanics, the open-closed principle is the cornerstone of object-oriented reusable design (Object Oriented Design or OOD. Other

Analysis on the model of data object mapping in PHP design mode and its design pattern PHP in the design pattern has a lot of different patterns, here we introduce a less common data mapping mode, I hope the article can help you. The data mapping pattern allows you to bette

classes in the system domain. (20) do 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 of

need to implement personality, the specific object will be called.Encapsulation of ClassesThe responsibilities of low-level modules should not be done by high-layer modules, or the encapsulation of classes will be broken.The specifics of the encapsulation of classes in a program are:1. Duplicate the object that defines the class.2. Cross-use of various kinds of objects, the correct usage is that after one

Software Engineering--the design of the face object of theory, method and practiceIn the phase of object analysis, it is necessary to focus on what the system does, while in the design phase, it will focus on the software implementation of the system, including architecture

your system. Be especially careful with classes whose names contain driver, Manager, System, Susystem. Plan an interface instead of implementing one. Be careful with classes that have a large number of access methods defined in the public interface. A large number of access methods means that the relevant data and behavior are not centrally stored. Be cautious about classes that contain too many non-communicating behaviors. Another manifestation of this problem is that many get and set func

/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. 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. Be careful with classes that contain too many non-communication behaviors. Another manifestation of this problem is

Just like the location of Newton's three major laws in classical mechanics, the Open-Closed Principle is the cornerstone of object-oriented reusable Design (Object Oriented Design or OOD. Other