Evidence-Based Assurance to Support Process Quality in the F/OSS Community

2007 ◽  
pp. 120-146
Author(s):  
Anas Tawileh ◽  
Omer F. Rana ◽  
Wendy Ivins ◽  
Stephen McIntosh
Keyword(s):  
Quality Assurance ◽  
Open Source ◽  
Open Source Software ◽  
Growth Rates ◽  
Development Process ◽  
End Users ◽  
Evidence Based ◽  
Software Developers ◽  
Substantial Growth ◽  
Development Processes

This chapter investigates the quality issues of the free and open source software (F/OSS) development processes. It argues that software developed within the F/OSS paradigm has witnessed substantial growth rates within the software developers’ community. However, end users from outside the community are still sceptical about adopting F/OSS because of the perceived lack of quality assurance mechanisms within the F/OSS development process. The authors aim to promote higher adoption of F/OSS artefacts outside the developers’ community by exploring possibilities to provide appropriate evidence based assurances that F/OSS artefacts will meet the quality levels expected by users.

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.

MAGISTER: Quality assurance of Magic applications for software developers and end users

2010 ◽  
Author(s):  
Csaba Nagy ◽  
Laszlo Vidacs ◽  
Rudolf Ferenc ◽  
Tibor Gyimothy ◽  
Ferenc Kocsis ◽  
...  
Keyword(s):  
Quality Assurance ◽  
End Users ◽  
Software Developers

Managing Knowledge in Open Source Software Test Process

2013 ◽  
pp. 135-149 ◽  
Author(s):  
Tamer Abdou ◽  
Peter Grogono ◽  
Pankaj Kamthan
Keyword(s):  
Open Source ◽  
Conceptual Model ◽  
Open Source Software ◽  
Software Test ◽  
Software Projects ◽  
Life Cycle Stages ◽  
Development Processes ◽  
International Testing ◽  
Testing Standards ◽  
Test Process

The increasing adoption and use of Open Source Software (OSS) motivates study of its development. This chapter explores the state-of-the art in OSS development processes, in general, and OSS testing processes, in particular. A conceptual model for software Testing Knowledge Management (TKM) that aims to provide an understanding of the testing domain is introduced. The TKM model is informed by earlier studies and guided by international testing standards. Moreover, the TKM model is equipped with different forms of knowledge, reusable across software projects. Using the TKM model as an integrative conceptual model enables understanding of how knowledge life cycle stages are mapped onto the test process of OSS, what type of knowledge is created at each stage, and how knowledge is converted from one stage to another. The chapter is supported by representative examples of OSS that are mature and currently in widespread use.

Managing Knowledge in Open Source Software Test Process

2015 ◽  
pp. 918-932
Author(s):  
Tamer Abdou ◽  
Peter Grogono ◽  
Pankaj Kamthan
Keyword(s):  
Open Source ◽  
Conceptual Model ◽  
Open Source Software ◽  
Software Test ◽  
Software Projects ◽  
Life Cycle Stages ◽  
Development Processes ◽  
International Testing ◽  
Testing Standards ◽  
Test Process

The increasing adoption and use of Open Source Software (OSS) motivates study of its development. This chapter explores the state-of-the art in OSS development processes, in general, and OSS testing processes, in particular. A conceptual model for software Testing Knowledge Management (TKM) that aims to provide an understanding of the testing domain is introduced. The TKM model is informed by earlier studies and guided by international testing standards. Moreover, the TKM model is equipped with different forms of knowledge, reusable across software projects. Using the TKM model as an integrative conceptual model enables understanding of how knowledge life cycle stages are mapped onto the test process of OSS, what type of knowledge is created at each stage, and how knowledge is converted from one stage to another. The chapter is supported by representative examples of OSS that are mature and currently in widespread use.

Collaborative Requirements Definition Processes in Open Source Software Development

2011 ◽  
pp. 189-208
Author(s):  
Stefan Dietze
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Open Source Software Development ◽  
Requirements Definition ◽  
In The Beginning

This chapter discusses typical collaborative requirements definition processes as they are performed in open source software development (OSSD) projects. In the beginning, some important aspects of the entire OSSD approach are introduced in order to enable an understanding of the subsequent description of the feedback-based requirements definition processes. Since the OSSD model seems to represent a successful way of dealing with the significant distribution and heterogeneity of its actors, some opportunities to adapt this approach also in other (software) industries are discussed. Nevertheless the entire OSSD model still exhibits several improvement opportunities that also are addressed in this chapter. In order to overcome possible weaknesses, several approaches to improve the described requirements definition approach are introduced. These improvements help to assure a higher level of efficiency and quality assurance for both processes and the developed artifacts, and furthermore also enable the consideration and acceptance of this approach in other domains and industries.

How the FLOSS Research Community Uses Email Archives

2012 ◽  
Vol 4 (1) ◽  
pp. 37-59 ◽  
Author(s):  
Megan Squire
Keyword(s):  
Software Engineering ◽  
Open Source ◽  
Open Source Software ◽  
Development Process ◽  
Relevant Literature ◽  
Research Community ◽  
Email Message ◽  
Object Of Study ◽  
Broad Overview

Artifacts of the software development process, such as source code or emails between developers, are a frequent object of study in empirical software engineering literature. One of the hallmarks of free, libre, and open source software (FLOSS) projects is that the artifacts of the development process are publicly-accessible and therefore easily collected and studied. Thus, there is a long history in the FLOSS research community of using these artifacts to gain understanding about the phenomenon of open source software, which could then be compared to studies of software engineering more generally. This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects. It provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email. The outcome of this paper is to provide a broad overview for the software engineering and FLOSS research communities of how other researchers have used FLOSS email message artifacts in their work.

Sign in / Sign up

Export Citation Format

Share Document