Innovation in Open Source Software Development: A Tale of Two Features

@inproceedings{Noll2007InnovationIO,
  title={Innovation in Open Source Software Development: A Tale of Two Features},
  author={John Noll},
  booktitle={OSS},
  year={2007}
}
  • J. Noll
  • Published in OSS 11 June 2007
  • Computer Science
Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. 
Ongoing software development without classical requirements
  • T. Alspaugh, W. Scacchi
  • Computer Science
    2013 21st IEEE International Requirements Engineering Conference (RE)
  • 2013
TLDR
Examination of data from several OSS projects is examined to investigate the conundrum of how a growing number of critical software systems are evolved and sustained yet provide quality and rich functional capabilities to users and integrators that accept them without question.
Participation and Open Innovation for Sustainable Software Engineering
This chapter explores the reasons why the innovation processes, in particular in software engineering, become more and more open and participative; and the implications on the sustainability of
Guiding Development of Contribution and Community Strategies in Open Source Software Requirements Engineering
TLDR
This thesis introduces the two concepts of contribution and community strategy and offers problem understanding of how organizations reason in terms of these questions, as well as guidance for how the different types of strategies may be developed.
A Community Strategy Framework - How to obtain influence on requirements in meritocratic open source software communities?
TLDR
A Community Strategy Framework (CSF) is presented to help firms create community strategies that describe if and why they need influence on the RE process in a specific OSS community, and how the firm could gain it.
How the FLOSS Research Community Uses Email Archives
  • Megan Squire
  • Engineering, Computer Science
    Int. J. Open Source Softw. Process.
  • 2012
TLDR
This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects and provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email.
Achieving Better Buying Power through Acquisition of Open Architecture Software Systems: Volume 1
Abstract : This research focuses on continuing investigation and refinement of techniques for identifying and reducing the costs, streamlining the process, and improving the readiness of future
The dual network structure of organizational problem solving: A case study on open source software development
TLDR
The dual network structure generated by the association between 72 contributors and 737 software bugs engaged during a full development cycle of the free/open source software project Epiphany is reconstructed and micro-level evidence of structural interdependence between “core” and “peripheral” members identified exclusively on the basis of their individual level of contribution to the project is provided.
Streamlining the Process of Acquiring Secure Open Architecture Software Systems
Abstract : The goal of this research is to continue investigating new approaches to acquiring secure open architecture (OA) software systems for the Department of Defense (DoD). Program managers,
Dynamic Models of Affiliation and the Network Structure of Problem Solving in an Open Source Software Project
TLDR
New stochastic actor-based models for two-mode networks that may be adopted to redress the limitations of current analytical strategies are introduced.
Achieving Better Buying Power through Acquisition of Open Architecture Software Systems for Web-Based and Mobile Devices
Abstract : Many people within large enterprises rely on up to four Web-based or mobile devices for their daily work routines personal computer, tablet, and personal and work-specific smartphones. Our
...
1
2
...

References

SHOWING 1-10 OF 44 REFERENCES
Understanding the requirements for developing open source software systems
TLDR
Eight kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation and management of requirements for developing open software systems, and this focus enables the consideration of a reformulation of the requirements engineering process and its associated artefacts, or (in)formalisms, to better account for the requirements for developed open source software systems.
The Usability of Open Source Software
TLDR
It is described how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.
Free and open source development practices in the game community
TLDR
These FOSS processes offer new directions for developing complex software systems that rely on lean electronic communication media, virtual project management, and version management mechanisms to coordinate globally dispersed development efforts.
A case study of open source software development: the Apache server
  • A. Mockus, R. Fielding, J. Herbsleb
  • Computer Science
    Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium
  • 2000
TLDR
This analysis of the development process of the Apache web server reveals a unique process, which performs well on important measures, and concludes that hybrid forms of development that borrow the most effective techniques from both the OSS and commercial worlds may lead to high performance software processes.
A framework analysis of the open source software development paradigm
TLDR
A framework was derived from two previous frameworks which have been very influential in the IS field, namely that of Zachman's IS architecture (ISA) and Checkland's CATWOE framework from Soft Systems Methodology (SSM), which is used to analyze the OSS approach in detail.
Cave or Community? An Empirical Examination of 100 Mature Open Source Projects
TLDR
Based on a study of the top 100 mature products on Sourceforge, a few surprising things are found: most OSS programs are developed by individuals, rather than communities, and the larger the project, the smaller the percent of project administrators.
Requirements Elicitation in Open-Source Programs
TLDR
One of the central points of this paper is that the program users become its co-developers.
Why Open Source Software / Free Software (OSS/FS, FLOSS, or FOSS)? Look at the Numbers!
This paper provides quantitative data that, in many cases, using open source software / free software (abbreviated as OSS/FS, FLOSS, or FOSS) is a reasonable or even superior approach to using their
An Overview of the Software Engineering Process and Tools in the Mozilla Project
TLDR
The software engineering aspect of a large Open Source project is described and the software engineering tools used in the Mozilla Project are covered, since the Mozilla process and tools are intimately related.
Maintainability of the Linux kernel
TLDR
Unless Linux is restructured with a bare minimum of common coupling, the dependencies induced by common coupling will, at some future date, make Linux exceedingly hard to maintain without inducing regression faults.
...
1
2
3
4
5
...