Proceedings of the Twenty-Fifth Hawaii International Conference on System Sciences 1992
DOI: 10.1109/hicss.1992.183281
|View full text |Cite
|
Sign up to set email alerts
|

DNN-disciplined natural naming: a method for systematic name creation in software development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

1995
1995
1997
1997

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 10 publications
0
5
0
Order By: Relevance
“…Guidelines for using natural naming have with abbreviated names (b). been published by Keller (1990), Laitinen and Sepp~inen (1990), and Laitinen and Mukari (1992). As shown in Figure 1, natural naming means that abbreviations are avoided.…”
Section: Figure I the Same Program With Natural Names (A) Andmentioning
confidence: 95%
“…Guidelines for using natural naming have with abbreviated names (b). been published by Keller (1990), Laitinen and Sepp~inen (1990), and Laitinen and Mukari (1992). As shown in Figure 1, natural naming means that abbreviations are avoided.…”
Section: Figure I the Same Program With Natural Names (A) Andmentioning
confidence: 95%
“…Textbooks on programming and software engineering usually state that descriptive names should be used. However, no instructions are given on how the names can be made descriptive and informative [10].…”
Section: General Observationsmentioning
confidence: 99%
“…Laitinen and Mukari [10] show that judging the relevancy of names is a means for analyzing the problems of an application domain. It is thus relevant to presume that software developers, at least unconsciously, use naming as a thinking tool.…”
Section: Observations Related To Understanding Communication and Thmentioning
confidence: 99%
See 1 more Smart Citation
“…However there is substantial evidence that programmers find the concurrent specification of source code and the derivation of identifier names that are generally understandable by other programmers to be a difficult task. These difficulties result from cognitive limitations [3,4,5,19,22]; education issues [6,9,11,14,16,17,18,23]; cultural practices on the part of the programmer [2,6,12,19,25]; and cultural practices on the part of the programmer's management [7,13,19,21]. These same researchers suggest that programmer characteristics such as the number of years programming experience will influence the degree of difficulty experienced by the programmer in devising identifier names.…”
Section: Literature Reviewmentioning
confidence: 91%