Skilled programmers are in greater demand, the skill levels required are higher, and software is harder to develop. Yet object-oriented methodologies are over 20 years old. This is not to say that OO can't work. In this article, I'll briefly discuss some reasons that OO has thus far failed to deliver. More importantly, I'll address some ways that organizations with average programmers can achieve high levels of reuse and shorten development cycles.
Less code means faster development and easier maintenance in the future.
Less code also means fewer chances for bugs, so it indirectly affects product quality. However, industry watchers report that there is only 15 percent average reuse in today's object-based projects. OO technology versus one developed using a different technology. This measurement, however, is impossible to perform, as such systems don't exist. Further, a search of the literature turns up no widely-used standards for measuring reuse.