Guest editors’ introduction to the special section from the international conference on software maintenance and evolution

IEEE Transactions on Software Engineering, 33(12): pp. 797-798

Engaging without over-powering: A case study of a FLOSS project

This is the post-print version of the published chapter. The original publication is available at the link below. Copyright @ 2010 IFIP International Federation for Information Processing.The role of Open Source Software (OSS) in the e-learning business has become more and more fundamental in the last 10 years, as long as corporate and government organizations have developed their educational and training programs based on OSS out-of-the-box tools. This paper qualitatively documents the decision of the largest UK e-learning provider, the Open University, to adopt the Moodle e-learning system, and how it has been successfully deployed in its site after a multi-million investment. A further quantitative study also provides evidence of how a commercial stakeholder has been engaged with, and produced outputs for, the Moodle community. Lessons learned from this experience by the stakeholders include the crucial factors of contributing to the OSS community, and adapting to an evolving technology. It also becomes evident how commercial partners helped this OSS system to achieve the transition from an “average” OSS system to a successful multi-site, collaborative and community-based OSS project

From "community" to "commercial" FLOSS: The case of moodle

This is the post-print version of the final published article that is available from the link below. Copyright © 2010 ACM, Inc.This paper documents the evolution of Moodle, an advanced Content Management System, and its transition from a purely volunteer-based project to one driven by commercial interests and stakeholders. The study of its evolution provides evidence of the sustainability of its process: increasing amounts of provided effort by developers correspond to similarly increasing produced outputs to the Moodle system. It is also evident how this OSS system, apart from achieving the transition to a successful multisite, collaborative and community-based OSS project, depends more on its community than its commercial partners

A Model-Based Approach to Impact Analysis Using Model Differencing

Impact analysis is concerned with the identification of consequences of changes and is therefore an important activity for software evolution. In modelbased software development, models are core artifacts, which are often used to generate essential parts of a software system. Changes to a model can thus substantially affect different artifacts of a software system. In this paper, we propose a modelbased approach to impact analysis, in which explicit impact rules can be specified in a domain specific language (DSL). These impact rules define consequences of designated UML class diagram changes on software artifacts and the need of dependent activities such as data evolution. The UML class diagram changes are identified automatically using model differencing. The advantage of using explicit impact rules is that they enable the formalization of knowledge about a product. By explicitly defining this knowledge, it is possible to create a checklist with hints about development steps that are (potentially) necessary to manage the evolution. To validate the feasibility of our approach, we provide results of a case study.Comment: 16 pages, 5 figures, In: Proceedings of the 8th International Workshop on Software Quality and Maintainability (SQM), ECEASST Journal, vol. 65 201

Editorial - Introduction to the special issue on deliberation with computers: exploring the distinctive contribution of new technologies to collaborative thinking and learning

Abstract not available