A case study of open source software development: the Apache server

  title={A case study of open source software development: the Apache server},
  author={Audris Mockus and Roy T. Fielding and James D. Herbsleb},
  journal={Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium},
  • A. Mockus, R. Fielding, J. Herbsleb
  • Published 1 June 2000
  • Computer Science
  • Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium
According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity… 
Requirements elicitation in open source software development: a case study
The results show that the majority of features are asserted by developers, based on either their personal experience, or knowledge of users' needs, suggesting that there is a common open source requirements approach that is independent of project size.
Open Source Software Development and Lotka's Law: Bibliometric Patterns in Programming
This research applies Lotka's Law to metadata on open source software development. Lotka's Law predicts the proportion of authors at different levels of productivity. Open source software development
Success Factors of Open Source Software Projects using Datamining Technique
A research to find the success factors of 5000 most-downloaded Open Source projects at sourceforge.net finds some interesting results in which these success factors may or may not be influenced directly by the project's initiator and other project's members.
A framework of code reuse in open source software
The assessment shows that reuse factors of projects managers and developers influence the OSS reuse, and a reuse system based on the proposed framework is implemented.
Patch Review Processes in Open Source Software Development Communities: A Comparative Case Study
  • J. Asundi, R. Jayant
  • Computer Science
    2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07)
  • 2007
The results show that while the patch review processes are not exactly identical across various F/OSS projects, the core members across all projects play the vital role of gate-keepers to ensure a high level of review for submitted patches.
Since 1990s, Open Source Software has made a major impact on the Software industry and has changed the way the software is developed. Normally, Open Source Software is developed in a collaborative
The GitHub Open Source Development Process
Open Source Software (OSS) projects, or software projects with publicly available source code, are realizing ever more important roles in both personal and business computing. As such, shifts in the
Free and Open Source Software organizations: A large-scale analysis of code, comments, and commits frequency
After analyzing the FOSS activities on the projects and organizations level, it is found that there is less activity now than there was a decade ago and the role of large formal FOSS organizations serving as intermediary between developers diminishes.
Understanding the Role of Core Developers in Open Source Software Development
Introduction The model of open source software (OSS) represents a disruptive paradigm in the software industry. Compared with the traditional proprietary software development, OSS is a radically new
Open source software development process modeling
This chapter draws attention to software process modeling for open source software development by proposing a three-layered open source Software Process Engineering Meta-model, which allows to describe fine-grained process model fragments characteristics of different open source projects.


Splitting the organization and integrating the code: Conway's law revisited
  • J. Herbsleb, Rebecca E. Grinter
  • Computer Science
    Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002)
  • 1999
A case study of what indeed turned out to be the most difficult part of a geographically distributed software project, i.e., integration, and shed light on the problems and mechanisms underlying the coordination needs of development projects generally, be they co-located or distributed.
Shared leadership in the Apache project
According to the Netcraft survey of November 1998, the Apache server and its derivatives are used by over 57% of publicly accessible Web sites, more than double its nearest competitor.
Software Engineering Principles
Many software practitioners think of software engineering knowledge almost exclusively as knowledge of specific technologies: Java, Perl, HTML, C++, Linux, Windows NT, and so on. Knowledge of
A field study of the software design process for large systems
A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.
Software Measurement: A Necessary Scientific Basis
  • N. Fenton
  • Computer Science
    IEEE Trans. Software Eng.
  • 1994
It is shown that the search for general software complexity measures is doomed to failure and the theory does help to define and validate measures of specific complexity attributes, and is able to view software measurement in a very wide perspective.
The cathedral and the bazaar
I anatomize a successful open-source project, fetchmail, that was run as a deliberate test of some theories about software engineering suggested by the history of Linux. I discuss these theories in
Conceptual Modeling of Coincident Failures in Multiversion Software
The authors formalize the notion of methodological diversity by considering the sequence of decision outcomes that constitute a methodology and show that diversity of decision implies likely diversity of behavior for the different versions developed under such forced diversity.
Open Sources: Voices from the Open Source Revolution
From the Publisher: Now in Open Sources, for the first time leaders of Open Source come together to discuss the new vision of the software industry they have created, through essays that explain how
Software Measurement for DoD Systems: Recommendations for Initial Core Measures.
Abstract : This report presents our recommendations for a basic set of software measures that Department of Defense (DoD) organizations can use to help plan and manage the acquisition, development,
A Methodology for Collecting Valid Software Engineering Data
An effective data collection method for evaluating software development methodologies and for studying the software development process is described and results show that data validation is a necessary part of change data collection.