A spiral model of software development and enhancement
ACM SIGSOFT Software Engineering Notes
Managing the development of large software systems: concepts and techniques
ICSE '87 Proceedings of the 9th international conference on Software Engineering
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
Automating process discovery through event-data analysis
Proceedings of the 17th international conference on Software engineering
The unified software development process
The unified software development process
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Future trends in software evolution metrics
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Measuring Fine-Grained Change in Software: Towards Modification-Aware Change Metrics
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
Empirical Software Engineering
Hi-index | 0.00 |
The development of Open Source systems produces a variety of software artifacts such as source code, version control records, bug reports, and email discussions. Since the development is distributed across different tool environments and developer practices, any analysis of project behavior must be inferred from whatever common artifacts happen to be available. In this paper, we propose an approach to characterizing a project's behavior around the time of major and minor releases; we do this by partitioning the observed activities, such as artifact check-ins, around the dates of major and minor releases, and then look for recognizable patterns. We validate this approach by means of a case study on the MySQL database system; in this case study, we found patterns which suggested MySQL was behaving consistently within itself. These patterns included testing and documenting that took place more before a release than after and that the rate of source code changes dipped around release time.