Towards a Process Maturity Model for Open Source Software

2008 ◽  
Author(s):  
Marcus Ciolkowski ◽  
Martín Soto
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Maturity Model ◽  
Process Maturity

OSS-TMM

2011 ◽  
Vol 3 (2) ◽  
pp. 1-22 ◽  
Author(s):  
Sandro Morasca ◽  
Davide Taibi ◽  
Davide Tosi
Keyword(s):  
Software Engineering ◽  
Open Source ◽  
Open Source Software ◽  
Real Life ◽  
Good Deal ◽  
Maturity Model ◽  
Engineering Development ◽  
Testing Techniques ◽  
Closed Source ◽  
Life Projects

Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test & Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.

OSS-TMM

2013 ◽  
pp. 59-78
Author(s):  
Sandro Morasca ◽  
Davide Taibi ◽  
Davide Tosi
Keyword(s):  
Software Engineering ◽  
Open Source ◽  
Open Source Software ◽  
Real Life ◽  
Good Deal ◽  
Maturity Model ◽  
Engineering Development ◽  
Testing Techniques ◽  
Closed Source ◽  
Life Projects

Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test & Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.

scholarly journals Assessing the Open Source Development Processes Using OMM

2012 ◽  
Vol 2012 ◽  
pp. 1-17 ◽  
Author(s):  
Etiel Petrinja ◽  
Giancarlo Succi
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Development Process ◽  
Maturity Model ◽  
Distributed Development ◽  
Capability Maturity ◽  
Bug Reports ◽  
Geographically Distributed ◽  
Development Processes ◽  
Management Approaches

The assessment of development practices in Free Libre Open Source Software (FLOSS) projects can contribute to the improvement of the development process by identifying poor practices and providing a list of necessary practices. Available assessment methods (e.g., Capability Maturity Model Integration (CMMI)) do not address sufficiently FLOSS-specific aspects (e.g., geographically distributed development, importance of the contributions, reputation of the project, etc.). We present a FLOSS-focused, CMMI-like assessment/improvement model: the QualiPSo Open Source Maturity Model (OMM). OMM focuses on the development process. This makes it different from existing assessment models that are focused on the assessment of the product. We have assessed six FLOSS projects using OMM. Three projects were started and led by a software company, and three are developed by three different FLOSS communities. We identified poorly addressed development activities as the number of commit/bug reports, the external contributions, and the risk management. The results showed that FLOSS projects led by companies adopt standard project management approaches as product planning, design definition, and testing, that are less often addressed by community led FLOSS projects. The OMM is valuable for both the FLOSS community, by identifying critical development activities necessary to be improved, and for potential users that can better decide which product to adopt.

An Algorithm for Gradual Patch Acceptance Detection in Open Source Software Repository Mining

2012 ◽  
Vol E95.A (9) ◽  
pp. 1478-1489
Author(s):  
Passakorn PHANNACHITTA ◽  
Akinori IHARA ◽  
Pijak JIRAPIWONG ◽  
Masao OHIRA ◽  
Ken-ichi MATSUMOTO
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Repository ◽  
Repository Mining ◽  
Software Repository Mining

Hacking Diversity

2019 ◽  
Author(s):  
Christina Dunbar-Hester
Keyword(s):  
Open Source ◽  
Human Resource ◽  
Open Source Software ◽  
Cultural Production ◽  
Equal Opportunity ◽  
Economic Power ◽  
Underrepresented Groups ◽  
Technical Production ◽  
Preferred Solutions

Hacking, as a mode of technical and cultural production, is commonly celebrated for its extraordinary freedoms of creation and circulation. Yet surprisingly few women participate in it: rates of involvement by technologically skilled women are drastically lower in hacking communities than in industry and academia. This book investigates the activists engaged in free and open-source software to understand why, despite their efforts, they fail to achieve the diversity that their ideals support. The book shows that within this well-meaning volunteer world, beyond the sway of human resource departments and equal opportunity legislation, members of underrepresented groups face unique challenges. The book explores who participates in voluntaristic technology cultures, to what ends, and with what consequences. Digging deep into the fundamental assumptions underpinning STEM-oriented societies, the book demonstrates that while the preferred solutions of tech enthusiasts—their “hacks” of projects and cultures—can ameliorate some of the “bugs” within their own communities, these methods come up short for issues of unequal social and economic power. Distributing “diversity” in technical production is not equal to generating justice. The book reframes questions of diversity advocacy to consider what interventions might appropriately broaden inclusion and participation in the hacking world and beyond.

Sign in / Sign up

Export Citation Format

Share Document