object oriented design book

same way through a common class.These three characteristics are also the basis for understanding the five principles of object-oriented design.The Five principles of object-oriented design ( These five principles are also the basis of 23

I'm just a bean before I know the 7 principles of object-oriented design! But the beans will eventually grow, don't they?1. Opening and closing principle : A software entity should open to the extension and close the modification. In other words, when a module is involved, it should be allowed to be extended without modification, that is, to change the behavior o

phase, the analyst only gives some textual description according to the user's request, in the design phase, the designer will make the screen visualization of these general descriptions, and may also consult the relevant technical experts; Before programming, the user's visual prototype should be further improved by graphic artists and behavioral artists to achieve The "user-friendly" definition standard; The implementation phase, the program develo

direct interaction, if necessary, can use a third party to forward the call. Our unique unique knowledge is the introduction of a façade object that provides a single, simple barrier between subsystems. Usually the three-layer or N-layer architecture of enterprise software, the separation between layer and layer is actually the embodiment of the appearance pattern.Enjoy meta mode, outraged, yell, let me try: objects make memory consumption too much.

1. Object-oriented design 1.1 Understanding object 1.1.1 Property Type(1). Data properties: A field that corresponds to an object that contains the position of a data value, where the value can be read and written. There are 4 attributes in the data attribute that describe t

involves the overall organization of software systems, global control, data access, and communication protocols between subsystems. In the MVC structure, the subsystems are divided into three types: model, view and controller.System design mainly describes the identification of design elements, data storage strategy, deployment subsystem and system design review

Labels: Object-oriented Design Principles After the previous in-depth explanation, we have basically made it clear about the solid principle. However, if you want to skillfully apply the solid principle, it is not enough to know what the solid is, we also need to know when and when the solid principle is applied (when or where ). Fortunately, the five independen

modified content, date, and modifier must be specified. 2 Glossary The terms used in this document are described. If some terms have already been described in the requirement specification, you do not need to repeat them here. 3 Use Cases The use case diagram (UML) must be used to describe each use case (normal processing) in Chinese. 4. design overview 4.1 Brief Introduction This part requires highlighting the methods used by the entire