Program Design Languages-An Introduction.

Author(s):  
Lorna L. Cheng
1983 ◽  
Vol 26 (6) ◽  
pp. 445-449 ◽  
Author(s):  
H. Rudy Ramsey ◽  
Michael E. Atwood ◽  
James R. Van Doren

1987 ◽  
Vol 27 (4) ◽  
pp. 337-347 ◽  
Author(s):  
Deborah A. Boehm-Davis ◽  
Sylvia B. Sheppard ◽  
John W. Bailey

1978 ◽  
Vol 22 (1) ◽  
pp. 709-713 ◽  
Author(s):  
H. Rudy Ramsey ◽  
Michael E. Atwood ◽  
James R. Van Doren

An experiment was performed to assess the relative merits of Program Design Languages (PDLs) and flowcharts as techniques for the development and documentation of detailed designs for computer programs. The use of a PDL by a software designer, for the development and description of a detailed program design, produced better results than did the use of flowcharts. Specifically, the designs appeared to be of significantly better quality, involving more algorithmic or procedural detail, than those produced using flowcharts. In addition, flowchart designs exhibited considerably more abbreviation and other space-saving practices than did PDL designs, with a possible adverse effect on their readability. When equivalent, highly readable designs were presented to subjects in both PDL and flowchart form, no pattern of short-term or long-term differences in comprehension of the design was observed. No significant differences were detected in the quality or other properties of programs written as implementations of the designs. Subjective ratings indicated a mild preference for PDLs. Overall, the results suggest that software design performance and designer-programmer communication might be significantly improved by the adoption of informal Program Design Languages, rather than flowcharts, as a standard documentation method for detailed computer program designs.


Sign in / Sign up

Export Citation Format

Share Document