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. 
View via Publisher
link.springer.com
12 Citations
Highly Influential Citations
1
Background Citations
3
Methods Citations
1
Results Citations
1

12 Citations

Ongoing software development without classical requirements

  • T. AlspaughW. Scacchi
  • Computer Science
    2013 21st IEEE International Requirements Engineering Conference (RE)
  • 2013
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

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?

How the FLOSS Research Community Uses Email Archives

  • Megan Squire
  • Computer Science
    Int. J. Open Source Softw. Process.
  • 2012
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

Streamlining the Process of Acquiring Secure Open Architecture Software Systems

The results show that the best ways to streamline the process for acquiring secure OA systems that are in line with DoD's Better Buying Power 2.0 (2013) guidelines are found.

Dynamic Models of Affiliation and the Network Structure of Problem Solving in an Open Source Software Project

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

The research is directed at identifying, tracking, and analyzing software component costs and cost reduction opportunities within the acquisition life cycle of open architecture (OA) systems for such Web-based and mobile devices.

References

SHOWING 1-10 OF 44 REFERENCES

Understanding the requirements for developing open source software systems

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

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

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 framework analysis of the open source software development paradigm

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

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

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

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

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.

The Cathedral and the Bazaar