By Topic

Fortran Can it be Structured-Should it be?

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
E. Horowitz ; University Southern California

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.

Published in:

Computer  (Volume:8 ,  Issue: 6 )