The QualOSS open source assessment model measuring the performance of open source communities

Soto, Martín; Ciolkowski, Marcus

doi:10.1109/esem.2009.5314237

Cited by 38 publications

(42 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…concerning the production of OSS in business ecosystems, customer relations and customer satisfaction, cost structures and revenues. In addition, OSS and the possible involvement of "noncommercial" actors (such as OSS communities) in business processes bear also a potentially strong impact on brand image and time-to-market, thus on business strategies that underlie business models (Soto & Ciolkowski 2009). Evidently, a business model that offers value propositions based on OSS but not supported by an OSS-related business strategy, is likely to fail because business risks deriving from OSS will be overlooked.…”

Section: Risks In Oss Projectsmentioning

confidence: 99%

Managing Risk in Open Source Software Adoption

Franch

Susi

Glott

et al. 2013

Proceedings of the 8th International Joint Conference on Software Technologies

View full text Add to dashboard Cite

Abstract:By 2016 an estimated 95% of all commercial software packages will include Open Source Software (OSS). This extended adoption is yet not avoiding failure rates in OSS projects to be as high as 50%. Inadequate risk management has been identified among the top mistakes to avoid when implementing OSS-based solutions. Understanding, managing and mitigating OSS adoption risks is therefore crucial to avoid potentially significant adverse impact on the business. In this position paper we portray a short report of work in progress on risk management in OSS adoption processes. We present a risk-aware technical decision-making management platform integrated in a business-oriented decision-making framework, which together support placing technical OSS adoption decisions into organizational, business strategy as well as the broader OSS community context. The platform will be validated against a collection of use cases coming from different types of organizations: big companies, SMEs, public administration, consolidated OSS communities and emergent small OSS products.

show abstract

Section: Risks In Oss Projectsmentioning

confidence: 99%

Managing Risk in Open Source Software Adoption

Franch

Susi

Glott

et al. 2013

Proceedings of the 8th International Joint Conference on Software Technologies

View full text Add to dashboard Cite

show abstract

“…Integrity is related to the availability of control mechanism to ensure system integrity. The OSS should provide level of user's authentication [11,12,14,16,17,18]. …”

Section: Information Qualitymentioning

confidence: 99%

Selection Criteria of Open Source Software: First Stage for Adoption

Sarrab¹,

Rehman

2013

IJIPM

View full text Add to dashboard Cite

Open Source Software (OSS) products started to become popular in the market as an alternative to closed source software. Companies and organizations are starting to adopt OSS on large scales and several governmental initiatives have encouraged the usage of OSS in the private sectors. The objective of this paper is to identify all possible OSS characteristics and propose new quality characteristics for selecting OSS in the adoption process. In general, the adoption of OSS among potential users in public sector agencies is still low and needs to be encouraged. This paper provides a brief history of OSS and open source's key programming languages. It also discusses the strengths and weaknesses of OSS. In order to improve user confidentiality, this paper identifies all possible OSS characteristics and proposes new internal quality characteristics for selecting OSS that can be added to each DeLone and McLean information system model dimensions.

show abstract

“…Maturity assessment models have been formulated to help users and integrators evaluate the quality of a FLOSS project versus another [59], [60], [63], [64], [65], [66], [67], [68]. These models provide a set of criteria to evaluate a FLOSS project.…”

Section: Process Maturity Modelsmentioning

confidence: 99%

Towards a Unified Definition of Open Source Quality

Mellado

Robinson

2011

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

Abstract. Software quality needs to be specified and evaluated in order to determine the success of a development project, but this is a challenge with Free/Libre Open Source Software (FLOSS) because of its permanently emergent state. This has not deterred the growth of the assumption that FLOSS is higher quality than traditionally developed software, despite of mixed research results. With this literature review, we found the reason for these mixed results is that that quality is being defined, measured, and evaluated differently. We report the most popular definitions, such as software structure measures, process measures, such as defect fixing, 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 are evolving, their quality is too, and it must be measured using metrics that take into account its community's commitment to quality rather than just its software structure. Challenges exist in defining what constitutes a defect or bug, and the role of modularity in affecting FLOSS quality.

show abstract

The QualOSS open source assessment model measuring the performance of open source communities

Cited by 38 publications

References 1 publication

Managing Risk in Open Source Software Adoption

Managing Risk in Open Source Software Adoption

Selection Criteria of Open Source Software: First Stage for Adoption

Towards a Unified Definition of Open Source Quality

Contact Info

Product

Resources

About