
This paper presents a proposed standard for documenting engineering computer programs. The need for good program documentation and for a standard procedure to prepare such documentation is discussed. The proposed documentation procedure is designed to help the engineer who is to use the computer program, the programmer who may have to modify it, and the computer operator who must run it. The recommendations are illustrated by a completely documented sample computer program.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
