Testing in the software development life-cycle : now or later
By: HUK, Faizul
.
Material type: 
ArticlePublisher: aug. 2000Subject(s): Software Development | Concurrent Testing | Life-Cycle Cost | Simulation | TQM | ReliabilityInternational Journal of Project Management 18, 4, p. 243-250Abstract: The most critical and visible principle of TQM in the Information System (IS) environment is the focus on zero defects in a software develpment project to achieve customer satisfaction. This paper presents results from a simulation study that suggests that greater performance towards zero defects can be achieved through testing after each phase (concurrently), in the development life-cycle of a software as opposed to testing after the coding of the system has been completed. The simulation model is developmed using four benchmark software development projects, and is validated using the Software Life-Cycle Managemetn Model (SLIM), developed by Quantitative Software Management (QSM). Three performance measures are used in comparing the two testing philosophies: time required to produce the software, the effort expended and the cost. The results indicate that the two approaches do not differ significantly on the first two measures, however, the costs are found to be dramatically different. This difference in costs leads to the conclusion that concurrent testing is superior. The cost superiority of concurrent testing can be attributed to the distribution of hours worked throughout the life-cycle, as opposed to being back-loaded in the maintenance of the system when the costs are much higher than the earlier phases in development
| Item type | Current location | Collection | Call number | Status | Date due | Barcode |
|---|---|---|---|---|---|---|
| Periódico | Biblioteca Graciliano Ramos | Periódico | Not for loan |
The most critical and visible principle of TQM in the Information System (IS) environment is the focus on zero defects in a software develpment project to achieve customer satisfaction. This paper presents results from a simulation study that suggests that greater performance towards zero defects can be achieved through testing after each phase (concurrently), in the development life-cycle of a software as opposed to testing after the coding of the system has been completed. The simulation model is developmed using four benchmark software development projects, and is validated using the Software Life-Cycle Managemetn Model (SLIM), developed by Quantitative Software Management (QSM). Three performance measures are used in comparing the two testing philosophies: time required to produce the software, the effort expended and the cost. The results indicate that the two approaches do not differ significantly on the first two measures, however, the costs are found to be dramatically different. This difference in costs leads to the conclusion that concurrent testing is superior. The cost superiority of concurrent testing can be attributed to the distribution of hours worked throughout the life-cycle, as opposed to being back-loaded in the maintenance of the system when the costs are much higher than the earlier phases in development
Click on an image to view it in the image viewer
There are no comments for this item.