This Article 
 Bibliographic References 
 Add to: 
The FreeBSD Project: A Replication Case Study of Open Source Development
June 2005 (vol. 31 no. 6)
pp. 481-494
Case studies can help to validate claims that open source software development produces higher quality software at lower cost than traditional commercial development. One problem inherent in case studies is external validity—we do not know whether or not results from one case study apply to another development project. We gain or lose confidence in case study results when similar case studies are conducted on other projects. This case study of the FreeBSD project, a long-lived open source project, provides further understanding of open source development. The paper details a method for mining repositories and querying project participants to retrieve key process information. The FreeBSD development process is fairly well-defined with proscribed methods for determining developer responsibilities, dealing with enhancements and defects, and managing releases. Compared to the Apache project, FreeBSD uses 1) a smaller set of core developers—developers who control the code base—that implement a smaller percentage of the system, 2) a larger set of top developers to implement 80 percent of the system, and 3) a more well-defined testing process. FreeBSD and Apache have a similar ratio of core developers to people involved in adapting and debugging the system and people who report problems. Both systems have similar defect densities and the developers are also users in both systems.

[1] D. Cooke, J. Urban, and S. Hamilton, “Unix and Beyond: An Interview with Ken Thompson,” Computer, vol. 32, no. 5, pp. 58-62, May 1999.
[2] T.T. Dinh-Trong and J. Bieman, “Open Source Software Development: A Case Study of FreeBSD,” Proc. 10th Int'l Software Metrics Symp. (Metrics 2004), pp. 96-105, 2004.
[3] J. Feller, “Meeting Challenges And Surviving Success,” Proc. 24th Int'l Conf. Software Eng. (ICSE-24) Second Workshop Open Source Software Eng., pp. 669-670, 2002.
[4] J. Feller, B. Fitzgerald, and A. Hoek, “Making Sense of the Bazaar: First Workshop Open Source Software Engineering,” ACM SIGSOFT Software Eng. Notes, vol. 26, no. 6, pp. 51-52, 2001.
[5] N. Fenton and S.L. Pfleeger, Software MetricsA Rigorous and Practical Approach, second ed. London: Int'l Thompson Computer Press, 1997.
[6] B. Fitzgerald and T. Kenny, “Developing an Information Systems Infrastructure With Open Source Software,” IEEE Software, vol. 21, no. 1, pp. 50-55, Jan.-Feb. 2004.
[7] K. Fogel, Open Source Development with CVS, first ed. Coriolis Open Press, http:/, 1999.
[8] E. Gamma, R Helm, R. Johnson, and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, 1995.
[9] M. Godfrey and Q. Tu, “Evolution in Open Source Software: A Case Study,” Proc. Int'l Conf. Software Maintenance (ICSM), pp. 131-142, 2000.
[10] F. Kerlinger, Foundations of Behavioral Research, third ed. Orlando, Fla: Harcourt Brace Jovaonvich College Publishers, 1986.
[11] D. Krantz, R. Luce, P. Suppes, and A. Tversky, Foundations of Measurement, volume I Additive and Polynomial Representations. New York: Academic Press, 1971.
[12] T. Lawrie and C. Gacek, “Issues of Dependability In Open Source Software Development,” ACM SIGSOFT Software Eng. Notes, vol. 27, no. 3, pp. 34-37, 2002.
[13] A. Lonconsole, D. Rodriguez, J. Borstler, and R. Harrison, “Report on Metrics 2001: The Science & Practice Of Software Metrics Conference,” ACM SIGSOFT Software Eng. Notes, vol. 26, no. 6, pp. 52-57, 2001.
[14] S. Lussier, “New Tricks: How Open Souce Changed the Way My Team Works,” IEEE Software, vol. 21, no. 1, pp. 68-72, Jan.-Feb. 2004.
[15] D.G. Messerschmitt, “Back to the User,” IEEE Software, vol. 21, no. 1, pp. 89-90, Jan.-Feb. 2004.
[16] J. Michell, An Introduction to the Logic of Psychological Measurement. Hillsdale, N.J.: Lawrence Erlbaum Assoc., 1990.
[17] A. Mockus, T. Fielding, and D. Herbsleb, “Two Case Studies of Open Source Software Development: Apache and Mozilla,” ACM Trans. Software Eng. and Methodology, vol. 11, no. 3, pp. 309-346, July 2002.
[18] Netcraft, “Nearly 2 Million Active Sites Running FreeBSD,” Netcraft, July 2003, 12nearly_2_million_active_sites_running_freebsd.htm .
[19] J.S. Norris, “Mission-Critical Development with Open Sourse Software: Lessons Learned,” IEEE Software, vol. 21, no. 1, pp. 42-49, Jan.-Feb. 2004.
[20] J. Nunnally, Psychometric Theory, second ed. McGraw-Hill, 1978.
[21] G. Perkins, “Cultural Clash and the Road to World Domination,” IEEE Software, vol. 16, no. 1, pp. 23-25, Jan./Feb. 1999.
[22] GNATS GNU Project, Gnats (version 4.0),, 2003.
[23] The Free BSD Project, FreeBSD (version 5.0), [computer software], http:/, 2003.
[24] E.S. Raymond, “Up from Alchemy,” IEEE Software, vol. 21, no. 1, pp. 88-90, Jan.-Feb. 2004.
[25] S. Schach, B. Jin, D. Wright, G. Heller, and J. Offutt, “Maintainability of the Linux Kernel,” IEE Proc.Software, vol. 149, no. 1, pp. 18-23, Feb. 2002.
[26] N. Serrano, S. Calzada, J.M. Sarriegui, and I. Ciordia, “From Proprietary to Open Source Tools in Information Systems Development,” IEEE Software, vol. 21, no. 1, pp. 56-58, Jan.-Feb. 2004.
[27] G. Wilson, “Is the Open Source Community Setting a Bad Example?” IEEE Software, vol. 16, no. 1, pp. 23-25, Jan./Feb. 1999.
[28] C. Wohlin, P. Runeson, M. Host, M. Ohlsson, B. Regnell, and A. Wesslen, Experimentation in Software Engineering: An Introduction. Kluwer Academic, 2000.
[29] M. Wu and Y. Lin, “Open Source Software Development: An Overview,” Computer, vol. 46, no. 6, pp. 33-38, June 2001.

Index Terms:
Index Terms- Software engineering process, process measurement, qualitative process analysis, testing and debugging, reliability, maintenance process, maintainability, open source software, measurement, defect density, code ownership, FreeBSD.
Trung T. Dinh-Trong, James M. Bieman, "The FreeBSD Project: A Replication Case Study of Open Source Development," IEEE Transactions on Software Engineering, vol. 31, no. 6, pp. 481-494, June 2005, doi:10.1109/TSE.2005.73
Usage of this product signifies your acceptance of the Terms of Use.