Extended:
1 repair of extended targets (delete, add, modify)
2 Replacement (full part replacement)
3 Retrofit (Add new function (function interface))
Expansion ideas:
Reference vehicle repair real-world expansion model
In the case of classes, when we write classes, we can write them apart, which is an object-oriented feature.
But when using, it is necessary to have data interaction, then how this class should be used, in order to easily expand it, that is, to
Corresponding solutions for each or one of the extension types (the essence of tangling, the present sex)
Write code is fundamental, the policy of package change with configuration file annotation is contrary to nature----should be encapsulated in change class, module, layer
A consistent pattern of hierarchical thinking is needed to allow for the expansion of the new new framework model that does not appear.
Data interaction without order
Orderly data interaction
Data interaction between methods
Data interaction between classes
Data interaction between modules
Data interaction between tiers
"Class interface" mode is feasible
Implementation of basic extensions, inheritance-polymorphism, policy mode, reflection
Basic considerations for decoupling, 6 types of relationships, dependencies, associations, aggregations, combinations, inheritance, implementation
From this point of view, the basic extension class belongs to the extension of the underlying code implementation, "Class interface" class belongs to the extended business logic implementation
Tool class, as the underlying class of the participating part of the business logic class, such as---validation class---A number of business logic classes require a partial call to the validation tool class
A functional implementation class that is used to completely construct the underlying class of the business logic class, such as---additions and deletions to the DAO class---The Business logic class that is modified by the actual conditions and additions
What is included in the extension