Journal of Software Maintenance: Research and Practice
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
An experiment to assess different defect detection methods for software requirements inspections
ICSE '94 Proceedings of the 16th international conference on Software engineering
Communications of the ACM
A quantitative comparison of perfective and corrective software maintenance
Journal of Software Maintenance: Research and Practice
Program understanding behaviour during enhancement of large-scale software
Journal of Software Maintenance: Research and Practice
An evaluation of the cognitive processes of programmers engaged in software debugging
Journal of Software Maintenance: Research and Practice
IEEE Transactions on Software Engineering
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Journal of Systems and Software
Types of software evolution and software maintenance
Journal of Software Maintenance: Research and Practice
Situated assessment of problems in software development
ACM SIGMIS Database - Special issue on infomration systems: current issues and future changes
Peer reviews in software: a practical guide
Peer reviews in software: a practical guide
Practical Software Maintenance: Best Practices for Managing Your Software Investment
Practical Software Maintenance: Best Practices for Managing Your Software Investment
Software Inspection
Software Maintenance Management
Software Maintenance Management
The non-homogeneous maintenance periods: a case study of software modifications
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
Taxonomy of Problem Management Activities
CSMR '01 Proceedings of the Fifth European Conference on Software Maintenance and Reengineering
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Software Reviews: The State of the Practice
IEEE Software
In their own words: CIO visions about the future of in-house IT organizations
ACM SIGMIS Database
Object-Oriented and Classical Software Engineering
Object-Oriented and Classical Software Engineering
The application of product measures in directing software maintenance activity
Journal of Software Maintenance and Evolution: Research and Practice
A study of student strategies for the corrective maintenance of concurrent software
Proceedings of the 30th international conference on Software engineering
Introducing function extraction into software testing
ACM SIGMIS Database
ACM SIGSOFT Software Engineering Notes
Measuring the Impact of Different Categories of Software Evolution
IWSM/Metrikon/Mensura '08 Proceedings of the International Conferences on Software Process and Product Measurement
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
Design and code inspections to reduce errors in program development
IBM Systems Journal
Hi-index | 0.00 |
Information systems portfolio management assumes that software will evolve to maintain alignment with operational needs, a goal that must be met through effective ongoing maintenance. Thus, a primary goal of software maintainers is to ensure that production code is updated without the introduction of defects. However, there is a dearth of research that examines the work product defects that occur as these applications evolve. The goal of this study is to characterize software evolution lifecycle work product defects and factors that may increase or reduce their occurrence. The study takes place within a global consulting organization conducting ongoing software maintenance for a Fortune 100 telecommunications firm by a project team assessed at Capability Maturity Model Integration (CMMI) Level 3. This study reports on 991 work product reviews conducted across the evolution activities of the ISO/IEC 12207 Software Development Life Cycle Processes. After controlling for team and expertise differences, the study's major finding is that corrective evolution projects inject a greater number of work product defects than enhancive evolution projects. This result does not arise from the schedule compression often associated with corrective evolution. Rather, it is concluded that the increase in work product defects is associated with the increased complexity of analysis-stage problem diagnosis found in corrective evolution projects. The analysis is augmented by additional covariates including the number of work product reviewers, preparation time of reviewers, and size of the project.