This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Higher Order Software
March 1976 (vol. 2 no. 1)
pp. 9-32
M. Hamilton, Computer Science Division, The Charles Stark Draper Laboratory, Inc.
The key to software reliability is to design, develop, and manage software with a formalized methodology which can be used by computer scientists and applications engineers to describe and communicate interfaces between systems. These interfaces include: software to software; software to other systems; software to management; as well as discipline to discipline within the complete software development process. The formal methodology of Higher Order Software (HOS), specifically aimed toward large-scale multiprogrammed/multiprocessor systems, is dedicated to systems reliability. With six axioms as the basis, a given system and all of its interfaces is defined as if it were one complete and consistent computable system. Some of the derived theorems provide for: reconfiguration of real-time multiprogrammed processes, communication between functions, and prevention of data and timing conflicts.
Index Terms:
structuring executive, Axioms, formal methodology, functional decomposition, interface correctness, specification, static verification
Citation:
M. Hamilton, S. Zeldin, "Higher Order Software," IEEE Transactions on Software Engineering, vol. 2, no. 1, pp. 9-32, March 1976, doi:10.1109/TSE.1976.233798
Usage of this product signifies your acceptance of the Terms of Use.