DocumentCode
1009717
Title
Fortran Can it be Structured-Should it be?
Author
Horowitz, Ellis
Author_Institution
University Southern California
Volume
8
Issue
6
fYear
1975
fDate
6/1/1975 12:00:00 AM
Firstpage
30
Lastpage
37
Abstract
There is no doubt about it, structured programming (SP) is making waves. Wherever one goes within the computing community people are asking what it is and how they can use it. And the answers they are receiving are sometimes very different. This inability to pin down a precise definition has caused the original concept of SP to become widely distorted. For example, a recent advertisement described SP as "a means of improving the quality of the code, improving project control, reducing the debugging phase of the project, forcing good software documentation as an integral part of the system design, and making programs less sensitive to turnover of project personnel."<R>1</R> Thus portrayed as a panacea for the entire programming process, it is not surprising that in a recent week-long seminar given by Dr. Dijkstra, he refused to use the term at all.
Keywords
Computer languages; Control systems; Debugging; Documentation; Programming; Software testing; Tree data structures;
fLanguage
English
Journal_Title
Computer
Publisher
ieee
ISSN
0018-9162
Type
jour
DOI
10.1109/C-M.1975.218980
Filename
1649456
Link To Document