skip to main content
10.1145/2025113.2025166acmconferencesArticle/Chapter ViewAbstractPublication PagesfseConference Proceedingsconference-collections
short-paper

Reputation-based self-management of software process artifact quality in consortium research projects

Published:09 September 2011Publication History

ABSTRACT

This paper proposes a PhD research that deals with improving internal documentation in software projects. Software developers often do not like to create documentation because it has few value to the individual himself. Yet the purpose of internal documentation is to help others understand the software and the problem it addresses. Documentation increases development speed, reduces software maintenance costs, helps to keep development on track, and mitigates the negative effects of distance in distributed settings. This research aims to increase the individuals' motivation to write documentation by means of reputation. The CollabReview prototype is a web-based reputation system that analyzes artifacts of internal documentation to derive personal reputation scores. Developers making many good contributions will achieve higher reputation scores. These scores can then be employed to softly influence developer behavior, e.g. by incentivizing them to contribute to documentation with social rewards. No strict rule enforcement is necessary.

References

  1. D. Bertram, A. Voida, S. Greenberg, and R. Walker. Communication, collaboration, and bugs: the social nature of issue tracking in small, collocated teams. In CSCW, pages 291--300. ACM, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. B. Boehm. Get ready for agile methods, with care. Computer, 35:64--69, 2002. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. N. Brown, Y. Cai, Y. Guo, R. Kazman, M. Kim, P. Kruchten, E. Lim, A. MacCormack, R. Nord, I. Ozkaya, R. Sangwan, C. Seaman, K. Sullivan, and N. Zazworka. Managing technical debt in software-reliant systems. In FoSER. ACM, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. R. H. Coase. The problem of social cost. The Journal of Law and Economics, 3(1):1--44, 1960.Google ScholarGoogle ScholarCross RefCross Ref
  5. B. Curtis, H. Krasner, and N. Iscoe. A field study of the software design process for large systems. Communications of the ACM, 31:1268--1287, 1988. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. S. Dencheva, C. R. Prause, and W. Prinz. Dynamic self-moderation in a corporate wiki to improve participation and contribution quality. In Eur. Conf. Comp.-Supp. Coop. Work, ECSCW. Springer, 2011.Google ScholarGoogle ScholarCross RefCross Ref
  7. A. Forward and T. C. Lethbridge. The relevance of software documentation, tools and technologies: a survey. In DocEng, pages 26--33. ACM, 2002. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. G. Hardin. The tragedy of the commons. Science, 162:1243--1248, 1968.Google ScholarGoogle ScholarCross RefCross Ref
  9. M. Harman. Why source code analysis and manipula- tion will always be important. In SCAM. IEEE, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. B. Hoisl, W. Aigner, and S. Miksch. Social rewarding in wiki systems -- motivating the community. In Online Communities and Soc. Comp. Springer, 2007. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. A. Hunt and D. Thomas. The Pragmatic Programmer. Addison-Wesley Longman, 1999. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. A. Jøsang, R. Ismail, and C. Boyd. A survey of trust and reputation systems for online service provision. Decision Support Systems, 43(2):618--644, 2007. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. W. E. Lewis. Software Testing and Continuous Quality Improvement. Auerbach, 2005. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. B. P. Lientz and E. B. Swanson. Problems in application software maintenance. Communications of the ACM, 24(11):763--769, 1981. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. J. S. Poulin. Populating software repositories: Incentives and domain-specific software. Journal of Systems and Software, 30:187--199, 1995. Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. C. Prause, J. Kuck, S. Apelt, R. Oppermann, and A. B. Cremers. Interconnecting documentation - harnessing the different powers of current documentation tools in software development. In Ninth ICEIS, volume ISAS, pages 63--68. INSTICC, 2007.Google ScholarGoogle Scholar
  17. C. R. Prause. Maintaining fine-grained code metadata regardless of moving, copying and merging. In 9th International Working Conference on Source Code Analysis and Manipulation, SCAM. IEEE, 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. C. R. Prause. A software project perspective on the fitness and evolvability of personal learning environments. In Exploring the Fitness and Evolvability of Personal Learning Environments, 2011.Google ScholarGoogle Scholar
  19. C. R. Prause and S. Apelt. An approach for continuous inspection of source code. In International Workshop on Software quality, WoSQ. ACM, 2008. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. C. R. Prause and M. Eisenhauer. Social aspects of a continuous inspection platform for software source code. In Workshop on Cooperative and Human Aspects of Software Engineering, CHASE. ACM, 2008. Google ScholarGoogle ScholarDigital LibraryDigital Library
  21. C. R. Prause, M. Jentsch, and M. Eisenhauer. Mica - a mobile support system for warehouse workers. International Journal of Handheld Computing Research (IJHCR), 2(1):1--24, January-March 2011. Google ScholarGoogle ScholarDigital LibraryDigital Library
  22. C. R. Prause, R. Reiners, and S. Dencheva. Empirical study of tool support in highly distributed research projects. In 5th International Conference on Global Software Engineering, ICGSE, pages 23--32. IEEE Computer Society, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. C. R. Prause, R. Reiners, S. Dencheva, and A. Zimmermann. Incentives for maintaining high- quality source code. In Psychology of Programming Work in Progress Meeting, PPIG WiP, 2010.Google ScholarGoogle Scholar
  24. J. Raskin. Comments are more important than code. ACM Queue, 3(2):64--62 (sic!), 2005. Google ScholarGoogle ScholarDigital LibraryDigital Library
  25. B. Selic. Agile documentation, anyone? IEEE Software, 26(6):11--12, Nov/Dec 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  26. D. Spinellis. Code documentation. IEEE Software, 27:18--19, 2010. Google ScholarGoogle ScholarDigital LibraryDigital Library
  27. R. D. Stacey. Strategic Management and Organisational Dynamics: the challenge of complexity. Financial Times, 1999.Google ScholarGoogle Scholar
  28. M. Umarji and F. Shull. Measuring developers: Aligning perspectives and other best practices. IEEE Software, 26(6):92--94, Nov./Dec. 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  29. L. Williams and B. Kessler. The effects of "pair-pressure" and "pair-learning" on software engineering education. In 13th Conference on Software Engineering Education & Training. IEEE, 2000. Google ScholarGoogle ScholarDigital LibraryDigital Library
  30. S. Wray. How pair programming really works. IEEE Software, 27:50--55, 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  31. T. Yamabe, V. Lehdonvirta, H. Ito, H. Soma, H. Kimura, and T. Nakajima. Applying pervasive technologies to create economic incentives that alter consumer behavior. In UbiComp. ACM, 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Reputation-based self-management of software process artifact quality in consortium research projects

      Recommendations

      Comments

      Login options

      Check if you have access through your login credentials or your institution to get full access on this article.

      Sign in
      • Published in

        cover image ACM Conferences
        ESEC/FSE '11: Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
        September 2011
        548 pages
        ISBN:9781450304436
        DOI:10.1145/2025113

        Copyright © 2011 ACM

        Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

        Publisher

        Association for Computing Machinery

        New York, NY, United States

        Publication History

        • Published: 9 September 2011

        Permissions

        Request permissions about this article.

        Request Permissions

        Check for updates

        Qualifiers

        • short-paper

        Acceptance Rates

        Overall Acceptance Rate17of128submissions,13%

        Upcoming Conference

        FSE '24

      PDF Format

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader