This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
April 1977 (vol. 10 no. 4)
pp. 47-53
N.F. Schneidewind, Navai Postgraduate School
Two particularly nagging ailments faced by the computer industry today are the high cost and late delivery of software.1,2The symptoms usually surface during software debugging, testing, and integration; but the ailments themselves can most often be traced back to the program design phase and the structural characteristics of the program. The significance of program structural characteristics has been recognized for some time, as witnessed by the emergence of structured programming,3,4,a methodology that sets out to (1) reduce programming errors; (2) design an understandable, readable, and therefore maintainable program; (3) increase our ability to detect errors; and (4) prove, if only informally, that the program is correct. But there is another tool available that has usually been overlooked in the software development process: simulation.
Citation:
N.F. Schneidewind, "The Use of Simulation in the Evaluaton of Software," Computer, vol. 10, no. 4, pp. 47-53, April 1977, doi:10.1109/C-M.1977.217712
Usage of this product signifies your acceptance of the Terms of Use.