Community Customers

2011 ◽  
pp. 510-521 ◽  
Author(s):  
Jeroen Hoppenbrouwers
Keyword(s):  
Life Cycle ◽  
Open Source ◽  
Community Participation ◽  
Open Source Software ◽  
Product Life Cycle ◽  
Development Process ◽  
Sales Process ◽  
Software Product ◽  
Specific Community

This chapter discusses the role of the project/product community in the open source product life cycle. It outlines how a community-driven approach affects not only the development process, but also (and more importantly) the marketing/sales process, the deployment, the operation, and in general the resulting software product. Participation in the community is essential for any organization using the product, leading to the concept of a community customer. Specific community participation guidelines are given to organizations and individuals who deploy and use open source software, further develop it, or offer lifetime services on the product.

Community Customers

2011 ◽  
pp. 1323-1334
Author(s):  
Jeroen Hoppenbrouwers
Keyword(s):  
Life Cycle ◽  
Open Source ◽  
Community Participation ◽  
Open Source Software ◽  
Product Life Cycle ◽  
Development Process ◽  
Sales Process ◽  
Software Product ◽  
Specific Community

This chapter discusses the role of the project/product community in the open source product life cycle. It outlines how a community-driven approach affects not only the development process, but also (and more importantly) the marketing/sales process, the deployment, the operation, and in general the resulting software product. Participation in the community is essential for any organization using the product, leading to the concept of a community customer. Specific community participation guidelines are given to organizations and individuals who deploy and use open source software, further develop it, or offer lifetime services on the product.

Measuring Open Source Quality

2011 ◽  
Vol 3 (3) ◽  
pp. 48-65 ◽  
Author(s):  
Claudia Ruiz ◽  
William N. Robinson
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Future Research ◽  
Process Measures ◽  
Quality Models ◽  
Resolution Rate ◽  
Research Results ◽  
Software Product

There is an ample debate over the quality of Free/Libre Open Source Software (FLOSS) with mixed research results. The authors show that a reason for these mixed results is that quality is being defined, measured, and evaluated differently. They report the most popular approaches including software structure measures, process measures, and maturity assessment models. The way researchers have built their samples has also contributed to the mixed results with different project properties being considered and ignored. Because FLOSS projects evolve with each release, their quality does too, and it must be measured using metrics that take into account their communities’ commitment to quality rather than just the structure of the resulting code. Challenges exist in defining what constitutes a defect or bug, and the role of modularity in affecting FLOSS quality. The authors suggest three considerations for future research on FLOSS quality models: (1) defect resolution rate, (2) kind of software product, and (3) modularity—both technical and organizational.

Measuring Open Source Quality

2013 ◽  
pp. 189-206 ◽  
Author(s):  
Claudia Ruiz ◽  
William N. Robinson
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Future Research ◽  
Process Measures ◽  
Quality Models ◽  
Resolution Rate ◽  
Research Results ◽  
Software Product

There is an ample debate over the quality of Free/Libre Open Source Software (FLOSS) with mixed research results. The authors show that a reason for these mixed results is that quality is being defined, measured, and evaluated differently. They report the most popular approaches including software structure measures, process measures, and maturity assessment models. The way researchers have built their samples has also contributed to the mixed results with different project properties being considered and ignored. Because FLOSS projects evolve with each release, their quality does too, and it must be measured using metrics that take into account their communities’ commitment to quality rather than just the structure of the resulting code. Challenges exist in defining what constitutes a defect or bug, and the role of modularity in affecting FLOSS quality. The authors suggest three considerations for future research on FLOSS quality models: (1) defect resolution rate, (2) kind of software product, and (3) modularity—both technical and organizational.

scholarly journals Integrated framework for strategic cost management based on target costing, ABC, and product life-cycle in PDP: Empirical experience

2020 ◽  
Vol 10 (1) ◽  
pp. 31-43
Author(s):  
Maísa Martins Ferreira ◽  
Selma Regina Martins Oliveira
Keyword(s):  
Life Cycle ◽  
Product Life Cycle ◽  
Development Process ◽  
Cost Management ◽  
Business Management ◽  
Target Costing ◽  
Product Lifecycle ◽  
Product Life ◽  
Integrated Framework ◽  
Strategic Cost Management

This study aims to contribute to the planning process on product management. To do so it presents a integrated framework based on strategic cost management, using the methods target costing, activity-based cost (ABC) based on the product lifecycle. This proposal was structured as it follows: Phase 1: determining Target Cost; Phase 2: determining ABC defrayal to the light of the defrayal based on the product lifecycle. The research was elaborated to the light of specialized literature, from which we extracted the variables to formulate the methodology. After that, to show the feasibility and plausibility of the method we applied a hypothetical case study based on the development process of a product to the light of a course/MBA in Business Management in Institution of Higher Education in Brazil. The results were satisfactory and validated the proposal suggested. The survey findings indicate that the integrated method between ABC, target costing and products lifecycle applied in MBA Business Management is quite satisfactory.   Keywords: Framework, target costing, activity-based cost (ABC), costing based on product life-cycle, product development process (PDP);

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