Welcome to the InfoSci Platform
Reference Hub3
Handling of Software Quality Defects in Agile Software Development

Handling of Software Quality Defects in Agile Software Development

J. Rech
Copyright: © 2007 |Pages: 24
ISBN13: 9781599042169|ISBN10: 1599042169|ISBN13 Softcover: 9781616927615|EISBN13: 9781599042183
DOI: 10.4018/978-1-59904-216-9.ch005
Cite Chapter Cite Chapter

MLA

Rech, J. "Handling of Software Quality Defects in Agile Software Development." Agile Software Development Quality Assurance, edited by Ioannis G. Stamelos and Panagiotis Sfetsos, IGI Global, 2007, pp. 90-113. https://doi.org/10.4018/978-1-59904-216-9.ch005

APA

Rech, J. (2007). Handling of Software Quality Defects in Agile Software Development. In I. Stamelos & P. Sfetsos (Eds.), Agile Software Development Quality Assurance (pp. 90-113). IGI Global. https://doi.org/10.4018/978-1-59904-216-9.ch005

Chicago

Rech, J. "Handling of Software Quality Defects in Agile Software Development." In Agile Software Development Quality Assurance, edited by Ioannis G. Stamelos and Panagiotis Sfetsos, 90-113. Hershey, PA: IGI Global, 2007. https://doi.org/10.4018/978-1-59904-216-9.ch005

Export Reference

Mendeley
Favorite

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.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.