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.

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.

scholarly journals Modding as an Open Source Approach to Extending Computer Game Systems

2013 ◽  
pp. 177-188
Author(s):  
Walt Scacchi
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Computer Game ◽  
Game Studies ◽  
The World ◽  
The Subject ◽  
Closed Source

This paper examines what is known about the role of open source software development within the world of game mods and modding practices. Game modding has become a leading method for developing games by customizing or creating Open Source Software extensions to game software in general, and particularly to proprietary closed source software games. What, why, and how OSS and closed source software come together within an application system is the subject for this study. Observational and qualitative is used to highlight current practices and issues that can be associated with software engineering and game studies foundations with multiple examples of different game mods and modding practices are identified throughout this study.

scholarly journals Leveraging Final Degree Projects for Open Source Software Contributions

Electronics ◽  
2021 ◽  
Vol 10 (10) ◽  
pp. 1181
Author(s):  
Juanan Pereira
Keyword(s):  
Graduate Students ◽  
Software Engineering ◽  
Computer Science ◽  
Open Source ◽  
Communication Skills ◽  
Open Source Software ◽  
Real World ◽  
Practical Experience ◽  
Multiple Challenges ◽  
Final Degree

(1) Background: final year students of computer science engineering degrees must carry out a final degree project (FDP) in order to graduate. Students’ contributions to improve open source software (OSS) through FDPs can offer multiple benefits and challenges, both for the students, the instructors and for the project itself. This work reports on a practical experience developed by four students contributing to mature OSS projects during their FDPs, detailing how they addressed the multiple challenges involved, both from the students and teachers perspective. (2) Methods: we followed the work of four students contributing to two established OSS projects for two academic years and analyzed their work on GitHub and their responses to a survey. (3) Results: we obtained a set of specific recommendations for future practitioners and detailed a list of benefits achieved by steering FDP towards OSS contributions, for students, teachers and the OSS projects. (4) Conclusion: we find out that FDPs oriented towards enhancing OSS projects can introduce students into real-world, practical examples of software engineering principles, give them a boost in their confidence about their technical and communication skills and help them build a portfolio of contributions to daily used worldwide open source applications.

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.

scholarly journals Open Source Paradigm: A Synopsis of The Cathedral and the Bazaar for Health and Social Care

2016 ◽  
Vol 23 (2) ◽  
pp. 488
Author(s):  
Tim Benson
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Social Care ◽  
Source Code ◽  
Comprehensive Description ◽  
The Third ◽  
It Impacts ◽  
Health And Social Care ◽  
Software Engineers ◽  
Closed Source

Background: Open source software (OSS) is becoming more fashionable in health and social care, although the ideas are not new. However progress has been slower than many had expected.Objective: The purpose is to summarise the Free/Libre Open Source Software (FLOSS) paradigm in terms of what it is, how it impacts users and software engineers and how it can work as a business model in health and social care sectors.Method: Much of this paper is a synopsis of Eric Raymond’s seminal book The Cathedral and the Bazaar, which was the first comprehensive description of the open source ecosystem, set out in three long essays. Direct quotes from the book are used liberally, without reference to specific passages. The first part contrasts open and closed source approaches to software development and support. The second part describes the culture and practices of the open source movement. The third part considers business models.Conclusion: A key benefit of open source is that users can access and collaborate on improving the software if they wish. Closed source code may be regarded as a strategic business risk that that may be unacceptable if there is an open source alternative. The sharing culture of the open source movement fits well with that of health and social care.

Sign in / Sign up

Export Citation Format

Share Document