Code complete: a practical handbook of software construction
Code complete: a practical handbook of software construction
An empirical study of communication in code inspections
ICSE '97 Proceedings of the 19th international conference on Software engineering
Assessing software review meetings: a controlled experimental study using CSRS
ICSE '97 Proceedings of the 19th international conference on Software engineering
Object-oriented inspection in the face of delocalisation
Proceedings of the 22nd international conference on Software engineering
A guided tour to approximate string matching
ACM Computing Surveys (CSUR)
Peer reviews in software: a practical guide
Peer reviews in software: a practical guide
Implementation of programming standards in a computer science department
ACM-SE 17 Proceedings of the 17th annual Southeast regional conference
Modern Operating Systems
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Qualitative observations from software code inspection experiments
CASCON '02 Proceedings of the 2002 conference of the Centre for Advanced Studies on Collaborative research
Labeling images with a computer game
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Technical and human perspectives on pair programming
ACM SIGSOFT Software Engineering Notes
Code Quality: The Open Source Perspective (Effective Software Development Series)
Code Quality: The Open Source Perspective (Effective Software Development Series)
Java extreme programming cookbook
Java extreme programming cookbook
An approach for continuous inspection of source code
Proceedings of the 6th international workshop on Software quality
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Hi-index | 0.00 |
Determining responsibility for a piece of source code is difficult when software is being developed collaboratively with weak code ownership. Nonetheless, a major factor for preventing "cowboy coding" and careless development of code is liability. We propose a tool for statistically acquiring per developer per document accountabilities and enable learning and self-monitoring processes within a development team while maintaining anonymity to a certain degree to not endanger team spirit. In this paper we want to examine possible social effects on the development team that employment of our tool has.