OOD using multiplexed elements
Author: gnicky URL: http://blog.9cbs.net/loconfuse/
It is necessary to improve in the process of OOD to make full use of existing builds, or collectively, using multiplexed elements in OO, which is conducive to software organization to increase development efficiency and improve software quality.
Software multiplexing can be divided into different levels such as program code level, design level, and analysis level, corresponding to program code components (class libraries) in multiplexing components, design components (OOD results, well-known description, reasonable detail Description), and different levels such as analysis components. The levels and capabilities of different levels of reusable components in software development reflect the level of software organizations and management levels (requires historical data accumulation to obtain sufficiently multi-reusable components).
The OOD phase should be multiplexed as much as possible, and a clear design representation is given for the multiplexing of the code level member. There are currently many object-oriented programming languages with class libraries. Each class in the class library is a reusable component. In addition, development work may have support for component libraries. The components in the component library may be classes, or the particle size is larger than the class, such as the assembly, user control, etc. in .NET.
When a class defined in the analysis phase, there is a design-level member corresponding to it, then the components should be fully utilized. After all, the reused member is confirmed to have feasible components, and can save a lot of design time. And programming work. This requires the use of multiplexes in the design to properly represent this multiplexing design to the programmer, which should utilize the reusable components of the existing code level.
Consistency of roughly divided the reuse: (These three levels of division only represent my personal point of view, using words may not be appropriate, please understand)
Level 1: Perfect
There is a class of class libraries or components that are fully meticated with the current design system, which is completely transplanted, in the same industry, this multiplexing situation occurs relatively high.
Class name "reuse"
Property 1
PROPERTY 2
Method 1
Method 2
Figure 1 third level
Level 2: Normal
Relative to existing components, the reusable portion accounts for a higher proportion. For the case, it can be an excess information that can be deleted, which may be inherited, which can be partially deleted, partially increased. These descriptions are passed to the developer by the following description. Level 3: confuse
A small amount can be reused, in the decision of two difficulties, it is very complicated to join a reusable method and occupy an important position throughout the class, then you can choose to multiplex. In general, only small partial properties and service can be reused, the differences between the two are very large, and the amount of work saves is negligible, and multiplexes can be considered.
summary:
On this issue, both multiplexing support, also support multiplexed, then consider multiplexing in OOD, must be familiar with the knowledge accumulation of the development organization, support multiplexed libraries, component libraries. At the same time, it is necessary to find multiplexing support from the aspect of the design, which is to support design, support code development.
