ABSTRACT
This chapter discusses the classes of code and provides recommendations for how to handle them. When structural coverage analysis first identifies noncovered code, the data should be examined and analyzed to determine if it is a requirements problem, a test case issue, or a code issue. Once it has been determined that the noncovered code is truly extraneous or dead, then time must be spent analyzing the impact of code and determining the best solution. Deactivated code is related to extraneous or dead code because it may show up as noncovered code during structural coverage analysis. The definition of extraneous code identifies dead code as a subset of extraneous code. Many developers have learned hard way that rapid removal of dead or extraneous code late in the project's life cycle can be problematic. Deactivated code is often used to create flexible yet fully compliant soft ware. Deactivated code allows configurability of the software to meet the needs of multiple users.
