Academia.eduAcademia.edu

Outline

Title
Abstract
Introduction
Scope
Software Design and Modelling
Conclusion
References
All Topics
Sociology

Fifty years of the psychology of programming

Profile image of Marian PetreMarian Petre

2019, International journal of human-computer studies

https://doi.org/10.1016/J.IJHCS.2019.06.009
visibility

…

description

33 pages

link

1 file

Abstract

For guidance on citations see FAQs.

Related papers

Behavioral Science of Software Engineering
Luke Church

IEEE Software

View PDFchevron_right
Software psychology: The need for an interdisciplinary program
Bill Curtis, elliot soloway

Proceedings of the IEEE, 2000

of computer users who have no formal mathematical, engineering, or computer science training. This review focuses on the state o f the art in Software Psychology-the study of human factors in computer systems. One area of software psychology, the psychology of programming, is picked for an in-depth discussion of research results. This area was selected for its interest to the readers of the PROCEEDINGS OF THE IEEE. The review then discusses the methodological issues involved in performing experimental research in software psychology. future trends are discussed both for the programming research reviewed here and for the whole field o f software psychology. The conclusions identify multidisciplinary training and research as critical to further progress in this field.

View PDFchevron_right
On the use of psychology in evaluating software documentation
Deborah Boehm-davis

Behavior Research Methods & Instrumentation, 1983

Recent research evaluating the usefulness of program documentation has borrowed techniques used in psychology to define the variables of interest and to measure those variables. The results of the research suggest that (1) using a branching or sequential program design language (POL) produces performance that is superior to that found with other formats (such as flowcharts), and (2) using a detailed design written in a POL leads to superior coding performance over other formats due, in part, to the small amount of translation that is required in mapping from the design to the code. These conclusions are based primarily on time and accuracy data. This paper discusses the research conducted in this area and the conclusions drawn. The influence of the methodology used to conduct these experiments on the evaluation of programmer performance is also discussed.

View PDFchevron_right
Modern Programming Practices: Implications for Human Factors Research
Michael Samet

[Incl IA i fi PH SECURITY CL.ASSIFICATION OF 'iiS PAGE 'When Dol. EnteredJ REPORT DOCUMENTATION PAGE BEFRE CL NORM I. REPORT UMBER 02. GOVT ACCESSION O. 3 REC T'S CATALOG NUMBER Research Note 80-18' 4i-4 0 _____________ 4. T'lT'-.Z 'and Su~btitle)

View PDFchevron_right
Software psychology: Human factors in computer and information systems. Ben Shneiderman. Cambridge, Mass.: Winthrop, 1980. Pp. xiv + 320
Marc Sebrechts

Applied Psycholinguistics, 1982

View PDFchevron_right
Behavioral Science and Diversity in Software Engineering
Henry Muccini

IEEE Software, 2021

View PDFchevron_right
On the difficulty of replicating human subjects studies in software engineering
Jorge Aranda

… Engineering, 2008. ICSE …, 2009

View PDFchevron_right
Models of motivation in software engineering
Helen Sharp

Information and Software Technology, 2009

For guidance on citations see FAQs.

View PDFchevron_right
Empirical studies of software engineering
Marian Petre

International Journal of Human-Computer Studies, 2004

Empirical studies of software engineering The Psychology of Programming Interest Group (PPIG) and Evaluation and Assessment in Software Engineering (EASE) are both 'grass roots' communities, one motivated by cognitive psychologists, the other by software engineers. Both examine theoretical and methodological issues in software development-but from different perspectives and traditions. Questions about software development, ranging from fundamental issues of problem solving and representation to highly applied issues of development processes and software maintenance, are complex and inherently interdisciplinary, making it essential that they be addressed from a variety of scientific perspectives. The PPIG and EASE constituencies have long sought ways to interact in order to broaden the discourse and embrace multiple perspectives. PPIG and EASE colocated their annual conferences in April 2003 at Keele University, supported by a grant from the UK's Engineering and Physical Sciences Research Council (EPSRC). The aim was to take advantage of the co-location to promote joint activities targeted at improving cross-fertilization of ideas between the two groups, and through them between psychology of programming and software engineering more generally. Cross-fertilization provides leverage to bring industrial relevance to psychology of programming pursuits, and to bring psychology of programming insights into empirical software engineering, thus contributing both to well-grounded theory about software engineering processes and to well-informed software development practice.

View PDFchevron_right
REFERENCING IN PSYCHOLOGICAL RESEARCH
Benjamin Omolayo

Fundamentals of Psychological Research, 2019

Literarily, “re-search” is synonymous to “searching again” meaning that a search has been done initially, and that another search is being carried out in order to discover something new or to further develop what has been done before. Human wisdom demands that when an individual does a research, and makes use of another person’s idea to solve a problem or in improving the understanding of a particular phenomenon, it is considered necessary that such a person, whose knowledge was used be recognised and acknowledged. The essence of referencing in psychological research or in any other discipline is to give credit to the researcher(s), whose ideas have been used or referred to in a new research study. Referencing is a way of acknowledging the sources of the words or ideas used in one’s research papers, articles, presentations and assignments. Since these ideas do not constitute part of personal intellectual property, ethics demands that a kind of recognition be given to the individual whose knowledge has been employed in a research. Invariably, the essence of referencing is to give credit to authors whose ideas have been used in a piece of academic work, and also to give some information to readers about the author and his/her work for further reading and clarification. It should be noted that referencing is very essential in research papers, essays and articles because these “rely heavily on empirical evidence” (Psychology Writing Centre, 2010, p.1).

View PDFchevron_right

References (71)

  1. Aaron, S., Blackwell, A.F. and Burnard, P. (2016). The development of Sonic Pi and its use in educational partnerships: co-creating pedagogies for learning computer programming. Journal of Music, Technology and Education 9(1), 75-94.
  2. Baddeley, A. D., and Hitch, G. (1974). Working memory. In Psychology of Learning and Motivation, 8, pp. 47- 89. Academic Press.
  3. Beckwith, L., Kissinger, C., Burnett, M., Wiedenbeck, S. , Lawrance, J., Blackwell, A., and Cook, C. (2006). Tinkering and gender in end-user programmers' debugging. ACM Conference on Human Factors in Computing Systems, pp. 231-240.
  4. Bellamy, R.K.E., and Carroll, J.M. (1992) Re-structuring the programmer's task. International Journal of Man- Machine Studies, 37(4), pp. 503-527.
  5. Bellucci, A., Vianello, A., Florack, Y., Micallef, L. and Jacucci, G. (2019). Augmenting objects at home through programmable sensor tokens: A design journey. International Journal of Human-Computer Studies 122, 211-231.
  6. Bergstrom, I., and Blackwell, A.F. (2016). The Practices of Programming. In Proceedings of IEEE Visual Languages and Human-Centric Computing (VL/HCC) 2016.
  7. Blackwell, A.F. (1996). Metacognitive theories of visual programming: What do we think we are doing? In Proceedings IEEE Symposium on Visual Languages, pp. 240-246.
  8. Blackwell, A.F. (2002a). What is programming? In Proceedings of PPIG 2002, pp. 204-218.
  9. Blackwell, A.F. (2002b). First steps in programming: A rationale for Attention Investment models. In Proceedings of the IEEE Symposia on Human-Centric Computing Languages and Environments, pp. 2-10.
  10. Blackwell, A.F. (2006). Ten years of cognitive dimensions in visual languages and computing. Journal of Visual Languages and Computing, 17(4), pp. 285-287.
  11. Blackwell, A.F. (2018). A craft practice of programming language research. In Proceedings of PPIG 2018.
  12. Blackwell, A., and Collins, N. (2005). The Programming Language as a Musical Instrument. In Proceedings of PPIG 2005, pp. 120-130.
  13. A C C E P T E D M A N U S C R I P T Blackwell, A.F. and Morrison, C. (2010). A logical mind, not a programming mind: Psychology of a professional end-user. PPIG 2010, pp. 175-184.
  14. Blackwell, A.F., Rode, J.A. and Toye, E.F. (2009). How do we program the home? Gender, attention investment, and the psychology of programming at home. International Journal of Human Computer Studies 67, 324-341.
  15. Blackwell, A.F., McLean, A., Noble, J. and Rohrhuber, J. (2014). Collaboration and learning through live coding. Dagstuhl Reports 3(9), 130-168. Edited in cooperation with Jochen Arne Otto.
  16. Blandford, A.E., Buckingham Shum, S.J., Young, R.M. (1998). Training software engineers in a novel usability evaluation technique. International Journal of Human Computer Studies, 49(3), pp. 245-279.
  17. Bødker, S. (2015). Third-wave HCI, 10 years later---participation and sharing. Interactions, 22(5), pp. 24-31.
  18. Brooks, F.P. (1975). The Mythical Man-Month. Addison-Wesley.
  19. Brooks, R. (1977). Towards a theory of the cognitive processes in computer programming. International Journal of Man-Machine Studies, 9(6), 737-751.
  20. Brooks, R. E. (1980). Studying programmer behavior experimentally: The problems of proper methodology. Communications of the ACM, 23(4), 207-213.
  21. Bryant, S., Romero, P. and du Boulay, B. (2008). Pair programming and the mysterious role of the navigator. International Journal of Human-Computer Studies 66(7), 519-529
  22. du Boulay, B., O'Shea, T., & Monk, J. (1981). The black box inside the glass box: presenting computing concepts to novices. International Journal of Man-Machine Studies, 14(3), pp. 237-249.
  23. Chee, Y.S. (1993). Applying Gentner's theory of analogy to the teaching of computer programming. International Journal of Man-Machine Studies, 38(3), pp. 347-368.
  24. Church, L. and M r oiu, M. (2016). A fox not a hedgehog: What does PPIG know? In Proceedings of PPIG 2016.
  25. Clarke, S. (2006) Evaluating a new programming language. In Proceedings of PPIG 2006, pp. 131-139.
  26. A C C E P T E D M A N U S C R I P T Clarke, S., Söderberg, E., and Luff, M. (2016) Panel discussion: PPIG in the wild -what should we be studying? Collins, N., McLean, A., Rohrhuber, J., & Ward, A. (2003). Live coding in laptop performance. Organised Sound, 8(3), 321-330.
  27. Curtis, B., Krasner, H., & Iscoe, N. (1988). A field study of the software design process for large teams. Communications of the ACM, 31(11), pp. 1268-1287.
  28. Davies, S.P. (1990). The nature and development of programming plans. International Journal of Man-Machine Studies, 32(4), pp. 461-481.
  29. Eco, U. (1995). The Search for the Perfect Language. Oxford: Blackwell.
  30. Ernst, G. W., & Newell, A. (1969). GPS: A case study in generality and problem solving. Academic Press. ISBN 9780122410505.
  31. Flor, N. V., & Hutchins, E. L. (1991). A case study of team programming during perfective software maintenance. Empirical Studies of Programmers: Fourth Workshop, p. 36-56. Intellect Books.
  32. Gentner, D., & Stevens, A. L. (Eds.) (1983). Mental Models. Psychology Press.
  33. Gilmore, D. J. Green, T. R. G. (1984). Comprehension and recall of miniature programs. International Journal of Man-Machine Studies, 21, 31-48.
  34. Goldstine, H. H. & Von Neumann, J. (1947). Planning and coding of problems for an electronic computing instrument. Report on the Mathematical and Logical aspects of an Electronic Computing Instrument Part II, Vol. 1-3. IAS ECP List of reports, 1946-57 nos. 4,8,11. Institute for Advanced Study, Princeton, New Jersey Green, T. R. G. (1977). Conditional program statements and their comprehensibility to professional programmers. Journal of Occupational Psychology, 50(2), pp. 93-109.
  35. Green, T. R., Petre, M., & Bellamy, R. K. E. (1991). Comprehensibility of visual and textual programs: A test of superlativism against the'match-mismatch'conjecture. Empirical Studies of Programmers: Fourth Workshop, pp, 121-146. Intellect Books.
  36. Green, T. R. G., & Petre, M. (1996). Usability Analysis of Visual Programming Environments: A 'Cognitive Dimensions' Framework. Journal of Visual Languages and Computing, 7(2), pp. 131-174.
  37. Guindon, R. (1990). Knowledge exploited by experts during software system design. International Journal of Man-Machine Studies, 33(3), pp. 279-304.
  38. Hoc, J.M. (1979). Le probleme de la planification dans la construction d'un programme informatique. Le Travail Humain, 42(2), pp. 245-260.
  39. Hoc, J. M. (1981). Planning and direction of problem solving in structured programming: An empirical comparison between two methods. International Journal of Man-Machine Studies, 15(4), pp. 363-383.
  40. Kankuzi, B. and Sajaniemi, J. (2016). A mental model perspective for tool development and paradigm shift in spreadsheets. International Journal of Human-Computer Studies 86, 149-163.
  41. Ko, A.J., Abraham, R., Beckwith, L., Blackwell, A.F., Burnett, M., Erwig, M., Lawrence, J., Lieberman, H., Myers, B., Rosson, M.-B., Rothermel, G., Scaffidi, C., Shaw, M., and Wiedenbeck, S. (2011). The state of the art in end-user software engineering. ACM Computing Surveys, 43(3), Article 21.
  42. Kostakos, V. (2015). The big hole in HCI research. Interactions, 22(2), pp. 48-51.
  43. Letovsky, Stanley, Pinto, Jeannine, Lampert, Robin, Soloway, Elliot (1987). A cognitive analysis of a code inspection. In: Olson, Gary M., Sheppard, Sylvia B., Soloway, Elliot (eds.) Empirical Studies of Programmers: Second Workshop, pp. 231-247. Ablex Publishing Corp.
  44. Leventhal, L.M. (1988). Experience of programming beauty: some patterns of programming aesthetics. International Journal of Man-Machine Studies, 28(5), pp. 525-550.
  45. Lewis, C., & Olson, G. (1987). Can principles of cognition lower the barriers to programming?. Empirical Studies of Programmers: Second Workshop, pp. 248-263. Ablex Publishing Corp.
  46. Lewis, C. (2017) Methods in user oriented design of programming languages. In Proc. PPIG 2017 Psychology of Programming Annual Conference, Delft, Netherlands, 1-3 July 2017.
  47. Lui, K.M. and Chan, K.C.C. (2006). Pair programming productivity: Novice-novice vs. expert-expert, International Journal of Human-Computer Studies 64(9), 915-925
  48. Magnusson, T. (2011). Algorithms as scores: Coding live music. Leonardo Music Journal, 21, 19-23.
  49. Maiden, N.A.M., and Hare, M. (1998). Problem domain categories in requirements engineering. International Journal of Human Computer Studies, 49(3), pp. 281-304.
  50. von Mayrhauser, A., & Vans, A. M. (1997). Program understanding behavior during debugging of large scale software. Empirical Studies of Programmers: Seventh Workshop, pp. 157-179. ACM.
  51. Miller, L.A. (1974). Programming by non-programmers. International Journal of Man-Machine Studies, 6(2), pp. 237-260.
  52. Moher, T. G., Mak, D., Blumenthal, B., & Leventhal, L. (1993). Comparing the comprehensibility of textual and graphical programs. Empirical Studies of Programmers: Fifth Workshop, pp. 137-161. Ablex, Norwood, NJ.
  53. Pandey, R. K. and Burnett, M.M. (1993). Is it easier to write matrix manipulation programs visually or textually? An empirical study. In Proceedings IEEE Symposium on Visual Languages, pp. 344-351.
  54. Pennington, N. (1987). Comprehension strategies in programming. Empirical Studies of Programmers: Second Workshop, pp. 100-113. Ablex Publishing Corp.
  55. Petre, M., and Blackwell, A.F. (1999). Mental imagery in program design and visual programming. International Journal of Human Computer Studies, 51(1), pp. 7-30.
  56. Rist, R. S. (1986). Plans in programming: definition, demonstration, and development. Empirical Studies of Programmers (pp. 28-47). Ablex, Norwood, NJ.
  57. Sharp, H. and Robinson, H. (2008). Collaboration and co-ordination in mature eXtreme programming teams. International Journal of Human-Computer Studies 66(7), 506-518,
  58. Sheil, B. A. (1981). The psychological study of programming. ACM Computing Surveys (CSUR), 13(1), 101-120.
  59. Shneiderman, B. (1983). Direct manipulation: A step beyond programming languages. Computer, 8, pp. 57-
  60. Sime, M. E., Arblaster, A. T., & Green, T. R. G. (1977). Reducing programming errors in nested conditionals by prescribing a writing procedure. International Journal of Man-Machine Studies, 9(1), pp. 119-126.
  61. A C C E P T E D M A N U S C R I P T Sime, M. E., Green, T. R. G., & Guest, D. J. (1973). Psychological evaluation of two conditional constructions used in computer languages. International Journal of Man-Machine Studies, 5(1), pp. 105-113.
  62. Simon, H. A. (1969). The Sciences of the Artificial. Cambridge, MA: MIT Press.
  63. Stefik, A. and Hanenberg, S.. (2017), "Methodological Irregularities in Programming-Language Research," in Computer, vol. 50, no. 8, pp. 60-63.
  64. Soloway, E., & Ehrlich, K. (1984). Empirical studies of programming knowledge. IEEE Transactions on Software Engineering, (5), pp. 595-609.
  65. Sonnentag, S. (1998). Expertise in professional software design: A process study. Journal of Applied Psychology, 83 (5), pp. 703-715.
  66. Sonnentag, S., Niesson, C., & Volmer, J. (2006). Expertise in software design. In: Cambridge Handbook of Expertise and Expert Performance. Cambridge: Cambridge University Press, pp. 373-387.
  67. Spohrer, J. G., & Soloway, E. (1986). Analyzing the high frequency bugs in novice programs. Empirical Studies of Programmers: First Workshop, pp. 230-251. Ablex Publishing Corp.
  68. Stylos, J., Clarke, S., and Myers, B. (2001) Evaluating a new programming language. In Proceedings of PPIG 2001, paper 22
  69. Sutherland, I.E. (1963/2003). Sketchpad, A Man-Machine Graphical Communication System. PhD Thesis at Massachusetts Institute of Technology, online version and editors' introduction by A.F. Blackwell & K. Rodden. Technical Report 574. Cambridge University Computer Laboratory Weinberg, G. M. (1971). The Psychology of Computer Programming. New York: Van Nostrand Reinhold.
  70. Weinberg, G. M., & Schulman, E. L. (1974). Goals and performance in computer programming. Human Factors, 16(1), pp. 70-77.
  71. Wiedenbeck, S. (1986). Beacons in computer program comprehension. International Journal of Man-Machine Studies, 25(6), pp. 697-709.

Related papers

Psychology of Programming Interest Group (PPIG) Work-in-Progress Workshop 2013 Proceedings
Louis Major

Proceedings from the Psychology of Programming Interest Group (PPIG) Work-in-Progress Workshop 2013 held at Keele University's School of Computing and Mathematics 8 – 9 July 2013.

View PDFchevron_right
Psychology of Programming Interest Group Annual Conference 2014
Benedict du Boulay
View PDFchevron_right
Behavioural Issues in Software Development: The Evolution of a New Course Dealing with the Psychology of Computer Programming
John Lenarcic

Issues in Informing Science and Information …, 2011

A historical account is presented of the evolution of a new postgraduate level university course dealing with the psychology of computer programming. An outline of the course is presented and its objectives are discussed, as well as possible reasons for its premature demise and initiatives that could be undertaken to resurrect the format in a new guise.

View PDFchevron_right
Psychological perspectives for software science
Ira Forman

Information Processing & Management, 1984

In developing his theory of software science, Maurice Halstead borrowed heavily from psychology for theoretical explanations of the equations he was developing. Other software researchers have used psychological theory to defend their techniques or conclusions. Unfortunately, the psychological principles they have employed have not always been the most recent developments in the field. In fact, most of the psychological explanations found in software science are based on research that is one to three decades old. Some of these principles have been taken out of context and used inappropriately.

View PDFchevron_right
The influence of the psychology of programming on a language design: Project status report
Brad A Myers

2000

This Conference Proceeding is brought to you for free and open access by the School of Computer Science at Research Showcase. It has been accepted for inclusion in Institute for Software Research by an authorized administrator of Research Showcase. For more information, please contact researchshowcase@andrew.cmu.edu. ... Recommended Citation Pane, John and Myers, Brad, "The Influence of the Psychology of Programming on a Language Design: Project Status Report" (2000). Institute for Software Research. Paper 766. http://repository.cmu.edu/isr/766

View PDFchevron_right

Related topics

  • Sociology
  • Computer Science
  • Psychology and Cognitive Sciences

    • Cited by

    Studying human-to-computer bias transference
    Tore Pedersen

    AI & SOCIETY

    It is generally agreed that one origin of machine bias is resulting from characteristics within the dataset on which the algorithms are trained, i.e., the data does not warrant a generalized inference. We, however, hypothesize that a different ‘mechanism’ may also be responsible for machine bias, namely that biases may originate from (i) the programmers’ cultural background, including education or line of work, or (ii) the contextual programming environment, including software requirements or developer tools. Combining an experimental and comparative design, we study the effects of cultural and contextual metaphors, and test whether each of these are ‘transferred’ from the programmer to the program, thus constituting a machine bias. Our results show that (i) cultural metaphors influence the programmer’s choices and (ii) contextual metaphors induced through priming can be used to moderate or exacerbate the effects of the cultural metaphors. Our studies are purposely performed with us...

    View PDFchevron_right
    580 California St., Suite 400
    San Francisco, CA, 94104
    © 2025 Academia. All rights reserved