Lessons learned from an open-source University Project P. Basdaras, K. Chalkias, A. Chatzigeorgiou, I. Deligiannis, P. Tsakiri, N. Tsantalis Department of Applied Informatics University of Macedonia Thessaloniki, Greece 10 th Int. WSEAS Conf. on Computers, July 13, 2006, Vouliagmeni, Greece
18
Embed
Lessons learned from an open-source University Project P. Basdaras, K. Chalkias, A. Chatzigeorgiou, I. Deligiannis, P. Tsakiri, N. Tsantalis Department.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Lessons learned from an open-source
University Project
P. Basdaras, K. Chalkias, A. Chatzigeorgiou, I. Deligiannis,
P. Tsakiri, N. Tsantalis
Department of Applied Informatics
University of Macedonia
Thessaloniki, Greece
10th Int. WSEAS Conf. on Computers, July 13, 2006, Vouliagmeni, Greece
Motivation
• Open-source software development widespread trend
• According to OSI, the basic idea behind open-source software
is that when programmers are free to read, redistribute and
modify the source code, the software evolves
• First spark: Netscape's Navigator (1998)
Motivation
• July 2005: Project Initiation
• CSSE Lab, Dept. Applied Informatics, U. of Macedonia, Greece
• Aims:
• to help students understand practices and become familiar
with the philosophical, technological, legal and social issues
• to log all aspects of the software development process • software versions• development effort• programmer capability• LOC• types of changes
• Can be expanded to many directions:• filling coupons• Statistical analysis of past data• Visualization• Use of AI• Information retrieval from Web• Risk analysis, portfolio management
www.openbet.gr
Project Description
• Programming Language: Java
• object-oriented language modular
• undegrads in our Dept. are familiar with Java
• large number of available API's facilitates development
• Development based on a widely used CVS
• Administrative team checks submitted code
• Every student is free to enhance functionality
• Project's Homepage maintains a "to do list"
Data Collection
• To obtain an account each participant provides info:
• age, studies, programming experience etc
• When committing a class (smallest piece of code than can be submitted):
Class Name: Consumed Time (mins):Maintenance adaptive: corrective: perfective:Locality of change Local: Propagated: origin of propagation (list):
Supporting Software
• Diff tool for comparing different versions
• extracts new, deleted, modified classes/methods
• Log form Analyzer
• records and visualizes information provided by developers
Observations
• Student participation helps to comprehend basic practices and
tools
• Development is carried out by a small group
• Intense activity when new requirements are published
• Number of bugs is limited
• Responsibility in following formal/informal rules