FURTHER READING For an excellent discussion of problems
FURTHER READING For an excellent discussion of problems with lines-ofcode measurements, see Programming Productivity (Jones 1986a). 26.3 26.4 26.4 Measurement’s Interactions with Other Practices Misleading information from lines-of-code measurements. Most measurement programs will measure code size in lines of code, and there are some anomalies with that measurement. Here are some of them: Productivity measurements based on lines of code can make high-level languages look less productive than they are. High-level languages implement more functionality per line of code than low-level languages. A developer might write fewer lines of code per month in a high-level language and still accomplish far more than would be possible with more lines of code in a Iow4evel language. Quality measurements based on lines of code can make high-level languages look as if they promote lower quality than they do. Suppose you have two equivalent applications with the same number of defects, one written in a high-level language and one in a low-level language. To the end-user, the applications will appear to have exactly the same quality levels. But the one written in the low-level language will have fewer defects per line of code simply because the lower-level language requires more code to implement the same functionality. The fact that one application has fewer defects per line of code creates a misleading impression about the applications’ quality levels. To avoid such problems, beware of anomalies in comparing metrics across different programming languages. Smarter, quickerways ofdoingthingsmay result in less code. Also consider using function points for some measurements. They provide a universal language that is better suited for some kinds of productivity and quality measurements. Side Effects of Measurement The main side effect of a measurement program is that what you measure gets optimized. Depending on what you measure, you might end up optimizing defect rates, usability, execution efficiency, schedule, or some other factor. Measurement’s Interactions with Other Practices A measurement program provides the foundation for improvement in areas including estimation (Chapter 
, scheduling (Chapter 9), and productivity- tool evaluation (Chapter 15). Although it is possible to design a measurement program so that it undercuts a rapid-development project, there is no reason that a well-designed measurement program should interact negatively with any other practice.
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.