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

Computer scienceSoftware constructionSoftware systemSoftware engineeringSoftware developmentSoftware sizingSoftwareVerification and validationSoftware metricSoftware frameworkSoftware design descriptionProgramming language

Affiliated Institutions

Related Publications

Publication Info

Year
1976
Type
article
Volume
SE-2
Issue
1
Pages
9-32
Citations
109
Access
Closed

External Links

Social Impact

Social media, news, blog, policy document mentions

Citation Metrics

109
OpenAlex

Cite This

Margaret Hamilton, S. Zeldin (1976). Higher Order Software—A Methodology for Defining Software. IEEE Transactions on Software Engineering , SE-2 (1) , 9-32. https://doi.org/10.1109/tse.1976.233798

Identifiers

DOI
10.1109/tse.1976.233798