Christian R. Prause
ABSTRACT
With multiple developers engaged in collaboratively writing software code, responsibility for a specific piece of code is difficult to assign. Nonetheless, responsibility is a major factor in achieving quality and preventing code from being developed carelessly. We present a new approach 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 in order to not endanger team spirit.
- J. Aiken. Technical and human perspectives on pair programming. SIGSOFT Software Engineering Notes, 29(5):1--14, 2004. Google Scholar
Digital Library
- Z. Bar-Yossef, T. S. Jayram, R. Krauthgamer, and R. Kumar. Approximating edit distance efficiently. In 45th Annual IEEE Symposium on Foundations of Computer Science, pages 550--559. IEEE, Oct. 2004. Google ScholarDigital Library
- E. M. Burke and B. M. Coyner. Java Extreme Programming Cookbook. O?Reilly, 2003. Google ScholarDigital Library
- G. Canfora, L. Cerulo, and M. D. Penta. Identifying changed source code lines from version repositories. In Proceedings of fourth International Workshop on Mining Software Repositories. IEEE, 2007. Google ScholarDigital Library
- B. Curtis, W. E. Hefley, and S. Miller. Overview of the people capability maturity model. Technical report, SEI - Carnegie Mellon University, 1995.Google Scholar
- L. E. Deimel and M. Pozefsky. Implementation of programming standards in a computer science department. In Proceedings of the 17th Annual Southeast Regional Conference. ACM Press, 1979. Google ScholarDigital Library
- A. Dunsmore, M. Roper, and M. Wood. Object-oriented inspection in the face of delocalisation. In Proceedings of the 22nd international conference on Software engineering, pages 467--476, New York, NY, USA, 2000. ACM Press. Google ScholarDigital Library
- J. Elster. The Cement of Society. A Study of Social Order. Cambridge University Press, 1989.Google ScholarCross Ref
- M. Fagan. Design and code inspections to reduce errors in program development. IBM Systems Journal, 15(3):182--211, 1976.Google ScholarDigital Library
- H. S. Gordon. The economic theory of a common-property resource: The fishery. Bulletin of Mathematical Biology, 53(1/2):231--252, 1991.Google ScholarCross Ref
- W. S. Humphrey. Managing Technical People. Addison-Wesley, 1997.Google Scholar
- P. M. Johnson and D. Tjahjono. Assessing software review meetings: a controlled experimental study using csrs. In Proceedings of the 19th international conference on Software engineering, pages 118--127, New York, NY, USA, 1997. ACM Press. Google ScholarDigital Library
- D. Kelly and T. Shepard. Qualitative observations from software code inspection experiments. In Conference of the Centre for Advanced Studies on Collaborative Research, page 5. IBM Press, 2002. Google ScholarDigital Library
- O. Kobayashi, M. Kawabata, M. Sakai, and E. Parkinson. Analysis of the interaction between practices for introducing xp effectively. In Proceedings of the 28th International Conference on Software Engineering, pages 544--550, New York, USA, 2006. Google ScholarDigital Library
- V. I. Levenshtein. Binary codes capable of correcting deletions, insertions, and reversals. Soviet Physics-Doklady, 10(8):707--710, February 1966.Google Scholar
- R. Lowrance and R. A. Wagner. An extension of the string-to-string correction problem. Journal of ACM, 22(2):177--183, 1975. Google ScholarDigital Library
- A. Mackus, R. Fielding, and J. D. Herbsleb. Two case studies of open source software development: Apache and mozilla. ACM Transactions on Software Engineering and Methodology, 11(3):309--346, 2002. Google ScholarDigital Library
- P. McCarthy, A. Porter, H. Siy, and L. G. Votta. An experiment to assess cost-benefits of inspection meetings and their alternatives. In Proceedings of the International Metrics Symposium, 1996. Google ScholarDigital Library
- S. McConnell. Code Complete: A Practical Handbook of Software Construction. Microsoft Press, 1993. Google ScholarDigital Library
- C. R. Prause and M. Eisenhauer. Social aspects of a continuous inspection platform for software source code. In CHASE '08: Proceedings of the workshop on Cooperative and Human Aspects of Software Engineering, New York, NY, USA, 2008. ACM. Google ScholarDigital Library
- C. B. Seaman and V. R. Basili. An empirical study of communication in code inspections. In Proceedings of the 19th international conference on Software engineering, New York, NY, USA, 1997. ACM Press. Google ScholarDigital Library
- H. Sutter and A. Alexandrescu. C++ Coding Standards. Addison-Wesley, 2005.Google Scholar
- A. S. Tanenbaum. Modern Operating Systems. Prentice Hall, 2001. Google ScholarDigital Library
- L. von Ahn and L. Dabbish. Labeling images with a computer game. In Proceedings of the SIGCHI conference on Human factors in computing systems, pages 319--326, New York, USA, 2004. ACM Press. Google ScholarDigital Library
- R. A. Wagner and M. J. Fischer. The string-to-string correction problem. JournalACM, 21(1):168--173, 1974. Google ScholarDigital Library
- K. E. Wiegers. Peer Reviews in Software: A Practical Guide. Addison-Wesley, 2002. Google ScholarDigital Library
Index Terms
- An approach for continuous inspection of source code
Recommendations
A catalogue of lightweight visualizations to support code smell inspection
SoftVis '08: Proceedings of the 4th ACM symposium on Software visualizationPreserving the integrity of software systems is essential in ensuring future product success. Commonly, companies allocate only a limited budget toward perfective maintenance and instead pressure developers to focus on implementing new features. ...
A method for detecting faulty code violating implicit coding rules
IWPSE '02: Proceedings of the International Workshop on Principles of Software EvolutionIn the field of legacy software maintenance, there unexpectedly arise a large number of implicit coding rules --- which are seldom written down in specification documents or design documents --- as software becomes more complicated than it used be. ...
Social aspects of a continuous inspection platform for software source code
CHASE '08: Proceedings of the 2008 international workshop on Cooperative and human aspects of software engineeringDetermining 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 ...
Comments