http://www.spinellis.gr/pubs/conf/2008-MSR-contr/html/GKS08.html This is an HTML rendering of a working paper draft that led to a publication. The publication should always be cited in preference to this draft using the following reference:
|
© ACM, 2008. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in the conference's proceedings, listed above.
Asset | Action | ID | Type |
Add lines of code of good/bad quality | CAL | P/N | |
Commit new source file or directory | CNS | P | |
Commit code that generates/closes a bug | CCB | N/P | |
Add/Change code documentation | CAD | P | |
Commit fixes to code style | CSF | P | |
Commit more than X files in a single commit | CMF | N | |
Commit documentation files | CDF | P | |
Commit translation files | CDF | P | |
Commit binary files | CBF | N | |
Commit with empty commit comment | CEC | N | |
Commit comment that awards a pointy hat | CPH | P | |
Commit comment that includes a bug report num | CBN | P | |
First reply to thread | MRT | P | |
Start a new thread | MST | P | |
Participate in a flamewar | MFW | N | |
Close a lingering thread | MCT | P | |
Bug Database | Close a bug | BCL | P |
Report a confirmed/invalid bug | BRP | P/N | |
Close a bug that is then reopened | BCR | N | |
Comment on a bug report | BCR | P | |
Wiki | Start a new wiki page | WSP | P |
Update a wiki page | WUP | P | |
Link a wiki page from documentation/mail file | WLP | P | |
IRC | Frequent participation to IRC | IFP | P |
Prompt replies to directed questions | IRQ | P |
| (1) |
| (2) |
| (3) |
| (4) |
Criterion | Our Metric |
Purpose | Assess developer contribution in agile and distributed working environments. |
Scope | A project developed by a distributed workgroup |
Measured Attribute | Degree of contribution to the development process |
Attribute Scale | Ratio scale |
Attribute Variability | There is no knowledge of the variability of the measured attribute prior to performing the measurements |
Metric Function | The proposed metric counts and weights the number of actions on project assets and the lines of code on a per developer basis. The highest those counts are, the more a developer has contributed to a project (see section 3) |
Metric Scale | Ratio scale: The higher the contribution value, the more a developer has offered to the project. |
Variability of readings | Some metric components are based on heuristics which may not work in certain cases. This may affect measurements in non-foreseeable ways. Metric components showing unstable results should be identified and excluded from the final version of the model. |
Attribute and Metric Relationship | The metric generally captures changes in the attribute well. Metric components are analogous to contribution, subject to variability. For 2 given developers d1 and d2, the equation c(d1) + c(d2) = c(d1+d2) is always valid. |
Side effects | No side effects can be foreseen. As the metric takes into account a variety of factors and it is automatically calculated it is difficult for developers to change their behavior towards optimizing the metric without increasing their actual contribution. |