Automating the measurement of open source projects. In Proceedings of the 1st International Workshop on Emerging Trends in FLOSS Research and Development, Minneapolis, MN, 2007. Identifying success and tragedy of floss commons: A preliminary classification of sourceforge. Journal of Software Maintenance and Evolution: Research and Practice, 13(1):3-30, 2001. Types of software evolution and software maintenance. International Federation for Information Processing, Springer, 2007. Silitti, editors, Open Source Development, Adoption and Innovation, pages 31-44. From the cathedral to the bazaar: An empirical study of the lifecycle of volunteer community projects. In ICSE '07: Proceedings of the 29th International Conference on Software Engineering, pages 511-518, Washington, DC, USA, 2007. An empirical study of the evolution of an agile-developed software system. In ICSM '03: Proceedings of the International Conference on Software Maintenance, page 65, Washington, DC, USA, 2003. In IWPSE '02: Proceedings of the International Workshop on Principles of Software Evolution, pages 103-107, New York, NY, USA, 2002. Metrics and analysis of software architecture evolution with discontinuity. The existing staged model for software evolution is therefore revised for its applicability on FLOSS systems. This paper focuses on the commonalities and differences between the evolution and patterns in the lifecycles of traditional commercial systems and free/libre/open source software (FLOSS) systems. The output of the what/why studies is exemplified by empirical hypotheses, such as the staged model of software evolution. The two perspectives are related in various ways: the study of the what/why is for instance essential to achieve an appropriate management of software engineering activities, and to guide innovation in processes, methods and tools, that is, the how. Research into traditional software evolution has been tackled from two broad perspectives: that focused on the how, which looks at the processes, methods and techniques to implement and evolve software and that focused on the what/why perspective, aiming at achieving an understanding of the drivers and general characteristics of the software evolution phenomenon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |