Parallel changes in large-scale software development: an observational case study
ACM Transactions on Software Engineering and Methodology (TOSEM)
IEEE Transactions on Software Engineering
Understanding and predicting effort in software projects
Proceedings of the 25th International Conference on Software Engineering
Determining the Distribution of Maintenance Categories: Survey versus Measurement
Empirical Software Engineering
Mining Version Histories to Guide Software Changes
Proceedings of the 26th International Conference on Software Engineering
Mining Version Histories to Guide Software Changes
IEEE Transactions on Software Engineering
Toward Understanding the Rhetoric of Small Source Code Changes
IEEE Transactions on Software Engineering
HATARI: raising risk awareness
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
On using Net Options Value as a value based design framework
EDSER '05 Proceedings of the seventh international workshop on Economics-driven software engineering research
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
Proceedings of the 28th international conference on Software engineering
TA-RE: an exchange language for mining software repositories
Proceedings of the 2006 international workshop on Mining software repositories
Information theoretic evaluation of change prediction models for large-scale software
Proceedings of the 2006 international workshop on Mining software repositories
How long did it take to fix bugs?
Proceedings of the 2006 international workshop on Mining software repositories
Effort estimation by characterizing developer activity
Proceedings of the 2006 international workshop on Economics driven software engineering research
Can software engineering solve the HPCS problem?
Proceedings of the second international workshop on Software engineering for high performance computing system applications
Replaying development history to assess the effectiveness of change propagation tools
Empirical Software Engineering
Predicting component failures at design time
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Beyond source code: the importance of other artifacts in software development (a case study)
Journal of Systems and Software - Special issue: Selected papers from the 4th source code analysis and manipulation (SCAM 2004) workshop
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Predicting Faults from Cached History
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Correlating Social Interactions to Release History during Software Evolution
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Which warnings should I fix first?
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Improving defect prediction using temporal features and non linear models
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Learning from bug-introducing changes to prevent fault prone code
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Journal of Software Maintenance and Evolution: Research and Practice
Automated classification of change messages in open source projects
Proceedings of the 2008 ACM symposium on Applied computing
Understanding bug fix patterns in verilog
Proceedings of the 2008 international working conference on Mining software repositories
Experience Report on the Effect of Software Development Characteristics on Change Distribution
PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
Using information retrieval based coupling measures for impact analysis
Empirical Software Engineering
Toward an understanding of bug fix patterns
Empirical Software Engineering
Predicting faults using the complexity of code changes
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Change impact graphs: Determining the impact of prior codechanges
Information and Software Technology
Characterizing software architecture changes: A systematic review
Information and Software Technology
Change profiles of a reused class framework vs. two of its applications
Information and Software Technology
Identifying static analysis techniques for finding non-fix hunks in fix revisions
Proceedings of the ACM first international workshop on Data-intensive software management and mining
Test coverage and post-verification defects: A multiple case study
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Empirical Evaluation of Hunk Metrics as Bug Predictors
IWSM '09 /Mensura '09 Proceedings of the International Conferences on Software Process and Product Measurement
An empirical study on the maintenance of source code clones
Empirical Software Engineering
Software support tools and experimental work
Proceedings of the 2006 international conference on Empirical software engineering issues: critical assessment and future directions
Automatically documenting program changes
Proceedings of the IEEE/ACM international conference on Automated software engineering
Automatic construction of an effective training set for prioritizing static analysis warnings
Proceedings of the IEEE/ACM international conference on Automated software engineering
Automatically identifying changes that impact code-to-design traceability during evolution
Software Quality Control
Do time of day and developer experience affect commit bugginess?
Proceedings of the 8th Working Conference on Mining Software Repositories
Automated topic naming to support cross-project analysis of software maintenance activities
Proceedings of the 8th Working Conference on Mining Software Repositories
Improving efficiency in software maintenance
Proceedings of the 8th Working Conference on Mining Software Repositories
Assessing programming language impact on development and maintenance: a study on c and c++
Proceedings of the 33rd International Conference on Software Engineering
Dealing with noise in defect prediction
Proceedings of the 33rd International Conference on Software Engineering
Reducing the effort of bug report triage: Recommenders for development-oriented decisions
ACM Transactions on Software Engineering and Methodology (TOSEM)
ReLink: recovering links between bugs and changes
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Micro interaction metrics for defect prediction
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
BugCache for inspections: hit or miss?
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Information and Software Technology
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
On the improvement of a fault classification scheme with implications for white-box testing
Proceedings of the 27th Annual ACM Symposium on Applied Computing
FASE'12 Proceedings of the 15th international conference on Fundamental Approaches to Software Engineering
Empirical Software Engineering
Time variance and defect prediction in software projects
Empirical Software Engineering
Controversy Corner: On the relationship between comment update practices and Software Bugs
Journal of Systems and Software
Controversy Corner: Preserving knowledge in software projects
Journal of Systems and Software
Identifying Linux bug fixing patches
Proceedings of the 34th International Conference on Software Engineering
A case study of cross-system porting in forked projects
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Multi-layered approach for recovering links between bug reports and fixes
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
The impact of tangled code changes
Proceedings of the 10th Working Conference on Mining Software Repositories
An empirical study of the fault-proneness of clone mutation and clone migration
Proceedings of the 10th Working Conference on Mining Software Repositories
Sample size vs. bias in defect prediction
Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering
CASCON '13 Proceedings of the 2013 Conference of the Center for Advanced Studies on Collaborative Research
Empirical Software Engineering
Hi-index | 0.00 |
Large-scale software products must constantly change in order to adapt to a changing environment. Studies of historic data from legacy software systems have identified three specific causes of this change: adding new features; correcting faults; and restructuring code to accommodate future changes. Our hypothesis is that a textual description field of a change is essential to understanding why that change was performed. In addition, we expect that difficulty, size, and interval would vary strongly across different types of changes. To test these hypotheses we have designed a program, which automatically classifies maintenance activity based on a textual description of changes. Developer surveys showed that the automatic classification was in agreement with developer opinions. Tests of the classifier on a different product found that size and interval for different types of changes did not vary across two products. We have found strong relationships between the type and size of a change and the time required to carry it out. We also discovered a relatively large amount of perfective changes in the system we examined. From the study we have arrived at several suggestions on how to make version control data useful in diagnosing the state of a software project, without significantly increasing the overhead for the developer using the change management system.