Handling of Software Quality Defects in Agile Software Development

Handling of Software Quality Defects in Agile Software Development

J. Rech (Fraunhofer Institute for Experiemental Software Engineering (IESE), Germany)
Copyright: © 2007 |Pages: 24
DOI: 10.4018/978-1-59904-216-9.ch005
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Software quality assurance is concerned with the efficient and effective development of large, reliable, and high-quality software systems. In agile software development and maintenance, refactoring is an important phase for the continuous improvement of a software system by removing quality defects like code smells. As time is a crucial factor in agile development, not all quality defects can be removed in one refactoring phase (especially in one iteration). Documentation of quality defects that are found during automated or manual discovery activities (e.g., pair programming) is necessary to avoid wasting time by rediscovering them in later phases. Unfortunately, the documentation and handling of existing quality defects and refactoring activities is a common problem in software maintenance. To recall the rationales why changes were carried out, information has to be extracted from either proprietary documentations or software versioning systems. In this chapter, we describe a process for the recurring and sustainable discovery, handling, and treatment of quality defects in software systems. An annotation language is presented that is used to store information about quality defects found in source code and that represents the defect and treatment history of a part of a software system. The process and annotation language can not only be used to support quality defect discovery processes, but is also applicable in testing and inspection processes.

Complete Chapter List

Search this Book:
Reset