Evaluation criteria for free/open source software products based on project analysis

Software Process Improvement and Practice

Volumn 11, Issue 2, 2006, Pages 107-122

  Cruz, David ^a   Wieland, Thomas ^b   Ziegler, Alexander ^a  

^a TECHNICAL UNIVERSITY OF MUNICH   (Germany)

^b Robotics Research Lab   (Germany)

Author keywords

F OSS; Free software; Open source; OSS; Product evaluation; Project analysis

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; COMPUTER APPLICATIONS; COMPUTER SCIENCE; DECISION THEORY; EDUCATION; INFORMATION TECHNOLOGY; PROBLEM SOLVING;

F/OSS; FREE SOFTWARE; OPEN SOURCE; OSS; PRODUCT EVALUATION; PROJECT ANALYSIS;

SOFTWARE ENGINEERING;

EID: 33744787136     PISSN: 10774866     EISSN: 10991670     Source Type: Journal    
DOI: 10.1002/spip.257     Document Type: Article

References (19)

1. Asklund U, Bendix L. 2002. A Study of configuration management in open source software projects. IEE Proceedings-Software 149(1): 40-46.
2. Boyle EI, Wenig S, Gollub J, Jin H, Botstein D, Cherry JM, Sherlock G. 2004. Go::TermFinder-open source software for accessing Gene Ontology information and finding significantly enriched Gene Ontology terms associated with a list of genes. Bioinformatics 20(18): 3710-3715.
3. Chen K, Schach SR, Yu L, Offutt J, Heller GZ. 2004. Open-source change logs. Empirical Software Engineering 9(3): 197-210.
4. Crownston K, Scozzi B. 2002. Open source software projects as virtual organisations: competency rallying for software development. IEE Proceedings-Software 149(1): 3-17.
5. DeLano WL. 2005. The case for open-source software in drug discovery. Drug Discovery Today 10(3): 213-217.
6. Feller J, Fitzgerald B. 2002. Understanding Open Source Software Development. Addison Wesley: London, UK.
7. Grand S, von Krogh G, Leonard D, Swap W. 2004. Resource allocation beyond firm boundaries: A multi-level model for open source innovation. Long Range Planning 37: 591-610.
8. Hang J, Hohensohn H, Mayr K, Wieland T. Benefits and pitfalls of open source in commercial contexts. In Free/Open Source Software Development. Koch S (ed.). IDEA Group: Hershey, PA, 2004. 222-241.
9. Hissam SA, Plakosh D, Weinstock C. 2002. Trust and vulnerability in open source software. IEE Proceedings-Software 149(1): 47-51.
10. Institute of Electrical and Electronics Engineers. 1990. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. The Institute of Electrical and Electronics Engineers: New York.
11. Koch S, Schneider G. 2002. Effort, co-operation and co-ordination in an open source software project: GNOME. Information Systems Journal 12: 27-42.
12. Kontio J. 1996. A case study in applying a systematic method for COTS selection. In Proc. 18th Int'l Conf. on Software Engineering (ICSE'96), Rombach HD (ed.). ACM/IEEE-CS Press: New York, Berlin, Germany, 201-209.
13. Lussier S. 2004. New tricks: How open source changed the way my team works. IEEE Software 21(1): 68-72.
14. Morisio M, Seaman CB, Basili VR, et al. 2002. COTS-based software development: Processes and open issues. Journal of Systems and Software 61(3): 189-199.
15. O'Mahony S. 2003. Guarding the commons: how community managed software projects protect their work. Research Policy 32: 1179-1198.
16. Payne C. 2002. On the security of open source software. Information Systems Journal 12: 61-78.
17. Seifert T, Wieland T. 2003. Prerequisites for enterprises to get involved in open source software development. In 1st Workshop of Open Source Software in Industrial Environments. Proceedings of Net.ObjectDAYS, Erfurt, Germany.
18. Sharma S, Sugumaran V, Rajagopolan B. 2002. A framework for creating hybrid-open source software communities. Information Systems Journal 12: 7-25.
19. Yoo TS, Ackermann MJ. 2005. Open source software for medical image processing and visualisation. Communications of the ACM 48(2): 55-59.