Discovering and Modeling Open Source Software Processes Abstract
BibTeX
@MISC{Jensen_discoveringand,
author = {Chris Jensen},
title = {Discovering and Modeling Open Source Software Processes Abstract},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Open source software (OSS) development has been shown effective as a software development paradigm. In over twenty years since its origin, we have learned a lot about its culture and motivations. Yet despite great interest in its lessons for process improvement, understanding, and participation among corporations, researchers, and would-be participants, few have actually sought to discover and model OSS processes. In traditional software engineering, processes are composed of several phases. For example, developers begin by determining what the system will do and how it will do it. These requirements are often described in terms of functional and nonfunctional operation, and are enumerated in a long document, which serves as a basis for system architecture and design later in the (waterfall) software lifecycle. open source software (OSS) projects do not typically have such documents [1]. Linux creator Linus Torvalds even argues against specifications on ideological grounds [2]. How then, do OSS developers know what to do? In an effort to begin answering this question, this paper is a survey of existing studies of OSS processes and a framework for future systematic discovery and modeling these processes. This framework is put into practice via a case study of the NetBeans requirements and release process. 1
Keyphrases
open source software os process several phase future systematic discovery release process great interest ideological ground software lifecycle software development paradigm os developer twenty year netbeans requirement long document case study linux creator linus torvalds system architecture process improvement nonfunctional operation would-be participant traditional software engineering
