Revalidation during the software maintenance phase
- 7 January 2003
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
Abstract
Software maintenance requires altering programs as a result of errors or changes in user requirements. However, during such modifications new errors may be introduced, causing unintended, adverse side effects in the software. Testing can prove to be expensive in terms of both human and computational resources. An examination is made of current selective retesting strategies which attempt to reduce such effort. Their advantages and limitations are described and a discussion is given of how these strategies could be extended and developed into a practical retesting tool allowing maintenance personnel to cope with large-scale revalidation procedures.<>Keywords
This publication has 8 references indexed in Scilit:
- Ripple effect analysis of software maintenancePublished by Institute of Electrical and Electronics Engineers (IEEE) ,2005
- Approaches to regression testingPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1988
- Partition Analysis: A Method Combining Testing and VerificationIEEE Transactions on Software Engineering, 1985
- Program SlicingIEEE Transactions on Software Engineering, 1984
- Theories of Program Testing and the Application of Revealing SubdomainsIEEE Transactions on Software Engineering, 1980
- Dave—a validation error detection and documentation system for fortran programsSoftware: Practice and Experience, 1976
- A Branch-and-Bound Algorithm for Zero-One Mixed Integer Programming ProblemsOperations Research, 1971
- A Theorem on Boolean MatricesJournal of the ACM, 1962