Access the full text.
Sign up today, get DeepDyve free for 14 days.
(1975)
The Mythical Moon.Month: Essooys on ScJtware Engineering
Structured programming series , vol . 8 : Program design study , Final Rept
H. Ramsey, M. Atwood, James Doren (1978)
A Comparative Study of Flowcharts and Program Design Languages for the Detailed Procedural Specification of Computer Programs
S. Sheppard, J. Bailey, Elizabeth Kruesi (1981)
The Effects of the Symbology and Spatial Arrangement of Software Specifications in a Debugging Task.
J. Brooks (1978)
The Mythical Man-Month: Essays on Softw
(1983)
Conference Record of the 10th Annual ACM Symposium on Principles of Programming Languages
Consists of 294 pages
(1983)
SIGCOMM '83 Symposium on Communications Architectures and Protocols Austin
(1974)
Structured progroomming series, val. VII: Documentation stoondards . Tech. Rept. RADC-TR-74-300
H. Mills (1980)
Structured Software Design
G. Weinberg (1971)
Psychology of computer programming
(1978)
The understanding process: Problem isomorphs . Cognitive Psych
B. Shneiderman (1982)
Control flow and data structure documentation: two experimentsCommun. ACM, 25
(1983)
Consists of 316 pages, 43 papers
B. Shneiderman, R. Mayer, Don McKay, P. Heller (1977)
Experimental investigations of the utility of detailed flowcharts in programmingCommun. ACM, 20
Consists of 320 pages; 28 papers
Herbert Simon, Michael Barenfeld (1969)
Information-processing analysis of perceptual processes in problem solving.Psychological review, 76 5
H. Simon, J. Hayes (1976)
The understanding process: Problem isomorphsCognitive Psychology, 8
J. Brooke, K. Duncan (1980)
An experimental study of flowcharts as an aid to identification of procedural faultsErgonomics, 23
S. Sheppard, Elizabeth Kruesi, B. Curtis (1981)
The effects of symbology and spatial arrangement on the comprehension of software specifications
R. Kammann (1975)
The Comprehensibility of Printed Instructions and the Flowchart AlternativeHuman Factors: The Journal of Human Factors and Ergonomics Society, 17
R. Jeffries, P. Polson, Lydia Razran, M. Atwood (1977)
A process model for Missionaries-Cannibals and other river-crossing problemsCognitive Psychology, 9
(1975)
L Structured software design
P. Wright, F. Reid (1973)
Written information: Some alternatives to prose for expressing the outcomes of complex contingencies.Journal of Applied Psychology, 57
(1983)
Consists of 318 pages
(1983)
The Papers of the 14th SIGCSE Technical Symposium on Computer Science Education Orlando
(1983)
Consists of 324 pages; 59 papers, 7 panels ACM/SIGCSE members $14; others $19
(1974)
The Progroom Development Process: The Individual Programme?
(1975)
Structured programming series Program design study, Final Rept
J. Aron (1974)
Program Development Process: The Individual Programmer
Structured progroomming series , val . VII : Documentation stoond - ards
T. Frederick, L. Cottrell (1983)
Proceedings of the 1983 computer science conference
M. Atwood, H. Ramsey (1978)
Cognitive structures in the comprehension and memory of computer programs: an investigation of compu
(1983)
Consists of 138 pages; 6 papers; 108 abstracts
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 PDLs rather than flowcharts as a standard documentation method for detailed computer program designs.
Communications of the ACM – Association for Computing Machinery
Published: Jun 1, 1983
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.