Natural naming in software development: Feedback from practitioners

  • Kari Laitinen
Software Development Issues
Part of the Lecture Notes in Computer Science book series (LNCS, volume 932)


During a five-year period several groups of software developers have been educated on using natural naming in software development. Generally, natural naming means avoiding abbreviations. In programming it means that program elements such as variables, tables, constants, and functions should be named using whole natural words and grammatical rules of a natural language. To assess the usefulness of natural naming and the importance of naming in general, we have requested the opinions of 52 software developers who have participated in naming courses or to whom a naming handbook has been introduced. The subjects had to judge the relevancy of 25 statements related to naming. The results of the inquiry indicate that most software developers, and especially the experienced ones, consider that natural naming facilitates their work.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    P. Coad, E. Yourdon: Object-oriented analysis. Englewood Cliffs, New Jersey: Prentice-Hall 1990Google Scholar
  2. 2.
    B. Curtis, S. B. Sheppard, P. Milliman, M. A. Borst, T. Love: Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics. IEEE Transactions on Software Engineering 5, 96–104 (1979)Google Scholar
  3. 3.
    B. Curtis, H. Krasner, N. Iscoe: A field study of software design process for large systems. Communications of the ACM 31, 1268–1287 (1988)Google Scholar
  4. 4.
    V. Fromkin, R. Rodman: An introduction to language, fourth edition. New York: Holt, Rinehart, and Winston 1988Google Scholar
  5. 5.
    A. M. Ibrahim: Acronyms observed. IEEE Transactions on Professional Communication 32, 27–28 (1989)Google Scholar
  6. 6.
    Intel: MCS-80/85 family user's manual. Santa Clara, California: Intel 1979Google Scholar
  7. 7.
    ISO 9000-3: Quality management and quality assurance standards — part 3: Guidelines for the application of ISO 9001 to the development, supply, and maintenance of software. Geneva, Switzerland: International Organization for Standardization 1991Google Scholar
  8. 8.
    D. A. Keller: A guide to natural naming. ACM SIGPLAN Notices 25, 5, 95–102 (1990)Google Scholar
  9. 9.
    K. Laitinen, V. Seppänen: Principles for naming program elements, a practical approach to raise informativity of programming. In: Proceedings of InfoJapan'90 international conference, part I. Tokyo: Information Processing Society of Japan 1990, pp. 79–86Google Scholar
  10. 10.
    K. Laitinen, T. Mukari: DNN-Disciplined natural naming, a method for systematic name creation in software development. In: Proceedings of 25th Hawaii international conference on system sciences, Vol. II. Los Alamitos, California: IEEE Computer Society Press 1992, pp. 91–100Google Scholar
  11. 11.
    K. Laitinen: Document classification for software quality systems. ACM SIGSOFT Software Engineering Notes 17, 4, 32–39 (1992)Google Scholar
  12. 12.
    D. Logsdon, T. Logsdon: The curse of the acronym. In: Proceedings of the international professional communications conference. New York: IEEE 1986, pp. 145–152Google Scholar
  13. 13.
    P. R. Newsted: Flowchart-free approach to documentation. Journal of Systems Management 30, 4, 18–21 (1979)Google Scholar
  14. 14.
    M. Page-Jones: The practical guide to structured systems design, second edition. Englewood Cliffs, New Jersey: Prentice Hall 1988Google Scholar
  15. 15.
    S. B. Sheppard, B. Curtis, P. Milliman, T. Love: Modern coding practices and programmer performance. Computer 12, 12, 41–49 (1979)Google Scholar
  16. 16.
    B. Shneiderman: Software psychology, human factors in computer and information systems. Cambridge, Massachusetts: Winthrop Publishers 1980Google Scholar
  17. 17.
    B. E. Teasley: The effects of naming style and expertise on program comprehension. International Journal of Human-Computer Studies 40, 757–770 (1994)Google Scholar
  18. 18.
    L. M. Weissman: A methodology for studying the psychological complexity of computer programs. Ph.D. Thesis. Toronto, Canada: Department of Computer Science, University of Toronto 1974Google Scholar
  19. 19.
    L. Wittgenstein: Philosophical investigations. Oxford, England: Basil Blackwell 1953Google Scholar
  20. 20.
    E. Yourdon: Modern structured analysis. Englewood Cliffs, New Jersey: Prentice-Hall 1989Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1995

Authors and Affiliations

  • Kari Laitinen
    • 1
  1. 1.VTT Electronics/Embedded SoftwareOuluFinland

Personalised recommendations