Higher Order Software—A Methodology for Defining Software
- 1 March 1976
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. SE-2 (1), 9-32
- https://doi.org/10.1109/tse.1976.233798
Abstract
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.Keywords
This publication has 7 references indexed in Scilit:
- Signal and Control within the Railway SystemPublished by Institution of Engineering and Technology (IET) ,2006
- DAIS avionic software development techniquesPublished by American Institute of Aeronautics and Astronautics (AIAA) ,1975
- Higher order software techniques applied to a space shuttle prototype programPublished by Springer Nature ,1974
- A tool for enforcing system structurePublished by Association for Computing Machinery (ACM) ,1973
- On the criteria to be used in decomposing systems into modulesCommunications of the ACM, 1972
- A technique for software module specification with examplesCommunications of the ACM, 1972
- BLISSCommunications of the ACM, 1971